Disabled automations continually become enabled
Disabled automations continually become enabled
I've had a problem for a year or more, so that's through numerous Home Assistant updates: I have about 15 automations that I've disabled, but they always become enabled again within a few days. I haven't been able to determine a trigger for the re-enabling.
Has anyone else encountered this? Does anyone have a suggestion?
There should be entries in the history/logbook for the automation entity itself (
automation.whatever). From there you should at least be able to determine, what changed the enabled state of your automation(s). If it is a service, you might have to search for specific calls of this service (e.g. in your other automations). It might also be an option to do a global text search for the entity IDs of your automations and/or any automation services. You could do this via the vscode addon if it is installed.I myself have never encountered this error and got a few disabled automations, which haven't changed their state over months and multiple updates/restarts.
Thanks for the assitance, @brainstorm@feddit.de.
One of my automations that was disabled but is now enabled has
turned off triggered by service Automation: Turn offabout a week ago in the Logbook. What does "turned off" mean for an automation?And in History it looks like this:
What part of this information is usable to search for what triggered the automation to be re-enabled?
Turned off or Turned on is the disable or enable action. If it’s changed by something in HA it should show what the trigger was too (like a user or other automation).
Here’s an example - it shows the automations that enabled our disabled this automation, and their trigger.
To prevent the automation from being changed you can rename it, that should break anything automatic that’s changing it. You can also try to chase down what’s changing it from logs (once renamed you should start seeing errors in your HA log file), or by searching for the entity_id in your yaml configuration files.
You could also search for the
automation.turn_offservice in your yaml files and see, if any match references your specific automations entity_id.