Echo and Multiple SmartThings Locations (Hubs)

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@scottalex

You’re saying for every child dashboard you’re able to generate a unique OAUTH client-id?

Not quite: You don’t get a unique “client-id”, but rather a unique “INSTALLATION-ID” … i.e., Each installed Instance of any SmartApp gets a unique “$app.id” (that’s what it is referenced as from inside the SmartApp instance, btw), and the OAuth process returns this by just calling the “/endpoints” REST-API.

This should be sufficient for any Third-Party service to keep a list of Locations under a SmartThings Account and link to them in one IFTTT or Amazon Echo account. (heck, even multiple SmartThings Accounts, actually, since the user could use different logins for each new “connection” they create.

So it is entirely supported on the SmartThings Platform (and we’ve demonstrated it with SmartTiles).

@Jim

Get SmartApp Endpoints

Using the access token, get the endpoint for the SmartApp:

GET -H “Authorize: Bearer ACCESS-TOKEN” “https://graph.api.smartthings.com/api/smartapps/endpoints”

A successful response will look like this (we will probably remove sending back the client secret soon, and the url is there for legacy purpose - use the uri):

{
“oauthClient”: {
“clientSecret”: “CLIENT-SECRET”,
“clientId”: “CLIENT-ID”
},
“uri”: “BASE-URL/api/smartapps/installations/INSTALLATION-ID”,
“base_url”: “BASE-URL”,
“url”: “/api/smartapps/installations/INSTALLATION-ID”
}