Hi
I need some help before I throw my hue bridge out the window.
I have flows to control my lights. It’s all looking good while testing, but for some bizarre reason Hue is ontroling my lights outside of flow LUX conditions. It now started using the Fibaro motion sensor to trigger Innr bulbs! Whilst Innr bulb is connected to Hue, Fibaro is not. Yet, it is triggering on the light when motion is detected! Am I going mad? Below is my flow and I can see that during testing it does not trigger. However as soon as I walk into the toilet in this case, Hue is triggering the lights to switch on.
Too confusing:
When testing a flow, you are acting as the trigger (the Toilet motion alarm is the real trigger);
The flow action cards are not fired, or started, because of the unmet condition.
only can only find out if the Toilet sensor actually triggers that particular flow or not, by adding notification cards!
Example:
Sounds like a forgotten automation somewhere? Either on Hue or on Homey?
In the web app, right-click on a device tile to see in which flows it is used.
However, flows triggered by Zone Activity won’t be listed.
You can install the ‘Audit’ app to log each ‘fart’ from Homey. Maybe you’ll find the culprit right away.
Hi @Peter_Kawa
Thanks for your reply. I have cleared the notificatons because it was working fine for most of the time and started playing up few days ago.
I have now added the notifications in as per below.
I am getting the notification for the motion detection, but not for the lights being switched on. Same thing is happening in the office now, and that flow is filled with notifications.
No notification about lights coming on, yet they are. And there are no other notifications. The toilet set up if only 3 weeks old, and the sensor is z-wave so Hue should not be touching it. Yet it is.
Just to add, there are no automations in Hue, or Alexa for any of these devices.
I am getting very close to doing a factory reset on Hue Bridge.
YW.
This means the lux value wasn’t less than 25, or your tag is from the wrong lux sensor.
I’d check that, and add a notification card to the orange output, with also the tag of the lux sensor added to it.
Then you’ll know why the lights aren’t turned on.
Hi @Peter_Kawa
Thanks for your suggestion. I have had lux notifications and other troubleshooting notifications set up in the office (which also behaves in the same way). Please see below. The Lux is way above 25 and the lights do switch on anyway. There is also a notification set up to tell me that the flow switched on the lights, and that does not show in the timeline.
But yet the lights get switched on by Hue, not by the flow.
Here is the complete logic for office lights.
“Turn all lights on” cards are a bit tricky, the log can show either “flow X turned on the light” or “App X turned on the light”.
No clue why Athom hasn’t thought of mentioning both at least.
Instead of that, just turn on a specific Hue light with the flow, to get clearer logs.
Other stupid log ‘fail’:
When a flow dims an App X light to zero, the log of that light just says: turned off by App X.
The device logging is really is just half implemented if you ask me.
