The Smart Home Storm Preparedness Checklist

Start with the chain that everything else waits on

A hub-based smart home does not get through severe weather because every bulb, sensor, lock, camera, and speaker has its own backup plan. It gets through because the small infrastructure chain underneath it stays alive long enough, or comes back in the right order: power, network, hub.

That is the practical center of a smart home storm preparedness checklist. Keep the modem or fiber terminal, router, smart-home hub, and any required switch powered. Know which automations run locally when the internet is gone. After the outage, bring layers back in order before deciding anything is broken.

The risk is not theoretical. The U.S. Energy Information Administration reported that customers averaged 11 hours of electric interruptions in 2024, nearly twice the prior-decade average, with major events accounting for 80% of those hours; when major events are excluded, routine interruptions are closer to about two hours per year [1]. The Census Bureau, using the 2023 American Housing Survey, reported that about 1 in 4 U.S. households, or 33.9 million households, had at least one complete outage in the previous 12 months, and 70% of those households had at least one outage lasting six hours or longer [2].

The phase checklist

Use the status labels plainly. Confirmed means the item is supported by documented device behavior, basic network topology, or cited guidance as of Aug. 25, 2026. Workaround means it is a reproducible operating practice, but the exact controls vary by device or app. Investigating means you should test your own setup before counting on it during a storm.

Before the storm: build the minimum viable stack

The minimum viable stack is the equipment that lets the smart home keep its brain and local network alive. In most hub-based homes, that means:

• Modem or fiber ONT
• Router or gateway
• Smart-home hub, such as a Home Assistant host, Hubitat hub, SmartThings hub, or similar controller
• The one switch needed to connect those devices, if they are not all wired directly
• One mesh node only if the hub or critical devices truly depend on it

Everything else has to earn a place on backup power. A camera recorder, NAS, PoE switch, second mesh node, display panel, or voice speaker may be useful, but each one shortens runtime and adds another boot dependency.

Size the UPS around watts, not vibes

The useful discovery is that the core stack is usually small. HomeTechHacker’s smart-home UPS guidance puts typical draw around 8–12W for a modem, 10–15W for a router, 3–6W for a hub, 10–25W for a switch, 10–30W for an NVR, and 20–60W for a NAS [3]. That makes the modem-router-hub chain a different problem from backing up an entire office.

HomeTechHacker estimates that an 850–1000VA UPS can keep a modem, router, and hub online for roughly 45–120 minutes, with a 20–30% headroom rule for sizing [3]. That range can cover many routine interruptions, but it is not a promise against a six-hour outage or a major-event restoration window. If you need deeper runtime planning, the UPS and power-station math belongs in Keep Smart Home Devices On With a UPS or Power Station, where the tradeoff is runtime, recharge behavior, and load size rather than another smart-home setting.

Do one unglamorous test before storm season: unplug the UPS from the wall while the modem, router, and hub are connected, then watch what stays online. If the hub survives but the router goes down because it was plugged into the wall, the automation system did not pass. If the router survives but the hub’s Ethernet switch dies, it did not pass either.

PoE cameras need the whole camera chain

PoE cameras are where people accidentally lie to themselves. Backing up only the router does not keep PoE cameras recording. The PoE switch must stay powered, the NVR must stay powered if recording is local, and the network path between camera, recorder, and router must survive. Installer guidance from ththeater makes the same practical point: the router alone is not the camera system [4].

That does not mean every camera belongs on the UPS. It means you should decide deliberately. If the storm plan is “keep the front door and driveway recording for the first hour,” then the PoE switch and NVR are part of that load calculation. If the plan is “keep local lighting and alerts alive,” the camera gear may be the first optional load removed.

Set power-on behavior before the hallway becomes a surprise

Many smart bulbs and plugs can return to ON after power is restored unless their power-on behavior is configured, and How-To Geek flags the obvious safety problem when connected loads are heaters, appliances, or anything that should not resume unattended [5]. Treat this as pre-storm work, not post-outage cleanup.

• For bulbs in bedrooms and hallways, choose the least disruptive restore state available: previous state, OFF, or a low brightness level if the product supports it.
• For smart plugs, avoid connecting space heaters, cooking appliances, pumps, or motor loads unless the device and use case are explicitly rated for it.
• For automations that run at sunrise, sunset, or on motion, check whether they will fire immediately after the hub reboots and sees stale device states.
• For locks and garage controls, confirm battery condition and manual operation before the storm, not during the outage.

Mark what is local and what is cloud-dependent

Zigbee and Z-Wave devices are often more resilient during an internet outage because the radio network and automations can run through a local hub, as long as that hub and the required local network equipment stay powered. Hubitat’s own internet-outage guidance makes this local-control distinction, while HomeTechHacker’s outage guidance makes the same practical split between local automations and cloud-dependent devices [6][7].

Protocol is not destiny. A Zigbee sensor attached to a hub automation that calls a cloud weather service is no longer fully local. A Wi-Fi device with a local API may behave better than a cloud-only Wi-Fi plug. A voice assistant may hear you perfectly and still be useless if the service behind it is unreachable. The test that matters is not the logo on the box; it is whether the action still runs when the WAN cable is unplugged and the hub remains online.

Keep safety boundaries outside the automation system

A smart-home checklist should not dilute basic power safety. Ready.gov says generators should be used outdoors at least 20 feet away from windows, doors, and attached garages, and both Ready.gov and the Red Cross emphasize working carbon monoxide detectors when using alternate power [8][9]. A smart plug, automation rule, or garage sensor does not make indoor generator use safer.

Do not put a sump pump on a standard computer UPS. Anker’s home-backup guidance warns that motor startup current can overload a typical UPS [10]. If water control is part of the storm plan, treat it as a separate power-design problem, not as one more load on the network UPS.

During the storm: protect runtime and avoid “repairs” caused by impatience

Once the storm is active, the job is mostly restraint. Do not use the infrastructure UPS as a convenience strip. Every phone charger, lamp, display, and speaker plugged into it reduces the time the modem-router-hub chain can stay up.

If the internet connection drops but local power remains, leave the hub alone unless you have a specific reason to shut it down cleanly. Local automations may still be running. Cloud integrations may be unavailable because the WAN is unavailable, not because the integration is damaged. Voice assistants and vendor apps are especially good at making an internet outage look like a device outage.

For Home Assistant households, Network UPS Tools integration can expose UPS state to Home Assistant, which makes it possible to automate load-shedding or notifications from UPS status rather than guessing from lights flickering [11]. That is optional, and it should be tested well before a warning is issued. If you want to go deeper on reducing load and recovering without waking every device at once, use the blackout-oriented patterns in Survival Mode Automations for Heat Wave Blackouts as a starting point.

If the UPS is close to exhaustion, shut down optional equipment first: NVR, NAS, extra access points, dashboards, and nonessential switches. Keep the modem, router, and hub together as long as the plan is to preserve local control. If the outage is going to outlast the UPS anyway, a clean shutdown is better than a corrupted database on a hub host or NAS.

After the storm: restart layers, not random devices

The hallway scene after power returns is familiar: half the bulbs are on, a dashboard says the hub is online, several cloud devices are missing, and someone suggests factory resets. This is where most avoidable damage happens. The first question is not “which device broke?” It is “which layer came back before the layer it depends on?”

Use this order: modem or fiber terminal first, router next, mesh access points after the router is stable, hub after the network exists, and endpoint devices last. HomeTechHacker and ththeater both describe this layered recovery logic for smart homes after an outage [7][4].

1. Power the modem or fiber ONT. Wait until it shows its normal service or link state.
2. Power the router or gateway. Wait for LAN and Wi-Fi to be available. If the WAN is still down, do not stop here; local control may still be useful.
3. Power mesh access points. Wait for them to join the mesh instead of forcing clients to roam while the mesh is still forming.
4. Power the smart-home hub. Wait for integrations, radios, and local databases to finish loading.
5. Then check endpoint devices: bulbs, plugs, locks, sensors, cameras, thermostats, and dashboards.

A hub that boots before the router may not get the network services it expects. A cloud integration that starts before internet service returns may mark devices unavailable. A mesh client may cling to a weak node while the nearest access point is still booting. None of those states prove the device is dead.

Let device state settle before touching pairing buttons

After the core stack is back, walk the system in layers. Check whether the router sees the hub. Check whether the hub sees its radios or integrations. Then check whether devices are actually offline or merely in the wrong state.

• For bulbs: confirm whether they returned ON because of power-on behavior, not because an automation fired.
• For smart plugs: verify the attached load before turning anything back on remotely.
• For battery sensors: allow time for the next wake interval before declaring them missing.
• For cameras: check PoE switch power, NVR status, and network path before resetting cameras individually.
• For voice assistants: wait for WAN service and vendor services before treating voice-control failure as a local smart-home failure.

Factory resets are last-resort operations. They erase working associations, create duplicate devices, break automations, and turn a recoverable state problem into a rebuild. If a device worked before the outage, power is stable, the network is stable, the hub is fully booted, and only then the device remains unreachable after normal retry windows, reset may belong on the table. Not before.

What should still work, and what probably will not

With utility power out and no backup power, most mains-powered smart-home equipment is simply off. Battery sensors may still sense, locks may still lock, and thermostats may run on battery depending on the model, but the automation system cannot coordinate much if the hub and network are down.

With utility power out but the modem-router-hub chain on UPS, local automations have a chance. A motion sensor can still trigger a locally controlled light if that light has power and the hub executes the rule locally. A leak sensor can still alert the hub locally, but push notifications may fail if the internet is gone. A thermostat automation may still run if the thermostat, HVAC equipment, hub, and local path all remain available.

With power restored but internet still down, the house may feel half-alive. Local dashboards may work. Local Zigbee or Z-Wave automations may work. Cloud-only Wi-Fi devices, vendor apps, and voice assistants may look broken until WAN service returns. That split is annoying, but it is useful: it tells you where to wait instead of where to reset.

With power and internet restored but devices still missing, return to the order: modem or ONT, router, mesh, hub, devices. If that chain is healthy, then troubleshoot the specific device. The storm did not make factory reset the first step.

References

1. Hurricanes in 2024 led to the most hours without power in the United States in 10 years, U.S. Energy Information Administration, Dec. 2025
2. About 1 in 4 Households Experienced a Power Outage in the Span of a Year, U.S. Census Bureau, Oct. 2024
3. How to Choose the Right UPS for a Smart Home, HomeTechHacker
4. What Happens to a Smart Home During a Power Outage?, ththeater
5. What Happens to Your Smarthome When the Power Goes Out?, How-To Geek
6. Does A Smart Home Work Without The Internet?, Hubitat
7. Preparing Your Smarthome for Outages, HomeTechHacker
8. Power Outages, Ready.gov
9. Power Outage Safety, American Red Cross
10. Essential UPS Home Applications, Anker SOLIX
11. Network UPS Tools (NUT), Home Assistant