Automations turning off /on after saving any automation

Configuration
1

hi All,
Newbie here…
I noticed all my automations are toggling ON>OFF whenever I do any automation change via the UI.
Is this normal?

Now, as I have automations running & waiting for ‘for’ to complete, they seem they do forget they were in the middle of waiting, they no longer execute I think I noticed?
How can this be avoided?

  - platform: state
    entity_id: person.xyz
    from: not_home
    to: home
    for: '00:10:00'
condition: []
action:
  - service: lock.lock
    data: {}
    target:
      entity_id: lock.smart_code_with_home_connect_technology
2

Whenever a new automation is created, or an existing one modified, the Reload Automations service must be executed so that Home Assistant registers the changes.

If a user creates/modifies automations with a text editor, they are familiar with the reloading process because they must manually run Configuration > Server Controls> Reload Automations.

If you use the Automation Editor, it is done automatically for you (when you save the automation).

However, as you have discovered, reloading automations also serves to initialize their triggers (i.e. the countdown performed by for is reset).

FWIW, I also use another home automation system and it is capable of registering a single new/modified automation (i.e. all other automations are not reloaded). Perhaps some day Home Assistant will work the same way.

1 Like
3

Thanks for your kind reply.

So my question is: is there a simple way to save /reload automations while keeping the ongoing triggers intact in HA?

TY

4

For the reasons mentioned in my previous post, no it’s not possible.