Are you replying to @kurtsanders or me?
My gateway is Sears
Both of you. MyQ is down for everyone as far as I can tell (the official MyQ app still works)
OK. I looked a little further up and saw they were having similar issues. I just wish Chamberlain and the MYQ guys would just play nice with everyone. lol
I agree, wonder if this is temporary or they have blocked the origin IP? I noticed that I am not getting any response from the MyQController code on my raspberry pi server
I have been using the old copy ninja version without issue and it stopped working for me as wellā¦my poller isnāt updating the door status. I am not in front of a machine to check the logs. Say it aināt so!!!
Ahhhhhhh Balls!
Out here too. MyQ app works still.
@brbeaird Looks like they have been making breaking API changes.
FWIW, I sent my requests through my own proxy to make sure they hadnāt simply blocked STās outgoing IPās. I got the same result going through my own private IP address.
The guys over here seem to have it reverse engineered already:
https://community.home-assistant.io/t/myq-componenet-issues/1860/229 - Jump to the bottom of that thread.
I think if you port over the commits from Feb 13 here (https://github.com/arraylabs/myq/commits/master) to your SmartApp, things will start working again.
Thank you. I also found where another guy reverse-engineered it here http://forum.universal-devices.com/index.php?
Just now I was able to reproduce it manually. Iāll need to work it into the SmartApp code now.
Iām working alongside you . Please note, the link I posted is hardcoding one appID for everything, and that does not work with my craftsman. If I send the craftsman appID, I can get logged in via Postman.
OK, I have working code now. Iāll submit it as a PR, no hard feelings if you use your own code instead
lol, I JUST got mine working, too. Iāll compare and see if weāre doing the same thing.
I was editing an old version, so I need to rebase in order to PR. Hereās what I did:
Added this method:
// HTTP POST call
private apiPost(apiPath, apiBody = [], callback = {}) {
if (state.session.securityToken) { apiBody = apiBody + [SecurityToken: state.session.securityToken ] }
try {
httpPost([ uri: getApiURL(), path: apiPath, contentType: "application/json; charset=utf-8", body: apiBody,
headers: [MyQApplicationId: getApiAppID()], ]) { response -> callback(response) }
} catch (SocketException e) {
//sendAlert("API Error: $e")
log.debug "API Error: $e"
}
And then called it via doLogin like:
private doLogin() { apiPost("/api/v4/user/validate", [username: settings.username, password: settings.password] ) { response -> log.debug "got login response data: ${response.data}"
if (response.status == 200) { if (response.data.SecurityToken != null) { state.session.securityToken = response.data.SecurityToken state.session.expiration = now() + 150000 return true } else { return false } } else { return false } } }
Note that I also added /v4/ to the login URL.
Thatās almost exactly what I did. Nice.
Hey everyone! Iāve pushed out an updated version of the MyQ Lite SmartApp that should fix the issue. Give it a shot and see if it starts working again for you.
Confirmed your changes work for me on my Craftsman, thanks!
Itās working for me again as well. Thanks for the excellent work on this!
Thank you for figuring this out guys! Great job! Chamberlain is working now for me.
Sorry for the dumb question, but how do I update the Smartapp via Smartthings IDE?
Nevermindā¦ I got the GitHub working.
Hey guysā¦
MyQ Community Manager, Official Rep
131 Posts 46 Reply Likes
The MyQ Connect SmartApp used a private endpoint that is not officially supported by Chamberlain. Due to impacts on our platform, we have informed SmartThings that we can no longer allow access by this SmartApp, and have closed the IP address it uses.
Although the MyQ garage door openers will not be able to run on the SmartThings platform in the short term, SmartThings is working directly with us to officially bring MyQ garage door openers and our functionality to SmartThings platform in the coming months.