I have a case where my automation/dashboard shows automations that are now not in my automations.yaml and if I try to delete from the dashboard i get ‘Only automations in automations.yaml can be deleted.’
I have in my configuration.yaml … automation: !include automations.yaml
How do i Remove the listed automations from my dashboard ?
Go to Settings → Devices & Services → Entities and delete the “restored” automations there.
so I now see below and cannot delete from the list , i cant see where in the files i can manually delete
This entity (‘automation.office_motion_2’) does not have a unique ID, therefore its settings cannot be managed from the UI. See the documentation for more detail.
Then this must have been created using YAML.
Delete the yaml and reload.
Delete the config/automations.yaml ? … the only automations in this are the valid ones , it does not contain the ones i want to remove so not sure how this makes a difference
have the same problem, tried:
All of this didn’t work for me, but it got me in the right direction to solve it anyway. What I did:
In the ‘developer tools - states’ I looked up the ID of the automation that I wanted to delete (it was already gone from automations.yaml). Then I created a new automation that turns on a random light through the GUI. When I saved it, I opened automations.yaml and replced the ID of the newly created automation, with the ID from the automation that didn’t excist anymore, but was still in my automations list. Restart
At that moment, I was able to delete the automation from the GUI.
It cannot be removed from Entities because it is listed as read-only, and cannot be selected. If you click on the info icon it shows " This entity (‘automation.somename’) does not have a unique ID, therefore its settings cannot be managed from the UI. See the documentation for more detail." which doesn’t help much.
It should be simple to remove these deleted automations. (They were deleted after all!) Why isn’t it?
Or another approach: If these undeletable deleted automations are not listed in automations.yaml, then where are they being persistently stored, so that they survive a restart? I have Studio Code Server and Terminal installed. Please point me at where they are hiding.
Never mind. Some time after the restart, theses undeletable deleted automations appear to disappear from the UI. (Why does it take so long?)
Creating an automation with the same name did the trick for me. Afterwards i was able to delete it and it was gone for good.
It looks like these automations appear when a new automation could not get saved properly and is closed anyways.
Great idea 
For me, resulted in yet another unremovable automation. Fortunately, at the same time, according to the vague description, I understood where it appeared there and removed the cause (non-functional code in configuration.yaml). Under what circumstances did your irremovable automation appear? Isn’t that related?
I Had several unremovable automations.
It’s nearly impossible to delete automations or entities in an easy way. They always leave a trail behind with no clue where is what located. After a full restart it’s still there.
Properly renaming is also not possible. The first time you name an item be very sure the name is correct. Changing the display name is easy. But when you rename an automation the id doesn’t change with is. Not even after a full restart
Found this link which stupidly worked for my automations.
in short:
Web interface > Developer tools > select tab “YAML” > under section “YAML configuration reloading”, click “ALL YAML CONFIGURATION”.
Refresh browser and they were gone.
I stumbled on a quick and dirty method to get rid of ghost automatons. Go to the list of automatons. Select the ghost automation (one click). Then select duplicate. Refresh the web page and it is gone.
THANK YOU!
I’ve been sitting here for more than an hour trying to fix this - not only did I see all those zombie automations, lots of my entities were also not getting updated, obviously due to this.
Once I did the ‘duplicate’ thing they all disappeared, and sensors started behaving properly.
This is really something that should be done automatically on restart.
Wow, thank you so much @VHKRMOTL ! This solved it all at once.
Unbelievable ! Don’t figure out the way the trick works, but it works. Thank you 
Thank You @VHKRMOTL. Worked for me as well.
More than 2 years later, it still works. Couldn’t find a better solution. Thank you very much.