Any solution for “As of 30 Dec, SmartThings will start restricting the TTL (time to live) of newly issued PATs to 24hrs. We will also lower the rate limits on the /devices endpoint for newly issued PATs. Both of these changes are intended to improve the security of the platform and give us better control over ingress routes to prevent disruption to the whole platform from potential accidental or intentional bad actors.”
Thanks
/ian
Hi Ian,
Can you add info about which of the several Homey SmartThings apps you’re using?
And, you can use the correct support channel right away, when you read the homey.app app page. Often there’s dedicated app topics available.
@Peter_Kawa there are 2 smartthings apps ( 1x Officiele Athom en 1x Community) and the official one doesn’t have an link in the Homey website
Besides that I do also have the issue where my Homey doesnt read my Samsung Dryer and washer since a short while.
Im also hoping for a solution
I count 3 
I can fully recommend the SmartThings community app by Adrian Rockall. ‘Official’ apps are often not the best choice imho.
The ‘official’ one has other support channels to report issues:
I have posted information in other topics, but just to keep everyone informed, I have heard that SmartThings are changing the rules of the PAT. Newly issued PATs will expire after 24 hours and will have tighter rate limits. That obviously makes them useless for use with Homey.
The only alternative is to switch to an OAUTH2 login, but the private tokens only support 500 users. That is also useless for Homey as my current app has around 1500 users.
It’s possible to request a token that supports more users, but I have not had a response to the request. Also, I believe those come at a cost, which I think is why Athom abandoned their official app.
Old PATs should continue to work as before, so if you have already been using the app then it should continue to work.
Unfortunately, I feel this is the end of SmartThings integration with Homey, unless I get a response about a more suitable OAUTH2 token.
Thanks for the heads up, Adrian.
That’s bad news for you and (new) app users.
Let’s hope you get a positive response to the OAUTH2 token request.
Being confronted with this at the moment I am wondering if adding the use of a smartthings hub could be an option? Or is an hub such as the Aeotec also hit by this limit?
ohw so stupid of me ive had an issue and deleted the old PAT and then created a new one …
Restoring a backup might restore the original PAT as well?
This doesn’t seem to omit the need to use a PAT
To circle back on the topic and not believing there might be a short term solution to this (as with Tuya) I purchased a Switchbot Mini Hub to support my use case of being able to operate the Air-conditioning within Homey.
@Doekse are there any ongoing talks with Samsung about this? Would be a shame to not have a working SmartThings integration anymore
Trying my best! Unfortunately, Samsung isn’t the easiest partner to work with 
Hoping this gets an update, thank you for working on this!
What about having users supply their own oauth key in the app settings?
I think @Adrian_Rockall might be able answer your question, Peter
Seems like the Samsung app was updated to support OAuth but it doesn’t work for me, I always end up with “Unauthorized Client” on the redirect back after the login. Anybody else more luck?
Hi,
Official smartthings app has had an update on the homey app store. It wil still first ask for a PAT but after that it will authenticate a other way and don’t use the PAT anymore. I did not check after 24 houres but this should work.
Correction. It still doesn’t work…
Edit: There is a update on the official Smartthings app 3.1.1! Testing it right now. I would let you know if it works after 24h.
Edit 2: It is fully fixed and the PAT is only needed for registering the OAUTH! It keeps working now on the official integration.
So if the PAT no longer works (which is the case for me), it would be handy if the app description would state that.
