MyQ Lite is no longer able to login to MyQ.com

[osborne1248]

Looks like this just happened again today. When trying to log in through MyQ in SmartThings getting the "The username or password you entered is incorrect. Go back and try again."

@brbeaird - can you work your magic please sir?

[chsull]

Ditto -- login is failing as of today.

[osborne1248]

Got message on another thread. He's working on it now. May be a few days before he knows anything.

[chsull]

Thanks!

[clmyers2019]

same here started getting before i updated everything

[phaldor8]

I have not updated and it’s happening to me as well so it is definitely something that myq did on their side

On Wed, Aug 25, 2021 at 09:29 clmyers2019 @.***> wrote:

same here started getting before i updated everything

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/brbeaird/SmartThings_MyQ/issues/126#issuecomment-905612153, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANQ4UK3LSPW45GYJMCKVGIDT6UD63ANCNFSM5CZJLBEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

-- Christopher Goodrich B.S., CISSP-ISSEP, ISSMP, HCISPP, RP @. @. 505-227-6130

[brbeaird]

Yep, MyQ changed something, and this is currently broken. I’m not sure at this point if it’s a permanent change - this has happened occasionally in the past where it comes back up the next day.

The good news is there is a newer version of the API login flow that some other integrations (HomeBridge, pymyq) are using successfully. The bad news is it is not a simple change to implement - a couple parts in particular I’m not really sure will work within Groovy. I will see what I can do, but it may be several days before I make any real progress.

[jasonkaruza]

Looks like per https://github.com/hjdhjd/homebridge-myq/search?q=v6 the main difference is around authentication for v6 using OAuth.

Starting with v6 of the myQ API, myQ now uses OAuth 2.0 + PKCE to authenticate users and provide access tokens for future API calls. In order to successfully use the API, we need to first authenticate to the myQ API using OAuth, get the access token, and use that for future API calls.

I'm not sure if the Smartthings Groovy implementation is the same as normal Java's, but it looks like there is an AuthConfig class that might help with Oauth: http://javadox.com/org.codehaus.groovy.modules.http-builder/http-builder/0.6/groovyx/net/http/AuthConfig.html

[brbeaird]

Yep. The nasty part here is that Oauth normally involves logging into a web form through a browser, which is not really something that is supported in groovy SmartApps in a way that would let the app properly get the resulting token. A couple of the other implementations are basically making http calls behind the scenes and scraping the HTML. It's not pretty and not easy, but in theory it should be possible.

On Wed, Aug 25, 2021 at 2:02 PM Jason Karuza @.***> wrote:

Looks like per https://github.com/hjdhjd/homebridge-myq/search?q=v6 the main difference is around authentication for v6 using OAuth.

Starting with v6 of the myQ API, myQ now uses OAuth 2.0 + PKCE to authenticate users and provide access tokens for future API calls. In order to successfully use the API, we need to first authenticate to the myQ API using OAuth, get the access token, and use that for future API calls.

I'm not sure if the Smartthings Groovy implementation is the same as normal Java's, but it looks like there is an AuthConfig class that might help with Oauth: http://javadox.com/org.codehaus.groovy.modules.http-builder/http-builder/0.6/groovyx/net/http/AuthConfig.html

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/brbeaird/SmartThings_MyQ/issues/126#issuecomment-905795920, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABXHM2A75APTP75BMM6MXQTT6U45RANCNFSM5CZJLBEQ .

[Moogacoder]

myQ is not working today even using their app. They must have an outage.

On Wed, Aug 25, 2021 at 3:07 PM Brian Beaird @.***> wrote:

Yep. The nasty part here is that Oauth normally involves logging into a web form through a browser, which is not really something that is supported in groovy SmartApps in a way that would let the app property get the resulting token. A couple of the other implementations are basically making http calls behind the scenes and scraping the HTML. It's not pretty and not easy, but in theory it should be possible.

On Wed, Aug 25, 2021 at 2:02 PM Jason Karuza @.***> wrote:

Looks like per https://github.com/hjdhjd/homebridge-myq/search?q=v6 the main difference is around authentication for v6 using OAuth.

