node-zwave-js: GE/Jasco 26932 does not support double tap events

Checklist:

  • I am not using HomeAssistant. Or: a developer has told me to come here.
  • I am not using ZWaveJS2MQTT. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem was not mentioned there.

Describe the bug

If I look at the zwavejs event stream, a single tap and double tap of my GE switch results in the same “Basic” output. If I compare that to a switch that works properly, a single tap produces a “Central Scene” event, while a double tap produces a “Basic” event.

Device information

Which device(s) is/are affected (make/model)? GE/Jasco 26932 / 26933 / ZW3008

What are the node IDs? Node ID 8

Did you change anything?

  • Yes: (please describe)
  • No

Did this use to work before?

  • Don’t know, this is a new device
  • No, it never worked anywhere
  • Yes, in: (specify application with versions)

How are you using node-zwave-js

  • zwavejs2mqtt (latest) docker image
  • zwavejs2mqtt (dev) docker image
  • zwavejs2mqtt Manual Docker build
    • node-zwave-js branch:
    • zwavejs2mqtt branch:
  • ioBroker.zwave2 adapter
  • HomeAssistant version XYZ
  • Pkg
  • Manual Docker build
    • node-zwave-js branch:
    • zwavejs2mqtt branch:
  • Manually built (as described in the docs)
  • Other:

To Reproduce

Steps to reproduce the behavior:

  1. Look at event stream in Home Assistant
  2. Tap the GE switch once and look at event stream. Tap the GE twice and look at event stream.
  3. Look at event stream and see that single and double taps produce the same “Basic” output.
  4. In the attached file switch_event.txt, I tried double tapping and single tapping, but as you can see, it’s all either “Basic” 0 or “Basic” 255.

Additional context

App Version 2.1.0 Zwavejs Version 6.6.0 Zwavejs-server Version 1.1.0

Logfile: Includes switch event, interview log and node export: ge_switch.zip

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 26 (10 by maintainers)

Most upvoted comments

You guys are pros. Thanks for investigating this.

+1
skyw33 on Mar 12, 2021

@skyw33 It might help to have a more methodical approach, instead of just tapping the buttons a bunch of times. It’s really difficult to correlate anything without knowing what is what. My suggestion would be to get a new log file, and do something like this:

  1. Make sure the motion detection is disarmed (leave the room or whatever).
  2. Trigger the motion detection w/o touching the buttons. Wait a few seconds.
  3. Single tap a button. Wait a few seconds.
  4. Double tap a button. Done.

If you do something like that and note the times you performed each step, it should be a lot easier to sort out the Basic Sets from the Notifications, and see which Basic Sets go with which tap actions.

+1
kpine on Mar 12, 2021

I suspect this is the issue. You have two types of notifications coming through with 0/255. Double taps and motion:

21:11:27.165 DRIVER « [Node 008] [REQ] [ApplicationCommand]
                      └─[MultiChannelCCCommandEncapsulation]
                        │ source:      2
                        │ destination: 0
                        └─[NotificationCCReport]
                            notification type:   Home Security
                            notification status: 255
                            notification event:  Unknown (0x00)
21:11:27.166 CNTRLR   [Node 008] [~] [Notification] Home Security[Motion sensor status] [Endpoint 2]
                      : 8 => 0

You need to try to differentiate in the trigger.

+1
blhoward2 on Mar 12, 2021
Read more comments on GitHub
← node-zwave-js: GE Switches and Dimmers do not reflect double-up or double-down because they use the BasicCC for those events
node-zwave-js: GE/Jasco ZW3008 and ZW4006 support double taps but configuration doesn't support →