Hello all. Been a while since my last post. I'm having some issues with my Garage Door opening unexpectedly. I am using a Zen16. As you can see from the logs, when I trigger the garage door (you'll see the line "Command" underneith), the Garage door opens. But then other times, you'll see that it opens without a Command. I'm not sure what is triggering it, but it's a little terrifying. I do have it integrated though Tonesto's Homebridge, but those commands are all logged. It seems as if the Zen16 is triggering on it's own. Thoughts?
You'll see the event window for the Switch On, on the 3rd row of the screenshot. No one asked the door to open there. You'll see my command for Off on the line above it and then the Multirelay sending an off command.
You are correct in assuming that if the command originated from the hub, it would be shown in logs. This appears to be originated from the device itself rather than internal to hub. I am not familiar with the Zen16 relay, but if my Linear garage door opener would do that, the first time it would happen, would be the last time the device was online.
I looked at the Auto-On/Off and thought that may be it too. I just disabled it after posting my first query. This started a while ago, but I thought that it may have something to do with Homekit, so I was playing around there first.
I'll monitor everything and see. I also suspect (wont know till I get home) that there may be a short somewhere. I'll check that too and report back .
Thanks everyone for all the advice. I'll do some testing this evening and report back.
Ok, so from what I figure, the relay was always set to Toggle mode. The Auto On/Off was also active. I turned off the Auto On/Off, and then went to change from Toggle Mode to Momentary (Garage). I couldn't change the relay mode. Nothing I did would work. The device just kept reporting back Syncing, 7 changes pending. There were a bunch of settings on the multi-relay that I was unable to change. tried power cycling, but nothing worked. So I went an updated the firmware. I'm on a C5 so I used the Z-Wave Firmware Updater. I downloaded the latest firmware and tried to flash. About half way through, I realized that I was flashing 2.0 to a 1.0 (hardware) device. I thought I had bricked my Multirelay. I Power cycles and re-paired the unit. Magically, it paired and reports a firmware of 1.2 (I can't explain). But in any case, I was able to set the relay to Momentary (Garage). It all works now. No phantom opening for now.
Hello folks, I recently upgraded to a Zen17. I was still having ghost opening issues. I thought everything was ok, and now, today, checked again and another ghost opening.
The lines coming from Homebridge are legit. Everything above that is an opening that wasn't authorized. Now this seems to happen once or twice and then never again throughout the day. It also only appears to be happening after an initial authorized opening.
Is the Z17 the latest model (LR-capable)? What driver are you using for it?
If you're not using Jeff's driver, I highly recommend moving to his - it's excellent, and exposes all the go-to parameters.
The auto-off parameter was wonky in some earlier versions of the Z16/7's firmware, but it's now working well on mine (latest gen Z17 on 2.00 f/w).
Double-check to ensure that your parameter-based auto-on/off settings on the relay are not conflicting in any way with the 2" auto-off you have set up there in your Zooz GDO app. Set auto-off in one or the other (relay or app), but not both.
Huh, yep, that looks good to me. This is odd then... I've never had a ghost opening action on any of my various Z16/17s I've had over the years out in my detached garage, so I'm not sure what to suggest next.
Are the logs you posted earlier the full logs at those times, or filtered? Is there anything else in the logs at the same time of the ghost activations that may hint at a connection?
What’s your power restore setting set to? Set it to always off. Otherwise if you have a power blip there is a chance it decides to activate for some reason.
Otherwise, according to your first post it does appear that it is activating by itself. Either from an input trigger or some sort of malfunction.
@hydro311 Its pretty busy here, but I don't see what would be triggering it. @jtp10181 Set to always off (unless I'm missing something int he parameters.
Just so its clear, this started happening under my Zen16. I tried a bunch of troubleshooting and now I'm on a Zen17. I thought the device itself was the problem, but now it looks like I was mistaken.
