Z-Wave Device Specific Settings
Device Categories
Motion or alarm sensors
In order for Open Peer Power 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.
You can set the settings of the Z-Wave device through the Z-Wave control panel.
Locks and other secure devices
These devices require a network key to be set for the Z-Wave network before they are paired, using the Add Node Secure option.
Open Peer Power stores logs from Z-Wave in OZW_log.txt
in the Open Peer Power configuration directory, when you pair a secure device you should see communication from the node with lines starting with info: NONCES
in OZW_log.txt
when the device is paired successfully with a secure connection.
Specific Devices
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 behavior it can be turned off.
Use the following example commands from a terminal session on your Pi where your Z-Wave stick is connected.
Note: You should only do this when Open Peer Power has been stopped.
Turn off “Disco lights”:
Turn on “Disco lights”:
If the above two commands give errors about not having that device, you should try replacing the /dev/serial/by-id/usb-0658_0200-if00
with /dev/ttyACM0
or /dev/ttyACM1
(depending on which tty your Aeotec stick is addressed to).
On some systems, such as macOS, you need to pipe the output of the echo
command, rather than redirecting to the serial device, to something like cu
(replacing /dev/zstick
acccordingly) to properly set the baud rate to 115200 bps:
Razberry Board
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 disable the Bluetooth modem service:
Once Bluetooth is off, enable the serial interface via the raspi-config
tool. After reboot run:
so that your serial interface looks like:
at this point simply add your user (openpeerpower) to the dialout group:
Aeon Minimote
Here’s a handy configuration for the Aeon Labs Minimote that defines all possible button presses. Put it into automation.yaml
.
Zooz Toggle Switches
Some models of the Zooz Toggle switches ship with an instruction manual with incorrect instruction for Z-Wave inclusion/exclusion. The instructions say that the switch should be quickly switched on-off-on for inclusion and off-on-off for exclusion. However, the correct method is on-on-on for inclusion and off-off-off for exclusion.
Central Scene configuration
To provide Central Scene support you need to shutdown Open Peer Power and modify your zwcfg_*.xml
file according to the following guides.
Inovelli Scene Capable On/Off and Dimmer Wall Switches
For Inovelli switches, you’ll need to update (or possibly add) the COMMAND_CLASS_CENTRAL_SCENE
for each node in your zwcfg
file with the following:
```xml %}
Zen27 (Dimmer): ```xml %}
Go to the Z-Wave Network Management section in the Open Peer Power Configuration, select the node which has just been updated and enable the scene support configuration parameter.
Once this is complete, you should see the following zwave.scene_activated
events:
Action | scene_id | scene_data |
---|---|---|
Single tap off | 1 | 7680 |
Single tap on | 2 | 7680 |
Double tap off | 1 | 7860 |
Double tap on | 2 | 7860 |
Triple tap off | 1 | 7920 |
Triple tap on | 2 | 7920 |
4x tap off | 1 | 7980 |
4x tap on | 2 | 7980 |
5x tap off | 1 | 8040 |
5x tap on | 2 | 8040 |
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:
```xml %}
Below is a table of the action/scenes for the Button (as a reference for other similar devices):
Action | scene_id | scene_data |
---|---|---|
Single tap on | 1 | 0 |
Double tap on | 1 | 3 |
Triple tap on | 1 | 4 |
Tap and hold wakes up the Button.
Fibaro Keyfob FGKF-601
For the Fibaro Keyfob, you may need to update the COMMAND_CLASS_CENTRAL_SCENE
for each node in your zwcfg
file with the following:
```xml %}
Below is a table of the action/scenes for the NanoMote Quad:
Action | scene_id | scene_data |
---|---|---|
Button one single tap | 1 | 7680 |
Button one hold | 1 | 7800 |
Button one release | 1 | 7740 |
Button two single tap | 2 | 7680 |
Button two hold | 2 | 7800 |
Button two release | 2 | 7740 |
Button three single tap | 3 | 7680 |
Button three hold | 3 | 7800 |
Button three release | 3 | 7740 |
Button four single tap | 4 | 7680 |
Button four hold | 4 | 7800 |
Button four release | 4 | 7740 |
Example Event:
Aeotec Wallmote
For the Aeotec Wallmote, you may need to update the COMMAND_CLASS_CENTRAL_SCENE
for each node in your zwcfg
file with the following:
```xml %}
Below is a table of the action/scenes for the Button (as a reference for other similar devices):
Action | scene_id | scene_data |
---|---|---|
Button single tap | 1 | 0 |
Button hold | 1 | 2 |
Button release | 1 | 1 |
HANK Four-key Scene Controller HKZN-SCN04
For the HANK Four-key Scene Controller, you may need to update the COMMAND_CLASS_CENTRAL_SCENE
for each node in your zwcfg
file with the following:
```xml %}
RFWDC Cooper 5-button Scene Control Keypad
For the RFWDC Cooper 5-button Scene Control Keypad, you may need to update the COMMAND_CLASS_CENTRAL_SCENE
for each node in your zwcfg
file with the following:
```xml %}
HeatIt/ThermoFloor Z-Push Button 2/8 Wall Switch
To get the Z-Push Button 2 or the Z-Push Button 8 working in Open Peer Power, you must first edit the COMMAND_CLASS_CENTRAL_SCENE
in your zwcfg
file.
- Go the Z-Wave control panel in Open Peer Power and make a note of the node number your wall switch has been assigned.
- Stop Open Peer Power.
- Make a backup of your
zwfcg
file, just in case. - In the
zwcfg
file, find theNode id
that corresponds to the number you noted in the first step. - Within the
Node id
you identified, highlight everything between<CommandClass id="91"
and</CommandClass>
(inclusive) and paste in the following:- 5.1 For the Z-Push Button 2:
```xml %}
- Save the changes you made the
zwcfg
file and start Open Peer Power back up.
Button presses will trigger zwave.scene_activated
with the following:
scene_id
: the number of the button you press from top left (1) to bottom right (8)
Logicgroup ZDB5100 Matrix
Once you’ve added the ZDB5100 to your Z-Wave network, you’ll need to update your zwcfg_*.xml
file with the below XML data. Stop Open Peer Power and open your zwcfg_*.xml
file (located in your configuration folder). Find the ZDB5100 device section and then its corresponding CommandClass
section with id=”91”. Replace the entire CommandClass section with the below XML data. Save the file and restart Open Peer Power.
```xml %}