Token Generator about smartthings_myq HOT 5 CLOSED

Hey @hjdhjd - I wanted to mention that my new version of this integration does use your library. Just wanted to say thanks - it is really awesome and greatly simplified the work I had to do. Cheers.
https://github.com/brbeaird/SmartThings-MyQ-Edge

from smartthings_myq.

If you keep hitting issues with token generation, sit tight. I may have another solution that actually brings the whole thing back into the SmartApp so we can avoid it altogether. Will be another few days probably.

from smartthings_myq.

Hi guys…I thought you’d find this helpful….I’m the author and maintainer of the Homebridge myQ plugin. I’ve finally gotten around to breaking out my API implementation as it’s own library @hjdhjd/myq that you can use.

It’s a full implementation of the v6 myQ API, and I’ve had thousands of users on it for almost a year. It’s solid, though welcome any contributions or feedback to further improve it. I thought I’d raise it to your attention…there’s a lot of independent efforts around myQ out there, and thought it might be a good idea to try to get some critical mass around a robust implementation for those of us supporting the various smart home ecosystems to collaborate for the good of all.

It eliminates the need for the token generation process you’ve got here, for what it’s worth. Library’s pretty straightforward to use, and you can look at my own Homebridge plugin to see it in action if you want a live example to work from.

Welcome any thoughts…good luck!

from smartthings_myq.

I was able to use @hjdhjd's library successfully. Here is the code:

import { myQApi } from '@hjdhjd/myq';

const myQ = new myQApi('<email>', '<password>');

await myQ.refreshDevices();
console.log(myQ.refreshToken);

However, I also discovered something else. The MyQ API seems sensitive to which IP address I'm using. While on WiFi at home, the MyQ app fails to login with There was an error connecting to the server. Please check your connection and try again.. That corresponds to the error I get from @hjdhjd/myq:

myQ API: https://partner-identity.myq-cloud.com/connect/authorize?client_id=IOS_CGI_MYQ&code_challenge=<challenge>&code_challenge_method=S256&redirect_uri=com.myqops%3A%2F%2Fios&response_type=code&scope=MyQ_Residential+offline_access 
Error: 400 Bad Request
myQ API: Unable to access the OAuth authorization endpoint.

However, when I switch to the mobile network or VPN, both work successfully.

Unfortunately, I cannot get the @brbeaird SmartApp to work - presumably because my SmartThings controller is sitting on my network, using my IP.

from smartthings_myq.

A couple things here:

• Thanks, @hjdhjd for dropping by and for that sweet library. I will definitely make use of it in the next generation of this app. Sadly, I cannot make use of it here because the actual logic of this SmartApp runs in the SmartThings cloud on Groovy, so I cannot directly use it as-is. Eventually, these cloud-hosted Groovy apps will be deprecated, and I will probably write some kind of self-hosted javascript equivalent that uses the new SmartThings API and imports the new myQApi npm package.
• The good news is the token generator is no longer needed with the latest SmartApp version I pushed out. @laalfonso - feel free to give the latest code a try if you want to avoid the need for a manual token. Details on that change are now on the Readme.

from smartthings_myq.