ZWave-JS - GE/Jasco/Honeywell Double Taps

ptdalen · February 20, 2021, 4:20pm

I tried to import using the import blueprint button in the HA UI under blueprints, then pasted in the URL for this post. That is where the error was thrown. I’ve added others using that process. Makes it kinda nice.

I was able to manually add the blueprint, by copying and pasting the yaml code above. Works great and thanks for saving me a good amount of time having to “fix” a lot of my older automations

freshcoast · February 20, 2021, 5:37pm

Ah, I didn’t even know you could do that. You’re probably right, maybe two blueprint code blocks in one post breaks the import. I added some URLs for importing, thanks.

jmwick · February 24, 2021, 5:58am

Are there any configuration or scene activation changes that need to be made in zwavejs interface? I added the automation using the blueprint, but can’t get the double tap to work. I’m using model ZW3008 smart motion dimmer with firmware 5.32.

freshcoast · February 24, 2021, 7:19am

Do you know for sure that the switch supports double-taps? If it does, the device config file is not setup to support it.

My GE 14294: https://github.com/zwave-js/node-zwave-js/blob/53f9c91c4120fd1b4ceedaa90f67f80e89a5767d/packages/config/config/devices/0x0063/ge_14294_zw3005.json

Your ZW3008: https://github.com/zwave-js/node-zwave-js/blob/3d72a75aa51db0a0b580f1c3277c56d84303d93c/packages/config/config/devices/0x0063/26932_26933_zw3008.json

The device config file needs to configure two things:

Auto-assign assocation group 3 to the controller
Set the treatBasicSetAsEvent compatibility flag which produces events for basic set

The ZW3008 config file is missing both of those. You would need to submit a PR to add the functionality, or submit an issue to request it to be updated.

jmwick · February 24, 2021, 11:42am

Thanks @freshcoast

I’m pretty sure these newer switches support double taps, but can’t find much useful specifics on how to create a json config file.

Someone in the Smartthings world has some info on a handler for a similar model:

github.com

mwav3/smartthingscode/blob/ccfd245160e67d04897dfc33219a33696507702a/devicetypes/mwav3/ge-46203-dimmer-switch.src/ge-46203-dimmer-switch.groovy

