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!

@brians Yes, it had an intermediate folder in the zip file ("evldsc-pg3-3.0.8") in the zip file, as you noted (I uploaded the wrong zip file). I think @bpwwer noticed it and cleaned it up for us. Trophy emoji to Bob!