Local smart home vs cloud: why local-first wins

Short version: in a cloud smart home, the brain lives on someone else's servers, so every light switch is a round trip to the internet and back — and the day the NBN drops, or the company pulls the plug, your house goes dumb. A local-first smart home keeps the brain in your house, usually on a small box you own running Home Assistant. It's faster, it dodges vendor lock-in, and it keeps working when the internet doesn't. If you're building a smart home from scratch, that's the call I'd make every time: own the brain, don't rent it.

The thing nobody tells you about "smart"

Most smart gadgets aren't smart. They're a dumb radio with a phone-home cable. You press a button in an app, that command leaves your house, hits the manufacturer's cloud, comes back, and only then does the light come on. You're paying a latency tax and an availability tax on every single action, for the privilege of a server in another country making a decision a box in your hallway could make instantly.

That's fine right up until it isn't. The cloud has a bad day, or the company decides the feature you bought is now a subscription, or they discontinue the product and switch the servers off — and your gear is suddenly a paperweight. It has genuinely happened: hubs, bulbs and cameras from real brands bricked overnight when the cloud behind them went dark. You didn't own a smart home. You were renting access to one.

Local-first means you own the brain

A local-first smart home flips it. The decisions happen on a box in your house — a cheap mini PC or a Raspberry Pi running Home Assistant, the open-source hub that's become the obvious answer for anyone who wants control. Your motion sensor talks to that box, the box decides, the light comes on. No internet involved unless you actually want to reach in from outside.

This is the part that matters and the part the glossy packaging skips: when the brain is yours, the home is yours. The automations are rules you wrote, stored on hardware you control. Nobody can change the app out from under you, paywall a feature you already paid for, or take the lights down because a data centre on the other side of the world fell over. Own it, don't rent it — it's the same principle whether you're running a business or running your lounge room.

Vendor bridge lock-in is the trap

Here's where most homes get quietly captured. You buy one brand's starter kit. It comes with the brand's hub — the "bridge" — and everything has to route through it and the brand's app. Want a different sensor that's cheaper or better? Doesn't pair. Want to mix two ecosystems? You now run two apps that don't talk. Every new device is a vote to stay locked in, because leaving means rebuying the lot.

The way out is open standards. Zigbee and Z-Wave have been the workhorses for years; Thread and Matter are the newer push to make brands interoperate. A local hub like Home Assistant speaks all of them at once. Pair a $15 Zigbee plug, a Thread sensor and a Z-Wave lock to the same box and they all just work together — no vendor bridge, no per-brand app, no permission needed from a manufacturer. You buy on merit and price, not on which walled garden you're already standing in.

A word on the cheap stuff, because it's the same lesson from a different angle: the bargain WiFi smart plugs and old cameras are usually the most cloud-dependent and the chattiest on your network. If you're keeping any of them, at least put them on their own WiFi lane so they can't crowd the gear you care about. Local control and good network hygiene go together.

It keeps working when the internet drops

This is the clincher, and it's not hypothetical in Australia. Plenty of homes are on a flaky NBN connection or running a network already stretched thin by a houseful of devices — and out in the bush, 5G is the whole internet, no fixed line at all. When that link wobbles, a cloud smart home goes blind: lights won't switch, the app spins, "device unreachable" everywhere. A local-first home doesn't even notice. The motion-triggered hallway light, the morning schedule, the door sensor that flicks on the porch — all of that runs on the box inside your walls. The only thing you lose is reaching in from outside, and the moment the connection's back, that returns on its own.

Think about what you actually want automated: lights, heating, security, the routine stuff that runs every day. None of it should depend on a server in another timezone being healthy. A house that copes is one where the important things keep working no matter what the line is doing.

Where the cloud actually earns its place

I'm not anti-cloud — I'm anti-dependent. There are jobs the cloud does well, and a sensible local-first home uses it on its own terms. Remote access when you're away. Voice assistants, if you want them. The odd integration that genuinely only exists online. The rule is simple: the cloud should be a convenience layer bolted on top of a home that already works without it, never the foundation the whole thing stands on. Local-first doesn't mean no internet — it means the internet is optional, not load-bearing.

Where it does cost you a bit is the setup. A cloud kit is plug-and-pray; a local hub asks you to run a small box and pair devices to it instead of to each brand's app. That's a couple of hours and a one-off learning curve, not a renovation — and you do it once. After that it's lower-cost to run (no subscriptions creeping in) and far harder to take away from you.

What I'd actually buy

If you're starting today and you want a home that lasts, here's the order I'd do it in.

1. Get a brain you own. A small mini PC or a Raspberry Pi running Home Assistant. This is the single decision the whole house hangs off — make it local from day one.
2. Buy on open standards, not brands. Zigbee, Z-Wave, Thread or Matter, and check each device says "local control" or "works with Home Assistant" before it goes in the trolley. If it only works through one company's cloud app, leave it on the shelf.
3. Add a Zigbee or Thread adapter. A cheap USB stick on the box lets it talk to the open-standard gear directly, no manufacturer bridge in the middle.
4. Keep automations local. Write the everyday rules — lights, schedules, sensors — so they run on the box, not the cloud. That's what survives an outage.
5. Bolt the cloud on last, if at all. Remote access and voice are extras you add once the home already works on its own.

The honest bottom line

A cloud smart home is quicker to unbox and slower to live with: a latency tax on every action, a subscription waiting to appear, and an off-switch held by someone else. A local-first home costs you a bit more setup up front and pays it back every day after — faster, cheaper to run, immune to outages, and genuinely yours. For most Australian homes, that's not a close call. Own the brain, buy on open standards, and let the cloud be the cherry on top instead of the foundation.

Frequently asked questions

Want a smart home built local-first — one you own, that keeps running when the internet doesn't? That's exactly the kind of setup we do. We'll pick gear that won't lock you in, get Home Assistant running properly, and leave you with a home that's actually yours. No lock-in, no upsell to gear you don't need. Tell us what you want to automate and we'll map it out.