Repeating notification - Invalid config for [automation]

Hi,

I have a problem with one logo. For the last few weeks at least, this bug has been popping up in my notification:

Logger: homeassistant.config
Source: config.py:443
First occurred: 8:06:56 (5 occurrences)
Last logged: 9:43:40

Invalid config for [automation]: required key not provided @ data[‘action’]. Got None required key not provided @ data[‘trigger’]. Got None. (See /config/configuration.yaml, line 1234).

The upside was that I went through the log and fixed the old settings (not all of them, unfortunately, but that’s the problem with specific integration). But that log still remains. I originally went through automation in a yaml file and removed the “data” entries with an empty field. This has helped (the error occurs in smaller numbers), but it still remains and will appear with each automation/restart performed (however, the automation works, thankfully).
I’m also puzzled that this guides me to line 1234, but the specific configuration is in the line below, not to mention that it’s a pretty vague direction anyway:

1232 # Cloud
1233 cloud:
1234
1235 automation: !include automations.yaml
1236 script: !include scripts.yaml
1237 group: !include groups.yaml

I found the same problem in historical contributions, the user solved it by moving automation to packages. Can you think of another cause?

The issue is in your automations.yaml.

Probably a typo or you deleted actions and left the rest of the automation.
But have a look in the automations file and see what you find

Yes, I got that, too, but unfortunately in this case, the log is pretty vague. You got a mistake somewhere between x hundred lines, try my best boy :slight_smile:

However, I was going through the settings in user interface mode and noticed a difference in behavior between the originally defined services and the new ones.

For example, if I use a triger to set the shutters to open, it doesn’t write position:0. Also, a difference in vacuum cleaner start-up:

date: {}
entity_id: vacuum.xiaomi_vacuum_cleaner
service: vacuum.start

service: vacuum.start
target:
entity_id: vacuum.xiaomi_vacuum_cleaner

Looks like this could be a problem. For me, that means going through all the automation. That’s not a very pleasant job.

I did, so for future generations.
I initially thought that some of the older configurations were in the way, as I suggested in a previous post. But in the end, it was “forgotten” automation. For some reason, in yaml file empty automation (id XXX) left. It didn’t show up in the user interface, of course, and it’s easy to miss in those x hundred lines.
I was a little surprised by automation.yaml’s behavior too. When I commented line on automation,yaml, the reboot deleted it. It was not a pleasant experienc with month-old backup.