Starting with v6 of the myQ API, myQ now uses OAuth 2.0 + PKCE to authenticate users and provide access tokens for future API calls. In order to successfully use the API, we need to first authenticate to the myQ API using OAuth, get the access token, and use that for future API calls.

I'm not sure if the Smartthings Groovy implementation is the same as normal Java's, but it looks like there is an AuthConfig class that might help with Oauth:

http://javadox.com/org.codehaus.groovy.modules.http-builder/http-builder/0.6/groovyx/net/http/AuthConfig.html

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/brbeaird/SmartThings_MyQ/issues/126#issuecomment-905795920 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABXHM2A75APTP75BMM6MXQTT6U45RANCNFSM5CZJLBEQ

.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/brbeaird/SmartThings_MyQ/issues/126#issuecomment-905799368, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAXSWYMQLXHZKHQGNF3QVLT6U5PDANCNFSM5CZJLBEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

[heisler3030]

actually the app is still working fine for me. Came over from https://github.com/thomasmunduchira/myq-api/issues/34 which is another project that started flapping today unfortunately.

[oferbarzakai]

same here - getting "MyQ command failed due to bad login". MyQ app directly works fine.

here is the log from the IDE:

[colinrblake]

My (own) iOS app is also failing as of yesterday. Have they turned off the V5 support?

CBL: response status code: 400
CBL: response data: {
    "SecurityToken": "",
    "ReturnCode": "0",
    "ErrorMessage": "please contact customer care, supportID: 14941968167351633782",
    "CorrelationId": ""
}

[dandrake2901]

Me too. Getting login errors from Smartthings when I try to control my garage door. Tried changing the password in the MyQ app. Can log into the MyQ app, but can't update the password in the MyQ Lite SmartApp in the Smartthings app.

[brbeaird]

Yes, it's going to be broken for everyone - sorry. MyQ made a change within the last 24 hours that breaks the version (v5) of the API we are using. At least one other project in github has successfully moved to v6, but it's a major change. I do think I'll figure out how to do it here, but with my schedule right now, it's not going to be quick, unfortunately.

[vrchlabak]

Thanks for getting on this!! Can't be without it!

[wtblock]

Good to know this is being addressed.

[benji1077]

Appreciate the investigation @brbeaird! I had just gotten automation back up and working and then ran into the “login error” noted above. Excited to get back to normal.

[wtblock]

I bypassed Chamberlain a long time ago by using a Z-Wave relay in parallel with the wired switch panel on my garage door controllers.

My Chamberlain gate controller is another problem however because it does not have a wired panel switch and can only be controlled via a remote or the MyQ hub.

While we are waiting for Brian to address the latest changes from Chamberlain, I decided to brut force a fix by modifying one of my remotes to be controlled by a ZigBee relay. If anyone is interested, I published a video here:

https://youtu.be/ImFzcnYiSzY

Regardless of whether or not the issue is resolved, having remote access to a remote will provide a solid backup if anything should go wrong in the future.

[oferbarzakai]

I bypassed Chamberlain a long time ago by using a Z-Wave relay in parallel with the wired switch panel on my garage door controllers.

My Chamberlain gate controller is another problem however because it does not have a wired panel switch and can only be controlled via a remote or the MyQ hub.

While we are waiting for Brian to address the latest changes from Chamberlain, I decided to brut force a fix by modifying one of my remotes to be controlled by a ZigBee relay. If anyone is interested, I published a video here:

https://youtu.be/ImFzcnYiSzY

Regardless of whether or not the issue is resolved, having remote access to a remote will provide a solid backup if anything should go wrong in the future.

i have done the same a while back trying to get out of the dependency of MyQ - while it works nicely as a backup, it breaks with automation. here is how: i have two people in my household (me and my wife) with automation rules to open and close the garage based on geolocation. with the MyQ app and the code brbeaird@ wrote the commands sent to the controller are specific to open/close so if both me and my wife are leaving at the same time (in the same car) the app will send two "close" commands to the controller which will simply close it, whereas with the workaround it will simulate two clicks on the remote which in affect will leave the garage door open (one will try to close yet the other will open it). same will happen when we come back: the app send two "open" commands which will open the garage while the workaround will simulate two clicks resulting in the garage door wither closed or stopped midway.

