Automation editor not working in 0.48

I’ve got about 20 automations that I copied over to automations.yaml and added the id. Here’s an example:

- id: set_away
  alias: 'Set away'
  initial_state: True
  hide_entity: True
  trigger:
    platform: state
    entity_id: input_boolean.alarm
    state: 'on'
  action:
    - service: climate.set_away_mode
      data:
        entity_id: climate.kitchen
        away_mode: true
    - service: climate.set_away_mode
      data:
        entity_id: climate.bedroom
        away_mode: true
    - service: climate.set_away_mode
      data:
        entity_id: climate.ryans_room
        away_mode: true

All my automations appear on the Automations tab. However, when I click on an automation, the screen is blank. I’m running a Chrome browser. If I try to add a new automation, I see the editor. Any suggestions?

1 Like

On first few times it was blank to me too… but today I see them. Maybe Chrome has some strange cache going on? Idk…

but then, even if you see the editor… it’s not prime time for use yet… lots of my automation has conditions and none of them are supported… even time trigger isn’t supported… so until then, it’s not much useful :slight_smile:

It is blank for me too :frowning:

I can see my automations, but i cannt edit anything since all “triggers” are showing “Not supported”, I’ve tried it on both my hassbian environment and my hass.io docker environment, same issue on both (docker enviroment completely empty so it’s using the standard configuration for HA 0.45.1)

My screen is blank too. When I try to create a new one it does not save the new automation.

We’re at 47.1 and the annotation editor is still not working for me with Chrome. I can create new annotations but I can’t edit existing annotations. Any suggestions?

I’m at 0.48 and the automation editor is still not working in Chrome. All my automations are in one file and I’ve preceded each automatic using a unique id.

Does this work for anyone! Any help would be appreciated.

I’m at 0.49.0, and it worked out for me after doing a hard reload on chrome (Crtl+F5).
But, I have to do it each time I launch the HA…

Can you post a snippet (two or three automations) from your automations.yaml file? Maybe there’s something about the structure we don’t get.

I also see only empty automations in 0.50.2 and can’t save new ones.
My automations.yaml is pretty simple:

- id: startup_notification
  alias: Startup Notification
  trigger:
    platform: homeassistant 
    event: start
  action:
    service: notify.pushover
    data:
      message: Home Assistant started.
- id: update_notification
  alias: Update notification
  trigger:
    platform: state
    entity_id: updater.updater
  action:
    service: notify.pushover
    data:
      message: 'There is a new Home Assistant release available.'

In the javascript console I see the following error:


GET http://myserver:8123/api/config/automation/config/startup_notification 404 (Not Found)

So for some reason the API Endpoint seems missing. Has this maybe something to do with not using https?

I added an nginx proxy with https but still get a 404.

frontend-7d59999….html:5 GET https://myserver.local/api/config/automation/config/startup_notification 404 (Not Found)

For some reason the api endpoint seems missing. Any ideas?

Okay, I found the issue. This ticket described it pretty good https://github.com/home-assistant/home-assistant/issues/8249 and linked to the solution in this ticket: https://github.com/home-assistant/home-assistant/issues/7823#issuecomment-314694547

I was missing the config entry in my configuration.yaml. It was introduced in 0.39 which was after my initial install.

configuration.yaml

config:

for me, it was as simple as using the right name for the automations.yaml file. I had this file from before, but it was called automation.yaml, not automations.yaml. this was apparently enough to display the automations, but not being able to edit them - very intuitive…