this post was submitted on 11 Sep 2025
19 points (95.2% liked)

homeassistant

16262 readers
1 users here now

Home Assistant is open source home automation that puts local control and privacy first.
Powered by a worldwide community of tinkerers and DIY enthusiasts.

Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation

Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @GreatAlbatross@feddit.uk

founded 2 years ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] CondorWonder@lemmy.ca 2 points 1 week ago (1 children)

You can try adding

continue_on_error: true

to the scene action so it doesn’t kill the entire automation. Note that if later parts depend on this action then they’ll fail in weird ways. The best thing is to fix the Zigbee network so the device doesn’t drop off but I know that’s not easy.

[–] Lemmee@sh.itjust.works 3 points 1 week ago

I might give this a try while I work on the actual underlying cause. The rest of the automation isn’t impacted. It just turns the lights a color when it starts, then resets the color when the automation finishes.