Smart things integration gives "reached max subscriptions limit" even after it has been "fixed" on the new version

[C0dezin]

The problem

I know this have been an issue before, but it still happens at version 2025.3.3 even tho I waited 10 hours as people told me.

It actually gives it no matter what I do with the device, turning on and off, turning volume up or down and etc.

IF another issue exists for that(considering 2025.3.3) please redirect me there.

What version of Home Assistant Core has the issue?

core-2025.3.3

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

Smart Things

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[figarciab]

Same problem here. Smartthings stop working a few minutes after updating to the new version.

[joostlek]

Can you make a screenshot where you see this?

[C0dezin]

Can you make a screenshot where you see this? @joostlek

[C0dezin]

"Falha ao executar a ação" stands for "Error while executing the action"

[joostlek]

Right, the limit of subscriptions is wrong here and will be fixed in 2025.3.4

[C0dezin]

Thanks for that, if possible, make a quick comment here when the version is released and in what commit it was fixed S2

[joostlek]

It's fixed in 2.7.4 of pysmartthings

[C0dezin]

Thanks

[home-assistant]

smartthings documentation
smartthings source

[C0dezin]

Fixed on dev, #140720

[aarnaegg]

This issue started for me after updating to 2025.3.4 with pySmartThings to 2.7.4.

[enedberg]

This issue started for me after updating to 2025.3.4 with pySmartThings to 2.7.4.

Same here. Started after I updated today (multiple updates and couple of reboots). Will wait and see if it goes back to normal later.

[joostlek]

Okay so the bug report was that this was shown during a command, which is fixed. So I am going to close this issue. It depends on what version you came from. If you came from 2025.3.0 or 3.1, you might have to wait