looking forward too see a fix from brbeaird@

[wtblock]

i have done the same a while back trying to get out of the dependency of MyQ - while it works nicely as a backup, it breaks with automation. here is how: i have two people in my household (me and my wife) with automation rules to open and close the garage based on geolocation. with the MyQ app and the code brbeaird@ wrote the commands sent to the controller are specific to open/close so if both me and my wife are leaving at the same time (in the same car) the app will send two "close" commands to the controller which will simply close it, whereas with the workaround it will simulate two clicks on the remote which in affect will leave the garage door open (one will try to close yet the other will open it). same will happen when we come back: the app send two "open" commands which will open the garage while the workaround will simulate two clicks resulting in the garage door wither closed or stopped midway.

looking forward too see a fix from brbeaird@

oferbarzakai@ I appreciate your concern but there is a simple workaround by creating two virtual switches ("Gate Open" and "Gate Close" in my case) using the WebCore smart app in SmartThings to create conditions based on the gate's sensor status where the virtual switches will open or close the gate.

Here is a screen shot of my WebCore piston:

Instead of having your automation activate the "Gate Remote" directly, it would only need to activate "Gate Open" or "Gate Close" and if either one of them are activated twice, the second activation will have no effect.

[oferbarzakai]

i have done the same a while back trying to get out of the dependency of MyQ - while it works nicely as a backup, it breaks with automation. here is how: i have two people in my household (me and my wife) with automation rules to open and close the garage based on geolocation. with the MyQ app and the code brbeaird@ wrote the commands sent to the controller are specific to open/close so if both me and my wife are leaving at the same time (in the same car) the app will send two "close" commands to the controller which will simply close it, whereas with the workaround it will simulate two clicks on the remote which in affect will leave the garage door open (one will try to close yet the other will open it). same will happen when we come back: the app send two "open" commands which will open the garage while the workaround will simulate two clicks resulting in the garage door wither closed or stopped midway. looking forward too see a fix from brbeaird@

oferbarzakai@ I appreciate your concern but there is a simple workaround by creating two virtual switches ("Gate Open" and "Gate Close" in my case) using the WebCore smart app in SmartThings to create conditions based on the gate's sensor status where the virtual switches will open or close the gate.

Here is a screen shot of my WebCore piston:

Instead of having your automation activate the "Gate Remote" directly, it would only need to activate "Gate Open" or "Gate Close" and if either one of them are activated twice, the second activation will have no effect.

nicely done! i will have to give it a try ;)

[oferbarzakai]

i have done the same a while back trying to get out of the dependency of MyQ - while it works nicely as a backup, it breaks with automation. here is how: i have two people in my household (me and my wife) with automation rules to open and close the garage based on geolocation. with the MyQ app and the code brbeaird@ wrote the commands sent to the controller are specific to open/close so if both me and my wife are leaving at the same time (in the same car) the app will send two "close" commands to the controller which will simply close it, whereas with the workaround it will simulate two clicks on the remote which in affect will leave the garage door open (one will try to close yet the other will open it). same will happen when we come back: the app send two "open" commands which will open the garage while the workaround will simulate two clicks resulting in the garage door wither closed or stopped midway. looking forward too see a fix from brbeaird@

oferbarzakai@ I appreciate your concern but there is a simple workaround by creating two virtual switches ("Gate Open" and "Gate Close" in my case) using the WebCore smart app in SmartThings to create conditions based on the gate's sensor status where the virtual switches will open or close the gate.

Here is a screen shot of my WebCore piston:

Instead of having your automation activate the "Gate Remote" directly, it would only need to activate "Gate Open" or "Gate Close" and if either one of them are activated twice, the second activation will have no effect.

i am testing this but i do not i follow you explanation for "if either one of them are activated twice, the second activation will have no effect." - why is that? say both me and my wife leaving the house, there will be two event that trigger "Close Gate" while the sensor is reporting "Open" hence there will be two "clicks" on the remote no? which will result in the door either open or stopped half way. what am i missing?

