Open meluvalli opened 4 months ago
After migrating automations forget about using yaml features like secrets, include, anchors, packages. Consider this as similar to a "storage mode" of Lovelace.
Glad to see someone created an issue for this - it would be excellent if secrets were allowed within the editor since Home Assistant is very focused on the UI/UX of things. At the very least, there should be a more descriptive error than Response error: 500
Checklist
Describe the issue you are experiencing
If you use the tag "!secret" to reference secrets.yaml in automations.yaml, you receive an error in FE saying "This automation cannot be edited from the UI, because it is not stored in the automations.yaml file, or doesn't have an ID."
Describe the behavior you expected
This error shouldn't be there and the automation does have ID's associated with them. If you remove all references from !secret, this problem goes away.
Steps to reproduce the issue
What version of Home Assistant Core has the issue?
2024.2.3
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
All (N/A)
Which operating system are you using to run this browser?
N/A
State of relevant entities
No response
Problem-relevant frontend configuration
Javascript errors shown in your browser console/inspector
No response
Additional information
FYI: This was also reported in the community forum.
https://community.home-assistant.io/t/this-automation-cannot-be-edited-from-the-ui/557254/3