Can anyone tell me why I regularly have flows that are disable, for no reason?
JST
Sometimes Flows disable themselves when they run/trigger too many times.
And what is often? 5 times a day? 10 times?
It’s like a flow that switches on the light in the bathroom. But then, sometimes it doesn’t switch anymore.
If that’s really the case, then Homey becomes useless
Often is multiple times per second.
Are you sure the flow is disabled (so you have to use the menu option to re-enable them again)? Or is the flow enabled but not triggered/executed?
If a flow is triggered multiple times per second continuously a flow will be disabled to protect Homey. Without this protection Homey would become unavailable.
It is always an error in the flow, the flow gets in a loop.
To detect the error, you can write an entry on the timeline and after the moment a flow becomes disabled you can see a lot of notifications. In the log of the device you can find which flow(s) is triggering the light.
If you share the flow (and the log of the device) we can have a look at it
The bottom part of your flow will run continuously, as the ‘turn on all lights’ and ‘turn off all lights’ card will also trigger the turned on/off cards of each individual lights. Which then in turn will trigger the zone card again.
You’ll need to change the flow to include a check to first verify if a light is already turned on and switch on only the lights that are tuned off. Similarly for the turn off flow.
2 Likes
Sunbeech is right. If you add a timeline card (after turn on/off all lights) you will see a lot off entries per second.
You are lucky that the flow will be disabled, otherwise your Homey would be stuck…..
1 Like
Actually I don’t really need these entries, because its rare that only one lamp (spot) is turned on or off. I might as well delete that part.
Thanks guys.
JST
1 Like
