jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-13 12:26:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add zwave.network_complete_some_dead event description (#6366)

Browse Source 
* Add zwave.network_complete_some_dead event description

* typo

* ✏️ Minor spelling fix
This commit is contained in:
Jan van Helvoort 2018-09-30 13:45:00 +02:00 committed by Franck Nijhof
parent 70036a273d
commit 98fee71fc0
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
source/_docs/z-wave/events.markdown
View File

@ -20,6 +20,17 @@ Home Assistant will trigger an event when the Z-Wave network is complete, meanin
event_type: zwave.network_complete
```
## {% linkable_title zwave.network_complete_some_dead %}
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.
```yaml
- alias: Z-Wave network is complete some dead
trigger:
platform: event
event_type: zwave.network_complete_some_dead
```
## {% linkable_title zwave.network_ready %}
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.