[RELEASE] Advanced Zooz Zen24 / Zen23 Central Scene Dimmer and Switch Drivers

Advanced Zooz Zen24 / Zen23 Central Scene Dimmer and Switch Drivers

  • All device configuration variables
  • Central Scene Functions (matching descriptions on zooz website)
  • Normal Dimmer / Switch functions
  • Z-Wave Direct Associations
  • Pushable Button Capability 8 buttons (matching descriptions from zooz website) These will be different button numbering from the built-in driver.

These drivers are based on new options in the latest firmware versions 3.8 (ZEN24) and 3.5 (ZEN23). It is highly recommended that you be on these versions.

Please let me know of any issues or missing functionality .. Or feature requests.

As usual make sure to hit configure after changing to this driver.

https://github.com/djdizzyd/hubitat/blob/master/Drivers/zooz/zen24-dimmer.groovy

https://github.com/djdizzyd/hubitat/blob/master/Drivers/zooz/zen23-switch.groovy

Dimmer Changelog:

2020-05-07: V1.0

  • Initial Commit

Switch Changelog:

2020-05-07: V1.0

  • Initial commit
6 Likes

Do you sleep? :laughing:
:+1:

1 Like

It’s overrated

3 Likes

Just curious, are the zen21 and Zen22 on your radar?

1 Like

Done dude :wink:

3 Likes

nice. thanks.

1 Like

anytime

I upgraded my Zen24 to the latest firmware with your utility (took about an hour to transfer) - thanks.

At the end of the upgrade I tried to do the exclusion for a good 45 minutes without success (including hitting the switch down fast for 6+ times, air gapping a few times). In needing the switch to function I eventually gave up and did an inclusion which worked fine first try.

Any suggestions I what I might want to do on the Hub before doing a forced removal of the old device? I already ran a Z-Wave repair.

1 Like

Nope.. that is what has to be done..

1 Like

@bcopeland, @stephack Bryan, Steven, I have a few ZEN23's and a Zen24, which are version 2.0 which were some of their first ones to come out. I changed their drivers to yours (Bryan) but encountered a problem. After changing and configuring all of them I noticed that the remotes (minimotes, they go through ABC) did not control any of the switches. As soon as I changed all or one of them back to the generic z-wave switch the remotes once again were able to control them.

Any ideas as to why? thanks

EDIT: No errors in the log, just shows a button push from the minimote. Minimote device page shows button push changes as well. ABC up to date.

This just showed up in the log.

dev:34422020-06-12 11:40:38.394 am debugKitchen Nook Light: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 5, reportsToFollow: 0, nodeId: [1])

dev:34422020-06-12 11:40:38.391 am debugparse:zw device: DD, command: 8503, payload: 01 05 00 01 , isMulticast: false

dev:34422020-06-12 11:40:38.222 am debugKitchen Nook Light: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 5, reportsToFollow: 0, nodeId: [1])

dev:34422020-06-12 11:40:38.198 am debugparse:zw device: DD, command: 8503, payload: 01 05 00 01 , isMulticast: false

dev:34422020-06-12 11:40:37.830 am debugDevice Specific Report: DeviceSpecificReport(deviceIdType:2, deviceIdDataFormat:1, deviceIdDataLengthIndicator:8, deviceIdData:[66, 81, 93, 139, 137, 204, 255, 17])

dev:34422020-06-12 11:40:37.791 am debugparse:zw device: DD, command: 7207, payload: 02 28 42 51 5D 8B 89 CC FF 11 , isMulticast: false

dev:34422020-06-12 11:40:37.685 am debugversion3 report: VersionReport(zWaveLibraryType:6, zWaveProtocolVersion:4, zWaveProtocolSubVersion:5, firmware0Version:20, firmware0SubVersion:15, hardwareVersion:1, firmwareTargets:0, targetVersions:[])

dev:34422020-06-12 11:40:37.590 am debugparse:zw device: DD, command: 8612, payload: 06 04 05 14 0F 01 00 , isMulticast: false

dev:34422020-06-12 11:40:37.489 am debugprocessAssociations cmds: [AssociationSet(groupingIdentifier:1, nodeId:1), AssociationGet(groupingIdentifier: 1), AssociationGet(groupingIdentifier: 2)]

dev:34422020-06-12 11:40:37.462 am debuggroup: 2 dataValue: null parameterValue: null

dev:34422020-06-12 11:40:04.249 am warndescription logging is: true

dev:34422020-06-12 11:40:04.248 am warndebug logging is: true

Unfortunately I'm not familiar with this driver or the one you are switching to/from.
My guess is that the issue lies in how each driver controls the specific load you want to control. One driver may use a switch capability while the other uses a button capability (central scene devices frequently do this). Depending on the differences between the 2 drivers, you may need to change how it is configured in ABC. We'll await @bcopeland's response because I'm sure he would be of more assistance than I, but in the meantime, please post a screenshot of the ABC section you have configured to control this specific switch.

This driver is only really meant for the latest firmware and version of switches. The V2 is basically a totally different device from what I have researched. The generic driver is the correct driver with V2.

@neonturbo I kind of wondered that myself. After all they are the original versions. I will keep them using the generic. Thanks

Here is the config for the minimote I used. I agree that it probably is in the switch because of it's version. Buttons 1,2,3 are ZEN23's. Button 4 is a LZW42 and the remote works fine for it.

I've switched over my Zen23 from ST to HE. The device shows up in my IDE and works perfectly, but I cannot add it as a tile in my dashboard. It doesn't show up on the list? I upgraded to these drivers and still no go. Any ideas?

Did you go through the process in the dashboard child app to check the box for that device, click update, then done back to app list?

1 Like

Thank you. That was it. Still getting used to differences between ST and HE. :slight_smile:

I just tested this driver on my zen24 - works better than the default one (my default one wouldn't dim when turned off and this one does). Why doesn't HE make this the default driver?

I have a whole house full of Zooz Zen23's from various times, Is there a way to query which version they are? 3.x 4.x?

I have version 3.0 of the Zen23. Will there be an issue if I use this driver. I see version 4.0 is the latest one being sold.