I realized last night that I was no longer able to control the door from the MyQ app either, however, I was still getting notifications from the app when I manually opened/closed the door and was seeing sensor updates in the app. I guess the garage door motor had stopped responding to the MyQ hub’s commands, like it unlearned the hub’s code(s). From what I can tell, there’s no way to reset just this particular issue. I had to factory reset MyQ, remove the device and go through the initial setup process again. It’s all working now. Very strange.
1 Like
Looks like their servers are down again.
Today the myQ account thing was offline. I disabled it and reenabled it, and it came back on line. It seems like I have had to do this a lot lately. I was able to control it through the MqQ iOS app, so I don’t think the problem is their servers.
I filtered the events log by myq:
2022-09-29 18:49:12.035 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@12bcb97::DecryptedEndPoint@a89439{l=/192.168.1.89:52188,r=partner-identity.myq-cloud.com/40.71.237.110:443,OPEN,fill=-,flush=-,to=68/0} to OFFLINE (COMMUNICATION_ERROR): Could not load login page
2022-09-29 18:52:14.071 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): Could not load login page to OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@1e11864::DecryptedEndPoint@16122af{l=/192.168.1.89:53084,r=partner-identity.myq-cloud.com/40.71.237.110:443,OPEN,fill=-,flush=-,to=47/0}
2022-09-29 18:53:17.298 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@1e11864::DecryptedEndPoint@16122af{l=/192.168.1.89:53084,r=partner-identity.myq-cloud.com/40.71.237.110:443,OPEN,fill=-,flush=-,to=47/0} to OFFLINE (COMMUNICATION_ERROR): Could not load login page
2022-09-29 18:55:17.946 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): Could not load login page to OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@7752ad::DecryptedEndPoint@9f708b{l=/192.168.1.89:53770,r=partner-identity.myq-cloud.com/40.71.237.110:443,OPEN,fill=-,flush=-,to=58/0}
2022-09-29 18:56:19.704 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@7752ad::DecryptedEndPoint@9f708b{l=/192.168.1.89:53770,r=partner-identity.myq-cloud.com/40.71.237.110:443,OPEN,fill=-,flush=-,to=58/0} to OFFLINE (COMMUNICATION_ERROR): Could not load login page
2022-09-29 18:57:20.007 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): Could not load login page to OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@32aef7::DecryptedEndPoint@3c074d{l=/192.168.1.89:47668,r=partner-identity.myq-cloud.com/13.83.98.203:443,OPEN,fill=-,flush=-,to=57/0}
2022-09-29 18:58:20.291 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@32aef7::DecryptedEndPoint@3c074d{l=/192.168.1.89:47668,r=partner-identity.myq-cloud.com/13.83.98.203:443,OPEN,fill=-,flush=-,to=57/0} to OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@189f863::DecryptedEndPoint@1e2adc6{l=/192.168.1.89:54450,r=partner-identity.myq-cloud.com/40.71.237.110:443,OPEN,fill=-,flush=-,to=50/0}
2022-09-29 18:59:21.000 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@189f863::DecryptedEndPoint@1e2adc6{l=/192.168.1.89:54450,r=partner-identity.myq-cloud.com/40.71.237.110:443,OPEN,fill=-,flush=-,to=50/0} to OFFLINE (COMMUNICATION_ERROR): Could not load login page
2022-09-29 19:00:21.331 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): Could not load login page to OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@3072af::DecryptedEndPoint@1d183ea{l=/192.168.1.89:54894,r=partner-identity.myq-cloud.com/40.71.237.110:443,OPEN,fill=-,flush=-,to=61/0}
2022-09-29 19:01:24.230 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): java.io.EOFException: HttpConnectionOverHTTP@3072af::DecryptedEndPoint@1d183ea{l=/192.168.1.89:54894,r=partner-identity.myq-cloud.com/40.71.237.110:443,OPEN,fill=-,flush=-,to=61/0} to OFFLINE (COMMUNICATION_ERROR): Could not load login page
2022-09-29 19:28:30.038 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): Could not load login page to OFFLINE (COMMUNICATION_ERROR): javax.net.ssl.SSLHandshakeException: Abruptly closed by peer
2022-09-29 19:29:31.103 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'myq:account:5c8e5ac110' changed from OFFLINE (COMMUNICATION_ERROR): javax.net.ssl.SSLHandshakeException: Abruptly closed by peer to OFFLINE (CONFIGURATION_ERROR): Could not login with credentials
Mine was offline as well, pausing and unpausing the account thing started it again. There was definitely an issue with their servers for a while. The binding tried to reconnect but eventually got an error during the login process that caused it not to retry again, this should only happen if the server specifically says the user is not authorized , so I would say that’s a bug, but I need to dig into that further .
3 Likes
I had the same unauthorized error. Disabling and enabling the bridge brought it back.
Adding thread here for insights from any MyQ binding experts here. Is there a way to control the bridge light? TIA
If the mobile app allows you to control this light, then yes its probably in the API, if not, then i doubt very much it’s controllable.
Good point, it is not. It only blinks when you close the garage.
@digitaldan does this binding work if you use the Google account on the MyQ app to login to it? Do I need to set up a separate password without using the Google account to allow it to function?
Yes you will need a username / password through myQ
am I the only one suddenly getting error on the myq account bridge? I get
COMMUNICATION_ERROR
Could not load login page
Nothing constant here in the US. It seems to go up and down every once in a while.
Mine was connected, but i just tried restarting and am getting this error now, i’ll take a look at getting a fix in for it.
COMMUNICATION_ERROR
org.eclipse.jetty.client.HttpResponseException: HTTP protocol violation: Authentication challenge without WWW-Authenticate header
1 Like
Even stranger is I am getting this returned to me during the login process
Login Code 429 Response {
"reason": "Too Many Requests",
"id": 5,
"isOk": false
}
But i don’t think it tried more then once or twice to log in…
Since today, I have same problem (location US)
So a little goolging shows this is a known (and partly fixed issue) with other myq API libraries, so hopefully should not be tough to fix in ours.
1 Like
Same here
I just took my Account Thing offline and back online and now get this error.
**COMMUNICATION_ERROR**
org.eclipse.jetty.client.HttpResponseException: HTTP protocol violation: Authentication challenge without WWW-Authenticate header
Hey just checking to see if there is an update on this?
This particular commit has the bulk of the changes needed to fix MyQ
Hope it helps to narrow the search.
I’m wondering if changing the binding to allow the end user to change the default, client_ID/user agent, URL and URI strings would reduce the need to update the whole binding each time chamberlain updates their API & OAuth methods.