I’m using a zooz zen17 for a garage door opener relay.
The clicker receiver is connected to the zen17 input (S1) and the zen17 corresponding relay (R1) is connected to the garage door opener.
The clicker receiver sends a signal to the S1 input that last for about 1/4 of a second. The zen17 automatically closes and then reopens the R1 relay for the same 1/4 second which is more than enough for the garage door opener to see the signal and open the door. This works without issue.
My challenge is that sometimes the S1/R1 is “on” for such a short period of time, that SmartThings never “sees” that the Zen17 was ever on at all. I have other automations/Scenes that get triggered when the Zen17 relay is turned on (lights and other things), however, during the times that SmartThings doesn’t “see” that the relay was on, it doesn’t run the Scenes.
This issue seems most likely to happen whenever my hub has sat idle for a while.
The hub is close to the relay…maybe 15ft max.
No, direct association is not a solution for this as I also incorporate SharpTools which needs the SmartThings hub to actually “see” the signal.
Zooz has updated the firmware on the Zen17 to allow for a new parameter to adjust for this, however, the SmartThings Driver for the Zen17 doesn’t take advantage of this new parameter yet.
Suggestions or am I out of luck until the driver gets updated?
So you don’t need the lights to turn off again when the relay closes?
If so, use zwave direct association to have the relay turn on a Z wave smart plug, which does not turn off again immediately and then use that smart plug coming on as the trigger in your smartthings routines.
I’m not sure when you want to have the plug turn off again, though, so that it’s ready for the next time.
So my lights are on a different hub than the zen17’s, so I can’t direct associate to them.
However, I’m pretty sure I have a smart plug that I’m not using at the moment that I could use as a bit of a sacrificial device with direct associate to act as my surrogate “longer signal” to make everything (including sharp tools) work more smoother with the short pulses.
Zwave direct association allows the trigger device (the zen17) to send a message directly to the target device (zen15) without going through the hub at all.
A routine wouldn’t work in this situation because if it did work, you wouldn’t need to do this. The whole point is that the hub is not always getting the message that you want it to. (or I suspect it is receiving the quick off before it runs the routine.)
Anyway, let’s try it and see what happens. We may need to make one more adjustment, but I’ll hold off on that until I see if it’s necessary.
Ok…after a dozen tries finally have both installed on the same security level. The Direct Association DOES work. However, the Zen15 now mirrors the Zen17…the Zen15 goes on and off with the same 1/4 second duration.