-
-
Notifications
You must be signed in to change notification settings - Fork 33.2k
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
Couldn't create a new subscription. Reached limit of subscriptions. #141121
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 |
What version were you running before? |
The current version was working fine but I had each update as it came. I waited on OS update for a week and when I saw Core also had an update I decided I better not fall behind. I'm sorry I don't keep track of the previous update version numbers. It was the last public release on everything. |
But like, did you update in the last month? |
Yesterday about 25 hours ago, both OS and Core |
You mean 2025.3.4? And when did you update before that? |
I believe this was my first OS update. The Core I've updated each time it has been released, within 1-2 days. Now I did have a catastrophic failure on the 2025.3.2 update that forced me to do a full restore but everything has worked and updated fine afterwards. |
So that means you rolled back to a previous version and that might be 3.1 or 3.0? In theory those 2 have issues with the connections, but I would expect it to recover within max 4-6 hours. Do you maybe have your location id so I can check with SmartThings? |
Sorry, I've looked through my phone SmartThings app to see if there is an ID listed. All I can find is it's set by my geolocation, my home address. I don't customize anything on it since I use it for very little. Two kitchen appliances and a handful of smarttags. All I can tell you is the location name is default, My home, and location mode, Home, and it has my home address as the geolocation. I never change anything and don't adjust anything. For me it's literally just a notification system. If you know how I can get my location ID please explain and I'll be happy to provide it. |
Yes, it rolled back to 3.1 and once booted I did a reboot to ensure nothing bad resulted from it. Then immediately tried updating again to 3.3 which worked. There had been no problems updating other than that. |
495c2b01-7359-4674-9d13-dee81c565422 |
I returned to check on the integration and it's back to working again. The only resolution I see that happened here was this error requires removing the integration and adding it again, then waiting for the recovery time frame (4-6 hours) to pass. As I mentioned originally it was errored for over 12 hours before removing the integration and adding it again. Then some time between my Opening Issue and this comment it started working with no other actions. |
I too am having this problem and I too updated both OS and Core. After update and the restart it does, I now have this error. My location ID 92fc4b45-603b-4b6e-bd25-d40cc923824d @chogardjr, when the integration was removed and re-added did you have to re-setup all your devices? Did they get new id's in home assistant? I have all my ID's mapped to cards and stuff in yamls and if my devices get new ids I'd have to re-setup all my screens. EDIT: I restore my home assistant VM from a backup that was preformed this morning that was working successfully. After restoring the VM and starting it, Home Assistant is now showing the following error for Smartthings:
Note I do not use nabucasa and self-host everything. EDIT 2: I see you asking what version people are on before updating and the errors happening. Since the restore rolled me back, I am on version Core 2025.3.1 OS 14.2. Should I upgrade to core 2025.3.4 and OS 15.0 and then wait as you've posted in other issues? Thanks. |
If SmartThings was the only thing not working restoring was the wrong approach if that rolled you back to later versions. You'll now need to update to the current versions then link SmartThings again, after deleting it, again. If you waited after deleting and linking again everything would have likely worked out without any further action. I did mention this in one of my posts. This is the way it has always been with the exception of their recent overhaul which did change the names of the sensors on some devices. Home Assistant takes all the names are they are listed in SmartThings so unless you renamed all your sensor/devices, everything will reappear as they were before. Like I mentioned in one of my posts, my dashboards with my SmartThings sensors and devices reappeared once SmartThings time frame passed and linking was successful. You just have to wait it out after readding SmartThings. It says NabuCasa because that is what they are using to link SmartThings to Home Assistant. |
Thanks @chogardjr. Indeed restoring a backup was not the right call - I forgot about the security token and how that invalidates it. The way to reauthenticate the integration (by going into the SmartThings app and finding the home assistant entry under routines -> Smartapps and tapping it) wasn't working for me so I resorted to removing and readding. That worked and it's now readded, but now I have to go through the painful process of restoring all my device helpers and fixing some of the renaming I did within home assistant as now nothing matches. The correct solve was probably to just wait it out and see if the "Reached limit of subscriptions." error fixed itself. |
I restarted home assistant this morning because two hacs components had been updated. I am running HA 2025.3.4 and have been since it was released. Prior to the restart, the smartthings integration was working. After the restart, I started getting the same error (error log quoted below) but it spontaneously cleared after about 15 minutes and all devices returned to normal. Logger: homeassistant.components.smartthings Couldn't create a new subscription The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Same issue for me. a7ffda03-e22c-4193-9133-34c9cd67098c |
Please update to 2025.4.1 |
Works. Thank you. Faced an unrelated issue, but got fixed after re-installing smartthings app on android. |
The problem
Pardon my ignorance but what does this mean? I updated both HA OS and Core yesterday and everything was working fine for about 10 hours. Late last night I noticed my devices were not reporting and thought I should wait it out like what was required before. It's now been 12 hours and it still hasn't corrected itself. I deleted the integration and readded it, an action that fixed it once before, but this has the same result except now my devices are gone. Not worried about the devices being gone since I don't rename anything. They will all return and dashboards will update.
I don't have a lot going on with SmartThings. I use it to monitor my Fridge and Range, I do not control anything through the integration. I'm not sure what happened or where to start. I'm hoping someone here can shine a light on what I can/need to do.
Core: 2025.3.4
Supervisor: 2025.03.3
Operating System: 15.0
Frontend: 20250306.0
What version of Home Assistant Core has the issue?
2025.3.4
What was the last working version of Home Assistant Core?
2025.3.4
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
SmartThings
Link to integration documentation on our website
https://www.home-assistant.io/integrations/smartthings
Diagnostics information
No response
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: