Next hotfix release will add reauthentication, so that at least gets a bit easier
4 Likes
New to HA
But same issue here.
I lose ST every 24 hours.
Also token cannot be reused.
I have to regenerate.
Any updates on a fix.
1 Like
look at the github above if you didn’t delete your old PAT you can pull the old one back out
Can you help explain what that will do for newbs?
I finding the same thing. Really rely on SmartThings. Please fix ASAP
1 Like
When you say next hotfix, is that Home Assistant?
2 Likes
Also looking forward to this fix andhopefully soon before my demo expires as I need to test the integration features as most of my devices are on smartthings and not worth paying if it doesn’t integrate.
Also affected by this annoying issue.
So I gave up waiting and frankly I don’t have much faith in SmartThings to remain stable (short term and changing their policies again) so going all-in on Home Assistant. If you didn’t delete your PAT there is a solution above.
I have MANY (40+) zwave switches and dreaded moving them over. I bought a Zooz 800 LR USB radio and followed this video and thread. It’s a little in the weeds and I’m “techy” but not a programmer but could follow along with the logic of the Zwave network. I would recommend watching the video 2-3x before starting. I think my devices are all working. If you plan on doing this I would recommend updating the firmware first, as and then downloading the software from silicon labs. I used these instructions:
I thought I should share as many of you are probably thinking the same, thanks to @cornellrwilliams for putting the video together.
Then I used JS UI and the configuration that I used was this video:
I’m in the same boat. I really hope we get the smartthings integration back.
From SmartThing Community Forum - Changes to SmartThings Personal Access Tokens (PAT)
As part of SmartThings’ ongoing work to improve our platform and deliver a high-performing and secure smart home experience for our users, we’re making some changes to how personal access tokens (PATs) work.
PATs were originally intended as a way to test and evaluate new integrations and SmartApps on the SmartThings platform. Since SmartThings provided an easy way to generate PATs over 10 years ago, they’ve been used extensively by our developer community to create and share new devices and unique integrations.
Unfortunately, their very nature (easy to generate, very wide scopes/permissions, and basically anonymous) have also become a problem over the years. The use of PATs for long-lived integrations was never their intent and presents a problem for how we manage the platform going forward. They’re a security risk due to the lack of scope restrictions. They’re incredibly opaque - we can’t really tell who’s using them or how, making management of our architecture and development of new features a challenge. There are also better ways to integrate with SmartThings, such as the widely used OAuth2 standard, which provides a much better authentication structure and flow with appropriate scope restrictions.
Starting at the end of December, we’re going to make some proactive changes to how PATs are issued to get back to their original intended uses - for testing, development, and evaluation of the SmartThings platform. As of 30 Dec, we 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.
Two important things to note:
- These changes only impact newly issued PATs. As of now we’re not making any changes to existing PATs. We know that of the 40k or so PATs in active use, a number of those are being used for critical integrations for users’ locations such as the 20k or so being used for Home Assistant. We don’t want to break that functionality and before we would consider making any changes to existing PATs, we’d want to have a paved path to keep our users’ locations functioning reliably.
- If you have an integration that requires generating new PATs for ongoing access, we’d encourage you to refactor that to use an OAuth flow so that it doesn’t rely on issuing new PATs to work in the future.
We’ve tried to design these changes in a way that safeguards the platform but also respects the existing use cases we know about (primarily ones like Home Assistant, InfluxDB, and development via the CLI). Since the use of PATs is highly opaque to us though, we’d really appreciate discussion from our users on other uses of existing PATs so that we’re aware of those going forward.
A possible solution to explore would be to utilize the Edge Driver and create an App for Home Assistant
Official SmartThings Production Driver Channel
SmartThingsCommunity - Github Repositories
SmartThings Community - Latest Developer Programs/Tutorials
How to Build Direct Connected Devices
1 Like
stopped waiting, I have started porting my devices off SmartThings Hub, and directly to HA via local Zwave stick. Actually had some instability with mushroom buttons on smartthings, bubble card buttons were more stable. But now on local z wave and off smartthings, both mushroom + bubble card buttons 100% bullet proof on local zwave
Well now this is really good news.
I started with HA in 2014. I recently purchased a new refrigerator and having HA integration was a big part of the buying decision and did my homework. Delivery was 13JAN2025. The past few days I’ve noticed having to create a new token, then realized it’s after every HA restart.
Now here I am reading this thread. Bummed to say the least. I’m still within a return window and am considering it. Are you listening Samsung?
3 Likes
Tokens are reset and expire after 24 hours after creation, an aggressive timeline if you ask me. Tokens created prior to their Oct/Dec 2024 change are grandfathered in and are not reset. Do not delete your old tokens
Check out that driver channel page. People have created a lot of drivers that can be added to your ST Hub.
Can we get a bit more details about this? Timing and what it would mean for users? Ty
1 Like
Same issue here, bought Samsung refrigerator mainly because of the integration and now this, if this will not be resolved that will be last thing I buy from them.
Please check the GitHub issue I linked for updates. We’re working with them to get this fixed and to get the integration to a better place.
There’s a comment where I’m asking for people who don’t have a long lived access token anymore to leave a 
emoji to size impact, so please find that one and leave the rocket behind.
Reauthentication is something to help people with a long lived token stop having their complete entry removed. So if your token is created after 30 December, reauthentication is of no use for you.
6 Likes
Will do. Thank you joostlek!
Ref Link to GutHub Issue Post:
This is here : https://github.com/home-assistant/core/issues/133623#issuecomment-2595028342
Thank you @joostlek
1 Like
I’m not sure anyone has mentioned this yet, but there exists a painful workaround through a trusted third party like Alexa, IFTTT, etc.
One of the two (either HA or Smarthings) needs a virtual device, and the third party needs a series of automations to keep the virtual device in sync with the real one.
a. If the virtual switch turns on, turn on the real light.
b. If the virtual switch turns off, turn off the real light.
c. If the real light turns on, then turn on the virtual switch.
d. If the real light turns off, then turn off the virtual switch.
It’s kludgey at best, introduces noticeable latency, is a nightmare beyond a few devices, and I haven’t fully tested it yet. But…in a pinch with one or two devices…I’ve previously used it to keep two otherwise-incompatible services in sync with each other.