Upgrades from 0.89.1 to 0.89.2 lost automation

Configuration
1

This morning I decided to upgrade from 0.89.1 to 0.89.2 . Automations were working fine. After upgrading, I’m receiving the below error.

Invalid config for [automation]: not a valid value for dictionary value @ data[‘action’][0][‘entity_id’]. Got None. (See /config/configuration.yaml, line 73). Please check the docs at https://home-assistant.io/components/automation/ Invalid config for [automation]: not a valid value for dictionary value @ data[‘action’][0][‘entity_id’]. Got None. (See /config/configuration.yaml, line 73). Please check the docs at https://home-assistant.io/components/automation/

Automation.yaml

  • alias: ‘Open Family Room Blinds Sunrise’
    trigger:
    platform: sun
    event: sunrise
    action:
    service: light.turn_off
    entity_id:
    - light.ESPBlindstl
    - delay: ‘00:00:10’
    - light.FRblind2
    condition:
    condition: time
    weekday:
    - sat
    - sun

  • alias: ‘Open Family Room Blinds Sunset’
    trigger:
    platform: sun
    event: sunset
    action:
    service: light.turn_on
    entity_id:
    - light.ESPBlindstl
    - delay: ‘00:00:10’
    - light.FRblind2
    condition:
    condition: time
    weekday:
    - sat
    - sun

2

Welcome to the forum. Can you please post the code (automations) as mentioned in the header of the forum (between </>)? Now not possible to troubleshoot

3

It looks like you’re using:

    service: light.turn_on
    entity_id:
      - light.ESPBlindstl
      - delay: '00:00:10'
      - light.FRblind2

Which isn’t anything close to valid :wink:

First problem is that light.ESPBlindstl is likely light.espblindstl (same for the other one) - entities are normally all lower case. Check the dev-states menu (looks like <> under Developer tools).

Second problem is that you’re passing a delay to the light service, and that’s not valid. Instead you’d need:

action:
  - service: light.turn_on
    entity_id:
      - light.espblindstl
  - delay: '00:00:10'
  - service: light.turn_on
    entity_id:
      - light.frblind2
2 Likes
4

That did the trick. Just started using home assistant. Using Haas.io with the configurator, checked my config it said it was good to go. lies :slight_smile:

5

Config being good in the UI means that there’s no major errors - the YAML is structured correctly.

Config check on the command line being good means there’s no duplicate section headings.

Neither guarantee that what you’ve written is actually going to work :stuck_out_tongue:

1 Like