Goose66

Looks like someone created a PR at arraylabs/pyMyQ that is working for folks, so hopefully I can get it implemented quickly. Of course, the day job.......

You’ll notice that was a month ago. That whole userAgent thing prompted the latest version of MyQ as discussed in the other posts for the past few weeks in this subforum. This 401 error is new - maybe less than3 or 4 days old. But as I said only seems to affect people who restart.

Just so everyone knows, I believe this and most of the previous issues the past month or so have been done by Chamberlain to specifically thwart non-authorized access to their cloud service. Just so you all know what we're dealing with.

I am seeing this from users of the the arraylabs library as well (the library used by HomeAssistant integration). No solution yet from the developer of arraylabs. My node server in my production environment is running fine, but I haven't restarted it in the last several days (or weeks). I can bring production down tonight and then start it up in the development environment and play with the userAgent header and retry timing to see if I can get it working.

Everybody (including non Polyglot users) are dealing with this issue, but it usually only happens on reconnection (e.g., restart of the node server). Last three or four posts in this MyQ sub-forum all deal with this issue and it's evolution over the last month or so, so I won't repeat all that here. Suffice to say if you are running the latest version of MyQ (the one released to deal with this very issue), then shutdown the node server, wait 30 minutes or so, and start it back.

Oh, I hear you on the "if it ain't broke" thing. But seeing that it is a forum of geeks, if you throw out some speculation on what's happening at a technical level on something, you're bound to get a response or two! 😉

The 429 error is starting to crop up in other circles. Evidently there is a header included in these that specify how long you need to wait before retrying and the numbers are like 30 minutes or more, so I may need to rework the retry logic to find and start using this number on the retry. Note again this seems to be somewhat limited to when the node server is restarted and it has to acquire a whole new oAuth token for access.

BTW, I followed the chain starting here: You may need one or two more reboots than what's specified in the Wiki before everything is done.

That is the latest (and likely last) version of PG3. You should upgrade to PG3x. My upgrade went nearly flawlessly. Had to delete and reinstall one of six node servers.

Why would it be "my router" that is "allowing both the IP and friendly URL to reply?" I don't think my router plays any role in mDNS. I would think the two entries would be result of some sort of configuration issue on the Polisy (in my case) that causes it to respond twice to the same mDNS broadcast - probably a misconfiguration in the local network interfaces. On second thought, the two entries are more likely the result of being in transition from the old discovery methodology to the new mDNS discovery metholodgy.

Nevermind, just had to delete it and reinstall it.

No messages in /var/log/messages. This is what I get when I try to start it: [admin@polisy /var/log]$ sudo service 000db953da90_4 onestart Starting NS000db953da90_4. su: unknown login: 000db953da90_4 /usr/local/etc/rc.d/000db953da90_4: WARNING: failed to start NS000db953da90_4

FYI, a lot of people around the World, evidently, are noticing that removing special characters from your MyQ password can help reduce the errors folks are getting when their app token expires and they have to re-login to the MyQ service, e.g., restarting the node server.

Np. I recognize that there are inconsistencies in the way all these node servers work - even among the ones I have written. A lot of this comes from legacy releases from Polyglot v2 (or even Polyglot v1). The MyQ node server was first released in 2018. I, for one, have expected for some time now that Polyglot would get subsumed by IoX (i.e., direct MQTT to IoX without intervening REST layer or PG3 database) and the Dashboard functionality brought into Admin Console, and that would be the opportunity to true up interface design paradigms, e.g., configuration parameters, device discovery, node management, heartbeat, status monitoring, notifications, and such. I think it’s still coming - just taking a lot longer than I expected.

Initial question: Are you using the "Discover Devices" button in the MyQ Service node?

Here's what the two instances I mentioned above look like: It gets an initial error in oAuth, e.g. a 401 error (not uncommon). It retries every minute (longPoll interval) for 6 or 7 minutes, then the server starts responding with the 429 - Too many requests error. So I think I need a longer retry on failure than the longPoll interval, or maybe after some number of failure retries, I crank down the frequency of retries. I'll put a TODO in the code for the next version.

