A Smart-Home Hurricane Checklist Is One Question Per Device

A smart home hurricane preparedness checklist for devices starts with the question most storm lists skip: if the grid is down and the internet is gone, what still works?

The official baseline is still the floor. The Red Cross tells households to prepare for living without power, water, gas, phone, and internet, including a 3-day Go-Kit and a 2-week Stay-at-Home Kit.[1] The National Weather Service and Ready.gov supply guidance includes 1 gallon of water per person per day for at least 3 days.[2] None of that is optional because a motion sensor cannot make water potable and a smart lock cannot keep a refrigerator cold.

But a smart home adds another dependency map on top of the normal hurricane plan. In 2024, U.S. electricity customers averaged 11 hours of power interruptions, nearly double the prior-decade average; Hurricanes Beryl, Helene, and Milton accounted for 80% of those interruption hours, and South Carolina averaged nearly 53 hours.[3] For smart-home planning, that turns power loss from an edge case into a design condition.

The useful version of the checklist is not “buy a sensor, buy a camera, buy a battery.” It is one label applied repeatedly: Works offline, Needs cloud, or Needs UPS. Apply it to power, connectivity, hub/controller, radio mesh, and then every device that matters after landfall.

There is real evidence that a local smart home can remain useful during a storm. In a Home Assistant community field report after Helene and Milton, a Florida home continued running “normally without connection,” including scheduled lighting, while Network UPS Tools sent shutdown messages to other devices before power dropped.[4] That is not a controlled study and it is not a guarantee for every house. It is still the kind of proof that matters: a complete local stack, under actual hurricane conditions, doing useful work without the cloud.

The four labels go on layers, not just gadgets

A device does not “work offline” just because it uses Zigbee, Z-Wave, Thread, Wi-Fi, or Matter. It works offline only if the chain under it also survives. A Zigbee leak sensor is local, but the alert may still die if the hub has no power. A Wi-Fi camera may have a battery, but its recording plan may depend on a remote service. A smart lock may still turn by hand, which is useful, while its remote status and automations disappear.

This is why the checklist belongs in compatibility, not shopping. The issue is whether the installed stack remains compatible with outage conditions.

Power: decide what gets minutes, hours, or nothing

Start at the shelf where the modem, router, switch, hub, and radio coordinators live. If that shelf has one outlet strip and no battery, the rest of the smart-home audit is mostly theoretical.

A small UPS is useful, but it is not a storm-power plan. PowerOutage.us estimates that a 600–1,000VA UPS can keep a modem and router drawing about 20W online for roughly 90 minutes to 3 hours.[5] CNET’s practical warning is blunter: most consumer UPS units are built for short grace periods, often around 15 minutes, not multi-hour outages.[6]

That does not make a UPS pointless. It makes its job specific. It can bridge short outages, prevent a dirty shutdown, keep a LAN alive while the ISP still has service, and give a hub time to shut down cleanly. It should not be counted on to carry a house through a multi-day outage unless it is part of a larger, tested power plan.

• Label the modem: Needs UPS if you expect internet or ISP voice service to last through short outages. Does not matter offline if your local automations do not need WAN and the ISP is likely to fail anyway.
• Label the router and main switch: Needs UPS. Local dashboards, Wi-Fi devices, Matter-over-Wi-Fi devices, and many hub integrations depend on the LAN even when the cloud is gone.
• Label the hub, coordinator, or controller: Needs UPS if it runs local automations, routes Zigbee/Z-Wave/Thread traffic, or coordinates shutdown behavior.
• Label nonessential smart loads: No backup unless they protect safety, access, water, or recovery.

If you already maintain a more detailed outage kit, keep this audit separate from buying decisions. NestGrid’s smart-home power outage gear guide is the place to compare backup categories. Here the point is simpler: which existing dependencies go dark first?

Connectivity: internet loss and LAN loss are different failures

A surprising number of storm checklists treat “internet down” as the end of the smart home. That is true for cloud-only systems. It is not true for every local system. The useful distinction is WAN versus LAN.

