dnomode wrote:maximum that we can extend the ON time length?
Pretty easy to add, I'll put that in the next release as well.
dnomode wrote:maximum that we can extend the ON time length?
dnomode wrote:Great plugin. Thanks.
I have several timers setup that require 5 to 9 steps to accomplish what I want. Not even close to how nice this plugin is. Thanks
I was wondering if it's possible to add a warning that your lights are about to turn off and a maximum that we can extend the ON time length? For example, 5 minutes before the Kitchen Light turn off Indigo dims the lights by 45% and the back up to the original level. This allows my wife to hit the on button again to add 30 more minutes. Every push will give us an addition 30 minutes of ON time up to a max of 2 hours.
Would something like this work with this plugin?
Thanks for the great plugin.
Edmond
dz1rfj wrote:for your kitchen, have you considered a motion sensor setup
dz1rfj wrote:start a countdown of 10 minutes. If no motion is sensed before countdown, lights turn off, if motion is sensed before the timer hits zero, it resets and gives another 10 minutes...
dz1rfj wrote:
Edmond- for your kitchen, have you considered a motion sensor setup? I created (thanks to the forums users) a motion flow that says when the lights are on ( a virtual switch is set to on if any kitchen light is on) if motion is sensed after the vswitch is on, start a countdown of 10 minutes. If no motion is sensed before countdown, lights turn off, if motion is sensed before the timer hits zero, it resets and gives another 10 minutes...
You might try doing another fresh install with the following steps if you didn't take them all before.
disable the plugin
stop the Indigo server
exit Indigo
delete the plugin file
delete the plugin preference file
restart the server
re-install the plugin
I've found in some cases that the plugin preferences file can get into a bad state (this has happened to some of my plugins) and I've found that deleting the preferences file can set things right. An added bonus of recreating the preferences file is that it will ensure the preferences file itself is clean and up to date and reflects the latest configuration options only.
Oct 7, 2018, 1:06:01 PM
EPS - Powermiser Error Exception in ui._cacheResults line 206: object of type 'NoneType' has no len()
CODE: if len(results) == 0 or index == "" or targetId == 0: return
EPS - Powermiser Error Error in plugin execution GetUiDynamicList:
Traceback (most recent call last):
TypeError: Expecting an object of type list; got an object of type NoneType instead
Users browsing this forum: No registered users and 4 guests