Possible API Being Updated

[a-bianucci]

Doors now showing unavailable.

Others are starting to notice as well.

Error Logs show:
File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 114, in _send_request
message = f"Error requesting data from {url}: {data.get('description', str(err))}"
UnboundLocalError: local variable 'err' referenced before assignment

Not sure if they are updating the API, or something else.

[rickscherer]

2020-12-16 14:28:39 DEBUG (MainThread) [pymyq.api] Sending authentication request to MyQ
2020-12-16 14:28:39 DEBUG (MainThread) [pymyq.api] Sending myq api request https://api.myqdevice.com/api/v5/Login
2020-12-16 14:28:39 DEBUG (MainThread) [pymyq.api] Attempt 1 request failed with exception: [Errno 104] Connection reset by peer
2020-12-16 14:28:39 WARNING (MainThread) [pymyq.api] Device update failed; trying again in 2 seconds
2020-12-16 14:28:41 DEBUG (MainThread) [pymyq.api] Sending myq api request https://api.myqdevice.com/api/v5/Login
2020-12-16 14:28:41 DEBUG (MainThread) [pymyq.api] Attempt 2 request failed with exception: [Errno 104] Connection reset by peer
2020-12-16 14:28:41 WARNING (MainThread) [pymyq.api] Device update failed; trying again in 4 seconds
2020-12-16 14:28:45 DEBUG (MainThread) [pymyq.api] Sending myq api request https://api.myqdevice.com/api/v5/Login
2020-12-16 14:28:45 DEBUG (MainThread) [pymyq.api] Attempt 3 request failed with exception: [Errno 104] Connection reset by peer
2020-12-16 14:28:45 WARNING (MainThread) [pymyq.api] Device update failed; trying again in 5 seconds
2020-12-16 14:28:50 DEBUG (MainThread) [pymyq.api] Sending myq api request https://api.myqdevice.com/api/v5/Login
2020-12-16 14:28:50 DEBUG (MainThread) [pymyq.api] Attempt 4 request failed with exception: [Errno 104] Connection reset by peer
2020-12-16 14:28:50 ERROR (MainThread) [homeassistant.components.myq.config_flow] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/myq/config_flow.py", line 50, in async_step_user
info = await validate_input(self.hass, user_input)
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.8/site-packages/pymyq/api.py", line 259, in login
await api.authenticate(username, password, False)
File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 170, in authenticate
auth_resp = await self.request(
File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 151, in request
return await self._send_request(
File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 114, in _send_request
message = f"Error requesting data from {url}: {data.get('description', str(err))}"
UnboundLocalError: local variable 'err' referenced before assignment

[a-bianucci]

Rick you thinking it's an updated API then as the URL is actually available or?

[rickscherer]

home-assistant/core#44303

[rickscherer]

Rick you thinking it's an updated API then as the URL is actually available or?

Perhaps an API change? I don't really know as a simple curl for authentication is throwing an error.

[a-bianucci]

That's how I read the logs to... that last line regarding local variable err wasn't sure about. Here is to hoping it just comes right back up.

[irctrakz]

The myq app on ios has a login URL of partner-identity.myq-cloud.com, that appears to be different than the existing /Login URL (api.myqdevice.com)

[a-bianucci]

irctrakz if I can figure out the curl string (not a coder), could try and replace the url with what you have see what happens.

[rickscherer]

irctrakz if I can figure out the curl string (not a coder), could try and replace the url with what you have see what happens.

I'm getting the same error against that URL, I believe it's all the same servers - just different FQDN based on client/application.... looking more like possible API change, or just an issue with their API service.

[irctrakz]

Looks like they may also be certificate pinning.... but tbh, my burp skills are rusty.

[rickscherer]

Looking more to be wider spread API issues, IFTTT <> MyQ isn't working either, and that is a supported connection.

[irctrakz]

Yeah, api.myqdevice.com returns a connection reset (not even a 500 or 302), but partner-identity.myq-cloud.com gives a 400

[hstern]

The server is return status code 401 Unauthorized for https://api.myqdevice.com/api/v5/Login

Response body is:

{'code': '401.102', 'message': 'Unauthorized', 'description': 'The current call is Unauthorized.'}

The API._send_request function was expecting err to remain in scope outside of the try-except block, which it doesn't. I submitted #54 to fix that issue so that the error can be properly reported.

Digging deeper, I was mistaken. The server is only dropping connection when you pass the 'User-Agent': 'okhttp/3.10.0' header, so Chamberlain myst be blocking that user agent.

Changing the user agent to 'pymyq' resolves the issue. My garage door is going crazy now.

[rickscherer]

Confirmed that changing User-Agent resolved the problem.