jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Rewriting the Z-Wave documentation (#3467)

Browse source 
* Z-Wave documents refactoring

* Continuing to update documentation for Z-Wave

* Wakeup correction

Note that it only applies to devices that can be battery powered (for example, my Aeotec sensor is USB powered, but as it supports Wake the option is shown)

* Polling impact notes

Example of what the impact of polling can be

* Fix object_id to entity_id
This commit is contained in:
DubhAd 2017-10-14 18:16:28 +01:00 • committed by John Arild Berentsen
parent 051997c9b8
commit 018890a3b8
12 changed files with 812 additions and 301 deletions
Download patch file Download diff file Expand all files Collapse all files

58
source/_docs/z-wave/device-specific.markdown
View file

@ -1,7 +1,7 @@
---
layout: page
title: "Z-Wave Device Specific Settings"
description: "Extended instructions how to setup Z-Wave."
description: "Notes for specific Z-Wave devices."
date: 2016-03-24 08:49 -0700
sidebar: true
comments: false
@ -10,43 +10,50 @@ footer: true
redirect_from: /getting-started/z-wave-device-specific/
---
## {% linkable_title Motion or alarm sensors %}
## {% linkable_title Device Categories %}
### {% linkable_title Motion or alarm sensors %}
In order for Home Assistant to recognize the sensor properly, you will need to change its configuration from `Basic Set (default)` to `Binary Sensor report` or `Alarm report`.
These devices will either show as a binary sensor or a sensor called `Alarm xxxx` and will report a numeric value. Test to see what value is what. Sometimes this is noted in the device manual.
As of version 0.30 you can set the settings of a Z-Wave device through the dev_service page of Home Assistant with the service: `zwave/set_config_parameter`.
You can set the settings of the Z-Wave device through the Z-Wave control panel.
The following parameters can be entered:
- **node_id** (*Required*): The node_id of the device that you are going to set a parameter to.
- **parameter** (*Required*): The index number of the parameter to be set. Refer to device manual or zwcfg_[home_id].xml
- **value** (*Required*): The value to set the parameter to. Refer to device manual or zwcfg_[home_id].xml
- **size** (*Optional*): The size of the value. It is normally not needed to specify this parameter, but in some cases it's needed. Check OZW.log for details on this.
### {% linkable_title Locks and other secure devices %}
You should check OZW.log to see if your new setting has been set.
These devices require a network key to be set for the Z-Wave network before they are paired, using the **Add Node Secure** option.
Example entry in dev-service, setting binary reports for an Aeotec Multisensor 6:
Home Assistant stores logs from Z-Wave in `OZW.log` in the Home Assistant config directory, when you pair a secure device you should see communication from the node with lines starting with `info: NONCES` in `OZW.log` when the device is paired successfully with a secure connection.
### {% linkable_title Specific Devices %}
```yaml
# Example entry in dev-service
{
"node_id": 42,
"parameter": 5,
"value": 2
}
### {% linkable_title Aeotec Z-Stick %}
It's totally normal for your Z-Wave stick to cycle through its LEDs (Yellow, Blue and Red) while plugged into your system. If you don't like this behaviour it can be turned off.
Use the following example commands from a terminal session on your Pi where your Z-Wave stick is connected.
Turn off "Disco lights":
```bash
$ echo -e -n "\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51" > /dev/serial/by-id/usb-0658_0200-if00
```
## {% linkable_title Locks and other secure devices %}
Turn on "Disco lights":
These devices require a network key to be set for the Z-Wave network before they are paired. This key is set in OpenZWave's `options.xml` which is located in OpenZWave's directory. This should also be the same directory as `config_path:` in your `configuration.yaml`. If it's not, make sure you have the same values in all the files you are using.
The option is commented out by default in `options.xml` and is a default key. Make your own unique key. The key is in Hexadecimals.
It is best to pair these devices in OpenZWave Control Panel or another Z-Wave tool that can show you logs while pairing. Home Assistant stores logs from Z-Wave in `OZW.log` in the Home Assistant config directory.
You should see communication from the node with lines starting with `info: NONCES` in `OZW.log` when the device is paired successfully with a secure connection. If you use OpenZWave Control Panel to pair, test the device before you save the configuration.
Make sure you copy the newly saved `zwcfg_[home_id].xml`into your Home Assistant configuration directory.
```bash
$ echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00
```
### {% linkable_title Razberry Board %}
##### {% linkable_title Aeon Minimote %}
You need to disable the on-board Bluetooth since the board requires the use of the hardware UART (and there's only one on the Pi3). You do this by adding the following to the end of `/boot/config.txt`, then rebooting:
```
dtoverlay=pi3-disable-bt
```
### {% linkable_title Aeon Minimote %}
Here's a handy configuration for the Aeon Labs Minimote that defines all possible button presses. Put it into `automation.yaml`.
@ -124,8 +131,7 @@ Here's a handy configuration for the Aeon Labs Minimote that defines all possibl
scene_id: 8
```
##### {% linkable_title HomeSeer Switches %}
### {% linkable_title HomeSeer Switches %}
For the HomeSeer devices specifically, you may need to update the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following: