Goose66

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.

The Discovery no longer works on PG3 or PG3x. UDI added the Zeroconf package (aka "Bonjour") into the standard build and starts it with the Polisy/eISY firmware in order to get it to respond to polisy.local. The downside of that is the node server can no longer start it's own Zeroconf listener for device discovery. There is a feature added to some version of PG3x that allows the node server to do discovery through PG3x, but I don't know what version that is and how widespread it is, so I haven't changed the code yet. In the meantime, just add the "hostname" Custom Configuration Parameter with the hostname or IP address of your Bond bridge, and the "token" Custom Configuration Parameter with the token value from the Bond app, and then the Discovery process will locate the bridge and create nodes for all of the devices. If you have multiple Bond bridges or SBB devices, you can add values for each of them to the respective "hostname" and "token" Custom Configuration Parameters separated by semicolons. Just make sure the hostnames and tokens are listed in the same order.:)

My concern at this point if I still had a 994 would be the SD card. I went through at least one SD card failure on my 994 and was dependent on UD support to get it back running. Especially since you are “starting from scratch” I would take this opportunity to upgrade to eISY and know you have support for the next 10+’years.

Have you tried Network Resources? Can you flash it with Tasmota and use the MQTT node server?

I imagine the thought is generally if there’s been any adjustments to outside lights other that “all off” then leave them alone.

I will add that the node server for these switches and modules works really well. It's all local (no Internet or cloud service) and communicates via the MQTT broker built into the Polisy/eISY, so it's fast. Status changes are updated instantly in IoX, so the nodes can be dropped into scenes and they will work with real-time feedback. And the telemetry and "last will and testament" MQTT messages sent by the Tasmota operating system keep all the states (including "Online" state) updated automatically, so the node server doesn't have to do any polling of its own. Once the Tasmota devices are configured to use the Polisy MQTT broker, they are all automatically discovered by the node server (via the Discovery button) and added to IoX. I suppose other Tasmota switches and modules similar to the Martin Jerry devices could also be added to this node server, but I would need some hardware to test with. I have a dimmer, a fan control switch, and humidity sensor switch on order. When I get these integrated, I will publish the node server.

I do want to point out that, while I completely agree there is a basic flaw in the program's design, this flaw you point out will not prevent the remaining lights from turning on after turning on the 'Entry Front Door Light', as may be interpreted from your post. That is because there is no WAIT or REPEAT statement in the running program that makes the program "re-entrant," thus once the Then branch of the program starts running, it will run to completion. If it were me, I would have a first, enabled program that had the "'Area 1 / FRONT.DOOR' is switched On" condition and a second, disabled program that had the remaining conditions and the commands from the Then statement. The "Then" branch of the first program runs the "If" branch of the second program. But neither using a variable to track the light nor structuring your programs with the "two-program" methodology (discussed ad nauseum in these forums) would appear to solve your problem of the program seemingly ignoring the sunset to sunrise condition.

I think (or hope) that it was just unfortunate timing. This is only a warning, and the node server will retry the connection every long-poll interval (default 60 seconds) until it is reconnected.

So nobody, eh? It would be interesting to know what their sales are. My luck is that they would go out of business before I could buy what I needed for my townhome.

So you weren't getting the same 403 error that was present in the original issue. You are getting "HTTPSConnectionPool(host='partner-identity.myq-cloud.com', port=443): Read timed out. (read timeout=12.05)" error. This generally means either your network is down or the partner oAuth server is down or busy. What's more, after upgrading to 3.2.22, it appears (from your log file) it only tried four times (over 4 minutes) before the node server was shut down. Try starting it again and seeing if it can connect now.

The node server can only have one sub-level. I keep all my node server service nodes in one "Node Server" folder, and the garage door openers in a "Perimeter" folder. Alternatively, you can just move them all under a "Garage Door" or "MyQ" folder.

Go ahead an DM me your log file.

You may need to refresh your Node Server Store. Yes, there usually is an "Update" button on the node server details page when an update is available for a node server.

Ok, try again. I had changed the "edition" of the node server from "Free" to "Standard" thinking I was fixing an error, but when I saw your screenprint it occurred to me that it may mean people can't update. @drprm1 Since your Update worked, please check that you weren't charged for it. If you were, I will work with @Michel Kohanim to arrange a refund.

Crap. That shouldn't be "Purchase," it should be "Update." Let me look again.

Try refreshing your Node Server Store. I was able to update it on my production Polisy in my home.

I have uploaded a new version of the MyQ Node Server (v3.2.22) to the Node Server Store. This version adds a User-Agent header to the oAuth calls as well as the API calls to get around the 403 unauthorized values. It also adds a new driver value for the MyQ Service node that is a Node Server Status value managed by PG3. See release notes at https://github.com/Goose66/NSDocs/blob/main/myq-pg3.md for more info.

While I lost remote connectivity to my Polisy, the reboot was evidently successful, PG3 and the MyQ node server restarted, and the MyQ node server ran for three days without any 403 errors or other authentication or connectivity problems. It also restarted successfully tonight when I got back to my development box. So I have uploaded new v3.2.22 of the node server that should take care of the User-Agent issue for now. I note that there is still conversations over on the arraylabs/pymq Github repository regarding folks still having problems in HA, so I will keep an eye on it. Also, the User-Agent value is user configurable in this version, but I didn't put any references in the instructions or release notes to that. Let's keep that under wraps until we need it. There is a new version of PG3x coming out that should have a way for me to change the User-Agent and potentially other auth values (e.g., application key) remotely across all installed node servers, so maybe that will be out and in widespread use before we need to mess with all this again. Thanks for your patience.

Sorry guys. I had it all (at least mostly) working and but now PG3 has completely died. Cannot get to the UI or IoX on my Polisy. Restarting the Polisy remotely did not help. And since I am remote, my options are rather limited. I will be back local on Sunday evening, and I can look at it then.