Attempting to make it more clear to users (particularly hass.io users) that the gactions cli can be run from any pc. Replaced "install" with "download" and a few other changes.
* Update freenas.markdown
The example provided for a chained command to mkdir /home and /home/.homeassistant was missing the second mkdir command. A copy and paste of this example would fail.
* Update freenas.markdown
Updated mkdir commands to use '-p' option.
The Samsung TV UEMU6199UXZG is recognized by Home Assistant but it needs to use port 8001 to enable the On/Off, Forward/Backward and the Volume control. The Play button is not working (it doesn't appear on the screen).
* Improved zwave security network key description
As someone adding a zwave device securely for the first time I found there were some gaps in the documentation.
* ✏️ Corrected small typo
* Update camera.markdown
Added an example for the new camera.snapshot service with a timestamped filename (seems to be a common request).
* ✏️ Updated PR with suggestions from arsaboo
* Add list of supported language variables.
* Replace supported languages list
Replaced list of supported language with a link to official list.
* ✏️ Improve link title
* I was a little confused...and still may be...
if I'm not mistaken, the comment I added should be true, but I was wondering if "devicename:" was actually something I was supposed to be using.
* ✏️ Corrected note styling
A few people have got lost by not adding the config (since it isn't explicit when you need it by). Added a new step 8 to point out that you have to have it in by now or you can't continue.
* Update guide for clarity
Recommends auto-starting by default, with manual starting as an option. Explicitly pull out the upgrade steps (since it also involves stopping HA first). Recommend install as a dedicated user.
* Minor changes
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.
Adding a note to make it clear that his only applies to Hass.io. We've had a number of questions on the forum and Discord that make it clear that people assume this applies to every install method.
