When I try to save edits to automations in the webbrowser I get a 404. (file is named automations.yaml)

[kristoffernolgren]

Home Assistant release (hass --version):
0.45.1

Python release (python3 --version):
3.4.2

Component/platform:
haspbian

Description of problem:
When I try to save something to the home automation, i get a 404, http://hassbian.local:8123/api/config/automation/config/1496087113456 404 (Not Found). I have named the file automations.yaml and included it in my configuration.yaml file. the chmod of automations.yaml is -rwxrwxrwx. I can see my automations, but when I click on them I get another 404, http://hassbian.local:8123/api/config/automation/config/playP3 404 (Not Found), also the automations work as expected.

Expected:
To be able to save and edit my automations

Problem-relevant configuration.yaml entries and steps to reproduce:
automations.yaml

- id: playP3
  alias: Play Rain Lullaby
  trigger:
    platform: state
    entity_id: input_select.lullaby
    to: "Rain"

  action:
    service: media_player.play_media
    data:
      entity_id: media_player.koket
      media_content_id: http://http-live.sr.se/p3-mp3-192
      media_content_type: audio/mp3
# If you select "None, turn the Chromecast off
- id: stopP3
  alias: Stop the Lullaby
  trigger:
    platform: state
    entity_id: input_select.lullaby
    to: "None"

  action:
    service: media_player.turn_off
    data:
      entity_id: media_player.koket

configuration.yaml

automation: !include automations.yaml

[fabaff]

Where is automations.yaml located?

[kristoffernolgren]

default hasspbianfolder/same folder as configuraition.yaml

/home/homeassistant/.homeassistant/automations.yaml

[corneyl]

Like I said in #7707: I think it would be a nice addition if the automations editor checks whether it can load/read/write automations at all, and shows an error with instructions on forehand.
Now it's just a matter of trial and error to see whether the API returns something useful and the front-end can be rendered.

[kristoffernolgren]

@corneyl you got it working? do you see what could be wrong with my setup? Atleast intentionally I'm using the default, that's what makes it weird that it's not working...

[corneyl]

Yes, I got it working, had used the wrong file name automation.yaml. Saving is also working.

[kristoffernolgren]

I'm running chrome ni osx might be worth mentioning, I get the error:

Currently Chrome is the only supported browser.

even though i'm using chrome, not sure if that is intended.

[nunofgs]

@kristoffernolgren I have the exact same problem. Can also see the automations on the frontend but clicking them or attempting to add a new one yields a 404.

Using Docker by the way.

[point-4ward]

Some people (me included) are having an issue where the save button doesn't do anything at all. No 404's, no nothing.

[Whytey]

The 404 is hidden in the javascript console.

For me, this was resolved by adding the 'config' component to my configuration.yaml, per the suggestion in #8334 (comment)

This issue could be closed, though ideally, we should update the doco to provide more guidance on dependencies for the automation editor.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