Yes I actually have a ZEN25 to test with as well. I figured the built in driver was working OK (without S2) but I just found a ST driver along with the ZEN30 today so I can use that as my base to start with. I will see what I can do.
3 Likes
Curious why you say the other advanced drivers aren't being updated anymore. @agnes.zooz said just last month that @bcopeland mentioned there'd be an update soon. 
Thanks so much. Looking forward to testing it.
It is confusing because Bryan (bcopeland) wrote these particular drivers before he was hired by Hubitat. Anything he wrote before he was hired is basically abandoned by him. He has stated that he hopes someone will carry on his previous projects.
The drivers Agnes Zooz is talking about getting updates are most likely the built-in Hubitat supplied drivers.
Out of curiosity, do any of the advanced parameter options here work to get rid of the press delay when scene mode is turned off?
Thanks!!
@hikeit you are looking to get rid of the ramp rate (the fade in/out when turning on/off)? Set the Ramp Rate setting to Instant, and the ZWave Ramp Rate to match the physical ramp rate. That should do the trick if I am thinking of what you want correctly.
I don't think the switches have a ramp rate setting, only the dimmers do.
I just tested my ZEN21 with and without the scene parameter enabled and physically tapping the switch. Both ways seems to be less than a 1s delay to turn on or off, no fade just instant on/off. I don't have any regular switches on a 3-way but if that's how yours is, is it only the extra switch with the delay? When using the secondary switch with my Zen27's I noticed there is a slight delay for the main switch to figure out what happened and to turn on the light. I also remember seeing another thread where someone was having an issue with a normal switch wired to a lamp and it was ramping it up instead of instant for some reason, I think he contacted Zooz support and they got it working right so not sure if it was a wiring issue or maybe a firmware update.
I'm just referring to the built in buttons, not the 3-way operation.
The delay I'm talking about is the "less than 1 second"... it's about 700 or 800 milliseconds from pushing the button to the relay flipping.
If I tell the switch to flip from zwave, it actually switches faster.
@chrismccracken (and everyone)
UPDATE:
ZEN30 Double Switch beta driver posted in GitHub for manual installation at this time (not in package manager). It appears to work 100% for me. I have my ZEN30 sitting here on my desk wired to an extension cord for testing the button presses. All parameters, scene buttons, and associations are supported. I used the same button numbers for the dimmer as the other ZEN switches (1-10), and then for the relay switch I am using (1-5) but sending the event to the child device. So if you want to trigger any RM actions on the relay create the rule on the child. Turn on the info logging to easily investigate what any of the button numbers are.
There are a few things with the child device stuff, and multichannel where I am not really loving the code from the original driver. I also am having a hard time making sense of what some of it is doing exactly, first time with multichannel and a child device. I am going to see if I can get some feedback in another post before I make this an official final version.
UPDATE:
Posted ZEN30 v1.3.2 to GitHub and added to Package Manager. Got most of my concerns worked out and it seems to working pretty solid in my testing. Tested with firmware 1.05 and 1.07 paired with S2 (not sure what changed in 1.07 yet but Zooz wanted me to try it). If you already had the beta installed if you run a Match Up in HPM it should find it.
Next Up: almost done adding the ZEN76 and 77 to the lineup. Will be 1.4.0 and all the switch drivers will merge, and the dimmer drivers will merge into two universal Zooz drivers (similar to the stock drivers). Less drivers for you, easier to keep the code in sync for me.
1 Like
Can you squeeze ZEN71 into your backlog please?
1 Like
I should be able to include the ZEN71/72 into the universal driver I am working on for 1.4.0 pretty easily. I did not even realize they had a ZEN71. They did not have their docs posted for the 76/77 until I asked about it this week. I will see if they can post the ZEN71/72 info as well. @Richard.Albert.Bryan can you switch your driver to "Device" press the Get Info button then send me the fingerprint that it logs (PM is fine).
I am getting close to having the ZEN76 working good, a few kinks to work out with the way a couple things have changed from the other switches. Otherwise very similar.
1 Like
Thanks for writing these drivers. I'm using them for my ZEN21 and ZEN27 devices -- will be adding the ZEN7x devices shortly. Replacing all 50+ switches in my new house (been in for 12 months now).
Is there any reason why the max dimmer value can't have a 100% value included? Go ahead and keep the 99% as default if you wish.
I've been editing your driver code to add can certainly edit the code to add this to the enum list, but as you do updates, I loose this and then have to edit again.
1 Like
The actual max value for the param is 99% per the docs. I have not tried setting it to 100 but it might not like it. There is validation in the code that checks to make sure the level itself is never set higher than 99 as well but it reports back to the user it is 100% visually. I could just change the name of the 99 setting to show 100% in the dropdown menu? Or are you actually setting the param to 100? Want to share your code with me using something like https://codeshare.io/ and I will check it out for my next version. (Can PM me the link).
My PC is down right now, but if you do a SetLevel to 100 from the commands at the top of the device page fir a ZEN27 you will see it goes confirms 100%. And there’s a subtle change on my fixtures when I do that. It helps me with the wife acceptance factor who doesn’t even like my dimming at all, lol.
I hate to tell you but as far as I can figure out you are only fooling yourself (and your wife). If you uncomment the log tracing at the very bottom of the driver you should be able to see where the switch actually reports back a level of 99. Now this is due to the fact that even if you put in 100 or anything over 100 into setLevel the driver corrects that to the max of 99 before it sends it. I took it one step further though, I used another tool to manually try to set the param 11 to 100, no dice, it just reports back whatever it was set to before, it refuses that value. So then I removed the validation from my driver, set my level to 20, then tried to set it to 100, nothing happens, it ignored the command. Set it to 99 and it goes to full brightness.
So, really the only thing that could be done is to just rename the 99% to show as 100% in the dropdown (but it will still set the param to 99). I sort of like leaving it as 99 though because that lines up with the Zooz docs saying the max is 99.
1 Like
You very well could be correct. I’ll check it out later when my PC is back online. Non Habitat issues right now 
Zen71 fingerprint
dev:5022021-01-10 03:24:33.765 pm infofingerprint mfr:"027A", prod:"7000", deviceId:"A001", inClusters:"0x5E,0x55,0x9F,0x6C"
dev:5022021-01-10 03:24:33.740 pm debugbuilding fingerprint for unknown Z-Wave device...
I just skimmed through the posts and didn't see this mentioned. Does your Zen30 driver fix the bug where pressing up on the paddle reports a press of the relay button? I have several Zen30s setup where the button is just a scene trigger and I had to pause all those rules because the 2.2.4 update did something to this. There's a fairly lengthy post on here somewhere about it.
