The lack of a clear direction for their IoT architecture is probably what bugs me the most about Samsung.
One one hand, they’ve put a lot of effort into making things run local. Custom edge drivers can run local, local Automations via Rules API, putting a hub into everything, putting a lot of time (and Money!) into evolving Matter and being an early adopter for it.
On the other hand, the SmartThings app still relies 100% on the cloud, there’s no local API for the hub they’re putting into everything now, and none of their appliances support the Matter standard they are helping develop.
The talking out of both sides of their mouth really wants to make you bang your head against the wall.
The Open Home Foundation (home Assistant) newsletter just went out. They address the SmartThings API subscription and say the HA integration for ST will fall under the $4.99/month individual plan.
I suspect the SmartThings integration in Home Assistant has mostly been used by people who were already in the process of moving over. Home Assistant generally supports a much wider range of devices and integrations than SmartThings does officially, and often with more complete functionality. For many of the remaining users, this $4.99 fee will probably just be the final nudge to finish migrating their devices fully into Home Assistant rather than keeping the bridge alive.
They’re offering A New Enhanced API Experiencetransitioning to paid API tiers in October 2026.
HA integration with ST has been a roller coaster, first the PAT changes few days before Christmas 2024 with no time to create a new integration, then in February 2025 SmartThings was proud to announce a new integration where both teams were “working closely” and just a year later they suddenly make that integration a subscription service. Was that the plan from the beginning?
I don’t know about Samsung appliances, but if they don’t have a local API, preferably standard, and the only way to integrate them anywhere is a montly subscription then it is indeed wise to avoid them, just as any other cloud-only device that is ultimately subject to the vendor will.
There are certainly users who keep SmartThings around to bridge Zigbee and Z-Wave devices, but my guess, without any hard data, is that the largest remaining use case is Samsung appliance integration.
So what’s going to happen now??? Are more developers going to leave? I’ve been here since 2016 but i’ve seen a lot of people leave every time samsung did major changes, new developers came in after and helped fill that void but I don’t know if that’s gonna happen again? Also i haven’t seen JD around, is he okay?
This sounds annoying. I’ve been using this platform for a long time, but only for very basic tasks - Set House to Alarm when everyone is gone, turn lights on and off around sunrise/sunset, etc. When I first read about it, it seemed like a nice, simple free solution.I’m not using it with any Samsung appliances.
I guess it’s time to begin looking into HA… (Grr… Another new system to research, understand and learn!)
Given the recent developments of Home Assistant confirming users will have to pay the individual SmartThings subscription to integrate it, then seems clear the subscription is not for the developers but for the regular end user wanting to enjoy the integrations.
Of course, developers will also have to pay it in order to develop it and test is since, for the platform, they are also users of the API.
I guess if the developer stops paying the monthly fee, as long as the end user keeps paying, the SmartApp will keep working for the user, is that right? Or if the developer stops paying the SmartApp stops working even if the user is already paying?
Based on past experience, there will be an awkward and slightly too long interval before someone gets the opportunity to tell us what the score actually is. I suspect most of us want to know:
Will we need to subscribe?
Is being a ‘non-commercial, individual developer’ something we get to elect to be?
What exactly does being one gain us apart from a smaller bank balance?
It is arguably sensible to manage SmartThings Locations and/or develop using separate non-personal accounts. However these are the same person wearing different hats. Has this been considered?
What are the likely implications for commercial applications we use? Increased costs to be passed on?
For my part I would consider myself less a developer than an ‘advanced user’ in that I use the Rules API for automations and a custom Edge driver, capabilities, profiles and presentations for my local VIRTUAL devices. I also dabble with apps but only have one vaguely serious one and that is pretty much dead in the water without renewable USER tokens.
Would I pay for a subscription? Possibly, but only one, and I would want to better understand why. If, as it seems based on the initial news, it will be possible to be on a ‘free tier’ yet be able to have hundreds of Routines, hundreds of devices, multiple Locations, and use add-ons like Map View and the various Life Services which really don’t need to be part of a core service, then I am going to see an injustice. The Michael is being extracted and a retort is appropriate.
I am taking minor preparatory action to better allow for bailing out, but nothing that I wouldn’t be wanting to do eventually regardless.
Thank you @orangebucket for that detailed explanation. So i guess stay tuned and for me, ill wait to see what alot of you guys do. If many of you bolt i may just follow. Im assuming the other 2 options will be hubitat, which thats where alot of former folks from here went to…i rememebr that one and home assistant. For me. My only delima is i just recently bought 3 airzone wifi adapters for my ductless units hat work with smartthings and moving forward is aamsung looking to charge airzone now? Plus I think the adapters i have dont work with home assistant… ill have to look that one up. Keeping fingers crossed the change is small and not upside down.
Only reason why I am using SmartThings API is so I can have all Samsung devices in HA. If this is going to be paid service then I can probably return them as you are going to break the functionality (putting it behind paywall). So I think only way for you would be to make local API available, otherwise people can return all Samsung gear
In anycase, without a free API is Samsung going to be added to my ban list and I will never buy any Samsung device again.
$60/year so I can automatically turn my TV’s to Art Mode when I go to bed? I don’t think so.
Instead, I’m going to return my three new Frame TV’s and spend $2000 on a different brand that isn’t putting individuals behind a paywall.
It took me two weeks to replace MyQ / Chamberlin when they did the same thing a few years back, I bet I can beat that timeline with my Samsumg products.
I’m done with buying Samsung appliances, I was pleasantly surprised when my washing machine and TV worked with home assistant and was useful in integration with my smart home. But now I’ll have to do some workarounds now.
Give the people a local integration, and charge for API access, one has to be daft to think an individual user would pay a subscription to control a handful of appliances.
