I have a lighting event designed to deal with a Hue behaviour. The issue (as most Hue users will know) is that if you turn off a Hue light remotely, and then later want to turn it on via the switch, you need to first turn the switch off, and then turn it back on (First World Problems, I know).
To get around this I created an event that says if the light switch is pressed On, and the Hue lights are off, then turn the Hue bulbs on. It worked fine for 24h, and then I started noticing that once in awhile the Hue bulbs just came on by themselves. Checking the log, there was nothing there except for the Event Trigger getting triggered. ie. no one pushing a button, making a change, or any other device getting switched. Basically the log just shows a passage of time with nothing happening, and then bam, the event triggers. Just wondering if there might be a bug, or if I'm taking the wrong approach or if there's a better setting to use?
Here's the Event:
Here's the Event with more details:
Any ideas? My current understanding is that "This device had its value set to..." Is a akin to "the button was just pressed" But perhaps I'm misunderstanding it.....
To get around this I created an event that says if the light switch is pressed On, and the Hue lights are off, then turn the Hue bulbs on. It worked fine for 24h, and then I started noticing that once in awhile the Hue bulbs just came on by themselves. Checking the log, there was nothing there except for the Event Trigger getting triggered. ie. no one pushing a button, making a change, or any other device getting switched. Basically the log just shows a passage of time with nothing happening, and then bam, the event triggers. Just wondering if there might be a bug, or if I'm taking the wrong approach or if there's a better setting to use?
Here's the Event:
Here's the Event with more details:
Any ideas? My current understanding is that "This device had its value set to..." Is a akin to "the button was just pressed" But perhaps I'm misunderstanding it.....
Comment