Photo by Anete Lusina on Pexels
The outage that exposes everything
Your internet drops for twenty minutes — a router reboot, an ISP hiccup, whatever. Suddenly your "smart" lock won't unlock from the app, your motion-triggered lights stop triggering, and the thermostat schedule you set up freezes wherever it happened to land. None of this shows up in a product review. It only shows up the one time you actually need it, which is usually the worst possible moment.
I've tested a lot of smart home gear at this point, and the thing that separates the stuff I keep from the stuff I return isn't features. It's whether the device still does its one job when the connection to some company's server in another state goes quiet. Most gadgets fail this test. A few don't. Almost nobody checks before they buy.
Why so much "smart" is actually just "cloud-dependent"
Here's the part manufacturers don't put on the box: a lot of consumer smart devices don't talk to each other directly. Your smart plug talks to the manufacturer's cloud, your phone talks to the same cloud, and the cloud plays translator in the middle. That's fine and invisible right up until your internet goes down, or the company's servers have a bad day, and now two devices sitting six feet apart in your living room can't coordinate anything.
This is different from local control, where the logic — "if motion, then light" — lives on a hub or device inside your house and never needs to leave your network to run. Local doesn't need the internet at all. Cloud does, every single time, even for something as dumb as turning on a lamp.
The frustrating part is you usually can't tell which one you're getting just by reading the app description. "Works with Alexa" tells you nothing about where the automation actually executes.
A worked example: the 2am routine that quietly breaks
Say you've got a motion sensor by your front door set to turn on the porch light after sunset. If that automation is cloud-based, here's what actually has to happen every time someone walks up your driveway: the sensor sends a signal to the manufacturer's server, the server checks the rule, the server sends a command back down to the bulb, and the bulb turns on. Four hops, all outside your house, all dependent on your internet connection being up at that exact second.
Now say your ISP does a maintenance window at 2am — a pretty ordinary thing for ISPs to do. For the next twenty minutes, that light just doesn't turn on. No error, no notification, nothing dramatic. It just silently doesn't work, and unless you happen to be standing there, you'd never know.
Compare that to a local Zigbee or Z-Wave setup running through a hub in a closet somewhere. The sensor and the bulb are both paired directly to that hub, on your own network, and the "if motion, then light" logic lives on the hub itself. Your internet can be completely dead and the light still turns on, because none of it ever needed to leave the house.
Where I landed on Matter (and why it's only a partial fix)
I've written before about whether the Matter standard is actually worth trusting yet, and one thing that discussion undersold is that Matter mostly solves the *compatibility* problem — getting a Google, Amazon, and Apple ecosystem to talk to the same device — without automatically solving the *dependency* problem. A Matter device can still be built to lean on the cloud for anything beyond the most basic on/off command, depending on how the manufacturer implemented it. Matter is a step in the right direction, but it's not a guarantee that your automations run locally. You still have to check.
The 10-minute test worth running on your own setup
Photo by William Bradshaw on Pexels
You don't need to guess at any of this. Pull the network cable out of your router, or just turn off Wi-Fi on your phone and walk around the house, for about ten minutes:
- Do your existing automations (motion lights, schedules, locks) still fire?
- Can you physically operate the device itself even without the app — light switch, lock keypad, thermostat dial?
- Does anything get stuck in a weird state that needs the app to reset?
If your critical stuff — locks, safety-relevant lighting, garage door — keeps working with no internet at all, you're in good shape. If everything goes dark until the connection comes back, that's useful information, and it's cheap to find out now instead of during an actual outage.
Not everything needs to be local — pick your battles
I'll push back a little on the purist version of this advice, though. You don't need a fully local, internet-free smart home. That's a lot of setup work for questionable payoff. Your video doorbell uploading clips to the cloud is fine — you don't need that footage the second your Wi-Fi blips, you need it eventually. Same with voice assistant queries, weather-based routines, or anything that's genuinely nice-to-have rather than load-bearing.
Where it actually matters is the small list of things you'd notice failing at a bad moment: door locks, security lighting, anything tied to safety, and probably your thermostat if you live somewhere winters get serious. Everything else can stay cloud-connected without much cost. Trying to make your whole house internet-independent is a weekend project that solves a problem you mostly don't have.
FAQ
Does Zigbee or Z-Wave always mean local control?
Not automatically — it means the device is capable of local control, but it depends on the hub. Some hubs (Hubitat, Home Assistant, and some Aqara and SmartThings configurations) run the automation logic on-site. Others still phone home to a cloud service even though the underlying radio is Zigbee or Z-Wave. Check the hub's documentation, not just the device's.
Is Wi-Fi always cloud-dependent, then?
Mostly, yes, for consumer gear — Wi-Fi smart plugs and bulbs are usually built to talk to a cloud service by default, since that's simpler for the manufacturer to support. There are exceptions, and some platforms let you set local-only automations even on Wi-Fi devices, but it's the exception rather than the rule.
Do I need a separate hub to get local control?
For most non-Matter Zigbee or Z-Wave gear, yes — you need something like Home Assistant, Hubitat, SmartThings, or a manufacturer hub sitting on your network to run the local logic. Matter is slowly changing this by building more of that logic into your existing Wi-Fi router or a Thread border router, but plenty of homes still need a dedicated hub to get real local reliability today.
The boring stuff wins again
This is basically the same conclusion I keep landing on with every smart home post I write: the flashy feature list matters less than whether the thing quietly does its job when conditions aren't perfect. A smart lock that needs the cloud to open is a worse lock than a dumb one. Run the ten-minute test on what you've already got before you buy anything else — you might find the gap is smaller than you think, or you might find your porch light has been failing silently for months.
Keep reading
- Your Phone Makes a Surprisingly Good Second Monitor. Here's When It's Actually Worth It
- Is the Matter Smart Home Standard Actually Worth Trusting Now?
- Water Leak Sensors Are the Most Boring Smart Home Purchase You Can Make. That's Exactly Why They Work
#smarthome #homeautomation #techtips
Comments
Post a Comment