Activate a scene via zwave association?

I have a Jasco Z-wave Motion Switch using the GE Z-Wave Plus Motion Switch Combo Driver. I would like to make it respond to double-taps, but this isn't available in the driver. The documentation (or some guy on Redit) claims that double-taps are sent on the Group3 association. I also have a nearby Zooz Zen32 Scene Controller. My thought is there might be some way to have the Group3 signal triggeran available scene activation on the Zooz.

My first attempt was to use a virtual switch, but those don't have a Z-Wave DNI, which is what I believe is required to enter in the Group3 association configuration. The Zen32 seems to have many DNIs, but I don't know how to pick a particular one. Nothing is clearly called something like "Button 3 double tap." for example. The Zen32 is node 0x29 and has the following command classes.

0x5E - Z-Wave Plus Info
0x9F - Security 2
0x55 - Transport Service
0x70 - Configuration
0x5B - Central Scene
0x25 - Binary Switch
0x8E - Multi Channel Association
0x59 - Association Group Info
0x85 - Association
0x86 - Version
0x6C - Supervision
0x73 - Powerlevel
0x72 - Manufacturer Specific
0x87 - Indicator
0x7A - Firmware Update Meta Data
0x5A - Device Reset Locally

My use case is to have the dbl-tap disable the motion automations in that room. I think I could do that with a scene, a variable, a virtual switch, or potentially other approaches. So if there are easier ideas, I'm open. Motion rules get reset to default when my Hubitat enters overnight mode.

I have seen this for some other zwave devices, possibly was another Jasco.

  • Set the group3 association to the hub itself (01).
  • Turn on debug logging, or change the driver to "Device"
  • Try the double tap and post a screenshot of any resulting logs.

Also post a screenshot of the device details from the info tab on the device page. Need to see the mfg/type/deviceId numbers.

Thanks for hopping on. Note log entries are in reverse order with oldest at the bottom. The oldest entry doesn't look promising.

dev:67 2025-04-29 05:30:30.129 PM debug ---CONFIGURATION REPORT V1--- workshopLights sent SwitchBinaryReport(value:0)
dev:67 2025-04-29 05:30:30.125 PM debug parse description: zw device: 2C, command: 2503, payload: 00 , isMulticast: false
dev:67 2025-04-29 05:30:30.120 PM info  workshopLights was turned off
dev:67 2025-04-29 05:30:30.117 PM debug ---BASIC SET V1--- workshopLights sent BasicSet(value:0)
dev:67 2025-04-29 05:30:30.042 PM debug parse description: zw device: 2C, command: 2001, payload: 00 , isMulticast: false
dev:67 2025-04-29 05:30:28.155 PM debug ---CONFIGURATION REPORT V1--- workshopLights sent SwitchBinaryReport(value:255)
dev:67 2025-04-29 05:30:28.152 PM debug parse description: zw device: 2C, command: 2503, payload: FF , isMulticast: false
dev:67 2025-04-29 05:30:28.142 PM info  workshopLights was turned on
dev:67 2025-04-29 05:30:28.139 PM debug ---BASIC SET V1--- workshopLights sent BasicSet(value:255)
dev:67 2025-04-29 05:30:28.136 PM debug parse description: zw device: 2C, command: 2001, payload: FF , isMulticast: false
dev:67 2025-04-29 05:30:26.576 PM debug ---CONFIGURATION REPORT V1--- workshopLights sent SwitchBinaryReport(value:0)
dev:67 2025-04-29 05:30:26.569 PM debug parse description: zw device: 2C, command: 2503, payload: 00 , isMulticast: false
dev:67 2025-04-29 05:30:26.562 PM info  workshopLights motion inactive
dev:67 2025-04-29 05:30:26.558 PM debug ---NOTIFICATION REPORT V4--- workshopLights sent NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 0, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:67 2025-04-29 05:30:26.553 PM debug parse description: zw device: 2C, command: 7105, payload: 00 00 00 FF 07 00 00 , isMulticast: false
dev:67 2025-04-29 05:30:26.548 PM info  workshopLights was turned off
dev:67 2025-04-29 05:30:26.545 PM debug ---BASIC SET V1--- workshopLights sent BasicSet(value:0)
dev:67 2025-04-29 05:30:26.534 PM debug parse description: zw device: 2C, command: 2001, payload: 00 , isMulticast: false
dev:67 2025-04-29 05:30:22.516 PM info  workshopLights was turned on
dev:67 2025-04-29 05:30:22.513 PM debug ---BASIC REPORT V1--- workshopLights sent BasicReport(value:255, targetValue:0, duration:0)
dev:67 2025-04-29 05:30:22.499 PM debug parse description: zw device: 2C, command: 2003, payload: FF , isMulticast: false
dev:67 2025-04-29 05:30:22.151 PM debug Turn device ON
dev:67 2025-04-29 05:30:22.027 PM info  workshopLights motion active
dev:67 2025-04-29 05:30:22.024 PM debug ---NOTIFICATION REPORT V4--- workshopLights sent NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 8, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:67 2025-04-29 05:30:22.019 PM debug parse description: zw device: 2C, command: 7105, payload: 00 00 00 FF 07 08 00 , isMulticast: false
dev:67 2025-04-29 05:29:48.610 PM warn  Association Group 3: Adding the hub as an association is not allowed (it would break double-tap).

