It's often been noted in the forums that Template Triggers are sometimes overload and that you want to use them sparingly. I haven't stress tested my system with this idea, but if the template triggers are tested every time any state changes, then that is the clarification that I've proposed in the documentation.
* Removes extraneous paragraph from docker documentation
It looks like this line was intended to go somewhere else, but got
erroneously bumped into the `Restart` section.
* Adds instructions to expose devices when deploying under docker
* Adds info about `docker-compose.yml` configuration to docker deployments
The docker command is pretty complicated and doesn't support automated
restarts. I think most users with want to use `docker-compose` (or
`docker swarm`) to deploy.
Added an example network_key line for configuration.yaml file.
I was having a hard time making it work because I was re-using an existing key from Razberry which was in a slightly different format. It wasn't until I "created" a new key to see the format.
* Added note about disabling Z-Way
A few people have had problems where they've installed the Razberry software, and it's then caused problems (locking the card, and/or over-writing the `zwcfg*.xml` file). Adding a note to ensure that if installed it is disabled.
* Minor changes
* Adding remark pertaining to secure devices
Per experience with Schlage locks, you need to 1st exclude them from the previous network/hub before you can enroll them in a new network. This seems to be true for secure zwave devices with anti-theft protection
* Clarification
Added clarification, that you may need to use the previous setup for the exclusion process,
* Minor changes
* Adds correction to Zooz switch manual
Adds correction to Zooz switch manual, which supplied incorrect instruction on how to include/exclude the switch from a Z-wave network.
* Fix name
Provide information to users so that they can determine the impact of the latest version on their system. Updates many times require changes to configuration, renaming of entities (z-wave for example), and deprecation of features,
I found that After=network.target was not robust enough for Auto-discovery to work correctly and find devices on the network. I changed this to After=network-online.target to wait until the network was completely "up" before starting.
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
