Samsung will soon start charging to access its smart home API

The trigger event

Samsung is rolling out a slate of paid tiers for SmartThings API access, with the $4.99 monthly tier positioned for "non-commercial, individual developers." Samsung's own framing: the new pricing lets the company "invest heavily in the enterprise-grade features our partners and users have been asking for," including stability improvements, new integrations, and a refresh of its Developer Center. The marketing pitch says investment. The architectural reality is that every advanced user is now a recurring revenue line item, whether they ship a product or just want their hallway lights to follow the sun.

Who actually gets caught

This is not just hobbyists running a single webhook. Home Assistant founder Paulus Schoutsen posted that the Home Assistant integration will fall under Samsung's new "personal plans." That puts anyone using Home Assistant as the automation brain — reading device states, firing routines, stitching cross-ecosystem logic against SmartThings gear — directly inside the blast radius. The same logic applies to Node-RED flows making authenticated HTTP calls, custom scripts running against the SmartThings endpoints, and any third-party bridge that needs API access to translate between ecosystems. The trap is structural: the moment your automation touches SmartThings beyond the stock mobile app, you are the developer in Samsung's eyes, and you owe a subscription for the privilege of talking to hardware you already own.

The workaround playbook

Audit before October. Walk your stack and inventory every integration hitting the SmartThings API: open the Home Assistant SmartThings integration page and confirm whether it uses the cloud-to-cloud path, scan your Node-RED flows for HTTP nodes pointing at SmartThings endpoints, grep your scripts for any authenticated call to the platform. If you rely on the cloud-to-cloud path through Home Assistant, you are already on the paid tier — the wrapper does not save you. Two pragmatic moves from here. Option one: pay the $4.99 and treat it as infrastructure cost, then lock down what you get in return — pin the device handlers and integrations you actually use, document the webhook payloads you depend on, and stop expanding your dependency surface on a platform that now has a meter running. Option two, the local-first path: migrate anything mission-critical to Matter or Zigbee devices that expose direct local control without phoning Samsung's servers, and run your routines through Home Assistant against the local API. Keep SmartThings for what it controls natively. Run your logic where the API is still free, and stop subsidizing a vendor that just turned its developer tier into a subscription product.