Excellent. I will try to keep an eye on it. I may need to back off on the frequency it tries to refresh the token on initial failure. It may just be a simple longPoll change, or it may need its own period setting.

I checked my log files under PG3x since my migration last week. I got the same 429 - Too many requests error back on 9/26 on every longpoll oAuth token refresh for approx. 3 hours around 1:00am and again on 9/29 for a similar timeframe. Otherwise the MyQ node server has run fine since the migration. At this point, it looks like it's a transient error having something to do with the partner Chamberlain is using for oAuth authentication. I don't see anything about it in the Issues for the pymyq library (from which the node server was patterned). If a bunch of people start getting it all the time, I will look into it further.

The previous error dealing with UserAgent was an HTTP 403 error, I believe. You're getting a 429 Client Error: Too Many Requests. I will have to look into it. In the meantime, what's your shortPoll and longPoll set to in your Advanced Configuration?

@dbarentine You still around here?

What's your need here? I am close to releasing a Tasmota node server (testing on PG3x now) specifically for Martin Jerry switches and modules, but could be expanded to support the Shelly products for simple control and monitoring if the devices have Tasmota installed as the firmware. Let me know what devices you have and if they have Tasmota installed (or you would be willing to flash them with Tasmota). Also, there is an MQTT node server (and an MQTT broker running on recent versions of PG3 and PG3x) that I haven't used but I believe can be configured to communicate with specific devices over MQTT via Custom Configuration Parameters without having to change out the firmware. Don't know if any of this fulfills your needs, but just let me know.

No problem. Another thing that I have considered is adding all of these optional Custom Configuration Parameters with their keys and "placeholder" values when the node server is installed (like we all do for required parameters). That would probably clear up some confusion as well, but could make for very long list of Custom Configuration Parameters for some of my node servers. I would have to add some code to accommodate both missing optional parameters and optional parameters that are present but with placeholder values (and maybe blanks), but the code wouldn't be hard. I will add a TODO for this node server to look into this for a future release.

Here are the current instructions and my settings: As you can see in the instructions, the "Custom Configuration Parameters" refers to the "Custom Configuration Parameters" section of the configuration page just below the instructions. Each Custom Configuration Parameter has a "Key" and a "Value." You need the two Custom Configuration Parameters shown: one with key "hostname" and a value of your IP address, and another with the key "token" and a value of the token string from your Bond bridge. I know sometimes it's so clear in our heads that it doesn't translate to others. If you can suggest better verbiage, I will consider upgrading the instructions.

I upgraded my Polisy from PG3 to PG3x last night and everything migrated successfully (after an arbitrary number of reboots) and is running except HoneywellHome node server. The node server appears to be running with an increasing "Uptime," but the Current Status is "Disconnected." The log file is from yesterday and shows the node server running properly all day and the graceful shutdown last night when the upgrade was started. Stopping and re-starting the node server does not produce a new log file or change the Current Status from "Disconnected." Whenever I restart the node server, I get the following in the PG3(x) log file: 9/29/2023, 05:56:31 [pg3] info: startNs:: Starting HoneywellHome 9/29/2023, 05:56:31 [pg3] info: call_udx: Making request to socket with url /rest/pg3.start.ns 9/29/2023, 05:56:31 [pg3] info: startNs:: HoneywellHome starting polls 9/29/2023, 05:56:31 [pg3] info: Starting HoneywellHome Info timer 0 9/29/2023, 05:56:31 [pg3] info: startNs:: HoneywellHome updating database (enabled, timestarted) 9/29/2023, 05:56:31 [pg3] info: startNs:: HoneywellHome started. There is nothing else in the PG3(x) indicating any problems with the HoneywellHome node server. The IoX Admin Console shows all blank entries. Is there any known incompatibility of this node server with PG3x? Anybody else running HoneywellHome on PG3x?

You need one Custom Configuration Parameter with a key “hostname” and a value of the IP address, and another Custom Configuration Parameter with a key of “token” and a value of the token string.