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 WallC-S, layout tweak
Moved the central scene configs to their own block, added entry for WallC-S based on feedback in Discord
* 🚑 Fixing the build
* 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
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
