Not all automations get reloaded after restart

Configuration
1

Hello!
I’m using HA since 0.30. I had been running 0.50 for quite a few time. A week or so ago I’ve updated to 0.70.1 and now I have a minor problem. Whenever I restart HA there is this one automation, that doesn’t get reloaded.
If then I go to Settings > General > Reload automations, it is reloaded along with other automations.
configuration.yaml:

...
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
...

cat /home/hass/.homeassistant/automations.yaml
- alias: "...."
  trigger:
    - platform: time
      at: '.....'
    - platform: time
      at: '......'
  action:
    - service: switch.turn_on
      entity_id: switch.........
    - service: switch.turn_on
      entity_id: switch.......
More similarly structured automations here ...

Dots are placeholders.
What’s the issue here? If it’s issue with HA, I’ll post an issue to github.

2

I see the same problems, it was there since 0.69.

A reload automations after restart fixes the problem.

1 Like
3

@ASMfreaK With lots of updates between your earlier and current versions, there will have been a few breaking changes that may be causing issues. Try running hass with the --script check_config at the command line.

4

Not sure if this is the problem but if the automation is off after a restart you could add; initial_state: 'on'

5

I’ve ran it earlier, but just for the sake of the argument:

(env) hass@myhost:~$ hass --script check_config
Testing configuration at .../.homeassistant
(env) hass@myhost:~$

Nothing :neutral_face:
If there was an error in config, then I could have fixed that as I was updating the configuration lately

6

It’s not turned off. It doesn’t show up at the web interface at all.

7

try removing and recreating one of the automations.???

8

I had the same problem I think mine were missing the ID’s

9

I’ve found the source of my problem. See this issue.
Though, I’m not sure how exactly does this issue cause this reload-trouble

10

Thanks for the update. Sad it is a problem for you though.