Recommended poll settings and program best practices

[DaveStLou]

I'm using to the MyQ Node server to open and close my garage door, set variables, trigger Blue Iris cameras and send me notifications.

The status of the door as reported by the MyQ Node server has some peculiarities that noticed:

• Opening the door using ISY programs the status changes to "Opening" for about 10 seconds and then back to "Closed" for 10-20 seconds before it changes finally to "Open".
• Closing the door using ISY programs is similar. The status changes to "Closing" for about 10 seconds then back to "Open" for another 10-20 seconds before it changes finally to "Closed".
• When opening the door externally via the app, the status never shows "Opening" but reports "Closed" for 90 seconds or more before it reflects the "Open" status.
• Similarly, when closing the door via the app, the status never shows "Closing" but reports "Open" for a minute or more before it reflects the "Closed" status.

I have the short poll set the default of 10 seconds and 60 for the long poll.

My question is what the recommended poll setting to have the timely status updates?

Also, what are best practices, recommendations, lessons learned, or examples for programs to have variables, cameras, notifications quickly let me know if the door is open (or opening/closing) and then again when the door is closed?

Thanks!

[Goose66]

When doors have been idle for some period, the Node server is in "inactive" polling mode and polls based on the longpoll setting. When a door state change is detected or a command is sent from the ISY, the Node server switches to an "active" polling and polls based on the shortpoll setting. It remains in active polling mode until there have been no more status changes/commands for 3 minutes. This accounts for the behavior you mentioned on closing because of the 10 second or so alarming period before the door starts moving on remote close (see # 6 in the release notes linked in the pinned topic - https://github.com/Goose66/NSDocs/blob/main/myq-pg3.md). This also accounts for the status taking a minute or more to show up when you open the door via the app and the Node server is in inactive (longpoll) mode. However, I have not experienced this type of behavior on an open, in that when I send an open command from the ISY the door begins to move almost immediately (1 or 2 seconds).

The purpose of this rather convoluted process is that it is important for the Node server to appear like an instance of the mobile app to the MyQ service. Remember that the MyQ Node server is a hack and not an (officially, at least) approved usage of the MyQ API. If we have a bunch of node servers pinging the MyQ service every 10 seconds 24/7, they will detect this and lock us out!

[DaveStLou]

Thanks for the explanation, @Goose66

You're right, my door starts moving nearly immediately. It's only the state as shown in the AC and UD Mobile app that is not timely.

With this understanding about polling, it makes the most sense for me NOT to use the MyQ app to open the door but instead use my ISY whenever possible whether that's via the UD Mobile app or by a REST call to trigger the door through the portal.

By the way, the link in the PG3 store for the MyQ Node server generates a 404 error as it points to https://github.com/Goose66/NSDocs/blob/main/MYQ-PG3.MD instead of the correct url: https://github.com/Goose66/NSDocs/blob/main/myq-pg3.md

You might fix that store link and the link in your reply above too, since it has a trailing "." which also ends up as a 404 error as well.

Thanks again!

 

[bhihifi]

@DaveStLou Have you thought about what happens if the door is opened using the GDO wall keypad or the in-car remote?

These openings don't come from an app or program so I wonder if you can have the same actions triggered when the door is opened another way and still do a Force Query first.

[DaveStLou]

12 hours ago, bhihifi said:

@DaveStLou Have you thought about what happens if the door is opened using the GDO wall keypad or the in-car remote?

These openings don't come from an app or program so I wonder if you can have the same actions triggered when the door is opened another way and still do a Force Query first.

Still a work in progress. I'm still scratching my head on how to trigger the Force Query in those scenarios and others.

[bhihifi]

On 4/4/2022 at 7:03 AM, DaveStLou said:

Still a work in progress. I'm still scratching my head on how to trigger the Force Query in those scenarios and others.

@DaveStLou

If you had a motion sensor monitoring the driveway, it could trigger the Force Query, then if the GDO was activated (such as when the driver uses an RF remote), you could know sooner that the door was opening without polling the MyQ service. But will the motion sensor trigger fast enough to make this work well? I'm going to experiment with an Insteon sensor to see.

I seek a way to turn outside lights on when the garage door is opened at night. Coming from inside, the program is not really needed since the outside light switch is next to the GDO control. I only need to have them switch on if opening from outside after dark, so the motion sensor might do the trick. 

Of course, you could have the motion sensor turn on the lights regardless of the GDO, as a safety measure, in which case the GDO status does not matter.

I also implemented a turn off timer program to switch off the outside lights after 10 minutes so they don't stay on all night if someone comes home and forgets to turn them off.

[DaveStLou]

16 hours ago, bhihifi said:

@DaveStLou

If you had a motion sensor monitoring the driveway, it could trigger the Force Query, then if the GDO was activated (such as when the driver uses an RF remote), you could know sooner that the door was opening without polling the MyQ service. But will the motion sensor trigger fast enough to make this work well? I'm going to experiment with an Insteon sensor to see.

I seek a way to turn outside lights on when the garage door is opened at night. Coming from inside, the program is not really needed since the outside light switch is next to the GDO control. I only need to have them switch on if opening from outside after dark, so the motion sensor might do the trick. 

Of course, you could have the motion sensor turn on the lights regardless of the GDO, as a safety measure, in which case the GDO status does not matter.

I also implemented a turn off timer program to switch off the outside lights after 10 minutes so they don't stay on all night if someone comes home and forgets to turn them off.

I still have an Insteon contact sensor on my garage door that I took offline when I installed MyQ. I'm thinking about re-enabling it so I could use it to trigger Force Query.

It does make the value of the MyQ less than I had hoped. It ends up being a belts-and-suspenders solution.

[bhihifi]

@DaveStLou Alas, it won't be the last belt & suspenders solution in your HA setup.

I got the MyQ before I got the Polisy so I was happy to have the MyQ app just to avoid the  "I drove away and can't remember if I closed the door" issue that inevitably resulted in returning home to check and annoying other passengers ;-).

I've been thinking about the same issue and the only other option would be to Force Query in large time increments (every 10 minutes?) and hope that it persists long enough when you need it.