Garage Door Ghost

Is that one of the pre-made buttons with the pig-tails or did you make it yourself?

What do your childs look like? Show from devices list, showing DNIs (like this)

On this post above Garage Door Ghost - #9 by philippompili

The logs are not making any sense to me.

  1. You pushed Closed on Homekit (so assuming door was open?)
  2. About 300 ms the virtual door reports is it open? Does not look like the door moved
  3. About 5s later relay flipped on/off again and door thought it was now closing
  4. Again door reports it is open right away and then nothing
  5. Another 5s and relay flips on/off again, door is closing
  6. Finally this time the contact sensor reports the door is closed
    About 12s for the entire sequence, probably the time it takes the door to close. So not sure why relay triggered 2 other times during that sequence?

Your other newer log you posted does not show a whole lot, but again no logs from the contact sensor.

Looks to me like either your contact sensor is not working right, or the Z17 is having a hard time communication with the hub. Could be a range issue or the mesh is trashed.

Possibly something is shorting the R1 but that should not trigger the relay on or off, it would only trigger the GDO itself and you would just see the contact sensor reports after the door was done moving (same as if you pushed that button).


Couple of settings you could change
Input Type S1C (#2) you dont have an input connected, just change that to the default.

Auto Off on R1 (#6) I would set that to 2, and change units to seconds. That would be the most reliable way for it to turn back off, the setting on the GD app will work as a backup.

Referencing your logs, what devices (or apps) are "dev:613" and "dev:1809"?

It looks like you have a (relatively new) Tailwind contact sensor but that wires from it going in to your Z17 look really old & beat up -- are those the wires that came with the Tailwind or is there a junction somewhere in between? Or maybe that's all just a weirdism with the picture such that that they look like that.

HI @jtp10181

  1. Pre made. Bought it specifically for this purpose. Used to have a normal garage door motor and when I upgraded to a wall-mount, the old (better) system no longer worked because of the new security in the buttons.
  2. Logs; I started the screenshot when i asked Homebridge to close the door. The rest of it doesn't make sense to me either. the contact sensor doesn't report back until the final open/close, yes the Z17 is clearly reporting as we can see the logs.
  3. As for the contact sensor, that is a new addition, but this problem existed prior to the contact sensor being installed. I sued to use a wireless one. I thought using a wired one right to the unit would make things better. (wrong)
  4. O thought about a short too, and I tried shorting it manually, and yes the contact sensor reported every time.
  5. I'm going to change those 2 settings #2 and #6.

@hydro311 #613 is the Garage door App
#1809 i the Garage Light Switch. (automatically turns on ro off based on motion and contact sensors)

Wires look beaten up because I repurposed cables that have an old cloth shield. Did that so I could hide them a little better. The wires are fine though. There is a junction in between,. The wires were not long enough coming from the contact sensor. Using a WAGO221. The connection is good (despite the shotty appearance)

Also, as a result of the changes made on the device;
[1:0, 2:2, 3:7, 5:0, 6:2, 7:0, 8:0, 9:0, 10:0, 11:0, 15:1, 16:0, 17:0, 18:0, 19:0, 20:0, 24:0, 25:5, 26:5, 27:0]

I've also removed the Auto Off on the App.

1 Like

Hopefully Jeff's suggestion will work well... I'm probably just being a nervous nelly, but if you change param 6 (and 15) to 2 seconds, I'd change the app's auto-off to 4 or 5 seconds (instead of also leaving it at 2).

It should be fine either way, but padding the backup a bit helps ensure nothing collides. My param 6/15 is 2", and I use 4" as my backup off time. I do my backup timing via a rule instead of the app, but it shouldn't matter either way.

Yes I would also do this, if the app detects the relay turns off by itself it wont fire another command so it works as a backup.

Also :point_down:

Hmm... reviewing all the details again, feels like some sort of a z-wave transmission issue.

Can you also post a chunk of you z-wave details page that includes this ZEN17. Just one full page screenshot is good for now so I can see the Z17 and some other devices to get a general idea of how things look.


So the Zen16 is also in this screenshot (which is sitting in a drawer right now)

Is this screenshot giving you what you need? Should I be looking for something in particular?

OK. 5 seconds it is. All other paras are unchanged.



Device list with DNIs (sorry, missed that request in an earlier post)

I forgot you have a C5, z-wave details is useless...

My only thought was if the hub is not getting an ack back from the device and it sends the command out again, but 5s is a hell of a delay, I dont think it would take that long.

You could turn on debug logging "Indefinitely" on the ZEN17 for now, that would give a tiny bit more detail. Also turn on both normal and debug logging on the Zooz app.

If it does it again grab some more logs. You can filter them down to the relevant apps/devices by selecting multiple devices in the filtering drop down. Maybe with the extra info it will make a little more sense....

Last questions, in the log I put the numbers all over, did the door perform as expected, you hit close and it closed? Despite the extra relay activations? Thats kind of what it looks like. Have there been other times when the door just opened by itself?

Yeah, those logs have some odd (and inconsistent per instance) timing stuff going on... Because of that, I'd agree that someting is getting lost / mixed-up in the mesh traffic.

Have you timed (stopwatch) how long it takes for your door to go up / down? Each is typically ~15" (which is why the Zooz app defaults to that value), but if yours is definitely longer/shorter than that, that may be a wrinkle in this too.

In an abundance of caution, you could try something like my setup... My goal is to never "touch" the relay with any unecessary commands (even a backup off):

I have the Z17 relay params 6/15 set for 2", but I leave the Auto-Off disabled in the Zooz GDO app. My backup rule looks like this ("GDO Button" = Z17 relay)... It shouldn't ever trigger unless the relay missed its own parameter-based 2" auto-off call (which hasn't ever happened AFAIK).

I thought the app did the same thing, if the relay is already off it skips its off command. Maybe not though, maybe it always tries at least once.

That could very well be true, and awesome if so... I just didn't know for certain, so I did the rule instead. It's admittedly a big abundance of caution, and admittedly shouldn't be necessary.

I'm just particularly paranoid about minimizing any/all touches to that relay -- I figure the less times I tell it to do something, the fewer chances for wires to get crossed :wink:

@hydro311 @jtp10181 thanks for all of this.

I'm going to make sure that Debug Logging stays on for all of the involved devices and apps.

@jtp10181 The Door does perform as expected. If I use the Hubitat App, clicking on Open trigger an open command immediately. Same with close. It all works as expected. Yesterday morning, (and other mornings from what I can tell) about a minute later after the garage door was closed, it reopened again. Closes itself, opens itself, closes, and then stops. I have a camera in the garage, so I caught all of this on video. I only noticed it this morning because i was going through my Homekit logs (as one does) and noticed the behaviour.

@hydro311 Good point on timing the garage. I'm going to do that today. I'm going to take a look at your backup rule as well, but won't build it until I've troubleshot everything else.

Again, thank you both for all of the troubleshooting and advice. I'm going to keep an eye on it and report back.

1 Like

Hello all, just wanted to report that there have been no ghost openings since my lat post on 29 August. This fix appears to be working.