Unless there are regional issues to consider, that redirect looks correct for ‘stage 3’. Your platform is returning the temporary code to SmartThings in a redirect URL.
That URL should be one of the ‘supported links’ in your mobile app so as I understand it the redirect action should be to open your app and it will then move on to ‘stage 4’. Is it opening a browser window instead?
@orangebucket It opens a browser window inside the SmartThings app. I have to select the option
“Open in Chrome browser” to see the page in the browser.
@orangebucket We have it working on Alexa and Google Home with this OAuth configuration.
If you go to Get Started With SmartThings Schema | Developer Documentation | SmartThings in Chrome and click on the https://c2c-us.smartthings.com/oauth/callback link, do you get taken to a webpage saying you can’t link your account or does the SmartThings app open up? It should be the latter although I find that I have to have SmartThings app already active for it to work.
Hi, @aalmada,
So, the URI registered in the field of Authorization URI is never called when you select your integration?
You should get a GET request to that URI as part of step 2 mentioned above, then, you’ll need to issue an authorization code and send it to the callback URL according to your region.
For example, considering the picture above, my integration calls this URL when I select it in the app:
Once step 4 is completed, SmartThings will have an Access Token to authorize its requests with your server.
You don’t need to get a Reciprocal Access Token for the state/discovery callbacks for SmartThings to call your Schema Connector (step 5).
Can you let us know which steps are working correctly and when the process gets stuck, please?
Are you using the Schema SDK?