[wtblock]

i am testing this but i do not i follow you explanation for "if either one of them are activated twice, the second activation will have no effect." - why is that? say both me and my wife leaving the house, there will be two event that trigger "Close Gate" while the sensor is reporting "Open" hence there will be two "clicks" on the remote no? which will result in the door either open or stopped half way. what am i missing?

I have been looking at this and there is a problem with just looking for a "switch changes", but instead should be "physically changes to on" which would prevent the second phone from activating it again. After a delay, the code needs to reset the switch to the off state but I am still looking at the best way to do that. Another issue is the sensor changes immediately when opening, but does not change on closing until the gate is fully closed. Hopefully I will post a better version soon.

[oferbarzakai]

i am testing this but i do not i follow you explanation for "if either one of them are activated twice, the second activation will have no effect." - why is that? say both me and my wife leaving the house, there will be two event that trigger "Close Gate" while the sensor is reporting "Open" hence there will be two "clicks" on the remote no? which will result in the door either open or stopped half way. what am i missing?

I have been looking at this and there is a problem with just looking for a "switch changes", but instead should be "physically changes to on" which would prevent the second phone from activating it again. After a delay, the code needs to reset the switch to the off state but I am still looking at the best way to do that. Another issue is the sensor changes immediately when opening, but does not change on closing until the gate is fully closed. Hopefully I will post a better version soon.

FWIW - here is a piston i created that does the needful. i would still go back to use brbeaird@ code and the MyQ APIs as it is much more elegant and simple.

[wtblock]

i am testing this but i do not i follow you explanation for "if either one of them are activated twice, the second activation will have no effect." - why is that? say both me and my wife leaving the house, there will be two event that trigger "Close Gate" while the sensor is reporting "Open" hence there will be two "clicks" on the remote no? which will result in the door either open or stopped half way. what am i missing?

I have been looking at this and there is a problem with just looking for a "switch changes", but instead should be "physically changes to on" which would prevent the second phone from activating it again. After a delay, the code needs to reset the switch to the off state but I am still looking at the best way to do that. Another issue is the sensor changes immediately when opening, but does not change on closing until the gate is fully closed. Hopefully I will post a better version soon.

FWIW - here is a piston i created that does the needful. i would still go back to use brbeaird@ code and the MyQ APIs as it is much more elegant and simple.

@oferbarzakai My goal was a little different, I wanted the device to work with Alexa which required the virtual switches to be returned to the off state as soon as the gate stopped moving. This would also prevent either of the virtual switches from being activated a second time until the gate motion stops.

So most of the following code was to track the movement of the gate:

[PhillySports]

Sorry if this is off topic and if it needs to be moved elsewhere or deleted, I understand, but I feel like this is as good at time and place as any others to ask the question. Unless I a misunderstanding what will happen when SmartThings shuts down Groovy & WebCore (which perhaps, hopefully, I am), but even if brbeaird is able to get this working again, isn't this just a VERY temporary fix at this point - in the sense that by year end, this -- along with all other custom DTH and Smartapps are going to stop functioning?

Perhaps this is a good time and excuse to switch over to HomeAssistant? Am I missing something? Is there a chance that EXISTING smartapps and custom handlers will continue to work? But as I understand it, this is NOT the case.

[brbeaird]

Unless I a misunderstanding what will happen when SmartThings shuts down Groovy & WebCore (which perhaps, hopefully, I am), but even if brbeaird is able to get this working again, isn't this just a VERY temporary fix

It's worth mentioning, yes. This effort is likely the last hurrah for the SmartApp, and I'm not exactly sure how long it will even be in place. If we're lucky, maybe the groovy shutdown will get pushed out for a bit. At that point, I do plan to rewrite this whole thing to use the new SmartThings API smartapp flow. The tough part is that it will not be quite as simple as it is today where people can copy/paste the code into a web-hosted IDE. But for anyone who is willing to try, I will document the steps needed to get it running. Regardless, there is no way I'm going to back to having to manually hit my garage door every time I need it to open 😄

