-
-
Notifications
You must be signed in to change notification settings - Fork 32.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smartthings integration broken and cannot be fixed. Getting 400 error trying to get token? #140462
Comments
Hey there @joostlek, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) smartthings documentation |
Are you running multiple HA instances? |
No, what gives you that indication? |
So far this issue only came up with people with multiple instances. For now I would advice to remove the integration and readd it |
Hmm, ok. Will I have to re-add all of the 22 or so devices or will they get recognized? |
In theory it should automatically recognize it. (and to be explicit, you should remove the HA integration, not remove something in SmartThings) |
OK, thanks! Will try it out an report back. |
I also encountered a similar issue, displayed as "Reached limit of subscriptions." |
The problem
Since I updated to 2025.3.2 this error shows up and is not resolving for me. I thought that it might get resolved after waiting for some time, but a whole day in and this doesn't seem to get fixed.
Anyone have an idea on if the issue is on my end? This was working fine for ages until today.
What version of Home Assistant Core has the issue?
core-2025.3.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Smartthings
Link to integration documentation on our website
No response
Diagnostics information
home-assistant_smartthings_2025-03-12T17-41-40.799Z.log
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: