Samsung puts a $5 monthly fee on the SmartThings API and pushes Home Assistant users toward local control
Announced in June 2026, the move to $4.99 per month for the SmartThings API for individual developers takes effect this autumn, ending years of free access for third-party integrations like Home Assistant, while the LocalThings project emerges to restore local control. For anyone driving Samsung devices from Home Assistant, the right answer is not to pay the subscription but to migrate automations onto local paths that no future fee can close.
June 2026. Samsung announces it will charge $4.99 per month for SmartThings API access for individual non-commercial developers. Autumn 2026. The fee takes effect, ending years of free access to one of the world’s largest smart-home ecosystems. 460 million. The registered-user count Samsung claims for SmartThings. Why it matters: the paywall does not touch the consumer app, but it taxes exactly the third-party integrations that made the platform open — and it accelerates the move toward local control.
What changes: the app stays free, the API goes paid
The distinction matters, because most users will never see a bill. If you control lights, plugs, or appliances through Samsung’s own SmartThings app, nothing changes: access remains free and automatic compatibility with thousands of devices is untouched.
The fee lands on people who reach SmartThings from other software. A Home Assistant setup that pulls Samsung devices into a single dashboard talks to the SmartThings API — and that access, free until now, sits behind a monthly payment. The same applies to custom automations and any third-party integration built on the API.
That is a change of nature for one precise kind of user: the enthusiast who built a customized automation system around the platform. An integration that already worked, at no cost, now carries a recurring charge — not because it broke, but because the account layer underneath belongs to Samsung, which is free to reprice it.
Samsung’s public justification is investment: the revenue will fund “enterprise-grade” features and a new Developer Center. But, as one recent analysis put it plainly, the $5 repairs nothing that was broken — it buys continued access to something that already worked, while the promised features are a commitment for later.
The community’s answer: LocalThings and local control
The open-source community’s reaction was sharp. Paulus Schoutsen, founder of Home Assistant, publicly criticized the move: “We’re all for choice, but feel very disappointed that users will have to decide whether to shell out for access in the shadow of yet another cloud paywall.”
The frustration is easy to understand. Home Assistant built its user base precisely on local, privacy-first control that reduces dependence on manufacturers’ cloud platforms. A monthly fee for Samsung’s API adds another layer of cost and fragmentation to an ecosystem the open-source world has worked to keep accessible and manufacturer-independent.
The concrete answer was not long in coming: LocalThings, a project born to bypass the paywall and restore local access to Samsung devices. It is the classic self-hosting reflex in the face of a platform fee: when the cloud closes its door, the community builds another one, on the local side. The project joins a long line — the one that turns every API paywall into an argument for owning your own access path.
The Matter irony: device interoperability does not guarantee platform openness
There is a deeper irony in this decision. Matter, the standard pushed by the industry’s big names, promises that your devices keep working no matter which ecosystem you choose. Samsung embraces it — the SmartThings app was redesigned with Matter 1.6 support.
But Matter standardizes the device layer, not the cloud APIs that platforms expose to power users. Samsung can adopt Matter for hardware compatibility while still charging for the API on-ramps that enthusiasts actually depend on. Interoperability at the device level does not guarantee openness at the platform level. That is the structural lesson of the paywall: open standards cover the hardware, not the cloud accounts that drive it.
The question now is one of precedent. Five dollars a month is a small number. But the smart-home industry is moving toward monetized developer ecosystems: paid API tiers, subscription-locked features, cloud services that used to be free. Each fee is easy to justify on its own; together they change the economics of the open, mix-and-match smart home that Matter was supposed to protect.
What is at stake for a self-hoster
The practical point, for anyone maintaining a Home Assistant or a custom integration, is to know where their automations actually live. If everything runs through the SmartThings app, nothing changes — and nothing costs. If the home depends on Home Assistant talking to Samsung’s cloud, watch how the integration projects respond to the fee, and which devices can move to local control over Matter, Thread, or a project like LocalThings.
The real cost is not the $5: it is the renewed dependence. Every automation stacked on a paid API becomes more expensive to maintain, and risks breaking if the integration maintainer decides the subscription is not worth it. The only durable guarantee is a path that no fee can close: local control, on your own network.
One practical nuance is worth remembering: the fee applies to the developer holding the API access, not to the end user directly. Each integration project will therefore decide whether to absorb the cost, pass it through, or drop SmartThings support — which means the price you actually pay is only as predictable as the project that maintains the bridge.
Migrating to local: where to start
For a self-hoster, leaving the paywall follows a four-step path, in order of cost-to-benefit. First, the inventory: list the Samsung devices your automations actually drive, and the path they use — the SmartThings cloud or a local route. Second, the standard: for each device, check whether it exposes a Matter, Thread, or documented local interface; that is the criterion that decides what comes next. Third, the pilot: test LocalThings or Home Assistant’s local integration on one non-critical device before flipping everything. Finally, the cutover: migrate automations one at a time, keeping paid cloud access only for devices with no alternative, until they can be replaced.
The guiding principle is the same as any infrastructure migration: do not break everything at once. Every automation moved to local is one less dependency on a price you do not control. And a device that cannot be driven locally is a device to replace eventually — not a subscription to endure indefinitely.
Verdict
The SmartThings API paywall is a signal, not a catastrophe: $5 a month will bankrupt no one. But it reveals where the dividing line really sits — between devices that stay open by standard, and cloud accounts that monetize by subscription.
If your automations run through the SmartThings app, do nothing: the change does not concern you. If you drive Samsung devices from Home Assistant, do not reflexively pay the subscription: migrate to local control — Matter, Thread, or LocalThings — on the devices that allow it, and keep paid cloud access only for those with no alternative. If you are buying new smart-home devices, make local control a purchase criterion, not a luxury: it is the only feature a future platform fee can never take back. The rule to remember: a device driven by your network belongs to you; a device driven by an API belongs to whoever sets the price of the API.