[RSwanson7]

I bypassed Chamberlain a long time ago by using a Z-Wave relay in parallel with the wired switch panel on my garage door controllers.

My Chamberlain gate controller is another problem however because it does not have a wired panel switch and can only be controlled via a remote or the MyQ hub.

While we are waiting for Brian to address the latest changes from Chamberlain, I decided to brut force a fix by modifying one of my remotes to be controlled by a ZigBee relay. If anyone is interested, I published a video here:

https://youtu.be/ImFzcnYiSzY

Regardless of whether or not the issue is resolved, having remote access to a remote will provide a solid backup if anything should go wrong in the future.

Do you have a Chamberlain with a rolling code? I am not able to hardwire a Zwave relay, i believe because of the rolling code. If i manually touch the two wires that connect to my wired Garage Door Controller the door does not open. It only opens when the button is actually pressed. Am I correct that you cannot use a simple relay when the Garage Door Opener is using a rolling code? Is there a way around that? or is the only way to use a battery remote control and connect the Zwave relay to that? Thank you,

[RSwanson7]

simple as it is today where people can copy/paste the code into a web-hosted IDE. But for anyone who is willing to try, I will document the steps needed to get it running. Regardless, there is no way I'm going to back to having to manually hit my garage door ev

Unless I a misunderstanding what will happen when SmartThings shuts down Groovy & WebCore (which perhaps, hopefully, I am), but even if brbeaird is able to get this working again, isn't this just a VERY temporary fix

It's worth mentioning, yes. This effort is likely the last hurrah for the SmartApp, and I'm not exactly sure how long it will even be in place. If we're lucky, maybe the groovy shutdown will get pushed out for a bit. At that point, I do plan to rewrite this whole thing to use the new SmartThings API smartapp flow. The tough part is that it will not be quite as simple as it is today where people can copy/paste the code into a web-hosted IDE. But for anyone who is willing to try, I will document the steps needed to get it running. Regardless, there is no way I'm going to back to having to manually hit my garage door every time I need it to open 😄

Is it likely that SmartThings will create a custom connection to MyQ? Looking at the MyQ app it says it works with Alarm.com, Google Assistant, IFTTT, etc. Is there any indication that SmartThings will be directly supported at some point?

[wtblock]

I bypassed Chamberlain a long time ago by using a Z-Wave relay in parallel with the wired switch panel on my garage door controllers. My Chamberlain gate controller is another problem however because it does not have a wired panel switch and can only be controlled via a remote or the MyQ hub. While we are waiting for Brian to address the latest changes from Chamberlain, I decided to brut force a fix by modifying one of my remotes to be controlled by a ZigBee relay. If anyone is interested, I published a video here: https://youtu.be/ImFzcnYiSzY Regardless of whether or not the issue is resolved, having remote access to a remote will provide a solid backup if anything should go wrong in the future.

Do you have a Chamberlain with a rolling code? I am not able to hardwire a Zwave relay, i believe because of the rolling code. If i manually touch the two wires that connect to my wired Garage Door Controller the door does not open. It only opens when the button is actually pressed. Am I correct that you cannot use a simple relay when the Garage Door Opener is using a rolling code? Is there a way around that? or is the only way to use a battery remote control and connect the Zwave relay to that? Thank you,

Rolling codes were implemented for wireless devices to prevent somebody from driving by your house and opening your garage door with a third-party remote. Direct wiring is not affected by Rolling codes. I did something very similar with my garage door openers when I put the relay on them, that is I shorted out the contacts to verify that I could open the garage door with a switch. Having said all of that, it is entirely possible that I'm not aware of some recent changes.

[brbeaird]

Is it likely that SmartThings will create a custom connection to MyQ?

Yes, that is my strong suspicion. I would guess that at this point, WebCORE and this app are probably the top two most common apps left on groovy. It would not surprise me if they waited until they could finally get a native ST-MyQ connection set up before moving forward with shutting down groovy. Still, even if that happens, I do worry that it will be restricted in some way where I'll end up writing my own implementation anyway. Who knows. Should be interesting to see where we are on this a year from now.

