* Update device-specific.markdown
Expand Aeotec Z-Stick section to provide alternative "pipe to cu" syntax for enabling/disabling "disco lights" on systems where redirection to serial devices doesn't work because the baud rate on the serial device reverts to 9600 when haas isn't running.
* ✏️ Tweaks
Updates include an alternate way of turning off the aeotec z wave 'disco lights' that is known to work on the latest Hass.io and Pi configuration (using ttyACM0 instead of the the by serial id method).
Also provides additional guidance on how to properly insert the aeotec nanomote xml code into the zwcfg*.xml file.
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
* Simplification of the supported controllers
Stripped it down to the key fact - *static controllers* are all that'll work with OZW.
Noted that Z-Wave Plus controllers are recommended, to take advantage of all the features of Z-Wave Plus.
Noted that S2 and Smart Start aren't supported by OZW
* Controllers restored
Restored the list of confirmed sticks, but taken out the lists of OSs because we just took the list from the OZW pages, and it's clear that's outdated and incomplete
Tested the Zooz z-wave Plus S2 Stick ZST10 with Home-Assistant. Zwave worked, nodes included and communicating using a Raspberriy Pi3 with the latest Hass.io.
Added info about the alarm_type from the openzwave code. I believe there is some mixed info based on older V1 alarms vs new V2 alarms. V2 have fixed alarm_types so I've separated the two to make it clear which one a user should look at.
