Description
Friendly pointer to @ehendrix23 and team...I've just pushed a substantive update to my reference implementation at https://github.com/hjdhjd/myq. I posted a similar issue to the Python-myQ project, and I'm unsure how the two projects relate but wanted to share...
I've gone through and essentially re-entered into the game of "mirror the app behavior" that myQ seems to be marching toward in their effort to become more pedantic about how you access the API. Just wanted to be helpful to the other myQ projects out there. The behavior in my implementation now essentially mirrors the native myQ app behavior when it comes to accessing the API, inclusive of all the headers (even the occasional typos and weirdness they choose to do or not do). I have opted to retain every aspect of the native app's behavior I can, even those that appear incomplete or incorrect, in an effort to "blend in", as it were.
My suggestion would be to adopt a similar approach. I suspect over time we're going to re-enter into a cat-and-mouse game now when it comes to the headers - especially when it comes to the app version.
Enjoy!