The current structure leads to confusion, which parts apply to Hass.io, or Hassbian, or ... As discussed in the architecture issue, I've moved all the platform specific parts to the end, even for those that require no actions.
I've also:
* moved the details for how to find the appropriate device path, and highlighting the likely default paths
* linked to a useful site that'll generate the content for the key, for those not using Linux
* stripped out the duplication of statements about the first run
* reordered the Hass.io section to put the GUI actions first, with a "you can also use the command line" rather than the other way around
* added details of how to pass the stick through on Docker
* put in a Community install section for other Linux, and Mac. Removed RancherOS
* expanded the wall of text note explaining the `ls` output so that you can actually follow it
We should consider recommending a network key for all z-wave installations. As users begin to add more and more devices they may not think about adding this later on as the network grows. Many users come to Discord or elsewhere and get confused as to why their Z-Wave device is not functioning correctly and come to find out they needed a network key and to add the device securely. As more and more Z-Wave Plus devices come out there are more security enabled devices as well. All locks and sensors are pretty much security devices.
* Pulled through notes of other path options
Added notes that for Hass.io there may be multiple path options depending on the device.
* Updated Hass.io note
* sync usb_path to other docs
The hassio zwave documents reference usb_path: /dev/ttyACM0, so this document should be in sync. After some discussion it appears that this could be variable, in which case there should be a good way to figure out the CORRECT answer rather than using a guess as example code without stating it as such. Possibly linking back to the linux "how to find" section?
* Removed manual set language per suggestion
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.
* Z-Wave documents refactoring
* Continuing to update documentation for Z-Wave
* Wakeup correction
Note that it only applies to devices that can be battery powered (for example, my Aeotec sensor is USB powered, but as it supports Wake the option is shown)
* Polling impact notes
Example of what the impact of polling can be
* Fix object_id to entity_id
