anytime
Hi Brian,
Thank you for taking the time to write these great drivers.
I noticed that when using your ZEN26 driver for my switches I no longer get press and hold button statuses for the switches that can be used in automations. Double taps register but hold and release don't work. Am I missing anything?
make a new rule using button device as a trigger and populate all buttons - you will now have 8 button presses instead of the four type for each button.
oh, and button 1 is now the lower paddle and button 2 is the upper.
Thanks Steve! I'll give it a shot. Appreciate the help.
I did what you said but nothing happens for buttons 5-8. I have the following register in the device details page:
single tap off = 1
single tap on = 2
double tap off = 3
double tap on = 4
Tap and hold does not register anything but the logs show this for the bottom button:
" 2020-05-08 03:09:04.948 pm debugparse:zw device: 6F, command: 5B03, payload: 5D 82 01 , isMulticast: false"
Then when released it shows:
" 2020-05-08 03:09:05.728 pm debugparse:zw device: 6F, command: 5B03, payload: 5E 81 01 , isMulticast: false"
so it looks like the driver is not registering press and hold, and release events?
The device doesn't send press and hold and release events.. So no.. The built-in driver must have been doing something other than central scene to accomplish this .. The central scene capability is documented as:
From the docs:
Upper Paddle:
1 x tap: load on to last / custom brightness; Scene 1, attribute 00 (button 1)
2 x tap: on to full / max brightness; Scene 1, attribute 03 (button 3)
3 x tap: enter inclusion (pairing) mode; Scene 1, attribute 04 (button 5)
4 x tap: Scene 1, attribute 05 (button 7)
Lower Paddle:
1 x tap: load off; Scene 2, attribute 00 (button 2)
2 x tap: Scene 2, attribute 03 (button 4)
3 x tap: enter exclusion (unpairing) mode; Scene 2, attribute 04 (button 6)
4 x tap: Scene 2, attribute 05 (button 8)
According to the docs.. but it seems to be reversed..
My drivers are always pure to the protocol specs.. so if you are needing hold and release then you may need to go back to the built-in driver
Thanks Brian, but I think you are referring to the ZEN27 Dimmer. Your right that the dimmer doesn't have the press and hold scene control because that is reserved for the dimming functionality but on the ZEN26 Switch it has the capability for press and hold/release. Maybe this just needs to be added to the driver?
The built-in driver has the capability (emulated I'm sure) because the device does not send hold and release on central scene commands
Interesting okay thanks!
Not sure if this helps but here are the logs using the built in driver for each type of button press on the switch:
dev:5752020-05-08 05:08:43.219 pm infoDownstairs Closet Light Button 2 released
dev:5752020-05-08 05:08:43.217 pm debugCentralSceneNotification(keyAttributes:1, sceneNumber:1, sequenceNumber:102)
dev:5752020-05-08 05:08:42.460 pm infoDownstairs Closet Light Button 2 held
dev:5752020-05-08 05:08:42.458 pm debugCentralSceneNotification(keyAttributes:2, sceneNumber:1, sequenceNumber:101)
dev:5752020-05-08 05:08:40.322 pm infoDownstairs Closet Light Button 2 doubleTapped
dev:5752020-05-08 05:08:40.318 pm debugCentralSceneNotification(keyAttributes:3, sceneNumber:1, sequenceNumber:100)
dev:5752020-05-08 05:08:39.347 pm infoDownstairs Closet Light switch is off
dev:5752020-05-08 05:08:39.344 pm debugBasicReport(value:0)
dev:5752020-05-08 05:08:38.935 pm infoDownstairs Closet Light Button 2 pushed
dev:5752020-05-08 05:08:38.932 pm debugCentralSceneNotification(keyAttributes:0, sceneNumber:1, sequenceNumber:99)
dev:5752020-05-08 05:08:22.481 pm infoDownstairs Closet Light Button 1 released
dev:5752020-05-08 05:08:22.479 pm debugCentralSceneNotification(keyAttributes:1, sceneNumber:2, sequenceNumber:98)
dev:5752020-05-08 05:08:21.669 pm infoDownstairs Closet Light Button 1 held
dev:5752020-05-08 05:08:21.666 pm debugCentralSceneNotification(keyAttributes:2, sceneNumber:2, sequenceNumber:97)
dev:5752020-05-08 05:08:19.681 pm infoDownstairs Closet Light Button 1 doubleTapped
dev:5752020-05-08 05:08:19.678 pm debugCentralSceneNotification(keyAttributes:3, sceneNumber:2, sequenceNumber:96)
dev:5752020-05-08 05:08:18.045 pm infoDownstairs Closet Light switch is on
dev:5752020-05-08 05:08:18.043 pm debugBasicReport(value:255)
dev:5752020-05-08 05:08:18.021 pm infoDownstairs Closet Light Button 1 pushed
dev:5752020-05-08 05:08:18.019 pm debugCentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:95)
Here is what comes out with your driver using the same order of button presses:
dev:5752020-05-08 05:12:12.886 pm debugparse:zw device: 6F, command: 5B03, payload: 6E 81 01 , isMulticast: false
dev:5752020-05-08 05:12:12.071 pm debugparse:zw device: 6F, command: 5B03, payload: 6D 82 01 , isMulticast: false
dev:5752020-05-08 05:12:09.593 pm infoDownstairs Closet Light button 3 pushed
dev:5752020-05-08 05:12:09.590 pm debugparse:zw device: 6F, command: 5B03, payload: 6C 83 01 , isMulticast: false
dev:5752020-05-08 05:12:07.543 pm infoDownstairs Closet Light was turned off
dev:5752020-05-08 05:12:07.542 pm debugBasicReport(value:0)
dev:5752020-05-08 05:12:07.540 pm debugparse:zw device: 6F, command: 2003, payload: 00 , isMulticast: false
dev:5752020-05-08 05:12:07.127 pm infoDownstairs Closet Light button 1 pushed
dev:5752020-05-08 05:12:07.125 pm debugparse:zw device: 6F, command: 5B03, payload: 6B 80 01 , isMulticast: false
dev:5752020-05-08 05:12:03.158 pm debugparse:zw device: 6F, command: 5B03, payload: 6A 81 02 , isMulticast: false
dev:5752020-05-08 05:12:02.355 pm debugparse:zw device: 6F, command: 5B03, payload: 69 82 02 , isMulticast: false
dev:5752020-05-08 05:12:00.124 pm infoDownstairs Closet Light button 4 pushed
dev:5752020-05-08 05:12:00.121 pm debugparse:zw device: 6F, command: 5B03, payload: 68 83 02 , isMulticast: false
dev:5752020-05-08 05:11:57.932 pm infoDownstairs Closet Light was turned on
dev:5752020-05-08 05:11:57.930 pm debugBasicReport(value:255)
dev:5752020-05-08 05:11:57.904 pm debugparse:zw device: 6F, command: 2003, payload: FF , isMulticast: false
dev:5752020-05-08 05:11:57.859 pm infoDownstairs Closet Light button 2 pushed
dev:5752020-05-08 05:11:57.826 pm debugparse:zw device: 6F, command: 5B03, payload: 67 80 02 , isMulticast: false
If you notice in the log it’s just keyattribute and scenenumber.. Which according to zooz docs maps to:
Upper Paddle:
1 x tap: load on to last / custom brightness; Scene 1, attribute 00 (button 1)
2 x tap: on to full / max brightness; Scene 1, attribute 03 (button 3)
3 x tap: enter inclusion (pairing) mode; Scene 1, attribute 04 (button 5)
4 x tap: Scene 1, attribute 05 (button 7)
Lower Paddle:
1 x tap: load off; Scene 2, attribute 00 (button 2)
2 x tap: Scene 2, attribute 03 (button 4)
3 x tap: enter exclusion (unpairing) mode; Scene 2, attribute 04 (button 6)
4 x tap: Scene 2, attribute 05 (button 8)
How does this driver differ from the stock driver?
It offers all the config options, follows the zooz docs for central scene functionality all the features of the latest firmware versions
1 Like
Oh okay. That’s interesting that the double tap maps to “full brightness” event though it’s a switch with only on/off. Thanks for explaining.
Here .. Does this make you feel better:
Upper Paddle:
1 x tap: load on; Scene 1, attribute 00 (button 1)
2 x tap: Scene 1, attribute 03 (button 3)
3 x tap: enter inclusion (pairing) mode; Scene 1, attribute 04 (button 5)
4 x tap: Scene 1, attribute 05 (button 7)
6 x tap: change LED indicator mode (see parameter 2)
Lower Paddle:
1 x tap: load off; Scene 2, attribute 00 (button 2)
2 x tap: Scene 2, attribute 03 (button 4)
3 x tap: enter exclusion (unpairing) mode; Scene 2, attribute 04 (button 6)
4 x tap: Scene 2, attribute 05 (button 8)
1 Like
Yes.. I posted the dimmer central scene docs.. Which map to the same attribute and scenes.. As you can see..
Hey, any chance your driver includes the inovelli code that allows you use the zwave association tool ?
No.. It’s easier.. Just put the node ids in preference
1 Like
on the source, you put the Node ID of the destination? or vice versa? or both?
destination.. Because the association is a one way thing.. It tells the device to send the command classes in that association to the associated nodes..
1 Like