The router is not just an internet appliance in a smart home. It is the address book and road system for local devices. If it loses power, a Home Assistant dashboard on a phone may not reach the server, a Wi-Fi plug may not accept local control, and a Matter-over-Wi-Fi device may be harder to recover even after power returns.

For a hurricane audit, write two separate lines for connectivity:

• Internet: Needs ISP and modem power. Assume it may disappear.
• Local network: Needs router/switch/Wi-Fi power. Preserve it if you want local control to mean anything.

This separation also changes how you test. Do not wait for a real outage to learn whether your app was reaching a hub locally or through a vendor relay. Pull the WAN cable or disable the modem, leave the router running, and see what still answers.

Hub and controller: local logic only counts if the box stays alive

Home Assistant, Hubitat, SmartThings, Apple Home, and other controller setups can look similar in a dashboard while having very different outage behavior. For hurricane purposes, the question is not which ecosystem is nicer on a normal Tuesday. It is whether the rule engine, device state, and radio paths still function without the internet.

Hubitat’s own offline-capability position is that a smart home can keep running without internet when automation is processed locally, while cloud integrations and remote access remain dependent on outside services.[7] Hubitat community users also describe practical backup patterns: hubs on 12V battery backups, surge protection, and attention to Zigbee router devices that need backup power if they are expected to keep the mesh healthy.[8]

That last point is easy to miss. A battery-powered Zigbee contact sensor can be awake, healthy, and useless if the powered repeaters it normally routes through have dropped. If the coordinator is on UPS but every nearby plug-in Zigbee router is dead, the edge of the mesh may vanish. Backing up the hub without considering radio topology is a half audit.

For Home Assistant owners, the field report from Helene and Milton is the model worth copying at the level of architecture, not exact hardware: local automations, local radios, UPS signaling, and graceful shutdown behavior.[4] If you already use Home Assistant, NestGrid’s grid-emergency auto-shedding blueprint is the adjacent pattern: it assumes the Home Assistant box, router, modem, and coordinator are on backup power, because the automation cannot save anything after its own nervous system is off.

Hub audit lines to write down

• Controller hardware: Needs UPS if it runs automations or stores device state.
• Zigbee coordinator, Z-Wave stick, Thread border router: Needs UPS if separate from the controller.
• Critical mesh repeaters: Needs UPS or replacement path if battery sensors rely on them.
• Cloud integrations inside the hub: Needs cloud even if the hub itself is local.
• Shutdown and restart order: Needs drill because the worst failures often appear after power comes back.

Devices: label the useful function, not the product category

A leak sensor, camera, thermostat, lock, and smart bulb cannot be sorted by category alone. The audit has to ask what you need from the device during and after the outage.

For each device, write the useful function in plain language first: “turn on hallway light at dusk,” “warn if water is under the washer,” “unlock side door with keypad,” “record driveway motion locally,” “keep HVAC schedule,” or “show freezer temperature.” Then label the dependencies.

The category that deserves the most suspicion is the one with a great app and no local fallback. There is no survey-grade number in the available material that says what percentage of smart-home products depend on the cloud, so the audit should not pretend there is one. The safe method is to test the installed device, not the marketing copy.

Hubitat’s offline framing and offline-smart-home build guides both support the narrower conclusion: local processing and local protocols improve outage resilience, while remote access, cloud automations, and cloud-only device features remain outside the house.[7][9] That does not make every local device reliable under storm conditions. It means the failure moves from “vendor server unreachable” to power, routing, firmware, and recovery behavior you can actually test.

If you want a companion device-by-device worksheet, NestGrid’s smart-home power outage behavior guide uses the same local-versus-cloud distinction outside the hurricane context.

Do not overread the Matter problem, but do test it

Matter deserves a separate note because storm outages create exactly the kind of power-cycle and reconnect conditions that expose weak recovery behavior. User reports across Home Assistant and Hubitat environments document Matter devices showing as “unavailable” after a power outage or power cycle; the Home Assistant GitHub issue is closed and user-reported, so it should be treated as a documented failure mode, not a universal guarantee.[10]

