Which Smart Home Devices Survive an Extended Power Outage?
An extended outage usually kills smart home controls through the internet drop, not the power drop: cloud-dependent devices fail first, while local Zigbee, Z-Wave, Matter, and Thread devices keep working if their hub and network path stay powered. That protocol split, plus the power-draw numbers, tells you which devices to prioritize and which backup layers — UPS, DC battery, cellular — your setup really needs.
Last updated
For an extended smart-home power outage plan, the first uncomfortable fact is that “extended” does not have to mean a weeklong disaster. The latest complete annual U.S. figure is for 2024: customers averaged 11 hours of electricity interruptions that year, nearly twice the prior decade’s annual average, with Hurricanes Beryl, Helene, and Milton accounting for 80% of those hours. The EIA published that analysis in December 2025, so it is a dated 2024 full-year measure, not a live 2026 outage forecast. [1]
Eleven hours is long enough for a phone battery to fall, a router UPS to empty, a cable node to go dark, and a family member to discover that the “smart” way into the house depended on a cloud request. The useful planning question is narrower than “will my smart home work?” It is: which controls remain available locally, and what has to stay powered for those controls to survive?

The outage that matters first may be the internet outage
A grid failure and an internet failure are separate events. They often arrive together, but they break different parts of the house. If the power goes out and your modem, router, hub, and key low-voltage devices stay powered, local control can continue. If the internet drops while your LAN is still alive, cloud-dependent devices can still become unreachable.
That split shows up clearly in a pull-the-plug test from HomeTechHacker: after disconnecting the internet, cloud voice control and Tuya-class Wi-Fi devices stopped working, while local-API Wi-Fi devices such as TP-Link, LIFX, and Shelly, plus Zigbee and Z-Wave devices, continued to operate through the local controller. [2]
Home Assistant’s own FAQ says it can work without an internet connection, with the important limit that integrations depending on cloud services will not. Hubitat makes the same basic point from its side of the hub world: locally processed automations and compatible local devices can keep running without the internet, while cloud integrations cannot. [3][4]

This is why a device’s radio label is only part of the answer. Zigbee, Z-Wave, Thread, and Matter can be strong outage choices because they are designed for local networks, but they still need the controlling path to be alive. A Zigbee motion sensor is not useful to an automation if the hub is dead. A Thread device still needs the right border-router path. A Matter device may be locally controllable, but the controller doing that local work still needs power. If you are choosing Matter gear specifically for local behavior, the same purchase-time questions apply: what controller owns it, what network path does it use, and what happens when the WAN is gone? For a deeper protocol view, see the site’s Matter and Home Assistant guide.
What usually survives, and what usually does not
The cleanest way to sort outage value is not by brand prestige. Sort by dependency chain. A device that can sense, decide, or be controlled locally has a short chain. A device that must ask a vendor cloud for every routine command has a long one.
| Device or control path | Likely outage behavior | What must remain alive |
|---|---|---|
| Battery Zigbee or Z-Wave contact, motion, leak, and temperature sensors | Can keep reporting locally if paired to a powered local hub | Sensor battery, hub, and the hub’s local network path |
| Matter or Thread sensors and controls | Can remain locally controllable when the Matter controller and required Thread or LAN path stay powered | Controller, Thread border router if needed, router or local network segment |
| Local-API Wi-Fi devices | Can remain controllable on the LAN if the router and controller are powered | Device power, Wi-Fi router or access point, local controller |
| Cloud-dependent Wi-Fi plugs, bulbs, cameras, and voice commands | May fail when the internet or vendor cloud path is unavailable, even if the house LAN still works | Internet service, vendor cloud, account services, and device power |
| Smart locks with keypads, batteries, and physical keys | Locking hardware can still function locally; app control depends on the lock, hub, bridge, and network path | Lock battery, physical key or code, and powered bridge only if remote or hub control is needed |
| Sirens and alarms tied to local automations | Can still sound for local sensor events if powered and locally integrated | Siren power or battery, hub, sensors, and local automation engine |
Battery sensors deserve more attention than they usually get in outage planning. They are not drawing from the dead circuit, and their job is simple: report that a door opened, water appeared, temperature fell, or motion happened. In a local system, those reports can still trigger a siren, notification inside the house, light, or dashboard state if the hub and the local network are running.
Locks deserve a stricter standard. A smart lock that still accepts a keypad code during an outage is useful. A smart lock with a physical key is less elegant and more reassuring. A lock that requires a phone, cloud session, or bridge for normal entry has shifted risk to the person standing outside. App convenience is pleasant on a normal Tuesday; manual entry is what matters when the network is down.
Cloud voice control gets only a small role in a serious plan. It may be the easiest interface when everything is healthy, but it is a poor emergency dependency. In the pull-the-plug result, voice control failed with the disconnected internet while local device paths continued. [2]
The local network path is part of the device
A local device is not an island. In practice, “local control” means a chain: the device, the radio mesh or Wi-Fi link, the hub or controller, the router or switch if needed, and the interface you are using to issue the command. Break the wrong link and the device may still be electrically alive while becoming operationally invisible.
That is why the modem question is separate from the router question. If you only care about local automations inside the house, the WAN can disappear and the LAN may still matter. If you want remote alerts, off-site camera access, cloud notifications, or a relative checking status from another city, then the modem, internet provider path, or cellular failover becomes part of the preparedness system. The same LAN-versus-internet distinction shows up in satellite setups too; the site’s Starlink smart-home compatibility guide covers that boundary in more detail.
A useful home test is blunt: put the modem on a switchable outlet or unplug its WAN connection, leave the router and hub running, then try the controls that would matter during an outage. Try a lock, a siren, a leak sensor automation, a motion light, a thermostat change, and any dashboard you expect to use. This test does not prove how long your batteries will last. It proves which devices were never local in the first place.
Backup power starts small because the critical load is small
The encouraging part is that the most important smart-home load is often modest. HomeTechHacker’s sizing guide estimates a modem at 8–12 watts, a router at 10–15 watts, and a smart-home hub at 3–6 watts, putting a typical small smart-home network in roughly the 25–40 watt range. These are author estimates, not lab measurements of your specific equipment. [5]
Measured UPS runtimes give a better feel for what that load means. Wirecutter’s 2026 lab testing reported that the CyberPower LE1000DG ran a 20-watt load for 3 hours and a 300-watt load for 12 minutes, with a listed price of $140; the CyberPower CP1350AVRLCD3 ran a 20-watt load for 4.5 hours at $196; and the Amazon Basics 800VA ran a 20-watt load for 1.5 hours at $70. Those are model-specific lab results, not a general promise that any UPS of the same size will behave identically. [6]
| Backup layer | Best use | What it protects |
|---|---|---|
| UPS for modem, router, switch, and hub | Short interruptions and multi-hour outages when the total load is modest | LAN control, hub automations, and possibly internet if the ISP path remains available |
| DC battery for 5V/12V hub-class gear | Keeping a small controller, alarm board, or low-voltage device alive without AC inverter losses | Hub-class devices and some security hardware |
| Cellular failover | Remote alerts and outside access when wired internet fails but local power is available | WAN connectivity, not the house’s electrical load |
| Portable power station or generator | Longer outages, refrigeration, medical equipment, larger networking stacks, or repeated recharge cycles | Broader household loads beyond the low-watt smart-home core |

