The Lights Are Still On. For Now.
You spent two weekends getting it right. The motion sensors, the thermostat, the door locks, the little hub sitting quietly on your router shelf. Everything talks to everything. You say "goodnight" and the whole house listens.
Then one morning there's an email. The company is "sunsetting" its platform. You have ninety days.
This happens more than most people realize. The consequences aren't just annoying, either. They range from mildly irritating to genuinely expensive, depending on exactly how your system was built, and understanding the mechanics is the only way to know which camp you're in.
Cloud-Dependent vs. Local: The Fault Line That Actually Matters
Most consumer smart home devices fall into one of two categories. The distinction determines everything about what happens when a manufacturer walks away.
Cloud-dependent devices do their thinking on the company's servers. When you tap your phone to dim the lights, your command travels to a data center somewhere, gets processed, and bounces back to the bulb. The bulb itself is basically a radio with a light attached, no brain of its own. When the servers go dark, the bulb becomes a very expensive piece of glass that only works with a physical switch.
Google's Revue TV product is a clean example. The moment Google stopped supporting the authentication infrastructure, units couldn't complete the sign-in process. Hardware that worked perfectly yesterday became a paperweight overnight, not because anything broke, but because the conversation it needed to have had no one left to answer.
Local-processing devices run their logic on a hub in your home or on the device itself. The cloud might handle remote access or voice commands, but the core automation lives on your network. These survive a shutdown much better. Zigbee and Z-Wave devices use open radio protocols. Pair them with a community-maintained hub like Home Assistant and they'll keep running indefinitely, long after the original app vanishes from the App Store.
The practical split: a smart lock that requires a cloud handshake to verify your PIN is a liability. A smart lock that stores credentials locally and only uses the cloud for remote management is recoverable.
What Actually Breaks, Step by Step
A shutdown rarely happens all at once. Think of it less like a power cut and more like limescale building up in a kettle: gradual, invisible, then suddenly critical.
First to go are usually the app and new account creation. Existing users can still log in for a while. Remote access from outside your home network goes next, because that routing lives on company servers. Then software updates stop, which matters more than it sounds. Unpatched firmware is a real security exposure on a device that sits on your home network.
Automations that relied on the company's cloud logic start misbehaving as those services are quietly retired. Finally, authentication tokens expire. At that point the hardware is effectively bricked unless you can flash alternative firmware.
Consider a scenario with some real stakes. Maya buys a smart home starter kit from a mid-sized company. Eight devices, one hub, roughly 200 automated rules she's built over three years. The company gets acquired. The acquirer has no interest in running the platform. Maya gets her ninety-day notice.
If her hub uses Zigbee radios and she's willing to spend a weekend migrating to Home Assistant, she saves everything. If her hub uses a proprietary radio protocol that only talks to the original cloud infrastructure, she's replacing hardware. Eight devices, three years of configuration work, gone.
Her neighbor Tom bought from the same company but went deeper: cloud-dependent door locks with no local fallback. Tom has a bigger problem. His locks won't accept codes until he buys new hardware entirely.
What People Get Wrong About This
The common assumption is that "smart" means resilient. More features, more reliability.
That's exactly backwards, and it's a costly mistake.
A standard dumb thermostat from the 1990s still works. A cloud-dependent smart thermostat from five years ago might not. Complexity without local fallback is fragility dressed up as sophistication.
People also underestimate how fast the ecosystem collapses around a single shutdown. Third-party integrations break first, often before the official sunset date, because developers stop maintaining them when they see the writing on the wall. Skills disappear from Alexa. Routines in Google Home stop triggering. Your system doesn't fail in one dramatic moment. It just quietly stops doing things, one by one, until you notice.
So what about open protocols? They help enormously, but they're not a complete answer. A Zigbee device is portable to a new hub. But if the device's firmware has a security vulnerability and the manufacturer is gone, no one is issuing a patch. You're running known-vulnerable hardware on your home network indefinitely. Worth knowing before you buy.
How to Build a System That Survives
You don't need to predict which companies will fold. You need to build with the assumption that any of them might.
Prioritize devices that support open protocols: Zigbee, Z-Wave, or the newer Matter standard, which was specifically designed to reduce platform lock-in by letting devices speak a common language across ecosystems. A Matter-certified device can theoretically be adopted by any Matter-compatible hub, regardless of what happens to the original manufacturer.
Run a local hub where you can. A Home Assistant instance on a small home server means your automations don't depend on anyone's data center. Remote access can still work through a VPN you control.
Before you buy anything, search the device's model number plus "local API" or "local control." A small but dedicated community documents which devices can be controlled without touching the cloud. If that documentation doesn't exist for a product, treat it as a cloud-only device and plan accordingly.
Ask yourself honestly: if this company disappeared tomorrow, what would I lose? If the answer is "everything," that's not a smart home. That's a rental you're paying for in hardware.
Every device you buy is a small bet on the company behind it. The only hedge that actually works is making sure the device can outlive the bet.