Samsung SmartThings API fees: who pays in October, who's stuck, and what it reveals about cloud-dependent smart homes

Samsung is ending free access to its SmartThings API in October, and the users who will feel it are not the millions running the standard SmartThings app. They're the technically engaged users who built custom setups on top of the free API, and some of them have no practical way around the new Samsung SmartThings API fees. Android Authority confirmed this week that paid tiers take effect in October, including a $4.99-per-month personal plan for non-commercial individual developers, with free access continuing through Q3.

Home Assistant is the clearest documented case of who gets caught. What follows is what that means in practice.

What changed: Samsung's new API pricing structure

Starting in October, Samsung will roll out tiered paid access to its SmartThings API. The individual-facing option is a $4.99-per-month personal plan for non-commercial developers, alongside separate commercial tiers for business partners, per Android Authority. Free access remains fully available through Q3, with no usage limits applied until the transition.

Worth clarifying what the API actually does before getting into who pays. It's the programmatic layer that lets third-party software, including Home Assistant, read device status and send commands through SmartThings. Standard app users never touch this layer. If you open the SmartThings app on your phone to turn off a light, this change has nothing to do with you.

Samsung's stated rationale is investment in "enterprise-grade features," including stability improvements, new integrations, and a refreshed Developer Center offering usage data and code optimization tools, as reported by The Verge last week. The specifics behind that rationale remain thin. Beyond general references to new integrations and expanded capabilities, Samsung has not released concrete details about what those improvements will actually deliver, Engadget noted last week. Samsung has also not publicly detailed how the new pricing will be enforced, whether per account, per token, or per some other measure. That question matters enormously for determining exactly who pays and how much.

Samsung SmartThings Home Assistant integration: who falls under the paid tier

Home Assistant is the most immediate and well-documented case. Founder Paulus Schoutsen wrote last week that the SmartThings integration "will be affected" by Samsung's new policy and "will fall under their new 'personal plans,'" per The Verge. That puts Home Assistant users connecting to Samsung devices through this integration in line for the $4.99 monthly fee starting in October, though Samsung has not yet specified whether billing applies per user, per app, or through some other arrangement.

The potential scope is meaningful. Roughly 9.8% of active Home Assistant installations with telemetry enabled use the SmartThings integration, according to Matter Alpha. Because Home Assistant analytics are opt-in and only a portion of users share usage data, Matter Alpha estimates that translates to approximately 200,000 installations, an extrapolation, not an official count.

The Home Assistant team's response framed the fee as one cost layered onto others. "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," Schoutsen wrote, per Engadget.

Several questions that will determine the real cost remain unanswered. Does each Home Assistant user need an individual developer account, or could the project negotiate a central arrangement? Do open-source or community projects qualify for any exemption? Samsung has not addressed either publicly. Those answers will determine whether $4.99 lands once per project or once per user, which is the difference between a manageable licensing cost and a per-household subscription nobody signed up for.

Why some users can't simply move off Samsung's cloud

For users who don't want to pay, the obvious question is whether they can route around the cloud entirely. For many, they can't.

The Home Assistant SmartThings integration is classified as "Cloud Push," meaning every command and every status update depends on Samsung's cloud infrastructure, according to Matter Alpha. There is no local control path. When that cloud connection sits behind a paywall, the integration follows it there.

For users with Samsung appliances, refrigerators, washers, and similar devices, the constraint runs deeper. Even where those appliances support the Matter standard, they currently cannot be commissioned directly into Home Assistant. SmartThings remains the Matter controller, making Samsung's cloud the only available integration path, per Matter Alpha. Matter compatibility, in those cases, is not a workaround.

For users whose Samsung devices depend entirely on SmartThings cloud services, there is currently no direct replacement for the official integration, Matter Alpha reports. For that group, the $4.99 fee isn't a premium tier for extra features. It's the price of keeping what already works.

What this means varies by audience. Native SmartThings app users are completely outside the scope of these changes. For Home Assistant users with Samsung appliances, the practical question is whether those devices route through the SmartThings cloud integration; for many Samsung appliances, no local alternative currently exists. Developers and custom integration builders face the same October deadline with enforcement mechanics still publicly undefined. Samsung has indicated additional details are coming, without specifying when.

The broader pattern: cloud APIs are a platform decision, not permanent infrastructure

Samsung's shift fits an established pattern. Multiple smart home manufacturers have restricted, modified, or shut down API access over the years, forcing open-source developers to update integrations or pull them entirely, according to Matter Alpha. One recent example: Haier initially asked the Home Assistant integration developer to remove the integration before reversing that decision after community pushback.

Schoutsen's framing of Matter is worth sitting with. He said he values the protocol primarily "because you can't be rug pulled," prioritizing resilience against vendor control over interoperability, per Matter Alpha. That's a candid statement about what the open-source smart home community has absorbed through repeated experience: cloud APIs are not neutral infrastructure. They belong to the platform, and platforms make changes.

Samsung can frame this as affecting almost no one, and by raw user numbers, that's accurate. Millions of standard SmartThings users are untouched. The burden falls on the portion of the user base that invested most deeply in the platform's API capabilities, the users who, in effect, trusted free access to stay free.

What's confirmed, what isn't, and what comes next

The individual developer plan costs $4.99 per month. Home Assistant's SmartThings integration falls under that tier. Free access continues through Q3 without usage limits, per Android Authority. Users and developers have roughly three months to assess their options.

What remains unresolved is significant. Samsung has not detailed enforcement mechanics, exemption possibilities for open-source projects, or what the fees will fund in concrete terms. Matter Alpha sought comment from Samsung and had not received a response at publication. Those details are likely to determine how broadly the October change is actually felt.

For users with Samsung appliances that can't currently be moved off the SmartThings cloud, the deeper issue isn't whether $4.99 is a reasonable price. It's that the decision was never theirs to make. October is a fixed point regardless of what Samsung clarifies between now and then.