It is a pretty uncommon use case to be fair. Firmware 1.80 now has the option to separate the inputs from the outputs, which may also have some effect on how this type of use is best implemented. I have not updated as I think that Jeff is working on changing the driver to accommodate the change.
I dont know about "working" on it. I have thought about it though 
I cannot keep up with Zooz!
I am actually finishing up some bug fix stuff related to the last update of this driver pack, not accounting for the ZEN52 1.80 yet. The separating the inputs is a huge change which will require a ton of testing time. I am thinking about posting some beta code and let everyone else bang on it so I dont have to!
4 Likes
UPDATE
Note: This does not add support for the ZEN52 1.80 with the separated switch/relay yet. That will be the next update when I get a chance.
Version [1.3.2] - 2025-02-14
- Fixed issue when child not detected entire device could be switched on/off (thanks @jbondc)
- Fixed issue with hidden settings getting stuck on initial settings sync
- Added automatic attempt to detect child devices when not found from component commands
- Added driverVersion state and automatic configure for updates / driver changes
- Updated support info link for 2.4.x platform
3 Likes
Thanks Jeff!
I just loaded it for my Z51 first here... The Support Info tile looks good on the Prefs tab, but on the Commands tab it looks like it took something's spot that had a Run button... Otherwise, it loaded like a champ and all seems well.
I haven't done my Z17s yet since I'm messing around with those at the moment, so I can't yet confirm if this happens there too.
FWIW, this is Edge browser on a Macbook (all latest prod versions)
Its supposed to look like that. It technically is a command, there is no way to get rid of the run button. If you run the command it prints that same link box to the logs. It was the only good way I could get the info on that first tab of the new device page.
1 Like
Right on - many thanks for the explanation (and the update!)
1 Like
4 posts were split to a new topic: Need with setting up ZEN17
New ZEN16 800LR.
I'll be darned if I can find any behavior difference in the Default Relay State options.
I've verified the parameter was actually changed in the device data box.
What am I missing?
Thanks.
The first option is normal logical operation, when you turn relay ON, it closes the circuit. Off is open (normally open / NO)
The second option should be when you turn the relay ON, it OPENS, so in this case Off would be On/Closed, normally Closed (NC)
The third one is complicated.
Read the Zooz advanced settings docs for more info, I can only fit so much text in the drop down. My driver just sets the setting, if the devices doesn't work right then contact Zooz.
1 Like
Thanks. They all seem to work like the default. At least I could not tell any difference from looking at the logs.
I think I'm needing a real NC relay, so I ordered a ZEN17.
You would need to also put a meter on the relay contact to check for Ohms (open or closed) to determine what is going on. I am pretty sure I tested it a long time ago when I first created the driver. Not to say there isn't a bug in the newer firmware but it worked right at some point.
Did that too. Verified that the parameters did change. I should check if there's a firmware update, but I just got it.
If you think about it, this is actually a really good sign. Our space doesn't have enough innovative players moving fast on product development.
1 Like
Hi @jtp10181 Jeff, wonder if you can test something for me and see if you have the same behavior, ZEN17 relay auto off. I have it set to 1 second and it works, I can hear it click off. However, this is not reflected in the driver status, once on it will stay indicated on and not turn back to indicated off (but it is physically) unless refreshed. Can't seem to figure it out.
It seems like it only works if R2 is also ON. With both starting as off, turn on only R1, the R1 auto-off is not reporting for me. I tried 1s and 3s. This hub is also on beta so could be related to one of the beta changes which I am testing. Not sure if you are on beta also?
Yep, also on Beta as well. So if both were switched on then auto off they would indicate?
Yes that what it is doing for me. This device has so many settings you can also get into conflict issues where things work in one case but not if some other setting is set a certain way.
ok that would work for now as I am only using one relay anyway
I switched my hub back off the (not to be discussed here) beta feature, I think you found a bug in the beta. Working fine for me now. With 1s it is so quick the hub does not even get the on event for the individual relay.
With 2s I can see logs correctly.
Thanks -- that latest behavior you describe (1" not even registering as an event) sounds super familiar to me from when I installed my 800LR Z17 (long ago before this beta).
I was drafting a response to Chad earlier to say that, so I'm glad you were able to confirm it.
I just remember that's why I ended up going with a 2" delay (which still works perfectly fine for the case of operating my GDO relay).
ETA -- at the time of my install, I just chalked that issue up to the fact my Z17 is out in my detached garage, so it's my farthest-away ZW device -- though paired LR, I figured maybe that overall distance contributed to the happens-too-fast reporting issue.