Samsung Just Taxed the Open Smart Home
When you own the device but rent the protocol, you don't own the device.
Samsung is charging developers to access the SmartThings API — and the real victim isn’t developers.
The story looks small. $4.99 a month for SmartThings API access. Non-commercial, individual developers. The kind of line item buried in a product blog post that gets twelve upvotes on Hacker News and then disappears. But the mechanism matters more than the price. Samsung is inserting a toll booth between users and the devices they own, and they chose to announce it three months before the October enforcement date — barely enough time for the ecosystem to react.
Home Assistant founder Paulus Schoutsen said it plainly: Home Assistant’s SmartThings integration will be affected. Home Assistant surpassed 2 million active installations worldwide in 2025, a 28% year-over-year increase. Those users didn’t buy into the Samsung ecosystem. They bought Samsung devices — bulbs, sensors, thermostats — and assumed the API was a stable interface, not a subscription line item waiting to be enabled. That assumption just got repriced.
This is the platform trap running in slow motion. The sequence is always the same: attract developers with open access, build network effects on their work, then monetize the dependency once switching costs are high enough. Samsung didn’t invent this playbook. AWS ran it on open-source databases. Twitter ran it on third-party clients. Apple runs it on the App Store. What’s different here is that the dependency is physical — it’s wired into your walls and ceiling. You can’t just swap out your Zigbee sensors the way you swap out a SaaS tool. The friction is measured in electrician visits and drywall, not API keys.
The steelman for Samsung’s move is that API infrastructure costs real money, free riders are real, and $4.99 is genuinely not much to ask for a professional-grade home automation backbone. That’s true. But it misidentifies who’s subsidizing whom. The third-party developers and Home Assistant power users who hit the SmartThings API aggressively are exactly the people who recommended Samsung hardware to everyone they know. They are the unpaid sales force. Charging them first is biting the distribution channel that made SmartThings meaningful. Samsung should know this — they’re a hardware company that’s been trying to win software for two decades and keeps losing.
The deeper issue is what this signals about the smart home space broadly. Every major platform — Google Home, Amazon Alexa, Apple HomeKit, Samsung SmartThings — is now in the same late-stage posture: the “openness” window is closing, the lock-in is deep enough, and the monetization squeeze is beginning. Matter, the cross-platform protocol that was supposed to solve interoperability, is a standard that platform owners can comply with technically while making the experience outside their walled garden deliberately worse. Compliance isn’t the same as commitment.
The users who will suffer most aren’t the Home Assistant nerds — they’ll find workarounds, fork integrations, or migrate. The users who will suffer are the people who listened to those nerds, bought Samsung hardware, and have no idea what an API is. They’ll just notice, sometime in 2027, that their automations stopped working. Samsung will have a support article. The support article will mention plans and pricing. That’s the actual cost of this announcement, and it doesn’t show up anywhere in the press release.
The smart home was supposed to be the consumer IoT success story — the sector where interoperability won. Instead it’s becoming another toll road with four competing operators and no consumer protection at the interchange. The devices get cheaper. The access gets more expensive. And the value accrues to whoever controls the API layer, not whoever paid for the hardware.
When you own the device but rent the protocol, you don’t own the device.