Automations get disabled

papadi · March 3, 2019, 6:41pm

Any idea why sometimes my automations get all disabled? I’m not sure of it happens during a restart or when I reload them. But it happened already two times while I was working with them, making changes, reloading them etc.

surge919 · March 3, 2019, 6:51pm

I was having the same issue. I was troubleshooting an automation that was firing and then realized it was disable.

Found this in another thread… thanks @DavidFW1960

Do you maintain your own Lovelace yaml or let HA do it?

you can add something like this to the automation…
- id: '1507434167221'
  alias: Coffee Maker Off
  initial_state: 'true'
That will make sure it is always enabled. It does seem that when you make a new one that it is automatically disabled however it should remember the state across reboots. Sometimes if you restart home assistant too many times close together (easy to do when you are changing/trying stuff) HA thinks an automation might be causing an error and it will disable all automations. This initial state will make sure they come on/stay on.

papadi · March 3, 2019, 11:20pm

Hmm… it might have been the case, both times it happened to me. Thanks…

papadi · March 4, 2019, 8:16am

Now that I think about it, if this is indeed the case, I would expect some kind of visible warning in the UI should this happen. For example a notification in the notification panel, if not a permanent warning at the top.

surge919 · March 4, 2019, 1:45pm

I made a card to show my automations for a quick visual check… Since I’ve added the initial state, they’ve always been enabled.

entities:
  - entity: automation.1
  - entity: automation.2
  - entity: automation.3
  - entity: automation.4
title: Automations
type: entities