homeassistant

11835 readers

10 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 1 year ago

MODERATORS

[email protected]

Disabled automations continually become enabled (lemmy.d.thewooskeys.com)

submitted 7 months ago by [email protected] to c/[email protected]

8 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 7 months ago (7 children)

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.

[–] [email protected] 1 points 7 months ago (6 children)

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?

[–] [email protected] 2 points 7 months ago

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.

load more comments (5 replies)