A few automations stopped working sinds 0.94.1

Configuration
1

Hello,

A lot of my automations stopped working when i updates to 0.91.1.
I have no clue why, didn’t see anything on the breaking changes…

An example of one of my automations is:
### Motion: Washok verlichting ###

- alias: Licht washok aan bij beweging
  trigger:
     platform: state
     entity_id: binary_sensor.motion_sensor_158d000155b629
     to: 'on'
  action:
    service: homeassistant.turn_on
    entity_id: light.fibaro_system_fgd212_dimmer_2_level_3
- alias: Licht washok uit na 1 minuten geen beweging
  trigger:
    platform: state
    entity_id: binary_sensor.motion_sensor_158d000155b629
    from: 'on'
    to: 'off'
    for:
      minutes: 1
  action:
    service: light.turn_off
    entity_id: light.fibaro_system_fgd212_dimmer_2_level_3

I can see that the motion is working as it should be, the light is also working as it should be.
Can see the motion is registering motion and i can turn the light on with a different switch in the frontend…

What am i missing here?

Thanks…

2

Check the States page and confirm the automations are all set to on.

If they are not, you can easily set them all to on :

  1. Go to the Services page.
  2. Select the service automation.turn_on
  3. For service data enter: all
  4. Click the CALL SERVICE button.
3

Geez, how stupid of me.
The automations where just off.
Have been thinking of this for days why this all just stopped working.
LOL :sleeping:

4

The fact they were all off may be due to a bug that’s been present since Home Assistant’s restoration feature was revised in version 0.84. It has been corrected in version 0.94.1 by the following PR:

The restoration feature records the state of your automation (and several other kinds of entities). When Home Assistant restarts, it restores the automations to their recorded state. This feature had a flaw (explained in the PR) that could cause all automations to be set to off on startup.

Before the bug was fixed, the suggested solution was to add initial_state: true to each automation in order to force it to be on upon startup. This overrides the restoration feature, is not a recommended solution, and has two negative side-effects (discussed elsewhere).

I recommend that anyone experiencing the same problem consider upgrading to 0.94.1, turn on all automations if they are off (instructions shown above) and then allow the corrected restoration feature to take care of the rest.

1 Like