Closed NTNWeezer closed 3 years ago
Seeing the same for several days. Same standard configuration.
[9/25/2021, 3:56:08 PM] [myQ] request to https://partner-identity.myq-cloud.com/connect/authorize?client_id=IOS_CGI_MYQ&code_challenge=frzVZuvB59tgdyIl5RzBPm7ka1XEjULWIR-J8VmyIOs&code_challenge_method=S256&redirect_uri=com.myqops%3A%2F%2Fios&response_type=code&scope=MyQ_Residential+offline_access failed, reason: write EPROTO 4402746816:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
[9/25/2021, 3:56:08 PM] [myQ] myQ API: Unable to access the OAuth authorization endpoint.
Same here
I see successful connection, then intermittent failures. Garage Door becomes unresponsive to HomeKit requests.
[9/26/2021, 1:36:13 AM] [myQ] myQ API: Discovered device family garagedoor: garage door (serial number: CG08601A1513, gateway: GW0E000A3707).
[9/26/2021, 1:36:13 AM] [myQ] myQ API: Discovered device family gateway: Murdstone Road [Chamberlain WiFi GDO AC 3/4 HP] (serial number: GW0E000A3707).
…
[9/26/2021, 1:44:22 AM] [myQ] request to https://devices.myq-cloud.com/api/v5.2/Accounts/a978f549-cab8-4498-bd57-3190233ea933/Devices failed, reason: getaddrinfo EAI_AGAIN devices.myq-cloud.com
[9/26/2021, 1:44:22 AM] [myQ] myQ API: Unable to update device status from the myQ API. Acquiring a new access token.
[9/26/2021, 1:44:36 AM] [myQ] request to https://partner-identity.myq-cloud.com/connect/token failed, reason: getaddrinfo EAI_AGAIN partner-identity.myq-cloud.com
[9/26/2021, 1:44:36 AM] [myQ] myQ API: Unable to acquire an OAuth access token.
[9/26/2021, 1:46:14 AM] [Nest] API observe: error Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:209:20) {
errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
[9/26/2021, 1:46:14 AM] [Nest] Retrying in 10 seconds.
[9/26/2021, 1:46:32 AM] [myQ] request to https://partner-identity.myq-cloud.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3DIOS_CGI_MYQ%26code_challenge%3D_FknstcdMZLOjW9Z9h0OAbb-vvtjQsBLtMghoKJPrG0%26code_challenge_method%3DS256%26redirect_uri%3Dcom.myqops%253A%252F%252Fios%26response_type%3Dcode%26scope%3DMyQ_Residential%2520offline_access failed, reason: getaddrinfo EAI_AGAIN partner-identity.myq-cloud.com
[9/26/2021, 1:46:32 AM] [myQ] myQ API: Unable to access the OAuth authorization endpoint.
Commented in #522 as well. All working normally again for me this morning.
Appreciate the alerts guys...as I've said in other issue reports like this one, this stuff happens end of month, in general, in myQ-land when the development team tends to push production server-side updates. Closing this issue since all is well that ends well...once more. :smile:
Hi there. I'm a homebridge newbie. I just installed the myQ plugin. It installed OK, accepted my login credentials and added the garage door to HomeKit satisfactorily. However, the plugin is non-responsive to HomeKit requests and is filling the homebridge error log with 'sucessfully connected to API" and then error messages
Is this the same error reported here?
This issue is locked to prevent necroposting on closed issues. Please create a new issue for related support requests, bug reports, or feature suggestions.
Describe The Problem:
MyQ API will not authenticate.
To Reproduce:
Restart home bridge or wait for refresh
Logs:
Restart home bridge or wait for refresh
Homebridge Configuration:
Screenshots:
Environment: