Skip to content

Commit 98fee71

Browse files
janvanhelvoortfrenck
authored andcommitted
Add zwave.network_complete_some_dead event description (home-assistant#6366)
* Add zwave.network_complete_some_dead event description * typo * ✏️ Minor spelling fix
1 parent 70036a2 commit 98fee71

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

source/_docs/z-wave/events.markdown

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,17 @@ Home Assistant will trigger an event when the Z-Wave network is complete, meanin
2020
event_type: zwave.network_complete
2121
```
2222
23+
## {% linkable_title zwave.network_complete_some_dead %}
24+
25+
Home Assistant will trigger an event when the Z-Wave network is complete, but some nodes are marked dead, meaning all of the nodes on the network have been queried. This can take quite some time, depending on wakeup intervals on the battery-powered devices on the network.
26+
27+
```yaml
28+
- alias: Z-Wave network is complete some dead
29+
trigger:
30+
platform: event
31+
event_type: zwave.network_complete_some_dead
32+
```
33+
2334
## {% linkable_title zwave.network_ready %}
2435
2536
Home Assistant will trigger an event when the Z-Wave network is ready for use. Between `zwave.network_start` and `zwave.network_ready` Home Assistant will feel sluggish when trying to send commands to Z-Wave nodes. This is because the controller is requesting information from all of the nodes on the network. When this is triggered, all awake nodes have been queried and sleeping nodes will be queried when they awake.

0 commit comments

Comments
 (0)