I have an automation that when triggered turns on a scene that sets my lights a specific way. Then the automation waits for a second trigger.
I noticed that the automation doesn’t continue after the second trigger, so I looked at the trace, and it looks like the scene setting step of the automation times out: “error: Timed out when calling async_turn_on for bulb xyz: <class ‘TimeoutError’>
It looks like this bulb xyz was dropped from my zigbee network, which isn’t always the most stable. So it’s not exactly uncommon.
So how do I safeguard my automations from being broken by a single piece of a scene being offline?
I remember searching for a similar workaround in the past. I’m not sure parallel will work because the whole automation is blocked on error if I recall correctly. A workaround I found suggested on the ha website (but never tried) was to put the command that may error in a script and run the script as “fire and forget” from the automation. If the automation doesn’t wait for the script to finish it won’t detect the error either. But, as other pointed out, try to make the zigbee network more stable first.