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?
Thanks for the assitance, @[email protected].
One of my automations that was disabled but is now enabled has
turned off triggered by service Automation: Turn off
about 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.
Thanks for the explanation and example, @[email protected].
I used Studio Code Server to search all files for “Automation: Turn Off” and “automation.turn_off” and “automation” - there were 100s (1000s?) of results. I scanned through them and didn’t see anything that looks like it was enabling these automations. And that’s the only record in my logbook around these automations being disabled.
So now I’ve renamed some of my automations and re-disabled them. In a few days they’ll either become enabled or I’ll search my logs for errors including their previous names.
You could also search for the
automation.turn_off
service in your yaml files and see, if any match references your specific automations entity_id.