Goose66

Also the Honewell Home plug-in (formerly node server) allows you to see the "Priority Type": "Pick a Room," "Follow Me," or "Whole House," but IoX can't change it or select a particular remote sensor.

Currently goes through the Cloud, and in a very circuitous route at that.

Afraid not. Neither setting nor determining the current controlling sensor is supported by the API. I don't believe you can in the Honeywell Thermostats, either. You may want to ask @Jimbo.Automates about Ecobee.

There’s been some changes to another project (not pymyq) that seem to be working, although the developer has shutdown posts from users to the issue in the GitHub repository. I am going to implement his changes this weekend and see if I can restart mine. Longer term, I am implementing some local solution as well (maybe ratgdo device), and if a node server is required I will make it free to all MyQ owners (or everyone if it’s easier). But ultimately I don’t’ want to give up on Chamberlain and MyQ, because there is a whole batch of Polisy/eISY users out there that are DIY enough to own one but not DIY enough to be wiring some 3rd party device into their garage door opener. We don’t want to forget about those folks!

Also, there should be no problem with restoring the nodes from a backup even if PG2 and the node servers are not running.

AFAIK no version of IoX has ever spontaneously deleted nodes, including just because the node server fails to respond. It just leaves the nodes with unknown state (status) values. The way the ISY Node Server REST API works, the ISY has no way of knowing whether the node server is just not currently responding or PG2 (or the RPi it's running on) has died. There are only four ways I know of to delete node server nodes: 1) delete them from the Admin Console (and, because PG2/RPi is dead, they won't get added back), 2) delete them from the PG2 Dashboard while ISY is running and available to PG2, 3) the node server code deletes them while the node server is running, or 4) delete the node server from the Admin Console (Node Servers-->Configure--><Node Server> and then "Delete" button on configuration page) and then all of the nodes for the node server are also deleted.

I am assuming the reason mine is still running is that I haven't rebooted in a while.

Just FYI, I've been waiting for two things to happen before a dive into this: 1) for the folks discussing the issue over at the pymyq Github repository to find/settle on a solution, and 2) for my MyQ node server to stop working. To date, neither of those have happened yet. But I will keep looking at it. EDIT: I should say I'm waiting on my production installation of the MyQ node server to stop working.

Also, depending on what you are looking for, there is a Tasmota node server available as well. Are your Sonoff devices using Tasmota firmware?

You don’t have to change the configuration of the generic MQTT broker, and you probably shouldn’t because there are other node servers using it as configured. What errors are logged in the node server log (not the pg3 log) when the node server is started?

It appears to only work with one model Genie (H8000D), which is not what I have. I have CM7600ICs which have a keypad controller sort of like MyQ that allow you to control the light and door separately and and lock the door. So I assume the device would have to be programmed to talk the Genie protocol, just like it's programmed to talk the MyQ Security+ 2.0 protocol. Maybe somebody has got it working with a Genie like mine.

I like the ratgdo device. It has everything I am currently looking for in HA integration devices: Wi-Fi, MQTT, and defined local API. I would be all over this IF I STILL HAD Chamberlain door openers. Unfortunately, my new townhome (not so "new" now, I guess) had Genie openers, and I bought the Chamberlain Smart Garage Control because I had the MyQ Node Server and IoX programs and Alexa routines that went with it. If there were a Genie version of the ratgdo, that would be cool. $30 per door would be a little tough to swallow after already paying $75 for my Chamberlain Smart Garage Control and a second door position sensor, but ultimately local control is the goal. A node server for the ratgdo would be a no brainer - you could use Network Resources or the free MQTT node server to get basic functionality, or we could copy the Tasmota node server with the MyQ profile to get a real garage door opener (possibly with independent light control) node server. I still have some hopes we can get in with the Chamberlain public API - it's better than nothing - but ultimately I think local is always the better choice when you have the option. I mean, that's why we all use the Polisy/eISY to begin with, right?

Just to be clear, I don't think it's necessarily "evil." Since they are, primarily, a hardware manufacturer, I'm sure they ultimately want to sell as much hardware as possible. Rather than trying to force people into their ecosystem and dominate the HA market (as many other OEMs seem to want to do), however, I think there need to put guard rails (and potentially fees) on access to their API may be more of a way to reduce their own fixed costs.

We haven't heard back from Chamberlain on the use of the public (or semi-private) API, but it may be a cost associated with using it. So Chamberlain may be shutting out unauthorized users in order to drive HA integrators to use the (perhaps pay-to-play) public API.

Not a lot to go on from "can't get a single node to work" so here's my generic suggestions: 1. Pick one of the node servers and concentrate on it. For example, let's look at the Hue PG3 Node Server. 2. Read fully the "More Information" in the Node Server Store, the Configuration information on the Configuration page in the Dashboard, and the release notes in the forum for the Hue PG3 Node Server. There may be a lot of information there about what your setup needs to look like as well as step-by-step instructions to install and configure the node server. 3. Once you've tried all that, post a new topic in the Hue PG3 Node Server forum with a detailed message of the symptoms you are getting that make it "not work."

