Battery backup is a chain, not a single feature. A security hub may stay on while the modem, router, camera, PoE switch, smart lock bridge, or monitoring path fails. Compare each system by the security jobs it preserves during a real outage: detection, local alarm, arming, communications, recording, access, and recovery.
Outage priority table
| Layer | Minimum useful behavior | What to verify |
|---|---|---|
| Alarm hub or panel | Processes sensors, arming, entry delay, and siren locally | Rated runtime, battery age, replacement process, low-battery alert |
| Door, window, and motion sensors | Continue reporting to the hub | Battery type, supervision, missing-device warning, replacement schedule |
| Communications | Sends alarm events when home internet is unavailable | Cellular or other backup path, plan requirement, signal, failover timing |
| Router and modem | Keeps app, cloud, and Wi-Fi devices online for a planned period | Combined watt draw, UPS capacity, ISP outage behavior, restart order |
| Cameras and storage | Records priority views or reports a clear failure | Camera power, recorder/PoE power, local versus cloud path, retention |
| Locks and access | Authorized people can enter without cloud or phone service | Physical key, keypad, local code, battery warning, bridge dependency |
1. Start with the alarm layer
The first job is keeping entry detection, local arming, entry delay, and a siren available. Ask whether these functions work when AC power and internet are both absent. A long camera runtime does not compensate for a hub that cannot process a door sensor or sound an alarm.
2. Separate battery backup from cellular backup
A battery keeps equipment powered. Cellular backup provides an off-site communication path when the home internet fails. They solve different problems. Confirm which device contains the cellular radio, whether a paid plan is required, what events are sent, how quickly failover occurs, and what happens where signal is weak.
3. Inventory every dependency
Draw the path from a door opening to the final response: sensor, hub, siren, router, modem, cellular radio, app, monitoring center, camera, recorder, and responder. Mark which parts use mains power, replaceable batteries, rechargeable batteries, PoE, USB, a UPS, or provider backup. Use the system documentation checklist to keep models, batteries, accounts, and recovery steps together without exposing secrets.
4. Size a UPS for the jobs that matter
Measure the actual combined draw of the modem, router, alarm bridge, recorder, PoE switch, and any priority camera equipment. Compare it with the UPS manufacturer’s runtime curve at that load; do not rely only on the large VA number printed on the box. Leave margin for battery aging and startup loads. Avoid placing devices on battery outlets when they do not support the security response.
5. Set realistic camera expectations
Many wired cameras stop when their power supply, PoE switch, recorder, or network loses power. Battery cameras may wake late, record short clips, or depend on internet and cloud services. Test the exact recording path. Decide which one or two views need backup rather than trying to preserve every convenience camera.
6. Protect access during an outage
Smart locks should have a tested physical key, keypad, local credential, emergency power method, or another manufacturer-approved fallback. Confirm whether codes work without the bridge, internet, phone, or Apple/Google/Alexa service. The smart-lock battery and outage checklist covers access recovery in more detail.
7. Run a controlled outage test
- Notify monitoring and use the provider’s approved test mode.
- Record the battery age, charge state, signal, device status, and time.
- Disconnect home internet and verify local alarms, backup communications, and app status.
- Disconnect AC power and test priority doors, keypad, siren, lock fallback, cameras, and recording.
- Leave the system on backup for a planned interval and watch warnings.
- Restore power and internet separately; confirm timestamps, alerts, device recovery, and charging.
Never create a dangerous electrical condition or bypass life-safety instructions. Use an electrician or qualified installer where required.
8. Check the system without Wi-Fi
“Works without Wi-Fi” can mean local sensors and siren continue, not that remote control, video, or monitoring remains available. Read the security system without Wi-Fi guide and test each required function rather than accepting a general label.
9. Plan battery maintenance
- Record installation dates and manufacturer replacement guidance.
- Replace weak sensor batteries before storm, wildfire, hurricane, or winter outage seasons.
- Inspect swelling, heat, corrosion, damage, and charger faults safely.
- Re-test after firmware, router, plan, panel, camera, or monitoring changes.
- Keep compatible spares without stockpiling old batteries indefinitely.
10. Compare three-year resilience cost
Include the hub, sensors, siren, cellular-capable equipment, required plan, UPS units, replacement batteries, camera power, recorder storage, PoE hardware, installation, maintenance, and test time. A lower monthly price can be poor value if the required backup path is missing; a higher plan can be wasteful if the household has not defined who responds.
Where Abode fits
For Abode, verify the exact hub, sensor, plan, cellular, battery, camera, and monitoring behavior for the configuration being purchased. Start with the Abode Smart Security Kit and compare current Abode plans. Then test the chosen setup with internet down, power down, and both restored.
FAQ
How long should a home security battery last in an outage?
There is no universal target. Choose a runtime from local outage history and the household response plan, then verify the exact hub, battery age, load, and provider specification with a controlled test.
Does cellular backup keep cameras online?
Not necessarily. Cellular backup may carry alarm events while cameras still require power, broadband, Wi-Fi, storage, or a separate service path.
Should I put my router on a UPS?
Often yes when app, cloud, Wi-Fi camera, or remote-control continuity matters. Confirm the modem, router, ISP, and upstream network can still operate during the outage.
What is the most important outage test?
Verify a priority door sensor triggers the local alarm and the intended response path when both AC power and home internet are unavailable.
Build a battery-backup operating plan, not just a runtime claim
A battery label does not tell you whether a security system will keep doing its most important jobs during a real outage. The useful question is narrower: which security actions must continue, which devices support those actions, who owns each dependency, and how will the household prove the full path before an emergency?
Start with outcomes. A working plan should preserve entry detection, a local alarm, a way to reach a responder, safe door access, and enough evidence to understand what happened. Live camera viewing, cloud clips, voice assistants, and remote automations may fail earlier because they depend on the router, internet service, vendor cloud, or a phone path. Write those differences down so nobody treats a powered device as a working security workflow.
Assign one owner to every power dependency
List the hub, keypad, siren, router, modem or fiber terminal, camera bases, PoE switch, recorder, access points, smart locks, and any cellular or radio accessory. Record the power source, battery type, last replacement date, expected degraded behavior, and named owner. Use the home-security equipment inventory to keep model and location data with the runtime record.
A device without an owner is usually the first one missed. The internet provider may replace a gateway, a camera may move to another outlet, or a new access point may be added without UPS power. After every equipment change, update the dependency map and repeat the relevant test instead of assuming the old result still applies.
Set a restore order before the lights go out
- Life safety and exit: keep doors mechanically operable, preserve smoke and carbon-monoxide equipment according to its own instructions, and do not block egress to protect electronics.
- Alarm core: confirm the hub, entry sensors, local siren, and keypad can complete an arm, trigger, silence, and disarm cycle.
- Communication: test the exact cellular, broadband, or phone notification path included in the current plan.
- Network: restore the modem or fiber terminal, router, required switch, and only the access points needed by security devices.
- Evidence: restore the recorder, camera base, or selected cameras that cover the highest-priority approaches.
- Convenience: reconnect voice control, non-security routines, and optional displays only after the security path is stable.
Post this order near the main UPS or place it in the household runbook. During an outage, a responder should not have to infer whether the recorder, router, or camera base comes first.
Measure the entire chain
Record four times: when utility power failed, when each device changed to backup power, when each security function stopped, and when service recovered. A hub may run longer than the router. The router may run while the upstream internet service is unavailable. A camera may remain powered but stop recording because its base or storage path failed. Functional runtime is the shortest time in the complete chain, not the longest battery result.
Run a separate internet-outage test so a broadband failure is not confused with a power failure. The two events can look similar in an app but require different recovery steps.
Protect the UPS from silent overload
Do not size a UPS from nameplate wattage alone. Connect the intended load, let batteries charge, record the displayed load where available, and test an orderly transfer. Keep high-draw appliances, heaters, printers, and unrelated entertainment equipment off the security UPS. Label every protected outlet and every unprotected look-alike outlet.
If a recorder or PoE switch has a safe shutdown process, document it. A short outage should not create a corrupted recorder or an unknown storage gap. Keep ventilation clear and follow the manufacturer’s placement, charging, and replacement instructions. Swollen, leaking, unusually hot, or damaged batteries are a stop condition, not a reason to attempt one more test.
Decide which cameras stay up first
Prioritize cameras by the decision they support. A front entry, driveway approach, detached-building door, or interior path to the alarm hub may matter more than a low-risk room. Record whether each selected camera needs local power, an access point, a base station, a recorder, cloud access, or a subscription feature. If one missing dependency removes the whole evidence path, the camera is not outage-ready.
For battery cameras, test recording and retrieval under the same settings used day to day. Cold weather, frequent motion, weak wireless signal, live viewing, and spotlight use can change runtime. Do not copy a vendor maximum into the household plan as a guaranteed result.
Keep access independent of the network
Every occupied door needs a tested mechanical or local fallback that authorized residents can use without the router, cloud, or a dead phone. Confirm the door can unlock from inside, the key or approved backup is available, and temporary credentials are removed after contractors or guests leave. Never trade safe egress for longer smart-lock battery life.
Use a maintenance trigger, not a vague annual reminder
Put the battery and UPS checks on the home-security maintenance calendar. Retest after a battery replacement, router change, camera move, monitoring-plan change, firmware update, or extended outage. Use the battery maintenance guide for replacement records and disposal boundaries, and the firmware update checklist when software changes power or recovery behavior.
Run a 60-minute battery-backup acceptance test
- 0–10 minutes: notify the household, put any monitored account in the approved test state, photograph the starting panel and UPS indicators, and verify every exit works.
- 10–20 minutes: remove utility power through the approved test method. Confirm the hub, siren, keypad, router, required network gear, and selected evidence devices transfer without an unsafe condition.
- 20–30 minutes: trigger one entry sensor. Verify the local alarm, app alert, and current monitoring or responder path separately. Record what fails when broadband is unavailable.
- 30–40 minutes: create and retrieve one test clip from each priority camera path. Confirm timestamps, storage destination, and account access.
- 40–50 minutes: unlock and relock the main occupied entry using the normal credential, then prove the mechanical or local fallback. Check that auto-lock behavior does not create an egress problem.
- 50–60 minutes: restore utility power. Confirm devices leave backup mode, network paths recover, cameras resume recording, the alarm returns to its intended state, and the monitoring test state is closed.
Pass only when the written priority functions work and the household can explain the failures. If a device reboots, a notification never arrives, evidence is missing, or an exit cannot be operated normally, record an owner and correction date. Repeat the failed segment after the change.
Launch blockers
- No tested mechanical exit or authorized entry fallback.
- An unlabeled UPS, unknown battery age, damaged battery, or unsafe extension arrangement.
- A monitoring plan or notification path that has not been confirmed against the current account.
- A camera described as protected when its router, base, switch, recorder, or storage path is not backed up.
- No named person responsible for restoring test mode, monitoring status, and normal automations.
