Ignore automation triggers after restart

Configuration
10

What you could do is right after the restart, run the following:

  - service: automation.turn_off
    data:
      entity_id:
        - group.all_automations
  - delay: 30
  - service: automation.turn_on
    data:
      entity_id:
        - group.all_automations

After 30 seconds, the states of some of entities that got messed up due to the start up should should have ‘stabilised’ and when you activate the automations again, they will no longer trigger unwanted automations to start (because an automation only starts at the moment of the state change). You can play with the 30 seconds of course if you need it to be longer or if it can be shorter. Also, you could specify the exact automations you want to exclude…

  - service: automation.turn_off / turn_on
    data:
      entity_id:
        - automation.name_of_the_automation_to_deactivate
        - automation.name_of_another_activation
        - automation.and_so_on_and_so_on
1 Like
11

I’ve been running into this issue lately. To conclude, put this into your automations:

- id: delayautomationsonrestart
  alias: 'Delay automations on restart'
  hide_entity: true
  trigger:
     platform: homeassistant
     event: start
  action:
    - service: automation.turn_off
      data:
        entity_id:
          - group.all_automations
    - delay:
        seconds: 30
    - service: automation.turn_on
      data:
        entity_id:
          - group.all_automations

I almost feel this should just be the default behavior of automations. Add a flag that allows automations to trigger on startup triggers.

3 Likes
12

That you for this, i couldn’t work out why my lights kept turning on when i rebooted my HASS

13

Hey - thanks for the suggestion @liquidox. This looks like it will solve my problem (same as others). But in practice, I am finding that home assistant loads this automation quite a bit later than the ones I want to inhibit at restart, so the problem remains unsolved.

I can’t find anything about how to determine which automations will load first. Looking at the logbook, it doesn’t appear to be alphabetical (either by automation name or by yaml file name).

Any thoughts? Any way to force the delayautomationrestart automation to load before all the others?

And I agree - this should be default. Don’t allow automations to fire until all the platforms have loaded / settled / whatever. Too much unpredictable behaviour as it is.

Thanks

14

Personally I have “fixed” it by moving all my automations over to AppDaemon, obviously not a solution for most people, but worked out for me. And now have all the power of AppDaemon, which is amazing.

15

I only have 1 automation that would go nuts when restarting Home Assistant: an automation which sends me a notification whenever certain devices in my network would go offline or come back online. Whenever I restart Home Assistant, that automation would send me a notification for every device stating it came back online (and sometimes even that it had gone offline first). So with 6 devices being monitored by that automation, I would get either 6 or 12 notifications on my phone.

I work around that by checking how long Home Assistant has been up and running: if it’s less than 5 minutes, then don’t trigger the automation. For this, I use a sensor:

- platform: uptime
  name: "HA runtime in minutes"
  unit_of_measurement: minutes

and then the following condition in said automation:

- condition: numeric_state
  entity_id: sensor.ha_runtime_in_minutes
  above: 5
9 Likes
16

Ah that’s perfect. Thanks David.

(PS it worked nicely, too)

1 Like
17

My problem isn’t quite the same but maybe you guys have figured this out while figuring out the problem in this topic. So I’ll borrow the topic a bit - sorry about that :slight_smile:

I have an automation that sends me a notification (ios) if a device becomes unavailable. This is mainly to monitor whether any of my many wireless Zigbee-sensors run out of battery. Now every time I restart HA, I get zillion notifications, because apparently HA considers the sensors being unavailable right before it shuts itself down. I tested that it happens in shutdown, not on start.

I doubt that there is a way (or at least it won’t be quick enough) to for example turn the automation off if HA receives a restart command? And then set the initial_state to ‘on’ so that it will come back on after start?

Any other ideas?

18

My suggestion would be to create a script that first disables the automation to send a notification and shuts down homeassistant afterwards. Do bear in mind: it needs to be a script as that can do consecutive actions.

If the problem is that you get a lot of reminders, then you can put a timer in place and use that as a condition (do not fire the notification if previous notification has been sent less than 5 mins ago)

Main drawback is that you always need to shutdown via that script.

19

Thanks! Actually this was so stupid simple that I almost feel embarrassed :slight_smile: I just added for: 00:04:00 to the original automation. This solves the problem completely. Below 4 minutes would probably also be more than fine but that works too for this purpose.

20

this worked so great thanks @fanaticDavid

1 Like
21

Checking uptime or restarts does not fix it because this problem also appears if you reload automations in the configuration.

22

Also running into this issue as well. Automation will immediately trigger, including as soon as the automation is turned on if using initial_state: false.

23

Anyone ever find a fix for this?

24

I still happily use the uptime timer and never reload automations (instead I always restart Homeassistant)

25

Since Home Assistant 2020.12.0, a fix is needed:

26

The way I have done it is this.

input_boolean:
  homeassistant_booted:
    name: Home Assistant has started up
    initial: off

automation:
  - alias: 'Hass Startup Notification'
    initial_state: on
    trigger:
      - platform: homeassistant
        event: start
    action:
      - service: notify.mobile_app_ios
        data:
          title: "HASS"
          message: "Home Assistant started!"
      - delay: '00:00:30'
      - service: input_boolean.turn_on
        data:
          entity_id: input_boolean.homeassistant_booted

And then check input_boolean.homeassistant_booted in the automations.

27

Hi all, sorry for digging this up, but I tried to use this solution and I get errors like this: In ‘numeric_state’: In ‘numeric_state’ condition: entity sensor.uptime state ‘2022-07-18T10:25:40+00:00’ cannot be processed as a number

The sensor was set up as described. Anyone else having this problem?

28

The uptime sensor back then was a duration in minutes that the server has been alive. The uptime sensor now is a time stamp when the server started. His post won’t work with that sensor.

29

replace that with:

{{((now() - as_datetime(states('sensor.uptime'))).seconds)|int > 60}}

for 1 minute

1 Like