--- title: "Z-Wave Device Specific Settings" description: "Notes for specific Z-Wave devices." ---
This Z-Wave integration is deprecated and replaced with a [new implementation based on Z-Wave JS](/integrations/zwave_js); it's currently in beta, and you can [try it now](/integrations/zwave_js/).
## Device Categories ### 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. 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. Home Assistant stores logs from Z-Wave in `OZW_log.txt` in the Home Assistant 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 Home Assistant has been stopped. 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 ``` Turn on "Disco lights": ```bash echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00 ``` 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: ```bash echo -e -n "...turn on/off string from examples above..." | cu -l /dev/zstick -s 115200 ``` ### 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`: For both processes below you will need to insert your SD card into your PC and open the `/boot/config.txt` file with your favorite text editor. #### Raspberry Pi 4 procedure Add the following paramaters to the bottom of the `/boot/config.txt` file. ```text dtoverlay=disable-bt enable_uart=1 ``` Reboot your Pi 4 without the Razberry Z-Wave hat first. Then shutdown, add the hat back, and boot again. #### Raspberry Pi 3 procedure Add the following parameters to the bottom of the `/boot/config.txt` file. ```text dtoverlay=disable-bt ``` Reboot your Pi 3. For Home Assistant OS this should be everything you need to do. You should now be able to use Razberry Z-Wave from `/dev/ttyAMA0`. For other operating systems such as Raspberry Pi OS you will also have to run the following command: ```bash sudo systemctl disable hciuart ``` You should also check the README for details on the overlays. You might find it in `/boot/overlays/README` on your SD-card. If it is not there you can find [the official version here](https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README).
It is possible to keep a limited Bluetooth functionality while using Razberry Z-Wave. Check `boot/overlays/README` on `miniuart-bt`.
`disable-bt` was previously known as `pi3-disable-bt`. If your OS is old, you might need to use this instead.
If you've installed the Z-Way software, you'll need to ensure you disable it before you install Home Assistant or you won't be able to access the board. Do this with `sudo /etc/init.d/z-way-server stop; sudo update-rc.d z-way-server disable`.
### Aeon Minimote Here's a handy configuration for the Aeon Labs Minimote that defines all possible button presses. Put it into `automation.yaml`. ```yaml - id: mini_1_pressed alias: "Minimote Button 1 Pressed" trigger: - platform: event event_type: zwave.scene_activated event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 1 - id: mini_1_held alias: "Minimote Button 1 Held" trigger: - platform: event event_type: zwave.scene_activated event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 2 - id: mini_2_pressed alias: "Minimote Button 2 Pressed" trigger: - platform: event event_type: zwave.scene_activated event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 3 - id: mini_2_held alias: "Minimote Button 2 Held" trigger: - platform: event event_type: zwave.scene_activated event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 4 - id: mini_3_pressed alias: "Minimote Button 3 Pressed" trigger: - platform: event event_type: zwave.scene_activated event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 5 - id: mini_3_held alias: "Minimote Button 3 Held" trigger: - platform: event event_type: zwave.scene_activated event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 6 - id: mini_4_pressed alias: "Minimote Button 4 Pressed" trigger: - platform: event event_type: zwave.scene_activated event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 7 - id: mini_4_held alias: "Minimote Button 4 Held" trigger: - platform: event event_type: zwave.scene_activated event_data: entity_id: zwave.aeon_labs_minimote_1 scene_id: 8 ``` ### 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. ### Inovelli Light/Fan Combo (LZW36) Follow the [instructions](https://support.inovelli.com/portal/kb/articles/installation-setup-lzw36-fan-light-red-series-gen-2-home-assistant-hass-io) provided by Inovelli. You will need to uncomment command class 38 in the imported configuration file. ```xml ``` ## Central Scene configuration To provide Central Scene support you need to **stop your Z-Wave network** and modify your `zwcfg_*.xml` file according to the following guides. Start your Z-Wave network again after editing `zwcfg_*.xml`. ### 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_*.xml` file with the following: ```xml ``` For Inovelli LZW30-SN and LZW31-SN switches with a third button for configuration, you'll need to add a third scene for that under the COMMAND_CLASS_CENTRAL_SCENE CommandClass: ```xml ``` Once this is complete, `zwave.scene_activated` events will fire according to which button press you perform. For information on what button press corresponds to what scene_id and scene_data in the event, see [Inovelli Knowledge Base > How To: Setting Up Scenes In Home Assistant](https://support.inovelli.com/portal/en/kb/articles/how-to-setting-up-scenes-in-home-assistant). ### Zooz Scene Capable On/Off and Dimmer Wall Switches (Zen21v3 & Zen22v2 - Firmware 3.0+, Zen26 & Zen27 - Firmware 2.0+, Zen30 Double Switch, Zen32 Scene Controller, Zen34 Remote Switch) Many Zooz switches that have been sold do not have the latest firmwares. Contact Zooz to obtain the over the air firmware update instructions and new user manual for the switches. Once the firmware is updated, the the new configuration parameters will have to be added to the `zwcfg` file. Replace the existing `COMMAND_CLASS_CONFIGURATION` with the one of the following options (depending on your model of switch): Zen21v3 (On/Off Switch): ```xml Normal mode: Upper paddle turns the light on, lower paddle turns the light off. Reverse mode: Upper paddle turns the light off, lower paddle turns the light on. Toggle mode: Either paddle toggles the light. LED Indication light function. Normal has the LED Indication on when the switch is off, off when the switch is on. Time, in minutes, for auto-off timer delay. Set the time (in minutes) after which you want the switch to automatically turn on once it has been turned off. Choose which physical and Z-Wave triggers should prompt the switch to send a status change report to associated devices. Status after power failure. Off: always turn light off. On: always turn light on. Restore: remember the latest state and restore that state. Enable or Disable scene control functionality for quick double tap triggers (Available for select hubs only). Enable or disable local on/off control. If enabled, you’ll only be able to control the connected light via Z-Wave. Scenes and other functionality will still be available through paddles. Choose the type of 3-way switch you want to use with this dimmer in a 3-way set-up. Changing this setting can allow you to control brightness and dim the light from both 3-way locations. Use a regular momentary switch (like the Zooz ZAC99 accessory switch) if value is set to 2. Set reporting behavior for disabled physical control. ``` Zen22v2 (Dimmer): ```xml Normal mode: Upper paddle turns the light on, lower paddle turns the light off. Reverse mode: Upper paddle turns the light off, lower paddle turns the light on. Toggle mode: Either paddle toggles the light. LED Indication light function. Normal has the LED Indication on when the switch is off, off when the switch is on. Time, in minutes, for auto-off timer delay. Set the time (in minutes) after which you want the switch to automatically turn on once it has been turned off. Choose which physical and Z-Wave triggers should prompt the switch to send a status change report to associated devices. Status after power failure. Off: always turn light off. On: always turn light on. Restore: remember the latest state and restore that state. Adjust the physical ramp rate for your dimmer (fade-in / fade-out effect for on / off operation). Values correspond to the number of seconds it take for the dimmer to reach full brightness or turn off when operated manually. This setting is for physical taps only, see parameter 17 to adjust Z-Wave ramp rate. Values: 1 – 99 (seconds). 0 – instant on/off. Default: 1 Set the minimum brightness level (in %) for your dimmer. You won’t be able to dim the light below the set value. Default: 1 Set the maximum brightness level (in %) for your dimmer. You won’t be able to add brightness to the light beyond the set value. Note: if Parameter 12 is set to value 0, Parameter 11 is automatically disabled. Default: 99 Double Tap action. When set to Full, turns light on to 100%. If set to Maximum Level, turns light on to % set in Parameter 11. Enable or Disable scene control functionality for quick double tap triggers. Enables/Disables the double-tap fucntion and assign brightness to single tap. Last level: single tap returns to last brightness level. Full/Max level: single tap returns to full/max level Enable or disable local on/off control. If enabled, you’ll only be able to control the connected light via Z-Wave. Scenes and other functionality will still be available through paddles. Set the time it takes to get from 0% to 100% brightness when pressing and holding the paddle (physical dimming). The number entered as value corresponds to the number of seconds. Default: 4 Choose if you want to set the Z-Wave ramp rate independently of the physical ramp rate (using an appropriate command in your hub) or if you want them to match. Set the custom brightness level (instead of the last set brightness level) you want the dimmer to come on to when you single tap the upper paddle. Default: 0 - last brightness level Choose the type of 3-way switch you want to use with this dimmer in a 3-way set-up. Changing this setting can allow you to control brightness and dim the light from both 3-way locations. Use a regular momentary switch (like the Zooz ZAC99 accessory switch) if value is set to 2. Choose how you'd like the dimmer to report when paddles are tapped and held and physical / Z-Wave control is enabled or disabled. Set reporting behavior for disabled physical control. Set the brightness level the dimmer will turn on to when off and when lower paddle is held DOWN for a second. Default: 20 ``` Zen26 (On/Off Switch): ```xml Normal mode: Upper paddle turns the light on, lower paddle turns the light off. Reverse mode: Upper paddle turns the light off, lower paddle turns the light on. Toggle mode: Either paddle toggles the light. LED Indication light function. Normal has the LED Indication on when the switch is off, off when the switch is on. Time, in minutes, for auto-off timer delay. Set the time (in minutes) after which you want the switch to automatically turn on once it has been turned off. Choose which physical and Z-Wave triggers should prompt the switch to send a status change report to associated devices. Status after power failure. Off: always turn light off. On: always turn light on. Restore: remember the latest state and restore that state. Enable or Disable scene control functionality for quick double tap triggers (Available for select hubs only). Enable or disable local on/off control. If enabled, you’ll only be able to control the connected light via Z-Wave. Scenes and other functionality will still be available through paddles. Set reporting behavior for disabled physical control. ``` Zen27 (Dimmer): ```xml Normal mode: Upper paddle turns the light on, lower paddle turns the light off. Reverse mode: Upper paddle turns the light off, lower paddle turns the light on. Toggle mode: Either paddle toggles the light. LED Indication light function. Normal has the LED Indication on when the switch is off, off when the switch is on. Time, in minutes, for auto-off timer delay. Set the time (in minutes) after which you want the switch to automatically turn on once it has been turned off. Choose which physical and Z-Wave triggers should prompt the switch to send a status change report to associated devices. Status after power failure. Off: always turn light off. On: always turn light on. Restore: remember the latest state and restore that state. Adjust the physical ramp rate for your dimmer (fade-in / fade-out effect for on / off operation). Values correspond to the number of seconds it take for the dimmer to reach full brightness or turn off when operated manually. This setting is for physical taps only, see parameter 17 to adjust Z-Wave ramp rate. Values: 1 – 99 (seconds). 0 – instant on/off. Default: 1 Set the minimum brightness level (in %) for your dimmer. You won't be able to dim the light below the set value. Set the maximum brightness level (in %) for your dimmer. You won't be able to add brightness to the light beyond the set value. Note: if Parameter 12 is set to value "Full", Parameter 11 is automatically disabled. Double Tap action. When set to Full, turns light on to 100%. If set to Maximum Level, turns light on to % set in Parameter 11. Enable or Disable scene control functionality for quick double tap triggers. Enables/Disables the double-tap function and assign brightness to single tap. Last level: single tap returns to last brightness level. Full/Max level: single tap returns to full/max level Enable or disable local on/off control. If enabled, you’ll only be able to control the connected light via Z-Wave. Scenes and other functionality will still be available through paddles. Set the time it takes to get from 0% to 100% brightness when pressing and holding the paddle (physical dimming). The number entered as value corresponds to the number of seconds. Default: 4 Choose if you want to set the Z-Wave ramp rate independently of the physical ramp rate (using an appropriate command in your hub) or if you want them to match. Set the custom brightness level (instead of the last set brightness level) you want the dimmer to come on to when you single tap the upper paddle. Default: 0 - last brightness level Choose how you'd like the dimmer to report when paddles are tapped and held and physical / Z-Wave control is enabled or disabled. Set reporting behavior for disabled physical control. Set the brightness level the dimmer will turn on to when off and when lower paddle is held DOWN for a second. Default: 20 ``` Zen30 (Double Switch): ```xml LED Indicator Mode for Dimmer. Normal has the dimmer (top) LED indication on when the switch is off, off when the switch is on. Default: Normal LED Indicator Mode for Relay. Normal has the relay (bottom) LED indication on when the switch is off, off when the switch is on. Default: Normal LED Indicater color for Dimmer. White, Blue, Green or Red. Default: White LED Indicater color for Relay. White, Blue, Green or Red. Default: White LED Indicater Brightness for Dimmer. Bright (100%), Medium (60%) or Low (30%). Default: Medium LED Indicater Brightness for Relay. Bright (100%), Medium (60%) or Low (30%). Default: Medium LED Indicator Mode for Scene Control. Enable/Disable LED indicators next to the dimmer lighting up when a scene is selected. Default: disabled Auto Turn-Off Timer for Dimmer. Sets the time (in minutes) after which you want the dimmer to automatically turn off once it has been turned on. Range: 1-65535. Default: 0 (disabled) Auto Turn-On Timer for Dimmer. Sets the time (in minutes) after which you want the dimmer to automatically turn on once it has been turned off. Range: 1-65535. Default: 0 (disabled) Auto Turn-Off Timer for Relay. Sets the time (in minutes) after which you want the relay to automatically turn off once it has been turned on. Range: 1-65535. Default: 0 (disabled) Auto Turn-On Timer for Relay. Sets the time (in minutes) after which you want the relay to automatically turn on once it has been turned off. Range: 1-65535. Default: 0 (disabled) On Off Status After Power Failure. Default: Restore both to prior state Ramp Rate Control for Dimmer. Adjust the ramp rate for your dimmer (fade-in / fade-out effect for on / off operation). Values correspond to the number of seconds it take for the dimmer to reach full brightness or turn off when operated manually. Note that 0 is instant. Default: 1 Minimum Brightness. Set the minimum brightness level (in %) for your dimmer. You won't be able to dim the light below the set value. Default: 1 Maximum Brightness. Set the maximum brightness level (in %) for your dimmer. You won't be able to add brightness to the light beyond the set value. Default: 99 Double Tap Function for Dimmer. When set to full, turns light on to 100%. If set to maximum level, turns light on to % set in Parameter 15. Default: full Enable/Disable Double-tap for Dimmer. Enables/Disables the double-tap fucntion and assign brightness to single tap. enabled: single tap turns on to maximum brightness level. disabled (last level): single tap returns to last brightness level. disabled (full/max level): single tap returns to full brightmess. Default: enabled Enable/Disable Load Control for Dimmer (Smart Bulb Setting). Enable or disable direct manual and Z-Wave control of the connected light (works great for smart bulb control). If disabled, the dimmer will no longer control the connected bulb directly but will still send on/off and brightness reports to the hub so you cn use them to create automations for your smart bulbs or other switches. Scenes and other functionality will still be available through the paddles. Default: manual disabled Enable/Disable Load Control for Relay (Smart Bulb Setting). Enable or disable direct manual and Z-Wave control of the connected light (works great for smart bulb control). If disabled, the relay will no longer control the connected bulb directly but will still send on/off and brightness reports to the hub so you cn use them to create automations for your smart bulbs or other switches. Scenes and other functionality will still be available through the paddles. Default: manual disabled Choose how many seconds it takes for the dimmer to go from 0% to 100% brightness when pressing and holding the paddle. Default: 4. Default Brightness Level On for Dimmer. Set custom brightness level (in %) for the dimmer to come on to at single tap. Choose 0 for last brightness level. Default: 0. Sets behavior of the dimmer when physical control is disabled Sets behavior of the relay when physical control is disabled Set the brightness level the dimmer will turn on to when off and when lower paddle is held DOWN for a second. Default: 20 Normal mode: Upper paddle turns the light on, lower paddle turns the light off. Reverse mode: Upper paddle turns the light off, lower paddle turns the light on. Toggle mode: Either paddle toggles the light. ``` Zen32 Scene Controller: ```xml Set the time (in minutes) after which you want the switch to automatically turn off once it has been turned on. Set the time (in minutes) after which you want the switch to automatically turn on once it has been turned off. Choose the type of 3-way switch you want to use with this switch in a 3-way set-up. ``` Zen34 Remote Switch: ```xml Choose the LED indicator mode for your Remote Switch Choose the LED indicator color for the upper paddle remote controle triggers Choose the LED indicator color for the lower paddle remote control triggers ``` For Zooz 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 ``` For the Zooz Zen30 Double Switch, you'll need to add the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following: ```xml ``` For the Zooz Zen32 Scene Controller, you'll need to add the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following: ```xml ``` Go to the Z-Wave Network Management section in the Home Assistant 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 Held off|1|7800 Held on|2|7800 Released off|1|7740 Released on|2|7740 The Zooz ZEN34 Remote Switch has shown inverted `scene_id` values compared to other Zooz switches as well as different `scene_data` values depending on production run: Recent production runs have appeared with: **Action**|**scene\_id**|**scene\_data** :-----:|:-----:|:-----: 1x tap on|1|7680 1x tap off|2|7680 2x tap on|1|7860 2x tap off|2|7860 3x tap on|1|7920 3x tap off|2|7920 4x tap on|1|7980 4x tap off|2|7980 5x tap on|1|8040 5x tap off|2|8040 Held on|1|7800 Held off|2|7800 Released on|1|7740 Released off|2|7740 Early production runs have appeared with: **Action**|**scene\_id**|**scene\_data** :-----:|:-----:|:-----: 1x tap on|1|0 1x tap off|2|0 2x tap on|1|3 2x tap off|2|3 3x tap on|1|4 3x tap off|2|4 4x tap on|1|5 4x tap off|2|5 5x tap on|1|6 5x tap off|2|6 Held on|1|2 Held off|2|2 Released on|1|1 Released off|2|1 ### 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 HomeSeer devices (as a reference for other similar devices): **Action**|**scene\_id**|**scene\_data** :-----:|:-----:|:-----: Single tap on|1|0 Single tap off|2|0 Double tap on|1|3 Double tap off|2|3 Triple tap on|1|4 Triple tap off|2|4 Tap and hold on|1|2 Tap and hold off|2|2 Some installations will see those details: **Top button ID: 1, Bottom ID: 2** **Action**|**scene\_data** :-----:|:-----: Single Press|7800 Hold Button|7740 2x Tap|7860 3x Tap|7920 4x Tap|7980 5x Tap|8040 ### Fibaro Button FGPB-101-6 v3.2 For the Button, 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 Keyfob (as a reference for other similar devices): **Action**|**scene\_id**|**scene\_data** :-----:|:-----:|:-----: Button one (Square) single tap|1|7680 Button one (Square) hold|1|7800 Button one (Square) release|1|7740 Button two (Circle) single tap|2|7680 Button two (Circle) hold|2|7800 Button two (Circle) release|2|7740 Button three (X) single tap|3|7680 Button three (X) hold|3|7800 Button three (X) release|3|7740 Button four (Triangle) single tap|4|7680 Button four (Triangle) hold|4|7800 Button four (Triangle) release|4|7740 Button five (Minus) single tap|5|7680 Button five (Minus) hold|5|7800 Button five (Minus) release|5|7740 Button six (Plus) single tap|6|7680 Button six (Plus) hold|6|7800 Button six (Plus) release|6|7740 Press circle and plus simultaneously to wake up the device. ### Aeotec NanoMote Quad Once you've added the NanoMote to your Z-Wave network, you'll need to update your `zwcfg_*.xml` file with the below XML data. Stop Home Assistant and open your `zwcfg_*.xml` file (located in your configuration folder). Find the NanoMote 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 Home Assistant. ```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: ```yaml "event_type": "zwave.scene_activated", "data": { "entity_id": "zwave.nanomote", "scene_id": 2, "scene_data": 7680 } ``` ### 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 Wallmote (as a reference for other similar devices): **Action**|**scene\_id**|**scene\_data** :-----:|:-----:|:-----: Button one single tap|1|0 Button one hold|1|2 Button one release|1|1 Button two single tap|2|0 Button two hold|2|2 Button two release|2|1 Button three single tap|3|0 Button three hold|3|2 Button three release|3|1 Button four single tap|4|0 Button four hold|4|2 Button four release|4|1 ### WallC-S Switch Use the same configuration as for the Aeotec Wallmote. ### HANK One-key Scene Controller HKZN-SCN01/HKZW-SCN01 For the HANK One-key Scene Controller, 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 ``` Below is a table of the action/scenes for the Buttons and associated Pictogram: **Action**|**Pictogram**|**scene\_id**|**scene\_data** :-----:|:-----:|:-----:|:-----: Button one tap|Moon and Star|1|0 Button one hold|Moon and Star|1|2 Button one release|Moon and Star|1|1 Button two tap|People|2|0 Button two hold|People|2|2 Button two release|People|2|1 Button three tap|Circle|3|0 Button three hold|Circle|3|2 Button three release|Circle|3|1 Button four tap|Circle with Line|4|0 Button four hold|Circle with Line|4|2 Button four release|Circle with Line|4|1 ### Remotec ZRC-90 Scene Master To get the ZRC-90 Scene Master working in Home Assistant, you must first edit the `COMMAND_CLASS_CENTRAL_SCENE` in your `zwcfg` file. 1. Go the Z-Wave control panel in Home Assistant and make a note of the node number your ZRC-90 has been assigned. 2. *Stop* Home Assistant. 3. Make a backup of your `zwfcg` file, just in case. 4. In the `zwcfg` file, find the `Node id` that corresponds to the number you noted in the first step. 5. Within the `Node id` you identified, highlight everything between `` (inclusive) and paste in the following: ```xml ``` 6. Save the changes you made the `zwcfg` file and start Home Assistant back up. Button presses will trigger `zwave.scene_activated` with the following: - `node_id`: the node of your Scene Master (useful if you have more than one) - `scene_id`: the number button you press (1-8) - `scene_data`: the type of press registered (see below) The Scene Master has eight buttons which can send four actions. The type of action is reflected in the `scene_data` parameter: **Action**|**scene\_data** :-----:|:-----: Single press | 0 Long press (2s) | 1 Release from hold | 2 Double-press | 3 Let's see how this works in an automation for a Scene Master that's assigned as Node 7: ```yaml - id: "1234567890" alias: "Double-press Button 2 to toggle all lights" trigger: - platform: event event_type: zwave.scene_activated event_data: node_id: 7 scene_id: 2 scene_data: 3 condition: [] action: - data: service: light.toggle target: entity_id: group.all_lights ``` ### 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 ``` Below is a table of the action/scenes for the Buttons: **Action**|**scene\_id** :-----:|:-----: Button one tap|1 Button two tap|2 Button three tap|3 Button four tap|4 Button five tap|5 When a button turns off, the controller sends `basic_set` in a generic `node_event` and does not specify which button was pressed. The status of the buttons is encoded into the `indicator` value, so in order to determine the status of each button, you need to refresh the indicator value. You can also control the LEDs for each button by setting the indicator value. For responsiveness, automations should be triggered with `zwave.scene_activated` events rather than the switch status. Here is an example configuration needed for the scene controller: {% raw %} ```yaml automation: - alias: "Sync the indicator value on button events" trigger: - platform: event event_type: zwave.scene_activated event_data: entity_id: zwave.scene_contrl - platform: event event_type: zwave.node_event event_data: entity_id: zwave.scene_contrl action: - service: zwave.refresh_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" switch: - platform: template switches: button_1_led: value_template: "{{ states('sensor.scene_contrl_indicator')|int|bitwise_and(1) > 0 }}" turn_on: service: zwave.set_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" value: "{{ states('sensor.scene_contrl_indicator')|int + 1 }}" turn_off: service: zwave.set_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" value: "{{ states('sensor.scene_contrl_indicator')|int - 1 }}" button_2_led: value_template: "{{ states('sensor.scene_contrl_indicator')|int|bitwise_and(2) > 0 }}" turn_on: service: zwave.set_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" value: "{{ states('sensor.scene_contrl_indicator')|int + 2 }}" turn_off: service: zwave.set_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" value: "{{ states('sensor.scene_contrl_indicator')|int - 2 }}" button_3_led: value_template: "{{ states('sensor.scene_contrl_indicator')|int|bitwise_and(4) > 0 }}" turn_on: service: zwave.set_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" value: "{{ states('sensor.scene_contrl_indicator')|int + 4 }}" turn_off: service: zwave.set_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" value: "{{ states('sensor.scene_contrl_indicator')|int - 4 }}" button_4_led: value_template: "{{ states('sensor.scene_contrl_indicator')|int|bitwise_and(8) > 0 }}" turn_on: service: zwave.set_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" value: "{{ states('sensor.scene_contrl_indicator')|int + 8 }}" turn_off: service: zwave.set_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" value: "{{ states('sensor.scene_contrl_indicator')|int - 8 }}" button_5_led: value_template: "{{ states('sensor.scene_contrl_indicator')|int|bitwise_and(16) > 0 }}" turn_on: service: zwave.set_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" value: "{{ states('sensor.scene_contrl_indicator')|int + 16 }}" turn_off: service: zwave.set_node_value data: node_id: 3 value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}" value: "{{ states('sensor.scene_contrl_indicator')|int - 16 }}" ``` ### HeatIt/ThermoFloor Z-Push Button 2/8 Wall Switch To get the Z-Push Button 2 or the Z-Push Button 8 working in Home Assistant, you must first edit the `COMMAND_CLASS_CENTRAL_SCENE` in your `zwcfg` file. 1. Go the Z-Wave control panel in Home Assistant and make a note of the node number your wall switch has been assigned. 2. *Stop* Home Assistant. 3. Make a backup of your `zwfcg` file, just in case. 4. In the `zwcfg` file, find the `Node id` that corresponds to the number you noted in the first step. 5. Within the `Node id` you identified, highlight everything between `` (inclusive) and paste in the following: - 5.1 For the Z-Push Button 2: ```xml ``` - 5.2 For the Z-Push Button 4: ```xml ``` - 5.3 For the Z-Push Button 8: ```xml ``` 6. Save the changes you made the `zwcfg` file and start Home Assistant 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) {% endraw %} ### 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 Home Assistant 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 Home Assistant. ```xml ``` Below is a table of the action/scenes for the ZDB5100 Matrix: **Action**|**scene\_id**|**scene\_data** :-----:|:-----:|:-----: Button one single tap|1|7680 Button one double tap|1|7860 Button one triple tap|1|7920 Button one hold|1|7800 Button one release|1|7740 Button two single tap|2|7680 Button two double tap|2|7860 Button two triple tap|2|7920 Button two hold|2|7800 Button two release|2|7740 Button three single tap|3|7680 Button three double tap|3|7860 Button three triple tap|3|7920 Button three hold|3|7800 Button three release|3|7740 Button four single tap|4|7680 Button four double tap|4|7860 Button four triple tap|4|7920 Button four hold|4|7800 Button four release|4|7740 Example Event: ```yaml - alias: "MatrixButton2" trigger: - event_type: zwave.scene_activated platform: event event_data: node_id: 2 scene_id: 2 scene_data: 7680 action: - service: switch.toggle target: entity_id: switch.office_fan ``` ### Zooz S2 MultiRelay (Zen16) Contact Zooz to obtain the over the air firmware update instructions and new user manual for the MultiRelay. Once the firmware is updated, the the new configuration parameters will have to be added to the `zwcfg` file. Replace the existing `COMMAND_CLASS_CONFIGURATION` with the one of the following options: ```xml On Off Status After Power Failure. Default: all relays restore to previous state Switch Type for Relay 1 (Sw1). Choose the wall switch type you want to connect to the Sw1 terminal. Default: toggle switch (state changes whenever the switch is toggled) Switch Type for Relay 2 (Sw2). Choose the wall switch type you want to connect to the Sw2 terminal. Default: toggle switch (state changes whenever the switch is toggled) Switch Type for Relay 3 (Sw3). Choose the wall switch type you want to connect to the Sw3 terminal. Default: toggle switch (state changes whenever the switch is toggled) LED Indicator Control. Choose if you want the LED indicator to turn on when any of the relays are on or if all of them are off, or if you want it to remain on or off at all times. Default: On when all relays are off Auto Turn-Off Timer for Relay 1. Sets the time (in minutes) after which you want relay 1 to automatically turn off once it has been turned on. Range: 1-65535. Default: 0 (disabled) Auto Turn-On Timer for Relay 1. Sets the time (in minutes) after which you want relay 1 to automatically turn on once it has been turned off. Range: 1-65535. Default: 0 (disabled) Auto Turn-Off Timer for Relay 2. Sets the time (in minutes) after which you want relay 2 to automatically turn off once it has been turned on. Range: 1-65535. Default: 0 (disabled) Auto Turn-On Timer for Relay 2. Sets the time (in minutes) after which you want relay 2 to automatically turn on once it has been turned off. Range: 1-65535. Default: 0 (disabled) Auto Turn-Off Timer for Relay 3. Sets the time (in minutes) after which you want relay 3 to automatically turn off once it has been turned on. Range: 1-65535. Default: 0 (disabled) Auto Turn-On Timer for Relay 3. Sets the time (in minutes) after which you want relay 3 to automatically turn on once it has been turned off. Range: 1-65535. Default: 0 (disabled) Enable/Disable Manual Control for SW1. Default: enabled Enable/Disable Manual Control for SW2. Default: enabled Enable/Disable Manual Control for SW3. Default: enabled Choose between second, minutes, and hours as the unit for Auto Turn-Off time for Relay 1. Default: minutes Choose between second, minutes, and hours as the unit for Auto Turn-On time for Relay 1. Default: minutes Choose between second, minutes, and hours as the unit for Auto Turn-Off time for Relay 2. Default: minutes Choose between second, minutes, and hours as the unit for Auto Turn-On time for Relay 2. Default: minutes Choose between second, minutes, and hours as the unit for Auto Turn-Off time for Relay 3. Default: minutes Choose between second, minutes, and hours as the unit for Auto Turn-On time for Relay 3. Default: minutes ``` ### Zooz S2 Outdoor Motion Sensor v2.0 (ZSE29) The configuration parameters will have to be added to the `zwcfg` file. Replace the existing `COMMAND_CLASS_CONFIGURATION` with the one of the following options: ```xml Set the value of basic set report sent to the light associated with the sensor in Group 2 (so the light turns on to the selected brightness level). 99 is the equivalent of full brightness in Z-Wave terms. default: 99 Enable or disable motion reports completely. If motion sensor is disabled, the device will not report motion at all to your hub. Adjust motion sensitivity where 10 is the most sensitive setting. default: 10 Set lux level trigger with 10 being the lowest reported value. The sensor will report motion to the hub and associated devices only if lux level is below the set value. 0 - set manually by lux knob; (default) 1 - ignore lux and always report motion; Set motion re-trigger time for the delay before the sensor reports no motion to the hub and associated devices after detecting the last motion activity. 0 - set manually by timer knob; (default) 5-720 (seconds) - set customer re-trigger time; Set lux reporting frequency to decide how often the snesor will measure and send brightness level data to the hub and associated devices. default: 30 (minutes) ``` ### Jasco 2 Button Remote (37792/ZW5307) Once you've added the remote to your Z-Wave network, you'll need to update your `zwcfg_*.xml` file with the below XML data. Stop Home Assistant and open your `zwcfg_*.xml` file (located in your configuration folder). Find the remote's 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 Home Assistant. ```xml ``` Below is a table of the action/scenes for the Jasco remote: **Action**|**scene\_id**|**scene\_data** :-----:|:-----:|:-----: Button one single tap|1|0 Button one double tap|1|3 Button one triple tap|1|4 Button two single tap|2|0 Button two double tap|2|3 Button two triple tap|2|4 Example Event: ```yaml - alias: "JascoButton1" trigger: - event_type: zwave.scene_activated platform: event event_data: node_id: 2 scene_id: 1 scene_data: 0 action: - service: switch.toggle target: entity_id: switch.office_fan ``` ### EATON On/Off & Dimmer (RF9501/RF9540-N/RF9640-N/RF9601-N) Once you've added the remote to your Z-Wave network, you'll need to update your `zwcfg_*.xml` file with the below XML data. Stop Home Assistant and open your `zwcfg_*.xml` file (located in your configuration folder). Find the remote's device section and then its corresponding `CommandClass` section with id="112". Insert the snippet below into the CommandClass section with the below XML data. Save the file and restart Home Assistant. ```xml Ensures that changes to the master node automatically notify accessory switches ```