SmartThings has never been part of my setup, so on paper the news from November 4 is not my problem. Samsung announced that the current SmartThings integration for Home Assistant stops working after December 15, 2026, and that the replacement needs a paid SmartThings API Developer Plan at $4.99 a month. Plenty of people will shrug, pay roughly the price of a coffee, and move on. I understand that.
What made me sit down and write about it is a detail further down the announcement. The plan is only sold in certain countries, and the cutoff applies to everyone anyway. I live in Switzerland. Going by the list reported at launch, Switzerland is not on it. So for a Swiss Home Assistant user with a SmartThings hub, the choice is not “pay or migrate.” It is simply “migrate.”
What SmartThings actually announced
The primary source is SmartThings’ own post in its community forum, “Changes to the SmartThings integration for Home Assistant”, published November 4. The key dates, as SmartThings lists them: API plans went on sale on November 4; a Home Assistant release on December 2 is expected to remove the ability to set up the old integration and introduce the new one; and from December 15 the current integration will no longer work.
To use the new integration you need an active Developer Plan and a 24-hour personal access token, which setup uses to load a custom OAuth app into your SmartThings account. SmartThings says your devices and automations carry over because automations store device IDs that repopulate when you re-add the integration. The plan includes 100,000 API calls per month per account and up to 10 OAuth apps, and SmartThings warns that hitting the limit “can impact functionality.”
Two honest caveats. First, this is Samsung’s timeline. When Matterhome.io and Local Smart Home Guide checked, Home Assistant had not announced the switch itself, and the pull request reworking the integration was still open. Second, the Home Assistant integration docs still carry an older warning about an October date and a “Personal Plan.” Treat December 2 as SmartThings’ plan, and check the December release notes when they land.
The country list is the real story
SmartThings’ post says the individual plan “will be limited to certain countries upon launch,” and that the December 15 date “applies to all Home Assistant users including users in countries where the Developer Plan is not available.” According to Matterhome.io’s reading of the SmartThings API page, the nine launch countries are the United States, Korea, Belgium, France, Germany, Italy, the Netherlands, Poland and the United Kingdom. SmartThings says availability may expand, without dates, and the authoritative list sits in the FAQ on its API page and in the Developer Center console. If you are outside those nine, check there before assuming anything, because I would love to be wrong about this.
But if the list holds, Home Assistant users in Switzerland, Austria, Spain, the Nordics, Canada, Australia and many other places lose the integration on December 15 with nothing to buy. That is the part I find hard to defend. Charging for API access is a business decision I can respect. Switching off a working integration for people you will not even sell the fix to is something else.
It was always a cloud integration
In fairness to Samsung, nothing local is being taken away here. The SmartThings integration in Home Assistant has always been a cloud integration: a device changes state, the event goes to Samsung’s servers, and Home Assistant hears about it from there. SmartThings also says its own app, routines, scenes and local Edge drivers are not affected.
That is exactly why this story matters to me even though it does not touch my hardware. Every cloud bridge in a smart home carries a quiet clause: this works for as long as someone else wants it to, on terms someone else sets. For years the SmartThings API was free, and that made it feel like infrastructure. It was never infrastructure. It was a courtesy, and courtesies can be repriced or withdrawn with six weeks’ notice.
This is the whole reason my HAOS box on a used EliteDesk runs its own radios. The Zigbee mesh lives on a coordinator plugged into the machine, Thread runs through a Connect ZBT-2, and neither cares what any company decides about its API pricing next quarter. It is more work up front. It is also the only setup I have found where an announcement like this one is something I read about rather than something I have to act on.
If you are affected, here is how I would approach it
The cheapest exit is for Zigbee and Z-Wave devices sitting on a SmartThings hub. Pair them to a coordinator that Home Assistant controls directly, through ZHA, Zigbee2MQTT or Z-Wave JS, and they stop needing a Samsung account at all. The cost is real, though: every device has to be reset and re-paired, and automations that point at the old entities need editing. With a dozen devices that is an evening. With sixty, it is a weekend, and not one you want to start on December 14.

Matter devices have the gentlest route. Matter supports multiple controllers, and SmartThings documents a share flow: open the device in the SmartThings app, use “Share with other services” to generate a pairing code, then add that code through the Matter integration in Home Assistant. The device then talks to Home Assistant locally, and you can leave it in SmartThings too, or remove it later.
Samsung’s own appliances are the hard case. For many washers, dryers, fridges and TVs, the SmartThings cloud is the only way into Home Assistant. If that is you and you live in one of the nine countries, $4.99 a month might be the pragmatic answer for now. If you live outside them, it is worth asking SmartThings developer support directly, since the post explicitly invites people in your situation to do that, and posting what you hear back on the Home Assistant forum so others benefit.
Whatever you choose, do the inventory now: open Settings, Devices and services, SmartThings, and list every device that comes through it. Mark each one as Zigbee, Z-Wave, Matter or “Samsung cloud only.” That one list turns a vague worry into a plan.
What I take away from it
I do not think Samsung is a villain here. Running an API costs money, and a paid tier with a clear price is more honest than a slow decay. What I do think is that a smart home deserves to be built so that this kind of news is an inconvenience, not an emergency. Every device you can move onto a radio you own is one fewer clause someone else gets to rewrite.
I will update this post once the Home Assistant December release notes are out and we know what the new integration actually looks like. If you are in Switzerland or another country outside the launch list and you have heard anything from SmartThings support, I would really like to know. The comments are open.
Featured photo: Pexels. Facts checked November 11, 2026 against the SmartThings community announcement and the coverage linked above.

Leave a Reply