Pulse time max value

[xoseperez]

Originally reported by: treowayne (Bitbucket: treowayne, GitHub: Unknown)

---

I have a bunch of Epurna'd Sonoff switches. On some of them I use the pulse time feature as a timer to automatically power down the attached device. A couple of devices are set to "pulse" for 3600 seconds (an hour), and that seems to work fine. I set up another one to pulse for 14400 seconds (four hours) and it stayed on overnight.

I am guessing the pulse time probably has a max value determined by the max value of a data type. It would be great if this maximum was larger (best case) or at least if the web interface would inform (or enforce) a maximum value.

Great work though Xose!

[xoseperez]

The pulse feature uses the Ticker library that (aparently) stores time internally in a 32bit variable representing microseconds, that gives you a max time span of around 71 minutes, so that might be the reason for the behaviour you describe. Honestly the pulse functionality was originally meant for short pulses (opening a garage door, triggering a door bell,...).

[xoseperez]

Limit the max pulse value in web interface

[xoseperez]

Removing milestone: 1.8.2 (automated comment)

[xoseperez]

Fixed with 1.8.2

[xoseperez]

Original comment by Stavros Korokithakis (Bitbucket: Stavros, GitHub: Stavros):

---

Is there any way to change the max value to around 60 minutes, at least? The current max of 60s is very restrictive, as I have a Sonoff that controls the light in a room I'm always only in for ~5 minutes, so I'd like it to turn off after 10m.