Automation gets disabled automatically

[Frimann_Bjornsson (Frímann Björnsson)]

I’m using a Philips remote to trigger an automation to set certain scenes. The problem I’m running into is that once a month or so, the automation get’s disabled automatically. So I need to log into HASS and re-enable it.

Anyone know what might be the cause?

Here are some screenshots of the automation that gets disabled:

[Stiltjack]

If the blueprint used device_ids and any of them became unavailable, that would disable it.

Why and how to avoid device_ids in automations and scripts

Don’t forget that the first post in a community guide is a wiki - feel free to add to it or correct it. This guide was written with reference to: Home Assistant 2023.8.3 Supervisor 2023.08.1 Operating System 10.5 Frontend 20230802.1 - latest 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. [image] It works… but it is certainly not a “great way to start” because it …