From 8f20b9dd65577456cd26f785ed6889adabb3e359 Mon Sep 17 00:00:00 2001 From: andrey-git Date: Sun, 15 Jan 2017 12:36:40 +0200 Subject: [PATCH] Add print_config_parameter service to z-wave (#1698) * Add documentation for print_config_parameter service to z-wave. * Add documentation for 'debug' customization attribute. * Sort services alphabetically. --- source/getting-started/z-wave.markdown | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/source/getting-started/z-wave.markdown b/source/getting-started/z-wave.markdown index b7c2b7381b7..8e0e7ebc224 100644 --- a/source/getting-started/z-wave.markdown +++ b/source/getting-started/z-wave.markdown @@ -81,6 +81,7 @@ Configuration variables: - **ignored** (*Optional*): Ignore this entitiy completely. It won't be shown in the Web Interface and no events are generated for it. - **refresh_value** (*Optional*): Enable refreshing of the node value. Only light component uses this. Defaults to 2 second delay. - **delay** (*Optional*): Specify the delay to wait for refresh of node value if you want other than 2 seconds. +- **debug** (*Optional*): Print verbose z-wave info to log. Defaults to False. To find the path of your Z-Wave USB stick or module, run: @@ -226,16 +227,17 @@ The `zwave` component exposes multiple services to help maintain the network. | ------- | ----------- | | add_node | Put the Z-Wave controller in inclusion mode. Allows one to add a new device to the Z-Wave network.| | 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. | -| change_association | Add or remove an association in the Z-Wave network | 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. | +| change_association | Add or remove an association in the Z-Wave network | | 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. | +| print_config_parameter | Prints Z-wave node's config parameter value to the log. | remove_node | Put the Z-Wave controller in exclusion mode. Allows one to remove a device from the Z-Wave network.| +| rename_node | Sets a node's name. Requires an `entity_id` and `name` field. | | set_config_parameter | Let's the user set a config parameter to a node. | 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.| | start_network | Starts the Z-Wave network.| | stop_network | Stops the Z-Wave network.| | 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".| -| rename_node | Sets a node's name. Requires an `entity_id` and `name` field. | 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.