[RSwanson7]

Do you have a Chamberlain with a rolling code? I am not able to hardwire a Zwave relay, i believe because of the rolling code. If i manually touch the two wires that connect to my wired Garage Door Controller the door does not open. It only opens when the button is actually pressed. Am I correct that you cannot use a simple relay when the Garage Door Opener is using a rolling code? Is there a way around that? or is the only way to use a battery remote control and connect the Zwave relay to that? Thank you,

Rolling codes were implemented for wireless devices to prevent somebody from driving by your house and opening your garage door with a third-party remote. Direct wiring is not affected by Rolling codes. I did something very similar with my garage door openers when I put the relay on them, that is I shorted out the contacts to verify that I could open the garage door with a switch. Having said all of that, it is entirely possible that I'm not aware of some recent changes.

I believe with Security+ 2.0 even the Wired Wall Button cannot be replaced by a simple press button and has to be a Chamberlain/Liftmaster device. So simply connecting a relay in parallel would not work. You would have to open the guts of the Wall Button and somehow simulate an actual button press. I'm not an electrician, or garage door opener expert, so I may have missed something, but this is my understanding.

[wtblock]

Do you have a Chamberlain with a rolling code? I am not able to hardwire a Zwave relay, i believe because of the rolling code. If i manually touch the two wires that connect to my wired Garage Door Controller the door does not open. It only opens when the button is actually pressed. Am I correct that you cannot use a simple relay when the Garage Door Opener is using a rolling code? Is there a way around that? or is the only way to use a battery remote control and connect the Zwave relay to that? Thank you,

Rolling codes were implemented for wireless devices to prevent somebody from driving by your house and opening your garage door with a third-party remote. Direct wiring is not affected by Rolling codes. I did something very similar with my garage door openers when I put the relay on them, that is I shorted out the contacts to verify that I could open the garage door with a switch. Having said all of that, it is entirely possible that I'm not aware of some recent changes.

I believe with Security+ 2.0 even the Wired Wall Button cannot be replaced by a simple press button and has to be a Chamberlain/Liftmaster device. So simply connecting a relay in parallel would not work. You would have to open the guts of the Wall Button and somehow simulate an actual button press. I'm not an electrician, or garage door opener expert, so I may have missed something, but this is my understanding.

I have not replaced an opener in several years, but I cannot understand the need to make a wired connection secure. If anyone has access to your garage, they could just push the button on the panel and would not need to short the contacts on the controller.

I must be missing something and if so, then modifying the remote will certainly work because my remote does use rolling codes and the switch on the remote circuit board is a simple push button.

[teba-home]

I have contacted MyQ support multiple times asking for integration with SmartThings and NEVER get a direct answer. I always got the stock were always looking at new integrations script. Same response when asking about Alexa integration (which floors me that it is Key by Alexa compatible but not Alexa). Maybe if everyone floods them with requests they might consider it?

[PhillySports]

You can use a zen 16 from Zooz to control multiple MyQ doors. Then you don't have to worry about cloud integration at all https://www.support.getzooz.com/kb/article/369-how-to-use-the-zen16-multirelay-as-a-garage-door-opener-on-smartthings/

It is my understanding that this (and similar workarounds) do not work with newer garage door openers. Look at the first few sentences of instructions on the web page from Zooz, "If your garage door opener uses a proprietary wireless control system, you will NOT be able to use the ZEN16 MultiRelay (or any other Z-Wave device)."

The only functioning workaround with these newer proprietary systems was MyQ Lite or hacking the remote control and welding in a relay switch.

[teba-home]

For anyone interested, I posted a work around on the ST forum. Here's the link... https://community.smartthings.com/t/myq-lite-stopped-working-yesterday-2021-08-26/230828/9?u=terri_baker

[hubmon]

Tried your work around without success. Alexa doesn't find the devices. Link confirmed in Alexa. Can open & Close Door with SC.

[teba-home]

@hubmon I missed adding a step. The instructions have been updated and should work now. Try again and let me know. If the alexa skill is already enabled you should be able to do a manual device discovery or disable/enable the skill to get the SC scenes.

