I Finally Figured Out Why My Local Run Device list is Always Empty

I have been using this link https://graph.api.smartthings.com/localDevice/list which does not work for me. the list is always empty. That is the link that is always given for the US version to view local run devices. I noticed when I logged into my IDE this morning that the link was different.

The link to view my local devices is really https://graph-na02-useast1.api.smartthings.com/localDevice/list
so if your local device list comes up empty log into your IDE and look at the web address its pointing you to. then change your link to match your actual web address. for me i just had to add whats in bold to the end of my web address https://graph-na02-useast1 .api.smartthings.com/localDevice/list
so that it looks like this https://graph-na02-useast1.api.smartthings.com/localDevice/list

this might help some that have the empty local device list problem. this also makes me wonder how many webservers they have running since na02-usaeast1 would imply multiple servers

4 Likes

The original “graph.api” is NA01 (I think they even added an alias or redirect… Try it?).

But there are obviously plans for lots more clusters (shards). I hope there’s an easy way provided for users to redirect without confusion (not just web services SmartApps).

Thanks! My lists were empty at the links you gave, but had entries at the other, so I must be on server one.

The community-created wiki page has been updated with both URLs: :sunglasses:

http://thingsthataresmart.wiki/index.php?title=FAQ

As I recall, they said when they added the UK server that they were also adding a second North American server after they ran into the Oauth problems.

4 Likes

na01 will not load for me. it prompts me to log in. I go ahead and log in then try na01 and get bounced back to https://graph.api.smartthings.com/. That makes me think they have some load balancing in place

1 Like

What would be good is perhaps in the ST app show the server link that you are using in the ‘about’ section.
Would save all the scratching around.

Just a thought…

2 Likes

That would be a good thought to add to the following area:

https://community.smartthings.com/c/mobile-app/features-feedback

You probably should include that smart apps will be the same way i will test in a few min but im sure they will be

1 Like

yea here is the smart apps that run local address
https://graph-na02-useast1.api.smartthings.com/localInstalledSmartApp/list

That’s the way I meant it works… i.e., “graph.api.smartthings.com” is, essentially, “na01…”; but the haven’t renamed the original yet and may never do so.

I’ve been told that “ide.smartthings.com” is the official URL for automatic redirect to the shard associated with your account;** though eventually “graph.api” may also serve this purpose, right now: “na01…” = “graph.api”.

###Gosh that’s a confusing paragraph how about this:

There are 3 shards currently (as far as I know; and there must be beta and dev shards too).:

  1. graph.api.smartthings.com; which should be eventually renamed to something like “https://graph-na01-useast1.api.smartthings.com”. The latter path currently redirects to the former, perhaps just as a convenience, or to set the stage for eventual renaming.

  2. https://graph-na02-useast1.api.smartthings.com; the shard for all new North American Accounts.

  3. https://graph-eu01-euwest1.api.smartthings.com; the shard for all UK / Ireland Accounts.

You can perhaps extrapolate what the names will be for future shards in EU and NA, … and DPRK :japanese_castle: :wink: … (yes… joking … DPRK = North Korea); obviously a South Korean shard is more likely first, right?

lol yes i see what you are saying.

1 Like