This is where confident runtime claims need discipline. A manufacturer’s runtime chart, an enthusiast’s wattage table, and an independent lab measurement are not the same kind of evidence. Wirecutter’s results are measured for particular UPS models under particular loads. HomeTechHacker’s load ranges are planning estimates. Your own modem, router, mesh nodes, PoE switch, hub, and ONT can move the number in either direction.
For exact runtime math and wiring choices, use a recipe rather than turning this into a shopping spreadsheet. The site’s UPS or power station guide is the better place for that calculation, and How to Power Your Smart Home Through a Blackout handles the broader tiered setup.
UPS: the layer for blips and hours
A UPS is the first backup layer because it solves the ordinary ugly failure: a short outage or flicker that reboots the modem, router, hub, and every automation that depends on them. It also gives you time to shut things down cleanly or ride through an outage that is measured in minutes rather than days.
HomeTechHacker’s UPS sizing guide points to the 850–1000VA range as a common smart-home sweet spot and notes a lifecycle tradeoff: traditional lead-acid UPS batteries are commonly in the 2–5 year replacement range, while lithium options may reach around 10 years. Those are guide-level planning statements, not guarantees for every battery or environment. [5]
DC battery: the quiet layer for hub-class devices
Some smart-home gear does not really need a full AC UPS. Hubs, alarm panels, and low-voltage boards often live in the 5V or 12V world, where a DC backup battery can avoid converting battery power to AC and then back down to DC. Konnected markets its backup battery for that 5V/12V hub class and rates it for 8–14 hours, but that is a manufacturer rating rather than an independently verified runtime result among the sources cited here. [7]
The practical judgment is simple: if one small controller is the difference between local sensors continuing and the whole system going blind, it may deserve its own direct battery path. That does not replace the router UPS if the controller needs the LAN. It protects one critical link from being dragged down by a larger backup load.
Cellular failover: useful only when remote connectivity matters
Cellular backup is often oversold as if it powers the smart home. It does not. It gives the home another internet path when the primary connection fails, assuming the cellular device has power and the cellular network is operating. T-Mobile describes cellular backup internet as a failover path for home connectivity, and Frontier frames backup internet selection around both power failures and network failures. [8][9]
If no one needs to see the house from outside, a local system can still be useful with no WAN. If you need remote leak alerts, alarm notifications, camera access, or remote help for someone at home, cellular moves from nice-to-have to part of the plan. It still belongs on backup power, or it will fail for the same mundane reason as the modem.
Generators and battery stations are for the outage the small layers cannot cover
Once the outage runs beyond the UPS window, the smart-home question merges into the household power question. Refrigeration, heat, medical equipment, sump pumps, device charging, and repeated network recharging are no longer a 25-watt planning problem. That is battery-station or generator territory.
The safety rules are not decorative. Ready.gov says generators and other gasoline-, propane-, natural gas-, or charcoal-burning devices should never be used inside a home, basement, garage, or camper, and should be kept outside and away from windows; it also recommends carbon monoxide detectors with battery backup on every level of the home. [10]
The manual controls are not a fallback detail
The most fragile part of an outage plan is often the assumption that someone will be able to use the app. A good plan leaves obvious physical paths: lock keys where the right people can reach them, keypad codes that work without the cloud, a garage release that can be accessed safely, and thermostat controls that can be operated at the wall.
Ready.gov includes manual-release awareness in its outage guidance, and WRAL’s smart-home outage advice specifically calls out practical checks such as knowing the garage door release cord, keeping physical lock keys available, and confirming thermostat local controls. [10][11]
This is also where smart-device shopping gets less glamorous. A garage door opener with an accessible manual release is better outage equipment than a cloud-only status tile. A thermostat with a usable faceplate matters more than a pretty app screen. A lock with a physical key may feel old-fashioned until the bridge is down and someone needs to get in.
How to choose devices before the outage
The purchase-time filter is harsher than a feature comparison chart. For every device that would matter during a long outage, ask four questions:
- Can it perform its essential job without the internet?
- If it needs a hub, controller, bridge, router, or Thread border router, is that equipment on backup power?
- If it uses a battery, what happens when the battery is low and the app is unavailable?
- If the smart path fails, can a person still operate the lock, garage door, thermostat, alarm, or light locally?
For sensors, prefer battery-powered Zigbee, Z-Wave, Thread, or other locally integrated devices when the event matters inside the house. For locks, prefer models with local entry methods first and remote features second. For sirens and alarms, make sure the trigger path is local if you expect them to work when the WAN is down. For Wi-Fi devices, separate local-API models from cloud-dependent ones; the radio is the same, but the failure mode is not.
Cameras deserve special skepticism. Many need substantial power, storage, cloud access, or vendor services to be useful. A camera that records locally to a powered NVR is a different outage device from a camera that mainly sends clips to the cloud. If camera coverage is part of the emergency plan, include its switch, recorder, storage, and viewing path in the backup load instead of treating the camera as a standalone device.
For recovery after the power returns, do not build the whole strategy around unplugging devices in a perfect sequence from memory. Layered troubleshooting belongs in a recovery guide, such as Smart devices won’t reconnect after outage? Fix the layer and How to Restore Your Smart Home After a Storm Power Outage. The preparedness decision is made earlier, when you decide which devices are local enough to be worth backing up.
What the finished preparedness stack looks like
A defensible extended-outage smart home is usually smaller than a normal smart home. It has battery sensors that still report, locks that still open, sirens that can still sound, and a hub that can still make local decisions. It puts the modem, router, switch, and hub on a UPS sized from measured or personally tested loads. It may give a low-voltage hub or security board a separate DC battery. It adds cellular failover only when remote access and remote alerts matter. It reserves portable power stations and generators for the duration and household loads the smaller layers cannot cover.
That stack does not promise uninterrupted automation. It gives the house a visible way to degrade: local controls first, backed-up network path second, remote connectivity only where it earns its keep, and manual operation underneath all of it.
References
- Hurricanes in 2024 led to the most hours without power in the United States in 10 years, EIA Today in Energy, Dec. 2025
- Preparing Your Smarthome for Outages, HomeTechHacker
- Does Home Assistant work without an internet connection?, Home Assistant
- Does A Smart Home Work Without The Internet?, Hubitat
- How to Choose the Right UPS for a Smart Home, HomeTechHacker
- The 3 Best Uninterruptible Power Supplies (UPS) of 2026, Wirecutter, 2026
- Backup Battery, Konnected
- How Does Cellular Backup Internet Work?, T-Mobile
- How to choose the best backup internet for power and network failures, Frontier, Dec. 2024
- Power Outages, Ready.gov
- Prepare for outages: Essential tips for smart home power failures, WRAL, Jan. 2026
Known issues with this device / protocol
Spec-version history
For active regressions on this protocol, see Update Watch.
No linked Update Watch entries yet.