The practical conclusion is modest: if a Matter-over-Wi-Fi switch, plug, lock, or sensor is important during storm recovery, test it after a router reboot, hub reboot, and device power cycle. If it comes back only after manual intervention, the label is not “Works offline.” It is “Needs drill,” and possibly “replace before hurricane season” if the function matters enough.

For recovery order after a utility outage, the related smart-home reconnect guide is useful because it separates Zigbee, Thread, Matter, hub, and router restarts instead of treating “reboot everything” as a plan.

Build the checklist as a status table

The checklist should be boring enough to use when wind is already in the forecast. A spreadsheet, note, or printed sheet is better than a perfect dashboard that requires the internet to open.

Those rows are hypothetical examples, not model recommendations. Your real table should use installed device names, room locations, batteries, and the exact hub or service each device depends on.

Run the offline drill before the forecast matters

A hurricane drill for a smart home is not dramatic. It is a controlled failure while the weather is still calm.

1. Charge or verify the UPS units that support the router, switch, hub, coordinator, and any critical mesh repeaters.
2. Save a local copy of the checklist somewhere accessible without cloud storage.
3. Unplug the modem’s WAN connection or otherwise remove internet while leaving the router and LAN powered.
4. Open the local dashboard, not the vendor relay, and record what still loads.
5. Trigger each important device: leak sensor, lock, light routine, camera recording, thermostat schedule, siren, shutoff valve, freezer sensor, or garage access.
6. Power-cycle selected devices that are likely to lose power during a real outage, especially Wi-Fi and Matter devices.
7. Reboot the hub and router in the order you would use after an outage, then note what reconnects without help.
8. Change the label on every failed row: Needs cloud, Needs UPS, Needs manual reset, or Replace.

The drill should produce decisions, not vibes. If the leak sensor only sends a push notification through a cloud service, it is not a local storm alert. If the lock works by keypad but not by remote app, its access function may be fine while its monitoring function is not. If the camera records to an SD card but the app cannot reach it, local evidence may survive even though remote viewing does not. Label the function that matters.

When something fails, do not fix everything at once. First decide whether the failure belongs to power, LAN, hub, mesh, cloud, or the device. The diagnostic structure is the same one used in ISP-versus-router-versus-hub troubleshooting; NestGrid’s Spectrum outage smart-home check is a useful template for keeping those layers separate.

What deserves backup or replacement

After the drill, the upgrade list usually gets shorter. A device deserves backup power or replacement when it protects one of four things: access, water damage prevention, basic lighting, or recovery information. A decorative lamp, cloud scene, or convenience speaker can fail without becoming a preparedness problem.

• Back up the router if local dashboards, Wi-Fi devices, or Matter-over-Wi-Fi devices are part of the storm plan.
• Back up the hub and radio coordinator if Zigbee, Z-Wave, or Thread devices provide alerts, locks, lighting, or shutoff actions.
• Back up only the mesh repeaters that critical battery devices actually use, or move the critical devices closer to a backed-up route.
• Replace cloud-only devices when the useful storm function has no local fallback.
• Keep manual controls working even when the smart layer is excellent.

The finished hurricane checklist is a dependency map with labels. Power: Needs UPS. Connectivity: Works offline only if the LAN stays up. Hub: Works offline only if local logic and radios stay powered. Device: Works offline, Needs cloud, or Needs UPS based on the function you tested. Stop there, with the drill results written down, before the next checklist turns preparedness back into shopping.

References

1. Hurricane Safety, Red Cross.
2. Hurricane Preparedness - Supplies, National Weather Service.
3. U.S. electricity customers averaged 11 hours of power interruptions in 2024, U.S. Energy Information Administration, December 2025.
4. Hurricane Prep Improvement Ideas, Home Assistant Community, October 2024.
5. Best Battery Backup UPS for Router, PowerOutage.us.
6. Power Outage? Here's How to Keep Your Internet on Like a Pro, CNET.
7. Does a Smart Home Work Without the Internet, Hubitat.
8. What are your battery backup strategies for Hubitat and network?, Hubitat Community.
9. Building an offline smart home, Android Authority.
10. Matter devices showing unavailable after a power outage or power cycle, GitHub.