then you should be getting an error in your logs at some point in the process. You could try to restart the supervisor as well.
Yes I have some errors, but not related to automations. At least not after I last reloaded automations about 1 hour ago. How do I reload supervisor? I don’t see it in the YAML configuration reloading list.
Thanks for helping!
Have you deleted the automation which is not showing up in the GUI, from the automation.hay looks. And checked there are no other automations in automation.yaml that are not in GUI.
Or delete all of automation.yaml and see if it solves anything. Afterwards,you,can copy back the automations, one by one
You can restart the supervisor by rebooting or through SSH with CLI if you set that up. Just post your full logs but I doubt it has anything to do with a spinning config check button. You could aslo just click the restart button which will also perform a config check and out put the errors. Either way, they are usually accompanied by logs.
I ran your yaml through a yaml checker and it’s valid yaml. So this is either completely unrelated or supervisor isn’t playing nice (reboot would fix)
Yes I deleted the duplicate automation you spotted in the automations.yaml, but still no success. If I comment out automations from configuration.yaml or just delete all content in automations.yaml I get a valid config check.
I started on the one by one automations through UI as I described in my opening post, but haven’t tried it through the automation.yaml yet.
Thanks for helping!
Ah, so restarting host (my intel nuc) will also do the trick?
After I click the restart button and nothing happens, I still don’t get a new entry in the log.
Are you running supervised or home assistant os?
I’m not sure. I followed an installation guide some months ago on how to install HA to a SSD. Can’t remember what guide, but it was through the home assistant web site. In the about page it says:
Home Assistant 2022.9.6
Supervisor 2022.09.1
Operating System 9.0
So at least it mentions Supervisor, so then it should be supervised?
I’m asking a lot of newbie questions here
Well, your config looks fine. Before you reboot, I would suggest adding ssh and/or samba so you can access your system if the reboot doesn’t go well.
I do have SSH and web terminal in my HA. Don’t know how to use it, but I installed after I read it was recommended in case something went wrong. I’ve restarted the host without any problem, but will still not get me a valid config, only an endless spinning wheel
If you rebooted and it started back up, then nothing is wrong other than whatever errors are in your logs. And you should fix them one by one.
I’ll try that next! It’s just a bit confusing that I get a valid message after I remove all my automations. But I’m sure there is a logical explanation. At least now I’m one step further so thank you!
You can use SSH to run a ‘long’ config check that will output all possible errors.
I know my approcah is very practical and not a nice technical solution. Your number of automations are fairly small, hence you can do it in 20 min.
- Start with a blank automations.yaml and check it works, incl reboot.
- Do a new simple automation and check that it works
- copy the automation back, one by one or in some groups, check that it works
- When it stops working, remove the automation again, and check that it works.
- Create the failing automation again from scratch, no copy.
Think you will find a character or some other strange stuff in automations.yaml during the process.
Or, you will expierence something leading to a different problem, outside the automations area.
Thanks khvej8, I like your practical approach. I will try this method if I still have problems after I remove other errors reported in my log. Thanks again for helping!