#Unable to delete/disable/change anything in automations

1 messages · Page 1 of 1 (latest)

paper ocean
#

I am totally lost (see title). Any advice?
The problem is:
I have one - exactly 1 - "dead" automation, there are no others.

This entity ('automation.automation_0') does not have a unique ID, therefore its settings cannot be managed from the UI.

I can't edit it visually.

This automation cannot be edited from the UI, because it is not stored in the automations.yaml file, or doesn't have an ID. (It definitely is in automations.yaml!)

I can tell it to migrate, but then I get stuck just the same when editing the YAML, see below.

I can't delete it (permanently),

Error loading automation (500).

I can't disable it: it briefly achanges to disabled, but after ~5 sec, it enables by itself.

After migrating, when editing YAML from the automation editor, I can't save any corrections, not even an empty one.
When I hit SAVE, it suggests

rename the automation.
This I can't reject. If I do rename, it asks for rename again... and again...
the only way to leave is to cancel the box

I edited the automations.yaml file from FileEditor. I can save without problems.
I restarted Home Assistant during all these processes, including reboot

The defective automation still can't be run/deleted/edited visually or as YAML: same errors as before.

I have more to add to this description, see appended file

📎 Unable_to_delete_disable_change_anything_in_automations.txt
low bay
#

I would delete it (/ copy it!) from the automations.yaml. Then reload, should be gone.

Next make a new automation from the UI. Switch to yaml mode and paste the whole automation. Just replace the - on the first line with a space.

sour jewel
#

There is something, I think a bug, or simply race condition if you will. I've updated one autoamtion yesterday and this morning I noticed it didn't fire. FAst forward, I just noticed that "automation is disabled and cannot be updated via UI as it does not exists in the automations.yaml file"...

#

even if I migrate, it gives me the opp to save it but then immediately pops-up that I can't modify it anymore as it is not in the automations.yaml file

#

Restarting system now

#

now I have 2 automations and none modifiable with UI

#

Hah, in fact ALL automations are now like above one...

low bay
#

automation.yaml does exist? Did you remove the import automation.yaml from the configuration.yaml?