From 33fd2250fd589961394f514f6df7f31404bfe44e Mon Sep 17 00:00:00 2001 From: JudgeDredd Date: Fri, 30 Jun 2017 03:00:38 -0400 Subject: [PATCH] further document add_node_secure (#8229) added documentation to *attempt* explanation that add_node_secure will also function for adding unsecure nodes. --- homeassistant/components/zwave/services.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/homeassistant/components/zwave/services.yaml b/homeassistant/components/zwave/services.yaml index 1869dc491f0..ea8a6eaa036 100644 --- a/homeassistant/components/zwave/services.yaml +++ b/homeassistant/components/zwave/services.yaml @@ -19,7 +19,7 @@ add_node: description: Add a new (unsecure) node to the Z-Wave network. Refer to OZW.log for progress. add_node_secure: - description: Add a new node to the Z-Wave network with secure communications. Node must support this, and network key must be set. Note that unsecure devices can't directly talk to secure devices. Refer to OZW.log for progress. + description: Add a new node to the Z-Wave network with secure communications. Secure network key must be set, this process will fallback to add_node (unsecure) for unsupported devices. Note that unsecure devices can't directly talk to secure devices. Refer to OZW.log for progress. cancel_command: description: Cancel a running Z-Wave controller command. Use this to exit add_node, if you wasn't going to use it but activated it.