Look at that, yes interesting.
Just heard back from Zooz about an issue I had with the Z51's latest 1.80 firmware...
You're going to hate this news with repect to your driver's future direction, but they confirmed that 1.80-equivalent firmware is not possible for the original hardare Z71s -- 1.80+ can only work with the ver 1.30 hardware models.
So for folks like me with the orignal-release hardware version, f/w 1.70 is (and will effectively remain) the end of the road.
I'm guessing all this applies equally to the Z52 too, but I don't have one myself.
The fun never ends!
Yeah I already knew that from discussions with someone else. @CuriousB I think via PM. I assumed Zooz had made this notation on their firmware downloads, I had not looked at it myself. The tricky thing is Zooz is calling it "hardware 1.30" when on the device itself it says "1.30 firmware" and nothing about hardware, and there is no where else to see this in data pulled form the device only by physically inspecting it.
@hydro311 So did they replace your device or advise to re-flash a prior firmware?
Actually does not matter much because I always account for backwards compatibility. I already have the ZEN16 driver working for v1 which does not have split sensors, and v2+ which can split the sensors. So no a problem really, just not a trivial update.
2 Likes
Yeah, it never jumped out at me that they snuck in that 1.30 hardware change -- it must've just been something unexciting in the guts, since was no "new chip!" or "now with LR!" sort of fanfare 
They hinted that they may be able to replace mine via warranty, but since my only issue is that my LED doesn't work as advertised on 1.80, I can live with that -- it's otherwise performing totally fine now on 1.80.
I asked them to let me know if they'd recommend rolling back to 1.70 for any reason, but no response yet -- I'll let you know if they do make that reccomendation and why.
But I may just roll back to 1.70 anyway -- heck, it perfectly worked fine on that too (and I'd get my LED back).
Glad to hear this wouldn't be too much of a helmet-fire with versioning -- I forgot you'd already been down this road with the Z16 -- good stuff!
I'll follow up again if any interesting respnse from Zooz -- thanks again for your tireless efforts on this stuff!
1 Like
It's a bit out of character for Zooz, they ignored their own standard h/w numbering and firmware numbering scheme for this one device. In fact they don't even show the 1.70 firmware on the OTA page but it is the terminal firmware load for the older h/w versions.
I have a few dozen Zooz devices in my home but only one of this device. All the others seem to comply with their hardware and firmware numbering norms.
Maybe the installed base is so small for this device it isn't worth the trouble of making changes to bring it in line. A bit more commentary on the OTA page would be helpful though.
1 Like
Feature Request!
I have a ZEN 51 Dry Contact Relay and noticed that in the Zooz firmware update (V1.80) they have added a new parameter (13) to separate the input from the output. If this parameter is set to 1, I believe the input is purely reported by the relay and the output can be controlled independently. However the driver does not support this feature, is it possible to update it?
Already discussed above:
[DRIVER] Zooz Relays Advanced (ZEN16, ZEN17, ZEN51, ZEN52) - #204 by jtp10181
Sorry, Zooz suggested I ask you directly, should have searched the posts first! Presume any update will be flagged in the Package Manager.
I will probably do a beta first, you can follow this thread for any updates:
[BETA] Zooz Advanced Drivers BETA Updates
23 posts were split to a new topic: ZEN16 800LR sensor status not updating
Hey! I'm a noob when it comes to Hubitat but I learn fast 
I bought a Zooz Zen52 to control my (roller) shutters.
Managed to include the device and made it kind of work.
The issue I'm having is that once the shutter reaches to totally opened or totally closed position the motor continues powered on. Is there a way to time the ZooZ Zen52 to open the circuit once the shutters are fully opened/closed? Alternatively, could I set a timer so it opens the circuit after a few seconds?
And is this driver the same one that's used natively by Hubitat, or do I need to install it apart?
Thanks for your work!
This is a community-developed driver, not the native/system driver Hubitat has.
Community-developed drivers (and apps) are sometimes created to fill a gap where there is no native version, and other times they bring more capability/features than the native version. This driver is an example of the latter.
The native/system drivers are typically designed to support basic (most commonly used) functionality without potentially overwhelming a (net-new) user by exposing every possible option/feature/capability. They are intended to give a reasonable balance of functionality and ease-of-use.
Basic info on switching between drivers can be found in the Documentation here, and there's a link to basic info about installing custom (community) drivers at the end of that article. Most developers inlcude install instructions at the beginning of their topic thread (like the first post in this thread).
2 Likes
Thank you so much @hydro311!
Do you know if the community driver offer functionalities to help me solve the issues bellow:
Issue 1: The button states don't automatically switch back to "off" once the shutters are fully opened or closed. Is there a way to set a timer so the button returns to the off position after a few seconds?
Issue 2: I'm using momentary physical switches, but I'd like to be able to press the button once and have the motor run all the way up or down with that single press. Right now, I need to hold the momentary switch to keep the relay circuit open. Is there a way to configure the ZEN52 so that one press tells the relay to open or close the circuit and stay in that position?
Thank you!
I unfortunately don't have any experience with the Z52 or using a relay like that to control blinds, but hopefully someone else will be able to chime in.
1 Like
Typically, all the Zooz products do AutoOn or AutoOff.
See link for ZEN52 advanced settings below.
While I don't have a ZEN52, @jtp10181 's drivers usually support this.
The documentation says 700 series and LR, so maybe no big changes on Zooz' part, for which @jtp10181 is doing changes.
Try installing @jtp10181 's driver and see if it works. Set it to AutoOff in X seconds.
Let me say also I don't have auto shades. Perhaps someone who actually uses this setup could answer best. Maybe create a separate thread? 
https://www.support.getzooz.com/kb/article/805-zen52-double-relay-advanced-settings/
I use a ZEN51 for a garage door opener. The dry contacts simulate a button press akin to the side of wall button. In this case I set Parameter 2 to 1 (auto off after 1 unit) and Parameter 10 to 2 (units are in seconds). The result is the relay closes for 1 second then opens each time activated. This is all supported in the preferences section of the driver.
Not sure if you application needs the button pressed the exact duration of the shade "rollering" or just quickly once to initiate the cycle. Hopefully not the former as that might not be as repeatable as you would want.
Not me. I'm good.
@gugavieira is the one seeking knowledge.
Why didn't you get a ZEN53, specifically designed for shades?
I believe everything you asked about could be done either with my driver directly, with one of the rule apps built into the hub.
Yes, Parameter 20 and 21, Momentary option, which are exposed with my driver:
https://www.support.getzooz.com/kb/article/805-zen52-double-relay-advanced-settings/
Combine that with an auto-off setting for the max time you want it to run.
1 Like
