myQ Issues.

[hjdhjd]

I've locked issues and commenting in this repo. I am aware that there are myQ API changes, and also aware that there are well-intentioned people that are trying to report issues or offer advice on how to address them. While I appreciate the positive intent, I do not find it productive to respond and address repeated "I'm having a problem" issues/comments or suggestions on addressing a set of challenges that most people who have not dealt with this specific API over a period of time.

For example, I've gotten a number of suggestions about addressing the 429 errors that the API generates. The suggestion is generally in the vain of "hey you should implement incremental backoff". A 429 HTTP error generally indicates you're querying an API endpoint too much and it's asking you to backoff, but that's not what the actual issue is in this specific case. The myQ API is using an aggressive posture to reduce the number of ways one can probe or login to the API. These errors will be generated in several scenarios, none of which involve spamming the API. It's an additional obstacle the myQ API has put into place.

Again - I appreciate the well-intentioned nature of most of these suggestions, but they aren't helping to move the ball forward. If you'd like to discuss the issues, you're welcome to join the Homebridge Discord and use the myQ channel and subthreads there to discuss them.