Right now this page has no examples using the optional entity_id field. I think we should include it in the top example because otherwise the template sensor will react to all state changes rather than just the one or two the user will care about. May also be nice to show an example of a list for the template sensor, but we do include one on the Binary Sensor Template page so maybe that's sufficient?
* Updated layout due to problems in presentation.
- Removed URL link to hassio.local
- Changed presentation/line breaks for example service calls
* Fix link instead of removing it
Suggesting this link to Xiaomi's website as hopefully this page won't disappear on us, but if anyone has a better page to suggest, I'd happy with that too. Just want to limit the broken links and figured the vendor's page should be most static
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 documentation for the json_attributes configuration.
* Updated to reflect change to make json_attributes a list rather than a boolean.
* Fixed json_attributes examples to mark templates in documentation as {% raw %}.
Also corrected typos in entity_id entries for examples.
* Add additional example
* 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
* Added netdisco note for Synology users.
The suggested steps for netdisco issue don't work for Synology users. I've added a link to forum post with confirmed steps.
* Minor changes
I just added a direct command to run for an advanced install. The docs at https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio need some cleanup too, but that is clearly a separate change.
I'm not a huge fan of adding code here that might change, but otherwise the linked document is confusing out of context, and I suspect that set of commands isn't actually that likely to change.