There’s been chatter in the pymyq repository of new errors but no solutions. It may be additional changes made to Chamberlain’s handling of the user-agent in order to continue to try to block unauthorized use of the mobile app API. Hopefully will see some solutions soon.

Could commissioning (at least for wifi or Zigbee connectivity) be done, even temporarily, through existing (perhaps hardware manufacturer-supplied) mobile apps, with IoX taking control once connected to the network? In other words, does Matter require IoX to control the devices end-to-end or can IoX just be a (one of potentially a plurality of) controller?

My diagnosis: You are running a new version of the launcher with your ISY running an old version of IoX. The current launcher involves two forms of discovery and access: the older broadcast method and newer mDNS. So when the ISY responds to broadcast discovery, the launcher expects there to be two paths to the ISY. But since your ISY isn't (can't) run Zeroconf for mDNS, the second path doesn't exist.

There was one request for Sonoff MINIR2. It looks similar in functionality and size to the Shelly 1, except much easier to wire (meaning less Wago connectors and more space in the J-box). Only 10 amp limit though, so if you are putting it into a standard 15A circuit in the U.S., it can't carry the max amperage load of the entire circuit (although especially with LED lighting, I doubt you would ever have more than 10A on you circuit). Also looks like it supports flashing of Tasmota OTA, instead of having to hook it up to your PC through a USB-to-TTL adapter like with the Shelly 1. As far as support in the node server, while it has a different template from the Shelly 1, I think you could get basic "Switch" module functionality (i.e., ON and OFF) functionality for it with the existing code. So I will add it to the list of supported devices in the next version and someone can test it for me.

Did you shut it down for a couple of hours and then retry?

Please put in a request here: This will consolidate discussion of additional device support.

What error are you getting? And, after the failure and reinstall did you give it the 75 minutes (or 2 hours) before you restarted the node server.

Ok, I think the 429 - Too many requests errors is an older (like several weeks) problem that still needs to be looked at, but it should only affect restarts and usually will resolve itself if you shutdown and don't retry for at least 75 minutes. Hopefully the newer 401 error is fixed (for now). The current code is a mish-mash of fixes and patches from changes to a couple of libraries on GitHub that have occurred over the last couple of years. I think there needs to be a complete restructuring of the oAuth authentication process, but outside of making it easier to maintain, I am not exactly sure HOW it needs to be restructured. The entire API is made to support the app. The oAuth authentication and token retrieval process works for a short access window, i.e. do authentication when the user starts the app, get the token, then use the token while the user is using the app. The token doesn't need refreshing for over an hour, so in the majority of cases, the user will have stopped actively using the app by then. Moreover, the app makes requests in spurts, where the node server makes requests on a steady basis every 20 seconds or 60 seconds (depending on active vs. inactive polling mode), hour-by-hour, day-in and day-out. Another difference - when a connection is severed (usually MyQ servers stop responding temporarily), the node server tries to reconnect every 60 seconds by going back to square one and go through the oAuth authentication process to retrieve a new token. After four or five retries, the oAuth servers will return a retry delay required to avoid subsequent 429 errors, but it is like the aforementioned 75 minutes. So that may work for the app, but for the node server that's just not going to work. Then there is the whole thing with userAgent, which is the change that appears to be specifically targeting the unauthorized users, and if Chamberlain is going to continue that game it's going to get harder and harder to keep it working. I think it needs one of two things: either learn how to track the app communication with the API in order to keep up with all the changes myself (instead of waiting on others to work through the issues), or change the node server to work with one of the two libraries out there and put the burden on maintaining operability on someone else. Neither is a great solution: the former requires a level of hacking that's above my paygrade, and the latter means we have no control over the timeline. For example, much of the learning that went into the current v3.2.23 fix came from the pymyq library from arraylabs. But the fixes for the last few months are in pull requests by individual users - the latest version of the library in pypi goes back to last December. In addition, both of the libraries that appear to be maintained are async, and the node server environment for PG3/PG3x is decidedly not async. All that to say it's complicated, I appreciate your patience, and I hope you understand why I made this one a subscription instead of a perpetual license. The ultimate solution would be for Chamberlain to publish a simple, public, REST-based API with a specified maximum polling frequency, and I think that would satisfy most users (i.e., you won't be able to turn on lights when a garage door is activated, but you can monitor door status and close them for security reasons over reasonable periods). After 5 or 6 years of working on this, though, I don't see that happening soon.

What is everyone's shortpoll and longpoll set to?

I have uploaded a new version of the MyQ Node Server (v3.2.23) to the Node Server Store. This version implements fixes to oAuth to try and keep up with the changes coming from Chamberlain. I would like to say this version should work for some time, however, I feel like we are chasing our tails right now with this and the node server is getting quite fragile. When it has a valid token, it works great. But every time you restart the node server (or potentially every 60 minutes when in refreshes the token) there is a chance that the authentication will fail. There are also a couple of bugs in this version that occur in rare network conditions that will take some time to run down, but I wanted to get a semi-working version out to you guys as fast as possible.