Table Of Contents
You paid $250 for a thermostat. It worked well for three years. Then the company changed their terms of service, and the device that had been operating locally now required a cloud connection (and a subscription) to access from your phone. You accepted the new terms, paid the monthly fee, and told yourself it was still worth it.
Six months later, the company was acquired. Twelve months after that, the acquiring company announced that the platform was being discontinued. The thermostat was still physically functional, sitting on your wall, but without the servers it depended on, it became an expensive temperature display.
This is not bad luck. This is the business model.
The Cloud Dependency Trap
The home automation industry discovered something important about fifteen years ago: hardware margins are thin, but subscription revenue is reliable. The most effective way to convert a one-time product sale into recurring revenue is to make the product dependent on a service you control.
So your “smart” light bulb requires an app that connects to a cloud server. Your irrigation controller uploads its schedule to a remote database and retrieves it on execution. Your security camera sends every frame to servers in another country before you can view it on a device sitting two metres away. The device on your wall or in your garden is not the product. It’s the entry point to the subscription.
When the subscription becomes unprofitable, the business changes terms. When the company fails, the servers go offline. When the product is acquired, the new owner has no obligation to maintain the infrastructure you depended on.
Some specific examples, not hypothetical:
Revolv was acquired by Nest (which was acquired by Google) in 2014. In 2016, Google remotely bricked every Revolv hub: devices that customers had paid $300 for. The over-the-air update simply disabled them. No replacement offered. No refund.
Wink had operated on a “no monthly fee” promise for years. In 2020, they sent customers an email announcing that service would be discontinued in 48 hours unless users subscribed to a $5/month plan. Automations that had worked for years stopped working immediately for anyone who didn’t pay.
Iris by Lowe’s shut down in 2019 with 30 days’ notice, rendering hundreds of thousands of devices non-functional.
SmartThings progressively removed local processing features over several years, migrating more and more automation logic to the cloud despite having initially marketed local processing as a core feature.
These are not outliers. They’re examples of an industry that has structured its products to extract ongoing value from hardware that customers believed they owned outright.
The Matter Illusion
You might have heard that “Matter”, the new industry-standard protocol backed by Apple, Google, and Amazon, solves this problem. It’s a compelling narrative: one standard protocol, local control by default, no more hubs.
But look closer. While Matter improves interoperability between devices, it doesn’t mandate independence from the cloud. Many Matter-certified devices still require the manufacturer’s app for setup, firmware updates, or “advanced” features. More importantly, most people use Matter via a “Matter Controller” provided by a big tech company.
If your Matter Controller is an Amazon Echo or a Google Nest Hub, you haven’t escaped the dependency. You’ve just standardised it.
The “kill switch” still exists. It just has a different logo.
The only way to truly own your automation is to run your own controller on your own hardware. Home Assistant is that controller.
What “Offline-First” Actually Means
Offline-first is not a feature. It’s an architecture decision made before the first line of code is written.
It means that every time-critical decision (turn on the irrigation, close the blinds, trigger an alarm) happens on hardware in your building, evaluated against rules stored on your hardware, without a round-trip to any external server. The internet connection, if present, is used for convenience: remote access when you’re away, notifications sent to your phone, weather data pulled for smarter automations. If that connection drops, nothing breaks.
Home Assistant, the open-source home automation platform on which the SEIN automation stack is built, was designed this way from the beginning. It runs on a Raspberry Pi (or any modest server) on your local network. Automations execute locally, typically in under 50 milliseconds. Sensors report locally. The entire system operates correctly without an internet connection.
Your data never leaves your network unless you explicitly configure it to. There is no cloud service to shut down. There is no company whose bankruptcy will leave you with an expensive paperweight.
The Subscription Isn’t the Worst Part
Cost is real: a thermostat that costs $7/month over ten years costs you $840 more than the sticker price suggested. But the subscription isn’t actually the worst part of cloud-dependent automation.
The worst part is the data.
Every sensor reading from your home is a record of how you live. When you wake up. When you’re away. When you’re home but inactive. What temperature you keep your house. How much water you use and when. What electrical loads operate at what times. These patterns, aggregated across millions of households, are commercially valuable in ways that aren’t fully disclosed when you accept the terms of service.
A home automation system that operates locally generates the same data, but the data stays on your hardware, in your home. It’s yours to use for optimising your own life. It’s not being used to model your behaviour, target advertising, or sold to an insurance company assessing your risk profile.
This is not paranoia. It’s the reasonable expectation that what happens in your home is your business.
A Working Alternative
The SEIN automation stack doesn’t require any external services to operate. Home Assistant runs locally. Sensor data is stored in a local database. Automations execute locally. Relay control happens over a local RS485 bus or local MQTT network. The only cloud dependency is optional: if you want remote access when you’re away, you set up a VPN or use Home Assistant’s cloud companion service, on your terms, for your reasons.
The relay bridge that controls irrigation solenoids and pumps announces itself to Home Assistant via MQTT Discovery, a standard protocol that creates entities automatically without configuration files. The MQTT proxy bridges external sensor nodes to the local broker. The irrigation terminal runs on your local WiFi. Nothing requires a paid account. Nothing breaks when a company changes its pricing.
This is achievable with off-the-shelf hardware and freely available software. The knowledge required is not trivial. Setting up Home Assistant, configuring MQTT, wiring relay boards: these take real time and effort. But they’re learnable, documentable, and shareable. Unlike a proprietary system, when you’ve figured it out, you can help the next person who wants to do the same thing.
“No subscription” does not mean no cost to anyone. Home Assistant is built by thousands of contributors who give time, expertise, and infrastructure. The relay hardware and firmware SEIN publishes exists because someone had to design, test, and document it. Open source is community-funded infrastructure, not a free lunch. If you build your automation on these tools and they work for you, the most useful thing you can do is contribute back: financially, through documentation, or by helping someone else get started.
Proprietary vs. Local-First
| Proprietary smart home | Home Assistant | |
|---|---|---|
| Upfront cost | $150–$500 per device | Hardware + setup time |
| Ongoing cost | $5–$30/month per platform | No subscription (community-supported) |
| Works without internet | Rarely | Always |
| Data stays local | No | Yes |
| Survives company closure | No | Yes |
| Fully customisable | Limited | Yes |
The Broader Point
The pattern that plays out in home automation is the same one that plays out in agricultural technology, in farm management software, in seed licensing, in satellite imagery, in precision agriculture platforms. The tools that could help growers, homeowners, and communities make better decisions are structured to extract recurring payment for access to those decisions. The underlying knowledge, data, and control remain with the platform provider, not the user.
Local-first automation is a small act of resistance to that structure. Not heroic. Not revolutionary. Just a deliberate choice to own the infrastructure for your own daily life, rather than renting it.
Your home is not a server farm’s endpoint. It’s where you live. The tools that help you manage it should be yours.
