Should automations run after devices disconnect

[JKauto]

I have several Shelly devices which I use in automations and after those devices were disconnected by Wi-Fi issues and then reconnected…I noticed my automations did not resume or trigger again?

Is there something that needs to be added to automations for redundancy to make sure they run even after devices might be temporarily unavailable?

[tom_l]

Don’t use device automations and the automations won’t be disabled when your devices go unavailable.

Why and how to avoid device_ids in automations and scripts

Background When you start writing automations, a device trigger seems the obvious choice. Everybody knows what a device is and it comes at the top of the UI dropdown list. [Screenshot from 2025-11-20 18-37-55] It works… but it is not a the best way to start because it is storing up problems for the future. Far better to use an entity, with state or numeric_state. This topic is part of the community-driven cookbook where you can find other topics you might be interested in or might like to …

[JKauto]

Yes I’m new at this, thanks for the direction