Do you need a driver for zen30? There is a built-in driver.. Does it not do what you need?
First off I'm new to Hubitat. Wink is in the trash with 4 relays. I found the article with saying that the driver was in the new update. It came into the device tree properly. Parent/Child The Light dimmer in is my dashboards and works great, but I'm having trouble with the fan. Should it be a button or a switch assignment on the Dashboard?
I’m not familiar with this device.. So I’m not sure
You can use it as a button or a switch to trigger an automation, but it needs to appear as a switch in the dashboard if you want to be able to turn it on and off.
My Zen 30's work fine. Driver is a dimmer with any feature I've needed, and a child device that is a switch. But curious of something is missing that i'm not thinking of.
1 Like
Despite the recent C7 hub and zwave radio upgrade I'm still having issues with these drivers not working. They report state properly but I'm not able to turn on/off. The generic Hubitat Zooz Central Scene Switch driver works fine but doesn't have the advanced features. Anyone else having similar experiences?
1 Like
I'm using this switch, and having issues while rolling over from ST to my new C7. I have it in a motion lighting scenario, with a ZooZ 4-in-1 sensor. It works fine for a few hours after setup, then stops working, will only work manual and even the buttons in the app won't turn it on/off. I'll have to look into the logs a bit more, since i do have the switch also running some Alexa routines.
@bcopeland which setting in your driver should I be using? I've looked at the raw zooz settings page: ZEN27 S2 Dimmer VER. 3.01 Advanced Settings - Zooz Support Center
I think it would be parameter 9, but I don't see parameters numbers listed in this driver.
I did have the same issue with at least the zen26 and a couple zen22, where these drivers were not working for me, they were reporting status fine but couldnt turn them on/off from the device or dashboard so i went back to the default driver. They work perfectly with the default driver, they report status and I am able to control them from the device page and from the dashboard. i would like to use the personalize drivers because they have way more options if not all but for some reason they didnt work for me in the exact same way than for you.
FWIW I have two Zen27's and am using the copland V1.4 driver. I've had no issues since installing...maybe 6 months ago.
One is within 20' of the hub the other ~26' as the crow flies. Or perhaps better said "as the field propagates".
I'm brand-new to HE (just got it yesterday) and am in the process of moving my devices over from SmartThings. My Zen27 (FW = 2.8) is completely unresponsive when using this driver (v1.4) but works perfectly with the built-in driver. Using "Zooz Central Scene Dimmer" as the type, it responds immediately. If I change the type to "Zooz Zen27 Central Scene Dimmer" and click Configure, the events log says that it was turned on/off, level is xx%, etc. but nothing actually happens. Switch back to the included driver and I'm back in business (but missing all the scene controls, etc.). Any suggestions? Please let me know what additional info is needed. Thanks in advance!
1 Like
I’ve seen this as well. I have a bunch of ZEN27 dimmers here, one at firmware 2.08, rest at 2.07.
I’m switching everything over to my new c-7 hub, and I somehow managed to include a couple of them as non-S2 devices (don’t ask me how though!). These non-S2 devices worked with this driver just fine, but the S2-connected nodes are only functional with the built-in driver.
Hope this helps some folks.
@agnes.zooz Should I submit a ticket directly to Zooz for this? It's important I get this working and assumed asking here was the right place to start, since it's a community-provided driver. (Why isn't a fully functioning driver included out of the box with Hubitat? The 2.8 firmware with numerous new features has been out since spring, if I'm not mistaken.) Very frustrating and a big step backward from SmartThings as far as this goes. 
If you're having any issues including or using your switch with Hubitat, definitely send us a message and we'll be happy to guide you through the process. We update the devices quite often since we take all user feedback and suggestions seriously but for these new settings to be available in Hubitat out of the box in the built-in driver, it would require Hubitat developers to add them there. SmartThings doesn't support any advanced settings without a custom handler and all custom handlers run in the cloud while HE allows you to use custom drivers locally which is a great advantage I think 
It'd be a great advantage ... if the custom drivers actually worked. I'll have to create a support ticket. 
Are you pairing the Zooz devices securely? I was able to get the custom drivers to work for devices not paired securely. For devices paired securely I've only been able to use the Hubitat generic Zooz drivers. I'm guessing the customer drivers weren't written to support S2 paired devices.
2 Likes
Yes, I believe that was the option provided when I paired the Zen27. I know nothing about Z-Wave security, nor should I need to. I just want my switches to work.
But thanks for the tip -- sounds like I may have to forget the device, scrap all the automations I've created around it, etc. and start over.
That unfortunately is the risk of using community based drivers. If they aren't maintained or if the device changes these no longer are valid. I am not sure if or when these might be updated.
There isn't much of anything Zooz can do about it, and Hubitat support will most likely tell you to use the stock (built-in) driver. And if I am reading it right, the stock driver works. So....
That sounds a bit drastic.
What are you missing by using the stock driver VS this community based one? There may be alternative ways to get this functionality. For example, you might be able to use the Hubitat Basic Zwave Tool to set certain parameters.
I'm only using the community-based driver because that's specifically what Zooz recommends. The included driver has 10 variables in the preferences; the custom driver has 23, including things like much more granular control of auto on/off timers, setting nightlight mode, different ramp rates for physical vs. Z-Wave and so on. It's not that I necessarily need to set all 23 today, but given that I bought the HE largely based on Zooz's apparent enthusiasm and support for it, it seems like I should be able to directly access all of the features of the switch. The stock driver works, but it's kinda like buying a sports car that can't get past third gear -- technically functional but hardly performing to expectations and potential.
I'm migrating from SmartThings and learning as I go, hardly a complete idiot but neither am I a seasoned coder. HE seemed like a great way to do that, so I'm frustrated that I've hit this stumbling block right out of the gate -- using the driver recommended by Zooz -- and have fewer capabilities for the switch now than I had with SmartThings (which also required a custom driver, but that one actually worked). I expected a learning curve and to have to put more effort into creating the automations and integrations -- that was a given that I welcomed -- but needing to use "alternative ways to get this functionality" when using the Zooz-recommended driver is an unwelcome surprise. I don't think my expectations were unreasonable.