[hubmon]

Alexa now finds the 2 Scenes. Thanks

[wtblock]

I rewrote the WebCoRE code I published earlier to simplify it and to support a warning beep prior to opening the gate or garage door.

There is a video on YouTube that describes the code and also illustrates how to integrate the code with Android Auto in your car as well as Alexa in the car.

The video is located here:

https://youtu.be/PrxMtKocahE

[hjackson2]

bbeard thanks for your efforts! Would love to know if/when you have a solution.

[brbeaird]

It is done. This is fixed with #129 Check out the new Readme - take note of the new token generator section.

[dandrake2901]

Sorry, but it's not working for me.

In the Smartthings IDE I updated both the Device Handler and the SmartApp from Github via the Repo. I downloaded the Windows version of the Token Generator, ran it, authenticated with my MyQ credentials and pasted the resulting code into the Settings of the SmartApp.

The MyQ Lite SmartApp on my phone show the SmartApp and Device versions both as 4.0.0. (Screenshot attached)

When I attempt to open or close the door from the SmartThings app, I get an error that says "A network or server error occurred. Try again later."

The door does open and close successfully from the MyQ app.

[firefox15]

Unfortunately, I have the same error message on mine. Still, props to you, Brian, for getting it turned around so quickly. This feels really close.

[spenjco17]

After I added the token, I had to modify my devices within the MyQ Lite SmartApp. Once I removed my garage and re-added it, everything works great. I will have to modify my webCoRE pistons but I can live with that. Thanks @brbeaird for sticking it to MyQ once again!

[brbeaird]

After you update, open the SmartApp, tap modify devices, then tap through that process. Then try again. If still no luck, you may try reinstalling.

On Fri, Sep 10, 2021 at 12:12 AM firefox15 @.***> wrote:

Unfortunately, I have the same error message on mine. Still, props to you, Brian, for getting it turned around so quickly. This feels really close.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/brbeaird/SmartThings_MyQ/issues/126#issuecomment-916636626, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABXHM2E6X7WYF4GBW7HK3XTUBGHTFANCNFSM5CZJLBEQ .

[firefox15]

After you update, open the SmartApp, tap modify devices, then tap through that process. Then try again. If still no luck, you may try reinstalling. … On Fri, Sep 10, 2021 at 12:12 AM firefox15 @.***> wrote: Unfortunately, I have the same error message on mine. Still, props to you, Brian, for getting it turned around so quickly. This feels really close. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#126 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABXHM2E6X7WYF4GBW7HK3XTUBGHTFANCNFSM5CZJLBEQ .

It looks like running through the wizard again fixed it. Thanks so much!

[hjackson2]

Thanks! Where can I find the readme file?

Thanks,

Hank

From: Brian Beaird @.> Sent: Friday, September 10, 2021 12:03 AM To: brbeaird/SmartThings_MyQ @.> Cc: hjackson2 @.>; Comment @.> Subject: Re: [brbeaird/SmartThings_MyQ] MyQ Lite is no longer able to login to MyQ.com (#126)

It is done. This is fixed with #129 https://github.com/brbeaird/SmartThings_MyQ/pull/129 Check out the new Readme - take note of the new token generator section.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/brbeaird/SmartThings_MyQ/issues/126#issuecomment-916611939 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD56WYMUDVDHI3OLX6ULSWLUBF7ODANCNFSM5CZJLBEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . https://github.com/notifications/beacon/AD56WYMGAHQMGICYND33EB3UBF7ODA5CNFSM5CZJLBE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOG2RGGYY.gif

[Xtropy74]

Working perfect for me after following the steps in the Readme to generate the code and then doing the "open the SmartApp, tap modify devices, then tap through that process" steps.

Thanks for the fix!

[SpazShark]

Working for me now as well after following the token generation instructions and modifying the devices.

I didn't do the "open the SmartApp, tap modify devices, then tap through that process" steps until I visited this site. Might be a good idea to add that to the end of the token generation instructions?

Great work on this - thanks so much for updating it!