System Logs for Flow Failures?

I have several advanced flows that all start with “When sunset is in 45 minutes.” For the last few days, only some of these flows are working. There doesn’t seem to be any pattern either: Today, one of the flows that turns on lights didn’t work, but it worked just fine yesterday and the day before. Also today, another flow turned on the lights, but it did not do so yesterday.

Is there any way to diagnose why any particular flow isn’t working when it shares the same ‘When’ card with another flow that is working?

Thanks!

Random things not working with flows are typically caused by sending commands (like “turn on light”) in parallel (“at the same time”), which is something that Homey cannot handle. It doesn’t generate any errors, it just drops random commands.

The typical solution is to introduce delays in between the commands.

Add a notification card directly after the WHEN card to see if the flow actually starts. Then add notification cards directly before the command that switches on a light to see the flow reaches that point.

I appreciate the feedback, but if sending multiple commands at the same time is something Homey cannot handle - that’s unacceptable for both the cost of the product and the modern computing era.

If that is true, the underlying system that handles scheduled commands should queue up any command with the same start time and fire them off in sequence. A few microseconds of delay wouldn’t be perceivable.

And still, it’s an issue that Homey has had for many years :man_shrugging:t3:

1 Like