As I'm sure all the MyQ plugin users know, the plugin has a tendency to stop working when the MyQ cloud servers are updated. This isn't really surprising, considering it's a reverse-engineered API with no official support or blessing from the MyQ system.
MyQ is in the process of rolling out their V6 API. When they shut off the V5 API, the plugin will stop working. No one in the HA community knows when that will be.
The plugin is based on an old version (1.2.1) of the pymyq library (https://github.com/arraylabs/pymyq). The library has now been updated (3.0.0) to work with the V6 API. Which is good for all the projects that use it directly, like home-assistant and homebridge (I think). But the Indigo plugin can't, since it's a Python3 only library.
I've been looking at the changes and it's going to be very. very difficult (if it's possible at all) to back-port the new authentication system to Python2. It's so heavily dependent on asyncio that I would have to start from scratch. And I don't think I'm interested in doing that.
If we're lucky, MyQ will continue to support V5 for a long time to come. Somehow, I doubt that will happen.
A better alternative would be to figure out how to use the Python3 library. Because if I can do that for this plugin, I can do it for other APIs that are also only supporting Python3. Anyone have an brilliant ideas on that?