Smart Home When the Internet Goes Down

A smart home without internet is the question every beginner asks five minutes after buying their first smart bulb: what happens when the Wi-Fi drops? The honest answer is that it depends entirely on what you bought. A house full of cloud-only Wi-Fi gadgets becomes a brick the moment your router resets. A house running on local protocols — Zigbee, Z-Wave, Matter, Home Assistant — barely notices.

This guide walks through which devices need internet to function, which keep working without it, how Matter changed the picture in 2024, and a practical layered approach that lets your most important automations (lights, locks, climate, security) keep running through outages without turning your home into a server-room project.

Most cheap smart-home gadgets — the £15 Wi-Fi plug, the budget bulb, the off-brand camera — round-trip every command through the manufacturer's cloud. You press the button on your phone. The phone sends the command to the manufacturer's server. The server sends the command to the device sitting two metres from your phone. If any link in that chain breaks (their server's down, your internet's down, the app crashes), the device sits there ignoring you.

This isn't an accident. Cloud round-tripping is cheaper for the manufacturer than building proper local control, easier for them to monetise (data, subscriptions), and easier to ship — they don't have to handle the awkward problem of letting your phone find their device on your local network. It's the dominant pattern in the cheapest tier of smart-home hardware.

The fix isn't 'avoid all Wi-Fi devices' — it's 'know which devices are local and which aren't, and architect around it'. The four protocols below are what 'local' looks like in practice.

Four protocols handle the bulk of local-first smart home traffic. Each behaves differently when the internet is down.

Zigbee

A short-range mesh network that doesn't touch your Wi-Fi or your internet. A Zigbee bulb talks to a Zigbee hub (Hue Bridge, SkyConnect, Sonoff dongle) over its own radio. The hub talks to your phone over your local network. Zigbee continues working completely with no internet, as long as you control it from a device on the same Wi-Fi (your phone, a wall keypad, or a voice assistant if it's also local).

Z-Wave

Same idea as Zigbee, different radio frequency, slightly slower mesh, generally better range and slightly higher quality build (Z-Wave devices certify more strictly). Same offline behaviour: works fine without internet via a local hub.

Matter (with Thread)

The 2024 protocol Apple, Google, Amazon and Samsung agreed on. Matter is the language; Thread is one of the radio layers it runs over (the other being Wi-Fi). Matter-over-Thread devices behave like Zigbee — local mesh, no internet needed. Matter-over-Wi-Fi devices behave like Wi-Fi — fine on a local network even if your internet's down, as long as their firmware doesn't insist on phoning home.

Home Assistant local

Home Assistant is software, not a protocol — but the philosophy is 100% local-first. Every integration is implemented locally where possible, and the platform itself runs entirely on a Raspberry Pi or mini-PC in your home. Our Home Assistant introduction covers the trade-offs of running it.

The matrix below is the practical answer most readers want. 'Survives' means the device responds to commands from a phone or wall switch on the local network when internet is offline.

The cluster of cloud-only failures (Nest cameras, Ring, generic Wi-Fi plugs) is what causes the most pain in real outages. People discover it the wrong way — power flickers, internet's down for an hour, and suddenly half their house has stopped responding. The Hue/Zigbee/Z-Wave/Home Assistant cluster is the cluster that quietly keeps working.

Matter is worth a separate paragraph because it's the protocol most beginners are confused about. The promise of Matter is that it gives you local control across Apple, Google, Amazon and Samsung simultaneously. The reality in 2026 is that this works for the basics — bulbs, plugs, sensors, simple switches — and is still patchy for the complex stuff (cameras, multi-zone climate, advanced lighting scenes).

What matters for outages is the 'multi-admin' feature: a single Matter device can be controlled by multiple ecosystems at the same time. So an Eve smart plug can be paired into both Apple Home and Home Assistant, and you can control it from either one. If Apple's services are down but your Home Assistant Pi is fine, you still get control. If your internet's down entirely, both systems control the device locally over Thread.

The catch: you need a Thread Border Router on your network for Matter-over-Thread to work. This is built into a HomePod mini, Apple TV (newer models), Google Nest Hub Max, and Aqara/Nanoleaf hubs. Without one, Matter-over-Thread devices can't talk to anything. Our Matter explainer covers the device-by-device picture.

The robust pattern most experienced smart-home users converge on has three layers. Each handles a different type of failure.

Layer 1: Local control as the default

Buy local-protocol devices (Zigbee, Z-Wave, Matter-over-Thread) where possible. Treat cloud-only Wi-Fi devices as a last resort, and only for things where 'doesn't work for an hour' is acceptable (e.g. a guest-room lamp).

Layer 2: A local hub on a UPS

A Raspberry Pi running Home Assistant — or a HomePod mini for a HomeKit-only setup — sitting behind a £40 uninterruptible power supply (UPS). The UPS gives you about 30-60 minutes of runtime through power blips. The router goes on the same UPS so the local network stays up. Our Pi setup guide walks through the hardware side.

Layer 3: Physical fallback for critical functions

The non-negotiable layer. Every smart lock should have a physical key. Every smart switch should still work as a regular switch (most do — they pass the 'dumb switch' test). Hardwired smart-home wiring should be wired so a failed hub doesn't leave the room dark. The pattern: every important automation should have a manual override that doesn't depend on any computer.

The most common offline-smart-home request is 'I want to ask Alexa to turn the lights off when the internet is down'. The honest answer in 2026 is: partial support, brand-dependent.

Amazon Echo (Alexa)

Echo devices have a local fallback that handles basic on/off commands for connected devices when internet drops, provided the devices are also local-control. The fallback doesn't handle complex routines, music streaming, news briefings, or anything that needs the cloud. Don't rely on it for the routine that opens your blinds in the morning.

Google Nest speakers

Limited local processing. Most commands need internet. The exception is local broadcast (intercom-style messages between speakers) and some Matter device control via Thread.

Apple HomePod / Siri

The most reliable offline voice option. Siri can control any HomeKit-enabled local device through the local hub (HomePod/Apple TV) without internet, as long as the command is straightforward and doesn't need a cloud knowledge lookup. 'Turn off the lights' works. 'What's the weather' doesn't.

Home Assistant Voice (Local)

The 2024-released local voice satellite from Home Assistant runs entirely offline using on-device speech recognition. Setup is more involved than buying an Echo and the wake-word recognition is rougher, but it's the only option that's genuinely 100% local. Worth considering if voice control during outages is a hard requirement.