You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add documentation for print_config_parameter service to z-wave.
* Add documentation for 'debug' customization attribute.
* Sort services alphabetically.
Copy file name to clipboardExpand all lines: source/getting-started/z-wave.markdown
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -81,6 +81,7 @@ Configuration variables:
81
81
- **ignored** (*Optional*): Ignore this entitiy completely. It won't be shown in the Web Interface and no events are generated for it.
82
82
- **refresh_value** (*Optional*): Enable refreshing of the node value. Only light component uses this. Defaults to 2 second delay.
83
83
- **delay** (*Optional*): Specify the delay to wait for refresh of node value if you want other than 2 seconds.
84
+
- **debug** (*Optional*): Print verbose z-wave info to log. Defaults to False.
84
85
85
86
To find the path of your Z-Wave USB stick or module, run:
86
87
@@ -226,16 +227,17 @@ The `zwave` component exposes multiple services to help maintain the network.
226
227
| ------- | ----------- |
227
228
| add_node | Put the Z-Wave controller in inclusion mode. Allows one to add a new device to the Z-Wave network.|
228
229
| add_node_secure | Put the Z-Wave controller in secure inclusion mode. Allows one to add a new device with secure communications to the Z-Wave network. |
229
-
| change_association | Add or remove an association in the Z-Wave network
230
230
| cancel_command | Cancels a running Z-Wave command. If you have started a add_node or remove_node command, and decides you are not going to do it, then this must be used to stop the inclusion/exclusion command. |
231
+
| change_association | Add or remove an association in the Z-Wave network |
231
232
| heal_network | Tells the controller to "heal" the Z-Wave network. Basically asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing. |
233
+
| print_config_parameter | Prints Z-wave node's config parameter value to the log.
232
234
| remove_node | Put the Z-Wave controller in exclusion mode. Allows one to remove a device from the Z-Wave network.|
235
+
| rename_node | Sets a node's name. Requires an `entity_id` and `name` field. |
233
236
| set_config_parameter | Let's the user set a config parameter to a node.
234
237
| soft_reset | Tells the controller to do a "soft reset". This is not supposed to lose any data, but different controllers can behave differently to a "soft reset" command.|
235
238
| start_network | Starts the Z-Wave network.|
236
239
| stop_network | Stops the Z-Wave network.|
237
240
| test_network | Tells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked "presumed dead".|
238
-
| rename_node | Sets a node's name. Requires an `entity_id` and `name` field. |
239
241
240
242
The `soft_reset` and `heal_network` commands can be used as part of an automation script to help keep a Z-Wave network running reliably as shown in the example below. By default, Home Assistant will run a `heal_network` at midnight. This is a configuration option for the `zwave` component, the option defaults to `true` but can be disabled by setting `auto_heal` to false. Using the `soft_reset` function with some Z-Wave controllers can cause the Z-Wave network to hang. If you're having issues with your Z-Wave network try disabling this automation.
0 commit comments