You should also try a two different ways to disable switch, that are not in user manual
Those are both good options. Zooz recommended a third option for ceiling fans of wiring them to constant power instead of the relay since they have a variable load. They said it would wear out the relay over time. They of coursed prefaced that by saying it has to be allowed by local building codes.
@krlaframboise I noticed the ZEN32 is now included in the Zooz platform drivers. Is that driver the same implementation as your groovy driver here?
I cleaned up the code and removed the association related functionality, but other than that it’s the same DTH.
It doesn’t execute locally and last time I checked none of the other built-in DTHs with child devices do, but I think a custom vid and/or custom capability would also prevent that.
question here, maybe I am overthinking this…
I have the ZEN32 large button programmed to turn on or off a Zigbee RGBW bulb. Relay Load Control for the ZEN32 is also set to ‘disable switch and z-wave’.
This works perfectly when using the physical button (as expected) but how can I turn on/off the ZEN32 controller and get it to trigger an on/off on the Zigbee bulb from the SmartThings app?
I am using the beta driver currently if that makes any difference
There’s a driver available for the Zooz ZEN32 Scene Controller on Zooz’s Edge Driver Channel.
I installed the ZEN32 today, and had no luck getting it added until I read these messages. Now that I have the Edge driver activated I can add it but only get one device in ST, no buttons. The options for all the buttons are there but I can’t use them. I tired tweaking the IDE per the old Zooz help site, but no luck. I have removed an re-added it several times using different approaches to adding it, all fail to show the buttons. Bummed because it seems like a nice piece of kit!
So I figured it out… I was trying to use it like old SmartThings stuff, routines and subs are in the main device window. Got it going now disregard above!
Unfortunately drivers for hub connected devices don’t support standalone child devices so I couldn’t implement it the same way as the old groovy DTH.
It works great! It’s nice having the ability to control devices from it and it all be local.
@TheSmartestHouse this means I connect just the line and neutral to the switch and I’ll have events from all 5 buttons? Would be awesome!
Yes, you don’t need to have anything connected to the load or traveler terminals, as long as the switch is powered, you can use it just as a scene controller.
Hi,
I installed the ZEN32 today with edge driver and no load wired. Would it be possible to change the setting to avoid flashing light every time you push a button ?
Not sure . . . maybe related to this setting below.
Enable / disable LED indicator for settings
Parameter 23: Choose if you want the LED indicators to flash whenever a parameter (setting) is adjusted on the device to confirm the change. Disable this feature if you’re using the LED indicators in automations.
flashing light = MAIN Button LED flashing twice
That parameter was added to the firmware after I wrote the driver which is why it’s not exposed on the settings screen, but that parameter is related to it flashing when you change a setting, not when you press a button…
I’m not sure if there’s a way to prevent the LED from flashing when the button is pushed, but changing the “LED Mode” option on the device details screen to “Always Off” might work.
Is it possible to associate 2 Zen32, for a 3-way switch implementation?
Thanks, yes I understand that, and have setup the virtual 3-way this way. I’m interested in direct device association though
@krlaframboise I don’t have firm numbers but I believe I am seeing a delay when using the top large button vs the smaller scene buttons. Is there logic in the driver that makes the large button slower to respond? Maybe some related to the load control for the switch. I use these as 5 button scene controllers for lighting. The lower buttons are more responsive most of the time.
The driver immediately emits the button pushed event when it receives the central scene notification so if that’s the event your referring to then the delay is on the device’s side.
That being said, the device might send reports to the association groups before sending the central scene notification so using the association feature might cause a delay…
