I was testing a few things and I manage to lost all my automations in the fronted.
Right now I get " entity not available: automation xxx "
The problem is in my configuration.yaml which is below
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# base_url: example.duckdns.org:8123
homeassistant:
time_zone: Europe/Athens
#discovery:
#automation: !include automations.yaml
# Text to speech
tts:
- platform: google_translate
I tried to add the âautomation: !include automations.yamlâ but the problem remains
In the log files I am getting
Invalid config for [automation]: [platform] is an invalid option for [automation]. Check: automation->platform. (See /config/configuration.yaml, line 14). Please check the docs at https://home-assistant.io/integrations/automation/
which is the #automation: !include automations.yaml
but with or without this line my automations are not available. Any ideas what I should do?
If you changed it say 3 weeks ago, didnât reload it and you restarted today, then that would have forced the reload âŚ
So it âwasâ caused by you updating (and by an inconsistent previous edit)
I am really not sure. I donât remember to alter it today and it was working fine for over a month.
Even if it should be sun.sun could it cause so much mess in order to loose all my automations?
Dear Mutt
thanks for your help. I am using HA only for 2 months, and most of my automations are completed with the help of this forum. You suggesting to check my automations but I am not able to find something wrong due to limited knowledge. How I could check them. The problems you are suggesting for all I can tell are not, since until this morning were fine. Thanks anyway and really hope someone can find a solution
Any your automation file is in the same directory as the configuration.yaml file? And the configuration.yaml you posted in your first post is the whole configuration.yaml?
No they are not.
However, I updated the configurator, and tried to add the ââautomation: !include automations.yamlââ
After a restart my automations are back!
Few days ago I tried to install a custom theme, and also tried to split my automations
I just added some lines like the following but I donât remember exactlyâŚ
Today before the update I checked the configuration file (in tools) and responded with error in these lines. So I erased them. I checked the config again it was green so I proceed with the update.
I am not really sure where the fault was but at least is working nowâŚ
You need to point the !include to the right direction, if the file you want to include is not in the same direction it will not work.
Letâs say you have this structure:
Of course it should be âdirectoryâ and not âdirectionâ
I assume that it needs to be this way, otherwise I could not imagine how the system would know which file you mean.
Letâs say you have a folder configuration, which contains configuration.yaml, a folder config and a folder automation. In the folder config you have a file automations.yaml and in the folder automation you have another file called automation.yaml. How would the system know which of these two automation.yaml file it should take?
I might be completely wrong here, however in my system it works this way, to be honest I never tried it otherwise.