core: MyQ Integration Intermittently Dropping Service

The problem

I noticed that when trying to open my garage door through the MyQ integration, it failed and reported that the entity was unavailable. I restarted Home Assistant, and it still said the entity was unavailable. A few moments later, the entity was available, and I was able to control the garage door opener. However, throughout the day, the entity has been switching between available and unavailable without my making any changes to the server.

Environment

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

System Health

version 2020.12.2
installation_type Home Assistant OS
dev false
hassio true
docker true
virtualenv false
python_version 3.8.6
os_name Linux
os_version 5.4.79-v7l
arch armv7l
timezone America/Detroit
Home Assistant Community Store
GitHub API ok
Github API Calls Remaining 5000
Installed Version 1.9.0
Stage running
Available Repositories 774
Installed Repositories 2
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Hass.io
host_os Home Assistant OS 5.9
update_channel stable
supervisor_version 2020.12.7
docker_version 19.03.13
disk_total 28.6 GB
disk_used 3.9 GB
healthy true
supported true
board rpi4
supervisor_api ok
version_api ok
installed_addons Let’s Encrypt (4.11.0), Samba share (9.3.0), SSH & Web Terminal (7.8.0), Home Assistant Google Drive Backup (0.103.0)
Lovelace
dashboards 2
mode auto-gen
resources 0

Problem-relevant configuration.yaml

# MyQ
cover:
  - platform: myq
    username: !secret myq_username
    password: !secret myq_password

Traceback/Error logs

Logger: homeassistant.components.myq
Source: helpers/update_coordinator.py:132
Integration: MyQ (documentation, issues)
First occurred: 9:53:18 AM (24 occurrences)
Last logged: 12:30:11 PM
Unexpected error fetching myq devices data: Error requesting data from https://api.myqdevice.com/api/v5.1/Accounts/ebe422d9-2264-4a26-9699-5c0cc9ed8c80/Devices: Server Error

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 144, in async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 132, in _async_update_data
    return await self.update_method()
  File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 223, in update_device_info
    devices_resp = await self.request(
  File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 154, in request
    return await self._send_request(
  File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 119, in _send_request
    raise RequestError(message)
pymyq.errors.RequestError: Error requesting data from https://api.myqdevice.com/api/v5.1/Accounts/ebe422d9-2264-4a26-9699-5c0cc9ed8c80/Devices: Server Error

Additional information

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 10
  • Comments: 18 (6 by maintainers)

Most upvoted comments

But even though that worked on somethings, others like MyQ still didn’t work properly. Any ideas on how I can dig into this and grab some of the info on this new API?

Most likely they are using certificate pinning which prevents MITM attacks. This means the app is expecting a specific certificate from the server. If it doesn’t get that, it stops functioning.

@bdraco - OK, I’ve opened this as a new issue on pymyq. Don’t know who can pick this up and possibly collaborate with the Homebridge MyQ efffort.

https://github.com/arraylabs/pymyq/issues/60

Has to be on the hub or HA because the MYQ apps still works perfectly

Seeing the same issue on my setup