Using above instructions container name includes the dash.
shiny % docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a9be19e6c76a homeassistant/home-assistant "python -m homeass..." 5 minutes ago Up About a minute 0.0.0.0:8123->8123/tcp home-assistant
shiny % docker restart homeassistant
Error response from daemon: No such container: homeassistant
[1] 67676 exit 1 docker restart homeassistant
shiny !1! % docker restart home-assistant
home-assistant
Added an entity_id to the template trigger, as is best practice. Added a warning that template triggers without an entity_id have major performance impacts, and directing people to template sensors as an alternative.
* update to synology docker install page
Unfortunately the Synology GUI way of installing Home Assistant through docker does not allow access to the USB devices to use a Bluetooth or Z-Wave radio (has to be done via ssh) - User Phil Hawthorne has provided great instructions on his blog to access these devices - so wondered if it was acceptable to provide a link (otherwise it would require adding quite a lot of info to the page)
Regards,
James
* Make a note
typo - the instructions suggest calling your container "homeassistant" but then refer to restarting a container called "home-assistant"
typo - "lose" instead of "loose" & "a" instead of "an"
additional - web interface accessible using http://synologyIP:8123
additional - how to restart from synology
* Update actions.markdown
Added note to remind users to update push settings within the app. There are multiple community questions around this and performing this update will take care of many issues when implementing actionable notifications.
* Correcting spelling
Corrected `Setting` to `Settings`
* Remove space
The docs gave the impression that saving an automation rule created in the automation editor would be sufficient for the rule to come into effect. You still need to reload the rules, which is why I've added this to the docs.
* Adding examples for notifications, disarming
* Remove old reference to options.xml
Options.xml isn't needed for network key anymore, it should be set in configuration.yaml. Linked that section back to the main Z-Wave page that explains it.
* Add blank lines
When I read this line, I was thinking that ALL THREE were required, otherwise it would fail. I believe the sentiment is that in order to utilize any of the three, they must fall under homeassistant: in order for them to work. Correct?
