Automation stopped working after upgrade to 88.1

Configuration
1

Hi… My proven automation which was working for months has stopped working after upgrade to 0.88.1

I’m not able to see any error in this and no error is reported in the log. It just does not work. Any help will be much appreciated.

Manually triggering the event from DEV tool also does not execute the action.

  • alias: Cam1 Motion Detected
    trigger:

    • platform: state
      entity_id: input_boolean.cam1_motion
      to: ‘on’

    action:

    • service: timer.start
      entity_id: timer.hall_fan

    • service: input_number.set_value
      data_template:
      entity_id: input_number.hall_fan_timer
      value: “{{states.input_number.auto_off_timer.state | int}}”

    • delay: ‘00:00:10’

    • service: input_boolean.turn_off
      entity_id: input_boolean.cam1_motion

2

use code markdown on your config so we can better see what is going on. to use markdown syntax press the key to the left of the one on your keyboard three times at the beginning of your code block and at the end
Like this
image

3

Hi… Thanks for a quick response to help.
‘MarkDown’ is something very new to me and haven’t heard or used before.
What does it do ? Could you please tell me how it helps to debug…?? Tx.

4

Anyway, just did what you said and I got the following error in validation.

Error loading /home/homeassistant/.homeassistant/configuration.yaml: while scanning for the next token
found character ‘`’ that cannot start any token
in “/home/homeassistant/.homeassistant/automations/Motion-Action-v13-test.yaml”, line 3, column 1

5

nit in your actual yaml just in the yaml posted above so it will be formatted as code

6 
- alias: Cam1 Motion Detected
  trigger:
    - platform: state
      entity_id: input_boolean.cam1_motion
      to: 'on'
   
  action:
    - service: timer.start
      entity_id: timer.hall_fan

    - service: input_number.set_value
      data_template:
        entity_id: input_number.hall_fan_timer
        value: "{{states.input_number.auto_off_timer.state | int}}"

    - delay: '00:00:10'
    - service: input_boolean.turn_off 
      entity_id: input_boolean.cam1_motion

I hope this is what you had asked for. Sorry, I was so dumb that I did not understand.

1 Like
7

no problem, did you check to make sure your entity id’s are the same some of mine changed after 0.88.1 other than that I cant see why this stopped working

8

Hmm…

Checked entity_ids thru the DEV Tools and using service commands the individual enities turning off and on, works fine.

9

Is the automation enabled? Check on the dev-state page, if the automation is “on”. Otherwise enable it by calling Service automation.turn_on

10

And if you execute the automation from the GUI? Does it execute the actions? Then at least you know if the trigger or the action is the culprit.

11

[SOLVED] Hi. You hit the nail on its head. That was exactly the problem. All my automations were ‘off’ [didn’t know how]. I found the same automation was triggered from DEV tools but not from HA. That’s how, I discovered all were off.

Thanks for your response.

12

It was a breaking change in the latest releases (0.86 if I remember correctly), where restoring states was changed. As a consequence, the initial state could not be recovered after restart once.

Since this change, the state is correctly restored so you can either add “initial_state: on” to every automation or call “automation.turn_on” services without any entity_id once.