Device Details

Device Id: 12338
Device Type: 18765
In Clusters: 0x5E,0x72,0x5A,0x73,0x27,0x25,0x2B,0x2C,0x70,0x86,0x71,0x60,0x8E,0x85,0x59,0x7A,0x56
Manufacturer: 99
MSR: 0063-494D-3032
Zw Node Info: D3 9C 00 04 10 01 5E 72 5A 73 27 25 2B 2C 70 86 71 60 8E 85 5C 59 7A 56 68 23

I think this is the driver from @JasonJoel ? Do you have a link to the driver post or code? It sounds like the double tap might already be supported.

It's been a couple years, so no memory of what I did, but this is the comment from the driver's code window. There isn't a dbl-tap command button available in the device's command tab, so I didn't think it was baked-in functionality. I noticed there are 2 recent updates to the driver, so I imported the new one and ran configure on the device. No change.

/*
 *  IMPORT URL: https://raw.githubusercontent.com/Botched1/Hubitat/master/Drivers/GE%20Z-Wave%20Plus%20Motion%20Switch%20Combo%20Driver/GE%20Z-Wave%20Plus%20Motion%20Switch%20Combo%20Driver.groovy
 *
 *  GE Z-Wave Plus Motion Switch Combo Driver
 *  Driver for GE Z-Wave Plus Motion Switch (26931) that can be all-in-one or expose the switch and motion sensor part of a GE Motion Switch device as separate child devices
 *
 *  1.0.0 (06/12/2021) - First version
 */

To my knowledge the motion switch and dimmer do not report anything on doubletap.

I would be happy to add it to the driver if someone discovers otherwise though.

This makes it sound like group 3 doesn't do that either, but I didn't run out and test it:
GE/Jasco in-Wall Motion dimmer/switch EXPLAINED - Other Devices & Integrations / Lighting & Load Control - Ezlo Community

As I added double tap to all my other jasco drivers (for hardware that supports it), I know I tested the motion switch/dimmer at one point to see if there was any way to get double tap from them, and didn't see any.

I just noticed there is another driver for this specific device ID 26931 by Matt Lebaugh. It seems to have a push command. Maybe I can do something with that. If not, my scene controller is about 20' away. Worst case is the shame and mockery I'll face from having to schlep halfway across my smart house to use a different light switch to do something. :blush:

@JasonJoel - The clue I found that a double tap might be possible is the second comment on this thread. Maybe it means something to you as a driver developer. Scenes (e.g., double tap) on the GE (Jasco) Enbrighten Motion Sensor Switch - Z-Wave - Home Assistant Community

Thanks @jtp10181 & Jason. I think this is as far as I'm going to go with this idea.

Worst case you could get a Zen34, zen37, or a single smart button and stick it to the wall nearby.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.