I continue to have the HTTPS Error 401 coming back after a few hours (days ?).
I can fix it by creating a new Personal Token on SmartThings and using that new one in the settings for the App. But it’s annoying and strange…
I found that someone posted a similar issue with SmartThings API integration on Reddit a few hours ago… Reddit - Dive into anything
I read especially that PATs were meant for short-term testing and development, but they’ve been used for long-term integrations and so newly issued PATs will expire after 24 hours (And I did create a new one recently indeed)
Just a quick update, all be it not a good one, Athom have reported that they also have never heard back about obtaining an OAUTH2 token that supports more users.
Basically, it appears that SmartThings just want rid of anything that’s not expanding their own ecosystem.
Aaah to bad im also fed up with stuff like this where the support changes after ive bought it (just recently also with my solar panels)
So just like my solar panels ive now installed a Shelly power measure in the socket of my Samsung clothes washer. To bad but this way im able to see when its finished and no cloud needed.
However ive noticed it uses 15watt while powered off also hours after it has been used that’s crazy, does anyone else also noticed this?
I have succesfully added my Suamsung Smart Tag version 1 using the apps and the Samsung token. When generating the token I made sure that I ticked all the boxes. However when I want to make a flow which would use the location of the Smart Tag I see no option to use that in the flow. The location status is just not there. I have a HP23. Any suggestions are welcome. Thanks, Idso.
Das mit den 500 benutzern ist wie gemeint ? Meinen die geräte oder was meinen die?
Ich habe gerade gelesen das man mit OAUTH2 auch token erstellen kann die aber auch nur 24std halten und die einloggen geschichte bei OAUTH2 besteht wohl auch aus 2 bedingungen client id und client secret
Und die app erfordert ja einen token im Konfigurationsfeld daher würde doch diese OAUTH2 methode gar nicht gehen oder ?
I replied directly to the error log as soon as it came in. Basically it has error code 429, which means there have been too many requests. Are you using the same tokens for any other integrations?