Automation Configuration Alert

I’m not sure if I am in the correct group for this, But I noticed this alert today when I signed into my hassio on my pi 3B+.

*** Start Copy/Paste ***
INVALID CONFIG

The following integrations and platforms could not be set up:

  • automation
    Please check your config.

*** End Copy/Paste ***

I’m sure it was from a recent edit to remove some zwave hardware that was showing up in the overview & was no longer in use (returned to seller, etc). So can someone guide me as to where I might have screwed up?

Thanks!
Jesse

One or more of your automations is invalid. Check the log for details and also run a config check.

Where do I find “config check” ?? Also the only thing close to a log that I can find is the logbook and I do not see any alerts in there.

Configuration > Server Controls > Configuration Check

That I ran & it comes up fine.

Also the only thing close to a log that I can find is the logbook and I do not see any alerts in there.Annotation 2020-04-21 192751|690x265

So on startup it reports the configuration is invalid but when you run Config Check it says there’s no problem?

basically…Or any time I add/edit an automation. & I started looking today because today my living room lights didn’t dim when I turned the TV on. But if I edit/add an automation, I get this alert in the notifications.

Annotation 2020-04-21 193756

Any errors at developer tools > logs?

Yes.

*** start copy/paste ***

Log Details (ERROR)

Logger: homeassistant.config
Source: config.py:405
First occurred: April 14, 2020, 7:28:10 AM (58 occurrences)
Last logged: 7:22:40 PM

Invalid config for [automation]: (See /config/configuration.yaml, line 13).

*** end copy/paste ***

& line 13 is “automation: !include automations.yaml”

I’m guessing automations.yaml is where my error lies.

So I can review & make sure that each section is configured correctly, can you show me where I can see a sample automations.yaml to see how the separate entities & such are listed?

What’s the first line in automations.yaml?

If it’s automation: then remove it.

It starts off with " - id: " then a single quoted number.

I plucked off the 1st 2 for you to see

So an update. I rebooted the server & it doesn’t show up the notice of the issue upon boot. It only shows the notification when I modify/create an automation

Do you always edit/create automations with the automation UI editor?

if yes, then there is one thing you can try…

rename your existing “automations.yaml” file to something else (I recommend “automations.yaml.old”) then create a new empty “automations.yaml” file.

Restart Ha and see if the error is gone. If so then do the next step.

If the above step is good then create a new automation using the editor and see if you get the error again.

If not then copy and paste the old automations from the automations.yaml.old file one automation at a time and reloading the automations from the “server controls” section after each copy/paste action until either your error comes back or you get them all moved back over and you are error free.

If you get the error at any time then stop. That is the automation with the error in it.

1 Like

I use the gui to create the automations but I use the cli to edit the yaml file with vi. How would I go about copying & pasting individually?

So to solve this, I deleted all the automations. Then delated the automations.yaml file & created an empty one.

Well that was kind of almost what I said to do…

Most people set up a way to access their configuration files remotely. It depends on how you have HA installed. I use WinSCP to access the files and Notepad++ to edit them. Others use Samba and VSCode.

When i deleted the automations from the gui, they stayed in the automations.yaml file.

I’m pretty sure that’s not supposed to happen. Again, I don’t use the ui editor but I have used it for experimentation and to help other users and I don’t remember having that issue.

As a matter of fact, I just created a test automation using the ui editor and it created the yaml in automations.yaml.

Then I deleted the automation using the ui and it also deleted the automation from automations.yaml too.

I’m not really sure what you did that prevented it from working that way for you, too.

I just restarted my Hassio VM and I received the same error. I have made no changes in the last month.