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-19 07:17:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Alphabetic sorting

Browse Source
This commit is contained in:
John Arild Berentsen 2016-08-07 18:29:12 +02:00 committed by GitHub
parent 04350e6291
commit 2132158ec6
1 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
source/getting-started/z-wave.markdown
View File

@ -92,24 +92,25 @@ Depending on what's plugged into your USB ports, the name found above may change
#### {% linkable_title Events %}
**zwave.node_event**
HomeAssistant will trigger a event when command_class_basic changes value on a node.
This can be virtually anything, so tests have to be made to determine what value equals what.
You can use this for automations.
Example:
**zwave.network_complete**
HomeAssistant will trigger a event when the zwave network is complete. Meaning all of the nodes on the network have been queried. This can take quite som time, depending on wakeup intervals on the battery powered devices on the network.
```yaml
- alias: Minimote Button Pressed
- alias: ZWave network is complete
trigger:
platform: event
event_type: zwave.node_event
event_data:
object_id: aeon_labs_minimote_1
basic_level: 255
event_type: zwave.network_complete
```
The *object_id* and *basic_level* of all triggered events can be seen in the console output.
**zwave.network_ready**
HomeAssistant will trigger a event when the zwave network is ready for use. Between `zwave.network_start` and `zwave.network_ready` HomeAssistant will feel sluggish when trying to send commands to zwave 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.
```yaml
- alias: ZWave network is ready
trigger:
platform: event
event_type: zwave.network_ready
```
**zwave.network_start**
HomeAssistant will trigger a event when the zwave network is set up to be started.
@ -131,25 +132,24 @@ HomeAssistant will trigger a event when the zwave network stopping.
event_type: zwave.network_start
```
**zwave.network_ready**
HomeAssistant will trigger a event when the zwave network is ready for use. Between `zwave.network_start` and `zwave.network_ready` HomeAssistant will feel sluggish when trying to send commands to zwave 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.
**zwave.node_event**
HomeAssistant will trigger a event when command_class_basic changes value on a node.
This can be virtually anything, so tests have to be made to determine what value equals what.
You can use this for automations.
Example:
```yaml
- alias: ZWave network is ready
- alias: Minimote Button Pressed
trigger:
platform: event
event_type: zwave.network_ready
event_type: zwave.node_event
event_data:
object_id: aeon_labs_minimote_1
basic_level: 255
```
**zwave.network_complete**
HomeAssistant will trigger a event when the zwave network is complete. Meaning all of the nodes on the network have been queried. This can take quite som time, depending on wakeup intervals on the battery powered devices on the network.
```yaml
- alias: ZWave network is complete
trigger:
platform: event
event_type: zwave.network_complete
```
The *object_id* and *basic_level* of all triggered events can be seen in the console output.
**zwave.scene_activated**
Some devices can also trigger scene activation events, which can be used in automation scripts (for example the press of a button on a wall switch):
@ -176,9 +176,9 @@ The Z-Wave component exposes four services to help maintain the network.
| ------- | ----------- |
| add_node | Put the zwave controller in inclusion mode. Allows one to add a new device to the zwave network.|
| add_node_secure | Put the zwave controller in secure inclusion mode. Allows one to add a new device with secure communications to the zwave network. |
| remove_node | Put the zwave controller in exclusion mode. Allows one to remove a device from the zwave network.|
| cancel_command | Cancels a running zwave 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. |
| heal_network | Tells the controller to "heal" the network. Bascially asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing. |
| remove_node | Put the zwave controller in exclusion mode. Allows one to remove a device from the zwave network.|
| 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.|
| 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".|