/**
 *  GE/Jasco 14294/46203/ZW3010 Z-Wave Plus Dimmer Switch
 *
 *  Contains code from https://github.com/nuttytree/Nutty-SmartThings/blob/master/devicetypes/nuttytree/ge-jasco-zwave-plus-dimmer-switch.src/ge-jasco-zwave-plus-dimmer-switch.groovy
 *
 *  Copyright 2020 Chris Nussbaum, Tim Grimley
 *  Contributors - Bradlee_S
 *  Thanks Chris for the original copy of this great code!
 *  Thanks Bradlee for the button programming to get this working in the new app's automations section
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 *	Author: Tim Grimley

This file has been truncated. show original

I will try adding an issue as you suggested.

jmwick · February 25, 2021, 10:52am

feature requested and being worked on…

decairn · April 8, 2021, 11:54pm

I have a GE 14291 switch that was working for double taps before 2021.4.0 and now it is not with me running 2021.4.0. I see the gist was updated to reflect what I think was the breaking changes in that release yet it’s not noticing the event. Any ideas on how to triage this? Do I need to delete/re-add the automation / blueprint in any way?

freshcoast · April 9, 2021, 12:04am

All I did was edit my blueprint files and replace the event name. Then I reloaded automations. That was sufficient for me to get the events working.

You can use the event listener to double check that the zwave_js_value_notification is being seen.

decairn · April 9, 2021, 12:09am

Confirming a reload of automations fixed it. A reboot didn’t do it on its own, nor did a delete and re-add of the blueprint.

ChuckieTodd · April 10, 2021, 6:27pm

The blueprint works well for me. I did notice some odd behavior if “local load” on the Z-Wave device was targeted at the controller. That caused the automation to fire on either double or single tap.

freshcoast · April 10, 2021, 7:29pm

Yeah, you can’t really use both, there’s no way to distinguish them.

gashpi · May 13, 2021, 7:06pm

Hi, this blueprint was working flawlessly until recently. Now I keep getting an error that says:

Error: UndefinedError: ‘dict object’ has no attribute ‘event’

I have no idea how to troubleshoot and was wondering if someone else is having the same issue.

franknitty69 · May 19, 2021, 3:46am

yep. confirmed. i have the same error. double taps was working fine maybe about a few weeks and no longer work.

error seems to be with: value: ‘{{ trigger.event.data.value }}’

rbray89 · December 19, 2021, 3:38pm

Just in case someone else has difficulty in getting this to work:

I restarted automations, and I added the dimmer to the group 3 association with the controller as the target in zwaveJS.

Not sure what made things work, but documenting here for others.

freshcoast · December 19, 2021, 3:57pm

What model do you have? Z-Wave JS does the controller association automatically, but that needs to be setup in the device config file.

rbray89 · December 19, 2021, 4:09pm

It reports as: 26932 / 26933 / ZW3008

Mattklev1 · December 22, 2021, 1:28am

fantastic!
Any chance you can add an OR condition to the selected device input.

For example - I have 3 light switch’s. If any one of the three switch’s are double tapped. Then I want to turn on all three of those switch’s.

ktownsend-personal · March 25, 2022, 5:12pm

@ChuckieTodd, I seem to have this problem of getting event for both single and double tap. I don’t see “local load” config on the device (this is definitely a GE/Jasco device, in-wall dimmer). I just switched over from legacy zwave and I was using double-click events in a ton of automations. Is there a trick to seeing the group 2 and group 3 settings on the device in Zwave JS?

ktownsend-personal · March 25, 2022, 9:37pm

Answering my own question, it looks like I need to switch from ZwaveJS to Zwavejs2Mqtt so that I can use the advanced UI to access the group associations of the devices.

These zwave variations are confusing. So far I have learned that:

ZwaveJS is official, but doesn’t have ability to set association groups. Possibly other limitations too.
The original built-in zwave integration (ozw 1.4 ), and the subsequent beta (ozw 1.6) are dead
Zwavejs2mqtt addon is effectively a superset of ZwaveJS with optional MQTT and an advanced UI
- Zwavejs2mqtt came first, then ZwaveJS was extracted from it as a minimum subset
The ZwaveJS integration can use either ZwaveJS addon or Zwavejs2mqtt addon, but not at the same time because the addon is what interfaces directly with the zwave controller hardware
- addon vs. integration is an important distinction to be aware of
- The ZwaveJS integration setup has a checkbox to install the official ZwaveJS addon, but if you uncheck it you can point the ZwaveJS integration to use your self-installed Zwavejs2mqtt addon instead

I welcome any additional clarifications on the practical differences in the zwave variations.

ktownsend-personal · March 27, 2022, 11:13pm

Following up on my adventure, I finally got Zwavejs2mqtt installed and by small miracle I didn’t lose my ZwaveJS config. The confusing part of changing over was knowing what URL to configure for the ZwaveJS integration (it is the name of the docker container running the addon) and then realizing the abort error it kept giving me when I saved that URL was something I could ignore and restart Home Assistant. I also had to remember to turn off the “start on boot” and “watchdog” switches on the ZwaveJS addon so that it didn’t interfere with the Zwavejs2mqtt addon until I get around to deleting the ZwaveJS addon.

Back to the problem at hand… double-clicking switches to run automations: using the advanced UI in Zwavejs2mqtt to examine the groups, it turned out the one switch I was testing with had both group 2 and group 3 pointing to the zwave controller instead of just having group 3. That’s why I was getting both single and double-click events. It turns out I need both single and double click for that switch, but unfortunately there isn’t any way to distinguish between the two types of click. That was already a limitation of ozw, so nothing lost in that regard. I just wish we could get some indication in the event payload to indicate the single vs. double click.

I appreciate having found this topic and the mention of groups 2 and 3 being involved in getting the double-click to work so I could find a path to success. I may grumble about how convoluted the zwave variations and migrations are, but in the end I have a functioning zwave network that isn’t going to be dropped in the next release of Home Assistant. I put off this migration for a year because it didn’t feel mature enough back when they announced ZwaveJS as the official replacement for the legacy zwave integration, and because I knew it was going to be a big chore to get it migrated completely (I have 65 zwave devices exposing 399 entities). I am happy that in the end I got it all migrated successfully. I hope this whole situation gets streamlined enough to give non-technical users a chance at successfully migrating their zwave.