It would be nice if there would be an option to turn on (or flash) a light for X seconds before the door starts closing.
My use case:
I would setup a color bulb to turn red for X seconds when a request is made to close the door.
I have had one situation occur where I manually opened the door while backing in the driveway and then shortly after, my door opening rule kicked-in but instead of opening the door, it closed it. Could have been a problem if I hadn’t noticed it and it had closed just as I started entering the garage!
To help with this, I will add the color bulb in a spot where it will be very obvious when backing in the garage so we will be warned if it is closing while we are backing in.
I guess if your garage lights were connected you could build a rule to flash the garage lights, have a 5, 10 or whatever amount of seconds wait and then open the door. Maybe build the rule with conditionals time of day, luminance, presence or motion in the garage area to determine when the conditionals would become relevant.
What would really be great if there was a way to connect to the MyQ hub which has the audio and visual warnings when the door closes from the MyQ app.
I'm seeing the status change to open/closed almost immediately upon activation of the actual door from the dashboard. Does this driver not wait for the tilt sensor to change the status? It's very obviously not changing based on the sensor.
So, V-Switch turns on The Flasher application starts Flashing lights about 5s before the Rule to close the Door starts. With the V-Switch is turn off (auto off) it will wait another 5s (configurable) then close the garage door with the lights flashing..
The timeout is set at 25 seconds. If I hit open or close from the device details screen, the contact status changes immediately, so I know it's not using the physical contact I defined in the setup. Am I wrong to expect it to use the physical contact or tilt sensor?
Ah! Right. Sorry, I looked at the message too quickly and thought you had made an update in the app code for this. That said, it’s a very good workaround!
Ah I should have stated that yes I intend to use a Zooz zen16. I guess this driver is open where you can use other devices as well, so that is definitely one difference.
Possible I will need to try both with the zen16 and see if there are any differences in behaviour myself. I was just attempting to be lazy.
If I understand it correctly the default (configurable) timeout of 25s is the amount of time the app waits to compare what was requested (open/close) vs what the contact/tilt sensor is reporting - not a delay in action. Then the virtual GDO is showing "status" based solely on the reporting of the contact/tilt sensor - which changes on mine about 2s after it starts opening and changes to closed about 2 seconds before it finishes closing - directly matching the status of my tilt sensor reporting.
Okay, added local control couple weeks ago - still not where I want it to be. Had issues with Zooz GDO app and decided to try this one. So far, this looks promising - have to test departure/arrival routines and see how it goes.
A couple of things - I also would love a "built-in" capability to play a sound/siren and/or flash a light. I too have manually opened my door on arrival because the local routines had not kicked off yet only to have the GDO start closing (thinking it was opening) as I started into my garage - not good.
Second issue I've yet to solve is the fact the app strictly relies on open/closed status of my tilt sensor and doesn't know if the door is "stopped" ala not fully opened. I often open my door 6-8" to facilitate heat dissipation and regardless of whether the tilt says "open/closed" a button push will ALWAYS close the door. So if the app/vGDO thinks the door is closed and an open request is called the GDO just knows a button was pushed and the door comes down. That DOES cause the app to recognize the door "failed to open" - but that is not until after the timeout (which I have at 15s). In testing I have found there are times where I have to cycle the door a couple times before it gets back in sync with reality.
I'm using this app for a gate opener. On my dashboard, I'm using the Garage (Control) template. Is there a way to eliminate the 'Are you Sure? Yes/No' prompt each time the button is pressed?
That's not part of the app that is a dashboard feature forbthay device type. Add a virtual switch and rule that sets the garage door to open or add the garage switch (not door )! to the dashboard
Howdy All, I've been using this app for a really long time ... however every now and then (eg 1 out of every 5 times) it doesn't actually open my garage door. The garage controller doesn't appear to be the issue and has a good z-wave connection directly to the hub.
My relay "auto-off" is definitely a long enough duration too.
The only thing I can't prove 100% is the app. It feels like sometimes it just doesn't trigger the relay but it does change the virtual door state to open - I know this as I get the notification.
I'm wondering if the app is turning the contact on/off rather than letting the controller manage this?
