I am cleaning up some unused automations, but all of my automations show this in the UI:
This automation cannot be edited from the UI, because it is not stored in the automations.yaml file, or doesn’t have an ID.
Yet, the automations are in the automations.yaml file and have an ID. I can manually delete them in automations.yaml then reload automations, but it appears that all of my automations now show this banner.
Any ideas?
Post your configuration. There’s a very good chance you’ve had a miss configuration for many years.
Start by posting configuration.yaml and how you include the automation file. Also, include the automation file name.
Thanks for the replies…
I have 220 automations. They have been working for many months and years, so I am pretty certain that Home Assistant is finding my automations.yaml.
You may be on to something as I have both default_config and the automations key.
I have split my keys to sepatate files:
automation: !include configuration/automations.yaml
camera: !include configuration/cameras.yaml
command_line: !include configuration/commandline.yaml
group: !include configuration/groups.yaml
mqtt: !include configuration/mqtt.yaml
openhasp: !include configuration/openhasp.yaml
recorder: !include configuration/recorder.yaml
rest_command: !include configuration/rest.yaml
script: !include configuration/scripts.yaml
scene: !include configuration/scenes.yaml
sensor: !include configuration/sensors.yaml
shell_command: !include configuration/shell_commands.yaml
template: !include configuration/templates.yaml
zone: !include configuration/zones.yaml #For Life360
Yeah, only automations.yaml inside the config folder can be managed by the UI. You’ve had a bad config for awhile that has accidentally worked.
try:
automation: !include automations.yaml
automation manual: !include configuration/automations.yaml
Or just move the automations.yaml to the main level of the config folder and drop off !include configuration/automations.yaml
I tried that, then I had no automations.
Virtually, maybe all of my automations are manually edited in YAML I find the UI difficult to use and the YAML code just looks more logical to me.
Is automation manual a valid key?
You need to check config and restart after you change any of that, just making sure you know…
Isn’t check config automatic with a restart? I am pretty sure I did a restart after moving the automations.yaml file and removing the include line. But I tried again and definitely restarted Home Assistant and got the “Start Automating” page.
But with the include line pointing to configuration/automations.yaml shows me all 220 automations.
Most if not all of my automations are created in YAML generally starting with the UI then switching to “edit in YAML”.
It’s used in an example in the documentation for “Splitting up the configuration”.
FWIW, here is what I have used in my configuration.yaml file for many years:
automation: !include automations.yaml
automation manual: !include_dir_merge_list automations/
So, in my case as @Sir_Goodenough suggested, I should have two different automations.yaml files?
automation: !include automations.yaml
automation manual: !include configuration/automations.yaml
##########
OK, made two automations.yaml files as above and all 220 of my automations are present.
I think what has changed is that in the past I would start editing in the UI by clicking on “Create new Automation” then going straight into “Edit in YAML”. I was always able to edit or modify my automations by clicking on the automation than “edit in YAML”. But now, I can’t. Now, I have to edit the automations.yaml file. This is new?
###########
Update
OK, thanks for the tips that got me back on track. My UI generated automations will go into config/automations.yaml and my manually coded automations are in config/automations and I added this line to my configuration.yaml:
automation manual: !include_dir_merge_list automations/
Thanks again for clearing this up for me.