Create automation leads to invisible automation in the UI (related to #100267)

[zenkraker]

Checklist

• [X] I have updated to the latest available Home Assistant version.
• [X] I have cleared the cache of my browser.
• [X] I have tried a different browser to see if it is related to my browser.
• [X] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

When you deploy the configuration.yaml with the following option:

automation: !include automations.yaml

You can create automations in the UI even though they should be "blocked" because you're using the automations defined in the configurations.yaml. The problem is that you can define a new automation in the UI, do all your steps and all what you need as usual, you click save and you get a green confirmation. But when you go back to the automations page, the automation you just created is gone (it is created in automations.yaml but it is not visible on the UI). There's also a discussion on the forum --> https://community.home-assistant.io/t/automations-not-saving/155921

Describe the behavior you expected

I would expect to see the automations page blocked entirely (visible but non clickable) if you use the configuration.yaml only (maybe display an info saying: automations are available by modifying the configuration.yaml only) OR have a check to see if automations.yaml can actually be saved (e.g check if #automation: !include automations.yaml is commented or similar) instead of getting a green confirmation and then don't see the automation on the UI

Steps to reproduce the issue

1. In docker, deploy a new HA instance with configuration.yaml with

   automation: !include automations.yaml in it.

2. Login, go in the UI, go into automations section, create an automation (even an empty one) and save it
3. Go back to automations page and the automation you just create is not visible (but visible in the automations.yaml)

What version of Home Assistant Core has the issue?

2024.10.1

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[karwosts]

I do think this will need a core issue, I'm not seeing much that can be done in the frontend:

• I'm not aware of any API that can indicate automations.yaml is missing
• When we save the automation, we get back a 200 OK message, indicating that everything saved successfully.
• Oddly enough core actually must be saving the automation in its memory, since if you copy the URL of the automation page and leave, you can get back to it after leaving and the automation is still saved.

• Actually it looks like if you comment out automations.yaml in configuration.yaml, saving an automation still writes to automations.yaml, it just isn't visible in the list of automations, but it still seems like it's saved to the disk.

  Seems like core should return some kind of error response to save command if it's not really going to save it. Not sure if that's technically difficult or not.

[alinclaudiu]

after save , the condition, action, trigger are renamed to conditions, actions, triggers , after that the UI is empty