My v2 is arriving tomorrow, but it would be replacing my Z17 out in my detached garage too... Weather is supposed to be ~50 this weekend (shorts weather again 
), so I'd love to give it a whirl.
But I have a couple family things to deal with, so I'm not confident I can carve out enough time to deal with a swap on that scale.
I'll more likely focus on the new 800 Z15s from the comfort of inside instead, and hope & pray for another warmish upcoming weekend.
Posted the driver in my relays package:
Hi Jeff -- posting this update here in this thread vs the Relays Advanced thread just to help keep that more-permanent thread cleaner...
I'm happy to report your driver works GREAT with the new Z16!
Unfortunately, the relay Auto-Off functionality isn't working, but I'm certain that's a Zooz firmware issue - they confirmed it was broken on the Zen17 fw 1.3 too. Z17 fw 1.4 dropped today, and they told me 1.4 will supposedly fix it, but my Z17 was already excluded when I saw the 1.4 fw this morning. I'm guessing they just didn't get that fix in the Z16's 2.0 code. But I'll submit a ticket with them today about that.
I'm just using one relay (R1) for my GDO ("0" value for param 21), but I'm using all 3 sw/snsr options for 3 dumb wired reed sensors - one for GD full closed, one for GD full open, and one for the garage service door.
As we suspected, the "0" value for params 12-14 works great to decouple the Ss from the Rs. I admittedly did not try the "2" setting for p 12-14 - I'm still puzzled by that one, so I'll ask Zooz about it when I tell them about the Auto-Off issue.
At first, none of the sensors were updating and after trying all sorts of reconfigurations & hail-Mary's for longer than I care to admit this morning, I was about to smash the darn thing on the garage floor... But then I noticed your Param 2-4 note about power-cycling the device. And of course, that worked - sensor statuses are all now updating lickety-split 
I also verified that your driver parameters are all setting correctly by comparing the Basic ZW Tool parameter report -- parameters all matched up exactly in both.
This driver rocks -- thank you very much!!
Yeah 12-14, Send Sensor Status only is what you want. Not sure what the point of the setting 2 would even be (Send All status but do not activate relay).
I let Zooz know about the power cycle issue. At first I thought something was wrong with the sensor notifications but then since they usually tell you to exclude the re-include when changing those I thought maybe a power cycle would help. Strangely enough it works right using a depreciated command class, which they have in there for compatibility on other systems, but I wanted to use the current notifications class.
You've probably already heard something similar from Zooz about the Param 12-14 value options, but I just got this response back from Nikke at support:
Both 0 and 2 disable actual control of the output from the inputs but with value 2, the device will send a report from the input to the hub when triggered as if it was coming from the output even without the output being physically triggered if that makes sense. It's useful only in edge cases and value 0 is recommended for classic decoupling of inputs from outputs.
Nikke also said they'll ask their devs about the Auto-Off bug -- I'll follow up on that when I hear more.
We absolutely do recognize it and value Jeff's contributions! We'll definitely look into referral options going forward 
Zooz confirmed that the Auto-Off bug exists, but only if you have the Ss decoupled from the Rs. This was the same bug the Z17 had on fw 1.3.
Zooz implied that's fixed now in the Z17 fw 1.4 (I'm not able to confirm), and they said to expect same fix in the Z16v2 fw 2.1 which they hope to drop before EOY.
The new 16 is still working great!
Hi Jeff,
I'm changing things up on my new Z16, and discovered a minor issue -- not sure if this is driver related or firmware related... I figured I'd run it by you first before asking Zooz.
Long story, but I'd now like to use DC Motor Mode (P24) to deconflict R1 and R2 from being on at same time.
When I attempt to set P24 = Enabled via the driver (and then hit Configure), I get this:
^^^^ this "Pending" message stays persistent through repeated Config and Refresh attempts
If I reset P24 = Disabled via driver, then everything syncs clean and all is as-expected with the logs.
This is NOT a big deal -- it's super easy to work around with tweaked rules, but I'm just curious if you can tell whether or not it's a firmware issue. I'm happy to supply any add'l info that may be helpful.
Thansk a ton!!
ETA - in case it's helpful, here's how my params are currently set up (w/ DC Motor = Disabled):
Seems like the device is not accepting the value of 1, so it just refuses it and keeps it at 0. May be a bug or possibly a built in undocumented restriction from your other settings?
Yeah, I suspect it may be something tied to another parameter setting or similar too.
I'll run it by Zooz -- many thanks!
Download the Hubitat app
