where you able to find a solution? zooz keeps advertising their tilt sensor but I can’t seem to make switch the state of open and close to match that of the tilt sensor.
The instructions linked in a different response seem to work well and apply to other virtual garage doors. [ST EDGE] Zooz Edge Driver Channel - #281 by MarkTr
for the actual ZEN17. what settings did you use for the garage door?
The relay itself is a means to send commands to open or close the door. Setting relay input as “Garage Door” makes it act as a momentary switch. Actual open or close status of the door is handled by tilt or contact sensor. Caveats, of course for MyQ garages.
Sorry I’ve been MIA, but I’ll respond to everyone within the next few days…
Is anyone else having battery issues with Zooz ZSE42 XS Water Leak Sensor. I replaced all the batteries 2 weeks ago and now they are reporting low battery.
Yes. Ditto the XS contact sensor. Not all of them for some reason. Wonder if it’s the type of battery for some reason (I’ve been using Duracell) or firmware (mine are 1.1). So when I get a chance, I was going to update firmware and also try a different brand of battery.
My five ZSE42s have gone through a dozen batteries in the ten months they’ve been in place. I upgraded firmware to 1.4 (the upgrade process probably used a fair amount of power). My ZSE41 is down to 43% over the same time (with no firmware update).
Measuring battery level is tricky - current draw might be over spec but it could also be bad voltage measurement.
I don’t think it’s a short check-in interval problem - these devices intermittently show as “offline”.
I don’t have ZSE42’s but have had a problem with ZSE41’s, it maybe a weak network?
I have two particular Zen72’s that would drop off and need to be paired again. One or the other would nearly always drop when removing other devices. They are both mounted in a two gang box with a GE fan controller which never drops. But they are the furthest switches from my hub. I added a z-wave outlet close to each them, updated the firmware and moved to edge at the same time and so far they have appeared to be rock solid. I added the z-wave outlets as close as possible to two Zooz ZSE41 open/close sensors that would discharge rapidly when the Zen72’s went down, the low battery notification was usually how I found out the Zen72 was offline as they are in the least used rooms in the house.
For the Zen17 universal device, what are the odds of getting the S1/S2 inputs configured such that one of the options for sensor is “smoke detector”, so I can use the built-in Smartthings routine with this instead of needing to setup a separate automation? Not a huge deal, but it would make things a little cleaner with the ST app. Thanks.
I am having the same issue with my ZEN17. The relays wont auto turn off even after setting the R1 Auto Off parameter to 2 seconds. I am also running 1.03. I just bought the unit on Black Friday. How do you fix this bug?
The battery levels jump around a lot so I’d wait until the battery level is really low for multiple days before replacing the batteries.
I checked the ZEN17 Change Log and what you’re seeing appears to be a firmware bug which is fixed in firmware 1.04 so you can fix it by updating the firmware.
Based on the description of the bug it sounds like you might also be able to fix it by changing the input type to Momentary, but I haven’t tried that…
It won’t be that difficult to do, but I have a lot of other things that need to be created and/or fixed before I can work on enhancements…
The originally had the wattage reporting interval of the ZEN25 set to 30 seconds instead of 5 minutes, but I fixed that back in September.
The handling of multiple z-wave reports sent to the hub at the same time is much more unreliable with drivers than DTH which is why it’s important to disable or reduce the number of reports being sent for metering devices.
The high value cap for what’s ignored is higher with the driver so if I lower that it might solve the problem, but that would only be the case if the values you’re seeing are occasionally higher than expected.
If you’re always seeing values outside the expected range then swap what’s plugged into that device with one of the others to see if it still reports the expected values.
I kept running into the same issue and than I realized that the device won’t report motion when the cover is open so maybe that was the issue.
I double checked the setting in the profile for the 32.32 firmware and none of the default values are outside of the specified range so I have no clue what could be causing the settings not to get displayed.
Since I can’t reproduce it and no other users have reported it the only thing I can think of is to remove the device and factory reset it.
Are you still seeing this problem and if so, do you also lose the ability to control it manually with the physical button?
Hi @krlaframboise yes, I still see that issue, and yes I losing the ability to control it manually with the physical button (I need unplug and plug again)
The loss of physical control is a hardware issue so you need to contact Zooz support.