Core: MyQ API changed and is broken on all versions

[broyuken]

The problem

MyQ shows unavailable

Environment

HA Core on RPi4
Home Assistant 0.109.4

• Home Assistant Core release with the issue: Home Assistant 0.109.4
• Last working Home Assistant Core release (if known): 0.108.x
• Operating environment (Home Assistant/Supervised/Docker/venv): HA
• Integration causing this issue: MyQ
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/myq/

Problem-relevant configuration.yaml

None, config flow. Shows unexpected error when I click submit.

Traceback/Error logs

2020-05-05 13:29:10 ERROR (MainThread) [homeassistant.components.myq.config_flow] Unexpected exception
  File "/usr/src/homeassistant/homeassistant/components/myq/config_flow.py", line 50, in async_step_user
  File "/usr/src/homeassistant/homeassistant/components/myq/config_flow.py", line 30, in validate_input
    await pymyq.login(data[CONF_USERNAME], data[CONF_PASSWORD], websession)
  File "/usr/local/lib/python3.7/site-packages/pymyq/api.py", line 167, in login
  File "/usr/local/lib/python3.7/site-packages/pymyq/api.py", line 124, in authenticate
  File "/usr/local/lib/python3.7/site-packages/pymyq/api.py", line 140, in update_device_info
  File "/usr/local/lib/python3.7/site-packages/pymyq/api.py", line 83, in request
2020-05-05 13:32:07 ERROR (MainThread) [homeassistant.components.myq.config_flow] Unexpected exception
  File "/usr/src/homeassistant/homeassistant/components/myq/config_flow.py", line 50, in async_step_user
  File "/usr/src/homeassistant/homeassistant/components/myq/config_flow.py", line 30, in validate_input
    await pymyq.login(data[CONF_USERNAME], data[CONF_PASSWORD], websession)
  File "/usr/local/lib/python3.7/site-packages/pymyq/api.py", line 167, in login
  File "/usr/local/lib/python3.7/site-packages/pymyq/api.py", line 124, in authenticate
  File "/usr/local/lib/python3.7/site-packages/pymyq/api.py", line 140, in update_device_info
  File "/usr/local/lib/python3.7/site-packages/pymyq/api.py", line 83, in request

Additional information

[AudioNutz]

I rolled all the way back to Home Assistant 109.1, and see the same issue. I wonder if the MyQ API changed again?

[broyuken]

I rolled all the way back to Home Assistant 109.1, and see the same issue. I wonder if the MyQ API changed again?

As did I. Still seeing the same issue

[dseven]

Pretty sure it's not a HA issue - I easily reproduced it with the test code for pymyq, outside HA.

[alokdhir]

same issue here.

[brianewman]

Rolled back to 0.108.9 and have same problem.

[dohlin]

Same issue here...guessing the API changed again.

[probot-home-assistant[bot]]

Hey there @bdraco, mind taking a look at this issue as its been labeled with a integration (myq) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[bdraco]

Looks like the api changed

[thedishking]

Same issue here.

[luisiam]

I am seeing the same issue

[bachya]

PLEASE STOP POSTING "ME TOO" COMMENTS. Continuing to do so will lock this issue. Instead, if you merely want to confirm that you are seeing the same issue, please add a 👍 emoji to this message.

[kyotodesertfox]

I deleted my MyQ integration thinking it was something screwy on my end. It wasn't, so DON'T do that!

It will not let me re-add the integration (Unexpected Error). It isn't bad credentials, as I can log into the phone app, but this may be a tell / sign that the API might be related to an authentication change (since I cannot login).

[bachya]

FYI, @bdraco is working on a fix: https://github.com/arraylabs/pymyq/issues/34#issuecomment-624274521

[bdraco]

Fixed here https://github.com/arraylabs/pymyq/pull/35

Needs @arraylabs or someone with access to review.

[vinmar1]

I rolled way back to 108.2 and it's still broken... has to be MyQ's end.

[kyotodesertfox]

I rolled way back to 108.2 and it's still broken... has to be MyQ's end.

@bdraco has found a fix. It's waiting for review.

[giachello]

Hi there, I just got this email from Wink signaling that MyQ is shutting off their integration. Are they wanting to cut 3rd party access completely?

Dear Wink Community,

Effective June 1st, 2020, Chamberlain will be terminating its partnership with Wink. Newly proposed terms from Chamberlain would have required Wink to generate tens of thousands of new MyQ users each year as well as pay hundreds of thousands of dollars in annual licensing fees.

[bdraco]

While I cannot guess what they are thinking, it would not be surprising if they moved to cut off all third party access as they are likely seeking to heavily monetize their API.