this post was submitted on 20 Feb 2024
6 points (100.0% liked)
homeassistant
12125 readers
16 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. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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 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?
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.