Old Personal Access Token stopped working after the expiration change

Developer Programs Support
21

I didn’t hear back from you @nayelyz, can I and all us HA users get PATs that last greater than 24 hours? I purchased zwave and zigbee usb sticks for HA and I really don’t want to move 40+ devices away from smartthings. I can return, and hope I do! Because I like the ST environment but this current state is not sustainable

22

Eeek.

I’ve played quite a bit with Webhook SmartApps and I like to keep the demarcation between what needs doing at the SmartThings end and what happens at the other end.

What happens at the SmartThings end is creating and managing an ‘app’ (which seems to be what the PAT supports in the HA integration) and installing/updating ‘installed app’ instances of it (which Strongman handles in HA via a web browser and a SmartThings login, which sure beats using the Developer Workspace to publish to the Discover menu in the mobile app).

The other end is a web script that handles POSTed lifecycle events sent by SmartThings, and also maintains a copy of the access and refresh tokens for ad hoc commands.

To me it appears that the PAT is overplaying its hand a bit. It could be optional, but instead it has become critical.

2 Likes
23

Yeah, annoyance reports are starting to flow as expected:

1 Like
24

If you didn’t delete your token on the Smartthings site then there may be a solution for you on Github. If you are like me and did, well time to ditch Smartthings… with most of my devices. Its a sad day I’ve been with them for 6 years.

2 Likes
25
1 Like
26

I have the exact same problem. My personal access token only work for a day, and then I get a 401 error.

For example using https://api.smartthings.com/v1/devices/

1 Like
27

Old tokens were not supposed to be affected. Only new ones created after the deadline.

1 Like
28

There are interim solution:

  1. If you have an old HA backup, you can extract the PAT: Error setting up entry Home for smartthings: Smarthngs 1.1.17, HA 2025.1.0 · Issue #119 · veista/smartthings · GitHub
  2. If you don’t have the old PAT, you may try to use IR transmitter (e,g, Broadlink) integrated into HA.
2 Likes
29

6 weeks later no update. I abandoned Smartthings after 7 years of use. Was bit of a pain moving 80 zwave devices and a dozen zigbee, changing all the automations etc. Its fine now and I prefer the home assistant app to smartthings. I am not a high level user of HA but some of the more complicated automations I ask Grok/ChatGPT to help with. Good luck to all the holdovers!

3 Likes
30

Hey, I tried it but it doesn’t works from the browser either.
“strongman-regional.api.smartthings.com says ERROR: Something went wrong. Please try to install the SmartApp again.”
And it throws an error in the HA log:
ERROR (MainThread) [homeassistant.components.webhook] Error processing webhook … etc…

31

If you’re trying to restart an integration that uses one of the older, non-expiring PATs, I’m honestly not well enough versed in HA to offer any thoughts beyond what I provided above.

If you’re just getting started with SmartThings in Home Assistant, I would strongly advise that you wait until they release the new integration (which is currently in beta).

1 Like
32

Beta is now open for Homeassistant 2025.3.

33

To @nathancu point, from the HA 2025.3 beta release notes:

  • @joostlek completely rewrote the SmartThings integration! In december, SmartThings shut down the authentication method that we used to use to connect with their platform. During the last 2 months we collaborated with SmartThings to get the integration up and running again. No more need to request a personal access token! You can just sign in using your Samsung account (like how you are used to with for example OneDrive). Another improvement we have done is that to get push updates, you don’t need to expose your instance to the internet anymore!

I’m particularly interested in that last sentence. Does this mean the integration is local now?

Also notable, breaking changes as part of the new integration with HA

The energy and power sensors have been removed for every device that has a switch. They rarely worked because there were no energy or power capabilities available to get data from. If you do have the capabilities, it will still work for you.
(@joostlek - #138313) (documentation)

There are a lot of states that are renamed, this might need an update in your automations or other config

  • Set options for dishwasher job state sensor in SmartThings (@joostlek - #139349)
  • Add translatable states to SmartThings media source input (@joostlek - #139353)
  • Add translatable states to SmartThings media playback (@joostlek - #139354)
  • Add translatable states to oven mode in SmartThings (@joostlek - #139356)
  • Add translatable states to oven job state in SmartThings (@joostlek - #139361)
  • Add translatable states to robot cleaner movement in SmartThings (@joostlek - #139363)
  • Add translatable states to robot cleaner turbo mode in SmartThings (@joostlek - #139364)
  • Add translatable states to washer job state in SmartThings (@joostlek - #139368)
  • Add translatable states to dryer job state in SmartThings (@joostlek - #139370)
34

I’m pretty sure it has to do with how auth works now but I’ll have to dig deep before I answer that for certain.

I think the HA Matter Bridge is still the preferred way to do local.

1 Like
35

No, it just means your Home Assistant does not need to accept incoming connections from the Internet, so no need to open ports, use tunnels or pay the HA Cloud subscription.

Instead of SmartThings servers connecting to your Home Assistant, it’s your Home Assistant connecting to SmartThings servers.

3 Likes
36

gotcha. thanks for the clarification.

1 Like
37

Looks like there was success with integration working in the 2025.3 update. Some people on the HA forums had issues with a washer/dryer, be sure to post on github with logs if that is the case.

38

A post was split to a new topic: Personal Access Token stopped working