Love this! The only other step might be to add a USB battery adapter for the coin battery.
2 Likes
I made a 3D printed housing for the ZG-2001 Zigbee Relay Switch. I don't think I can post the STL files in the forum, but if you're interested in printing your own just PM me. I could also print one and mail it to you if you want.
8 Likes
Stupid Question Time!
My contact switches have Common, Normally Open, and Normally Closed connections. When and why would we use normally open vs normally closed? I know - obvious, right?
I ask because when I was initially wiring my open and closed sensors to Zen17 I was only able to get them to report using NO. NOW I'm seeing they are failing to report on initial change (closed to open) which is hosing my rules because they don't report until after a full open full close cycle THEN report correctly.
Is the circuit only "tested" for open/closed at certain points?
These are used in different scenarios but in your case you want to use NO, normally open. Think of the button you are pressing, normally it’s not pressed meaning it’s “open”/aka not connecting a circuit. When you press it, it completes/closes the circuit until you release the button.
NC can be useful with security contact sensors. I have a zone on my security system that monitors 4 windows in a room. They are “normally” closed but when one opens (not all), the security system senses that one of the windows is open. It doesn’t know which one but the fact that one is open, it breaks the circuit and thus the security panel knows one is open.
Hope this makes sense.
1 Like
Right, for the GDO contact it is definitely NO and closes to push the button. But my reed sensors would not report at all when I tried NO - they only report when used on NC. ZEN17 doesn't have a "choice" for NO/NC on the sensor side, just S1/C or S2/C.
The real question is why do my closed sensors fail to report open when the GDO opens the first time. Feels like they are sleeping and don't wake up the first time the GDO cycles. And it only seems to happen if GDO has been closed for > 24 hours. Weird.
Inspired with the solution here, I roll up my own garage door switch without any relay. I have been developing this for a couple weeks and document them in the Environment sensor thread. I am really close to install it on my garage. I need to buy one more reed switch. I think it is time for me to share my solution here. Perhaps, it could help someone here.
I notice the remote (at least chamberlain, liftmaster and craftman) is a 3V device. I think it should be safe to connect the buttons to a 3.3V MCU and toggle GPIO to simulate a button press. I have a drawing on what I think about how the button works.
I used a clone arduino UNO which operate on 3.3V. I hook it up to Zigbee Environment Sensor which also act like a Thingshield. Here is how it look like. I transplant the GD remote on the second mezzanine.
Here is 37 seconds demo video.
Since, it is over kill to use arduino to just push a button, I added a few sensors on the board. I have a couple contact sensors. I have motion sensor and vibration sensor hook up as well. Here is how they look in hubitat.
As pictured, I am able to click buttons on my remote. I can monitor temperature, humidity, pressure, light of the garage and detect power outage in the garage. I am hoping that I can use the vibration to tell me the door is moving. I am able to detect motion inside the garage. At this point, I am able to detect whether the door is fully open or closed with 2 contact sensor.
I am sorry if this is too long. I primarily just want to share that the garage door remote may work without relay. You can simulate the button click with simple GPIO toggle with an 3.3V MCU. Toggling this way is very fast. I set mine to toggle in the order of 10 milliseconds which is probably unwise to do with a relay.
3 Likes
One issue I am continuing to fight with is when I want the GDO to open based on presence and if wife and I arrive together HE sends the "on" command then sends it again - which stops the door from opening. I've put some logic around it based on 2 contact sensors plus my multisensor for vibration, but still don't have it quite right. Works great if one of us leave or arrive, but not for multiple.
Here's a dumb question that might help me fix my GDO issue.
If a virtual switch is "on" and a rule turns the switch "on" does that trigger a 'turns on' trigger? or does 'turns on' have to mean changed from another state to "on"?
I have not gotten to setup my rule yet. My plan in this scenario is to check the contact sensors status. I am thinking to ignore any momentary button push command when your door is "opening" or "closing". A door is in these states when the fully opened and fully closed contact sensor is not engaged. Would that work to solve this particular issue?
I'm using LGK Virtual Garage Door.
Using the built in virtual switch driver, if it’s turned on a second time while already in the on state, it will not create a new trigger. And yes this will work for you.
Edit: as a side note, this virtual switch drive has the option to do just that, send another event if the switch is turned on and is already on. Useful in some cases.
I currently have the Zooz GDO installed, but I do NOT use it with my automations because it accepts multiple pushes of open or close and causes the actual door to stop or reverse when undesired. Part of the problem is the app accepts additional "pushes" while the door is in "ing" state. i.e. if door is opening you can push either open or close and it will trigger the door to stop where it is. If the door is closing you can push either button and the door will reverse and open.
Not sure if LGK vGDO behaves the same - might have to try it again.
I understood this point now. My switch driver does not have the contacts information as well. I do not think that my switch need this logic. I do not plan to approach it this way.
I am thinking to use RM as my automation(or an app). In this rule, I am imagining that I will pull in information from the contact sensors when my cars are detected. At that point, I will toggle the remote button only when the closed contact sensor is detected.
I think of my GD switch as my physical remote. I can have multiple physical remote and got into the same issue that you describe. I visualize myself as the rule (or an APP). In this rule, as I see my car approaching, I would click on my remote button if the door is fully closed. If I see a second car coming and garage door is not fully closed, I would not click on the remote. Just FYI, this is my plan. I thought I just share with you.
1 Like
Scroll back to my post Local Control Options for MyQ Garage Door Openers - Get Help / Devices - Hubitat
I'm using a GV to determine the status of the door based on 2 contact sensors and a multisensor. The I have a RM that uses this GV to determine if it should activate the relay once (closed to open) or twice (stopped to open). Have a separate rule to close on departure, but we almost never don't close it manually on departure. Not sure if that part works right or not, lol.
I have not review all of your rule and any suggestion you have gotten. I just want to bring one thing quickly that may happen. Have you consider what happen to your rule if there is a delay on the GD contact status reporting? That delay of reporting the status of the contact sensor could caused the wrong condition be evaluated when the second car comes in. I suppose if you turn on logging and track the sequence you may verified whether this is the case,
I been using Universal Security+ 2.0 interface module on my garage door opener for a little over a year now in combination with ZEN17 relay and Zwave+ tilt sensor.
Still works flawlessly for us and never had a single issue with it.
We use Homebridge to connect the garage door to our Apple Homekit on our iPhone.
1 Like
Can you expand on your usage? What are your triggers, what actions are you taking, which vGDO driver are you using?
I think I finally have mine working right. It is complex using 2 contact sensors and a multisensor (tilt/motion) and switched back to the LGW vGDO - Zooz vGDO was bad at sending repeated commands and messing things up.
This post are the steps I have taken using the interface module to trigger the opener with a tilt sensor. It have app and driver instructions which I follow to a T
I tried following that and it would not work for me. Problem is, the SmartThings MultiSensor takes 1-2 seconds to report "open" when the door starts moving. If two people "arrive" at the "same" time (> 2 seconds and < 15 seconds) the arrival routine tells Zooz to open the GDO and the second request causes a second trigger of the ZEN17 and stops the door. The LGW ignores multiple requests to open or close when it has already been triggered.
I would not want my garage door opener to ignore the multiple request.
Reason is that often I open my garage door a foot or so before sending a request again to halt it from opening any further from the closed position.
I think that how garage door operate or at least it how it operate for me for the most of my life when I own a garage door opener where you send a signal to the opener then when it open just enough like few inches off the ground or a foot then you quickly send a signal to halt it from opening any further.
This allow your garage to cool down on a hot summer or let your outdoor pet to enter without having to expose your whole garage out in the public etc.
3 Likes
