mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-15 13:26:54 +00:00
Update on z-wave docs because of upcoming change (#9095)
* Update z-wave section
* ✏️ Tweaks
This commit is contained in:
parent
a1aef58f95
commit
b15c6a065f
@ -39,26 +39,15 @@ The `zwave` component exposes multiple services to help maintain the network. Al
|
|||||||
| test_node | Tells the controller to send no-op command(s) to a specific node. Requires `node_id` field. You can specify amount of test_messages to send by specifying it with `messages` field. In theory, this could bring back nodes marked as "presumed dead"
|
| test_node | Tells the controller to send no-op command(s) to a specific node. Requires `node_id` field. You can specify amount of test_messages to send by specifying it with `messages` field. In theory, this could bring back nodes marked as "presumed dead"
|
||||||
| update_config | Attempt to update OZW configuration files from git to support newer devices. After you run this, wait a few minutes then stop Home Assistant. You can now back up your `zwcfg_*.xml` file, then delete the relevant entries from your `zwcfg_*.xml` (between and including `<Node id="?">` and `</Node>`), and finally start Home Assistant. |
|
| update_config | Attempt to update OZW configuration files from git to support newer devices. After you run this, wait a few minutes then stop Home Assistant. You can now back up your `zwcfg_*.xml` file, then delete the relevant entries from your `zwcfg_*.xml` (between and including `<Node id="?">` and `</Node>`), and finally start Home Assistant. |
|
||||||
|
|
||||||
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 `autoheal` to false. If you're having issues with your Z-Wave network, try disabling this automation.
|
The `soft_reset` and `heal_network` commands can be used to help keep a Z-Wave network running reliably. This is a configuration option for the `zwave` component. The option defaults to `false` but can be enabled by setting `autoheal` to true. This, however, is bad practice since it introduces overhead that can be avoided since you only need to do a `heal_network` whenever one of the following actions are done:
|
||||||
|
|
||||||
|
- Adding/Removing a new node
|
||||||
|
- Moving a node around
|
||||||
|
- Moving the Controller
|
||||||
|
- Removing a Dead Node
|
||||||
|
|
||||||
<p class='note'>
|
<p class='note'>
|
||||||
Using the `soft_reset` function with some Z-Wave controllers can cause the Z-Wave network to hang.
|
Using the `soft_reset` function with some Z-Wave controllers can cause the Z-Wave network to hang.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
```yaml
|
To trigger a `heal_network`, one can always use *Settings -> Z-Wave Network Management -> Heal Network* from the GUI whenever one of the above actions took place.
|
||||||
# Example configuration.yaml automation entry
|
|
||||||
automation:
|
|
||||||
- alias: test at 2:30am
|
|
||||||
trigger:
|
|
||||||
platform: time
|
|
||||||
at: '2:30:00'
|
|
||||||
action:
|
|
||||||
service: zwave.test_network
|
|
||||||
|
|
||||||
- alias: heal at 2:32am
|
|
||||||
trigger:
|
|
||||||
platform: time
|
|
||||||
at: '2:32:00'
|
|
||||||
action:
|
|
||||||
service: zwave.heal_network
|
|
||||||
```
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user