6 Commits

Author SHA1 Message Date
ArnoGit
4b14d45bab Adding remark pertaining to secure devices (#4075)
* 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
2017-11-26 10:02:56 +01:00
DubhAd
b4ba6bb2d3
Added note about Heal
Added Heal step to instructions, to ensure that all nodes learn about the new node
2017-11-12 21:55:23 +00:00
DubhAd
3686974b7d
Tweaks for readability 2017-11-08 19:26:47 +00:00
Ryan Sandridge
c13673dc8b Provide a script for macOS to generate the secure key (#3867)
Without including the LC_CTYPE=C environment variable on macOS, tr returns a "Illegal byte sequence" error.
2017-11-02 08:32:25 +01:00
DubhAd
e8a743760c
Clarifications
Fixed note classes, added emphasis to Add Node Secure, highlighted that the default Add Node is non-secure
2017-10-27 18:36:11 +01:00
DubhAd
018890a3b8 Rewriting the Z-Wave documentation (#3467)
* 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
2017-10-14 19:16:28 +02:00