Re: Timed Devices plugin
Posted: Sat Aug 26, 2017 7:34 pm
@ stuartcolman:
This request is not as straightforward as it seems. Starting the timer when the last tracked device goes off is incompatible with the 'Any Change' logic (which by definition ignores the difference between on and off). Additionally, the plugin would have to either maintain a tally of how many devices are on (which runs the risk of getting out of sync if there are communication hiccups) or repeatedly querying Indigo about the state of devices (which adds considerable overhead). It could be done, but would break the lean structure of the code as it stands now, which I'm not eager to do.
But as I said before, you can use a Persistence Timer to accomplish this for a single device/variable.
This request is not as straightforward as it seems. Starting the timer when the last tracked device goes off is incompatible with the 'Any Change' logic (which by definition ignores the difference between on and off). Additionally, the plugin would have to either maintain a tally of how many devices are on (which runs the risk of getting out of sync if there are communication hiccups) or repeatedly querying Indigo about the state of devices (which adds considerable overhead). It could be done, but would break the lean structure of the code as it stands now, which I'm not eager to do.
But as I said before, you can use a Persistence Timer to accomplish this for a single device/variable.