Your ISP has an outage. Your internet is down. You expected your local network to keep working: lights still controllable through wall switches, smart speakers still able to play locally-stored music, automations still firing. Instead, half your smart home is broken. Voice commands fail. Some scheduled automations skip. Smart speakers stop playing. The dependencies on the cloud are deeper than you realized.
Map your dependencies
For each smart home function, identify what it depends on:
- Voice commands: depend on cloud (Alexa, Google, HomeKit cloud)
- Automations triggered locally (motion sensors, schedules): often local on capable hubs
- Smart speakers playing music: depends on streaming service which is cloud
- Smart cameras: depend on cloud for both local viewing and recording (depending on model)
- Lights via wall switches: local if the wall switch directly controls the bulb
- Smart locks: usually local for BLE, cloud for remote
Knowing what is local versus cloud lets you predict outage behavior.
Test by simulating an outage
Unplug your modem briefly. Note what stops working. After 5 minutes, plug it back in.
The failures you observe during the simulation are your cloud dependencies. Each one is a candidate for redesign toward local execution.
The voice assistant during outage
Voice ecosystems are heavily cloud-dependent. Alexa and Google Assistant essentially do not work without internet. HomeKit can still respond to local commands but loses external integrations.
For critical functions that need voice during outages: build them as physical buttons or scene controllers (wall-mounted smart buttons, dedicated remotes). These work without voice and without internet.
The hub’s cloud dependency
Different hubs have different levels of cloud dependency:
- Hubitat: fully local. Almost everything works during outages.
- Home Assistant: fully local for core function. Optional cloud features may break.
- SmartThings: Edge drivers are local. Cloud routines stop working.
- HomeKit: local for accessories, but iCloud sync is degraded.
- Hue: local for bulb control. Cloud-dependent for remote access and voice integration.
- Aqara: most functions need cloud, even local-looking ones.
If your hub is cloud-heavy and you care about outage survival, consider migrating to a more local platform.
The DNS cache cliff
Even “local” hubs may need DNS to resolve manufacturer cloud endpoints. If your DNS server is your ISP’s and the ISP goes down, DNS lookups fail.
Configure your router to use external DNS (1.1.1.1 or 8.8.8.8) so DNS continues to work even if your ISP is down. Your router’s connection to these external resolvers depends on internet, but cached responses keep working briefly.
The router as the failure point
If your modem and router are integrated and the modem fails, your router’s local Wi-Fi may also fail. Smart devices on Wi-Fi cannot communicate with each other or with your phone.
Use a separate modem and router. If the modem fails, the router keeps your local network functional.
The smart speaker offline behavior
Smart speakers vary widely in their offline behavior:
- HomePod: plays locally stored music via AirPlay from another Apple device on local network.
- Google Home Mini/Nest Mini: limited offline; cannot play music without internet.
- Echo Dot: limited offline; cannot play music without internet.
- Sonos: can play music from local NAS or USB drive without internet.
If music during outages matters, Sonos or AirPlay-based setup is more resilient.
The smart camera during outage
Most consumer cameras require cloud for live viewing, even from inside the house. During an internet outage, you cannot see the camera even from your phone next to it.
Cameras with local-only options:
- Reolink (with NVR or local recording)
- Ubiquiti UniFi Protect
- Synology Surveillance Station with compatible cameras
- HomeKit Secure Video (records to iCloud but live view is local if your hub is HomeKit)
For local-first camera viewing, these are worth considering.
The automation engine during outage
If your automation engine is in the cloud (some SmartThings routines, Alexa routines), they do not fire during outages. Local engine routines (HomeKit, Hubitat, Home Assistant) continue to fire normally.
Move critical automations to the local engine. Keep cloud-only automations for non-critical functions.
The DHCP lease renewal
If your DHCP lease expires during an extended outage, your router may not be able to renew it (depending on whether the router has internet for renewal). Some devices lose their IP and stop functioning.
Use long DHCP lease times (24 hours minimum) so brief outages do not cause lease expiry. Some routers default to 1-hour leases which is aggressive.
The OAuth token refresh
Cloud integrations use OAuth tokens. During an outage, tokens may expire. After the outage, refreshing requires reaching the OAuth server, which may be unreachable.
This causes a delay in restoration: the outage ends, your local network works, but your cloud integrations remain broken until you manually re-authorize.
The cellular fallback
For critical needs, a cellular fallback can keep your smart home internet-connected during ISP outages.
Options:
- Cellular hotspot from a phone
- Cellular modem with automatic failover (some business-class routers support this)
- Dedicated cellular IoT plan for the smart home equipment
The cost-benefit depends on how often your ISP has outages and how critical the smart home features are during them.
The UPS for the hub
An uninterruptible power supply on your hub and router keeps them running through brief power outages (which often coincide with internet outages). The combination of UPS plus cellular fallback means your local network stays up through both power and ISP outages.
The realistic accept of cloud
Some cloud dependencies are not worth eliminating. The complexity of building a fully local smart home is significant. Most users find that occasional cloud failures are an acceptable cost.
For households with the time and interest to invest in local-first, Home Assistant is the most powerful option. For most users, the right balance is local-first for critical and convenience-cloud for everything else.
The local-first audit worth doing once
Make a list of every smart home automation that matters to you. For each, ask: does this work without internet? The ones that do not are candidates for local-first redesign. Maybe not all of them, but at least the safety-critical ones.
This audit is uncomfortable because it reveals dependencies you forgot about. Once done, the redesign work spans weeks, but the result is a smart home that survives ISP problems without drama. The pattern for designing resilient automations is in our resilient routines guide.
