-
-
Notifications
You must be signed in to change notification settings - Fork 32.9k
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
Samsung purposefully broke SmartThings integration on Dec 30 #133623
Comments
Hello. I confirm the above! Today my token stopped working, I created a new one and when registering access (on the Samsung website) a notification appeared that access was created for an hour! What should I do? |
This aligns with what I am seeing. Currently popping open the |
I'm trying to look into this but it doesn't look like we can use our normal oauth flow. |
Whew who ever gets SmartThings to stop giving me rate limits and doesn't make me get a new PAT every 24 hours will be my hero. Sure you guys have seen it but here's their documentation on the OAuth flow: https://developer.smartthings.com/docs/connected-services/oauth-integrations |
I am an old user of PAT. I restored from backup with mandatory new PAT. Now all my ST integration expired after 24 hours. Any progress for OAuth developement? |
Any word on the OAuth ? Half of my automations break every day due to an invalid token issue |
I recommend you make a new thread here: https://community.smartthings.com/latest |
Why would I make a thread there? This is an issue with Home Assistant using PATs vs the OAuth method SmartThings wants people to use.... SmartThings has made the change and are not going back, this has to be changed on the home assistant integration side |
Also encountered this problem. Besides the short TTL i can only issue 1 commnd in 20 seconds due to rate limiting. |
After PAT expire, HA get data only from read-only entities. I cannot execute actions. This is valid only If you do not restart HA. Temperature sensors values are correct. Strange ! |
So after a small bit of investigation, I If you look closely, the type of grant being used is If my assumptions are correct, there's an additional problem, this repository has been archived on May 9, 2024. I don't know if there's an additional fork of this repository that is being supported. |
I wasn't aware of this and it coincided with me finally tidying up my SmartThings devices with the hass-smarthings-remove script. I thought I'd borked the integration by doing that. Subscribed to this thread to see when a solution drops. It's a major impact for me as my front door lock is connected via SmartThings to add redundancy (if I can't unlock with Home Assistant, I can fall back on SmartThings) but my family all use HA exclusively. |
Interested in seeing what the solution to this will be ... |
@joostlek 4% of the community are using this integration (and it is a key feature of NabuCasa). Is there any timeline to fix this problem ? |
Why would it be a key feature of nabu casa? We're still looking into but trust me, it's difficult. I don't have any timeline as for now |
@joostlek one of the reasons why I'm using NabuCasa is because the integration with Amazon and Smartthings was made easy. And thank you for taking a crack at it ! |
@Jens-Wymeersch I recommend moving away from Samsung products and SmartThings, they broke this on purpose despite having received plenty of warning. |
@NewsGuyTor we have in total 7 A/Cs - 6 of the 7 are controlled locally but one with smartthings. I'm not planning to replace these devices in the near future (cost is way too high). |
For some reason, integration over PAT has been working for me for the last two or three days. I have not noticed any changes in the integration itself, and I was also unable to find any changes on Samsung's side (using community.smartthings). Any idea what is happening? |
@snok3r-krk Interesting, I've just recreated a PAT to test this, and at least the very strict API limits are not there right now (was like 1 request / minute?). Will have to wait to see if it has longer TTL too, or if they just relaxed the limits. |
ST reversed their decision temporarily for those with legacy PAT. All users who did not delete and create a new PAT should be good until HA fixes with OAUTH. |
I'm not sure what you mean? Why would you want to run it as custom component? The integration doesn't work without SSE and isn't planned to work that way |
there are many that don't use default config or cloud in their configs. now samsung has also one ring to rule us all, as we all are linking to one st app and it's just that 'sse' which should be optional... |
There's nothing I can do for that, I'm sorry |
no worries, I have workaround. anyway, I checked the other problem with fan oscilation and now the problem leads to payload in pysmartthings. will get back to you with details.
|
it's old ac, new app can't even add it (after that it works normally) `2025-03-01 15:16:12.100 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Home for smartthings During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Can you please download the device status and the device overview json? You seem to know how the API work. It would be helpful as I think we should support this one as well |
@joostlek here is get_devices result from pysmartthings and export from my.smartthings. Let me know if you need something else, I'm just playing with this since yesterday... |
@joostlek those two PRs solves my problem with AC, just need to fix tests (still new to python...) and here is a PR to fix |
@Ishima do you also have the device status per device? |
@joostlek which endpoint is it? |
thanks for help with tests, I can't fire them locally.... |
|
ok, give me few minutes |
But let's continue this conversation in your PR |
good thing you wanted to check, pyST has problem with |
It did just accept it right? I made it so that it logged everything |
just to verify, did you change your device_ids or were they uppercase to begin with? |
Just letting you know that I have my entities back but there is no updates
to there state I have a washing machine. Is there anything I need to do
that I'm missing?
…On Sun, 2 Mar 2025, 08:19 Joost Lekkerkerker, ***@***.***> wrote:
@Ishima <https://github.com/Ishima> do you also have the device status
per device?
—
Reply to this email directly, view it on GitHub
<#133623 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7YJPQ2ZUMTTIHQLUFMA3AD2SK5JLAVCNFSM6AAAAABT574YT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJSGYYTMNRZGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
[image: joostlek]*joostlek* left a comment (home-assistant/core#133623)
<#133623 (comment)>
@Ishima <https://github.com/Ishima> do you also have the device status
per device?
—
Reply to this email directly, view it on GitHub
<#133623 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7YJPQ2ZUMTTIHQLUFMA3AD2SK5JLAVCNFSM6AAAAABT574YT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJSGYYTMNRZGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@joostlek it's working under HA, this error is from pyST, didn't saw it before as I just fixed blockers from HA logs. |
Oh but that shouldn't be a blocker, it should just parse it as string |
@miketarg please create a separate issue |
I have just few devices, but for other users this month release will be interesting :) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This issue is fixed and the fix is included in 2025.3. Users will be able to control their SmartThings devices again without having to re-authenticate. We always recommend to buy devices that work locally. If people buy cloud devices, we will work with the cloud manufacturers to make sure that those devices work for you. |
@balloob it's not working like that and entire conversation from the closed PR is about that. You need to have |
We only support Home Assistant when the I will lock this issue now, as each comment pings a lot of people and the issue has been resolved. If people experience any issue with the new integration, and use a supported Home Assistant installation with |
Anyway, I want to massively thank you all for helping me in this journey! I had a blast working with you all, and I am proud of the end result. A ton of people have tried out the beta so far and for the size of the change, not a lot of issues came up, all thanks to the provided test data and help. I enjoyed having a project again to throw a ton of time in and to hyperfocus into. If you like the work I (and many others) do, consider subscribing to Home Assistant Cloud, as it enabled me to work full time on Home Assistant and to make our beloved piece of software better every day. Also note that I started a place for SmartThings users to collaborate and gain common knowledge on how the API of their devices work. So if you want to see more features or want to help out on this (you don't need to be a developer to help out) be sure to checkout the Discord server https://discord.gg/EJYdwMCz7K. 🫡 |
The problem
https://community.smartthings.com/t/changes-to-personal-access-tokens-pat/292019
TLDR: Newly generated PATs will only work for 24 hours, which will be absurdly annoying for new users of this integration, so a change to OAuth auth is needed ASAP.
What version of Home Assistant Core has the issue?
NA
What was the last working version of Home Assistant Core?
NA
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: