Devices deleted an hour after creating an API key

Developer Programs Support
1

Since last year I have 3 Samsung Windfree AC which are all visible and controllable within the SmartThings app.
I now wanted to have the status of all devices in my home automation screens, so I created an API key and used Postman to get the device ids. Then I queried the devices to check the answer json and created the corresponding items in my home automation (OpenHAB).
This whole process took me about an hour.

While I was creating a nice widget to view the AC on screen I realized that the REST API calls returned 401 unauthorized in the meanwhile. Checking the token on account.smartthings.com/tokens, it was gone.
So I created a new one, but the calls still returned an error.
Checking back in Postman I now get an emtpy device array:
{
“items”: ,
“_links”: {}
}

What happend?
I can still see the devices on v3.account.samsung.com/dashboard/devices, but they are also gone in my SmartThings app and the app can’t add them again → Error 15-200.

So can anyone tell me how to fix the API stuff?
And why does the working stuff use v3.account and the token is not in v3?

BTW: loging in into my dot smartthings dot com redirects to my dot smartthings dot com/location and shows me an empty page? Does Samsung have platform issues at times?

2

My SmartThings is working for me in the US.

I did get redirected to a page to accept terms and conditions. I don’t normally get that.

Do you have an Ad or Popup blocker that might have prevented the contents of that page from displaying?

1 Like
3

Yes.

But that’s not necessarily what you ran into.

Several people did report some platform problems on Monday, for what that’s worth.

Devices barely responding, status' not updating.... hub status not even showing offline when unplugged (15 July 2024)

4

That’s because you are viewing your Samsung devices in your Samsung account.

SmartThings uses the Samsung account for authentication but otherwise does its own thing.

Nothing else you described made much sense. The 401 is consistent with an invalid token, or in your case a deleted one. It’s all too easy to delete a token on the management page but you usually realise if and when you’ve just done it and it doesn’t sound like you did. In any case other stuff doesn’t sound right.

Weird stuff can go on with the API on occasions, particularly when you start picking up the wrong datacentre for your region, but it is pretty niche.

Currently the only thing remotely ‘different’ I am seeing in the API is that the /accounts endpoint has recently started returning a 401, but that seems to be a bit of a relic anyway.

5

Hi, @TiQ. Welcome to the SmartThings Community!

I think you should visit the Advanced Users app > devices to see if your devices are listed there. It consumes the SmartThings API. If your devices are registered in the SmartThings platform, they should appear.

6

Thanks a lot.
It all resolved a day later when I was able to readd my devices and they were also available over the API with the new key.
Just seems that somehow everything was deleted.
But at least I could put everything together again.