Security Camera Offline, Not Recording Motion Events Fix

Search Intent Opening

If your security camera is offline in the app, misses motion events it should record, or requires daily unplugging to restore function, the failure is in its power, Wi-Fi, or motion detection subsystem. Follow this procedure to isolate the fault.

Search Query Coverage Block

Users commonly describe this as:

security camera offline won’t reconnect
camera not recording motion events
security camera goes offline every few hours
camera misses events when it should record
camera showing offline in app but powered on
security camera needs daily reboot
camera not detecting motion at night
ir lights on but camera offline
camera disconnects from wifi randomly
security camera not sending alerts
camera works then goes offline permanently
motion detection turned off by itself
camera offline after firmware update
camera has red light but app says offline
security camera recorded nothing during break in

Observed Failure Patterns

Offline with Steady IR LEDs: Camera’s infrared LEDs are illuminated (visible red glow in dark), but the app shows “Offline” or “Cannot Connect.” Indicates a Wi-Fi module crash where the low-power IR circuit remains active but the main CPU/radio is not responding. Does NOT indicate a network outage.
Missed Event with Log Gap: Reviewing the timeline shows large gaps (hours) with no recorded events during times of known activity. The camera may still be “Online” in the app. Indicates a failed PIR (passive infrared) sensor, corrupted SD card, or a firmware bug that halts recording. Does NOT indicate a sensitivity setting issue.
Cyclic Reboot/Offline: Camera works for 8-48 hours, then goes offline. It may or may not auto-recover after 10-30 minutes. Pattern repeats. Indicates thermal throttling, a failing power supply, or a memory leak in the firmware. Does NOT indicate a router issue if other devices are stable.
Motion Detection Auto-Disabled: The motion detection toggle in the app is found switched OFF without user action. Re-enabling it may hold for hours or days before it disables again. Indicates corrupted configuration memory or a firmware bug that resets the setting on crash.

Most Common Root Causes (Ranked by Field Frequency)

Failing Wi-Fi Module: The surface-mount Wi-Fi radio chip or its power regulator overheats or fails. The camera loses association with the router and cannot rejoin. Triggered by continuous high bitrate streaming or heat. Confirmed by the camera having strong signal in router admin when working, then disappearing entirely when failed. Disproved if the camera regains connection after a simple router reboot (points to router issue).
Under-Specified Power Supply: The included wall adapter cannot sustain the camera’s current draw, especially when IR LEDs are on and streaming. Voltage sags cause the CPU to reset. Triggered by cold temperatures (increased IR current) or long cable runs. Confirmed by measuring voltage at the camera’s barrel connector while streaming; a reading below 4.8V (for a 5V system) indicates insufficient power. Disproved if voltage remains stable above 5.1V during failure.
Failed PIR Motion Sensor: The pyroelectric sensor that detects heat movement dies or becomes desensitized. The camera may record only when it receives a “digital” alert from another sensor (like sound) or not at all. Triggered by moisture ingress or component failure. Confirmed by creating obvious heat motion (walking close) in a quiet environment; if no detection or IR kick, the PIR is likely dead. Disproved if the IR LEDs turn on in response to motion (shows the sensor works).
Corrupted MicroSD Card or Storage Controller: The card develops bad sectors or the camera’s internal memory controller fails, halting all recording even though the camera appears online. Triggered by frequent writes or power loss during write. Confirmed by removing the SD card and testing it in a computer with H2testw or F3, or by trying a new, high-endurance card. Disproved if the camera also fails to record to cloud when subscription is active.

Rapid Triage Checklist (2-Minute Tests)

IR Sensor Test: At night, cover the camera lens with your hand for 5 seconds, then remove. The IR LEDs should turn OFF when covered (no reflection needed), then turn back ON when uncovered. If they stay on or off regardless, the light sensor or IR control circuit is faulty.
Power Supply Test: With the camera plugged in and streaming, use a multimeter to measure DC voltage at the end of the barrel connector (tips to inner/outer). It must read within 0.2V of the adapter’s rated output (e.g., 5.0V – 5.2V for a 5V adapter).
Local Ping Test: Find the camera’s IP address in your router admin. Open command prompt, run ping [camera IP] -t. Let it run. During an “offline” event, if pings time out (100% loss), the camera’s network stack is down. If pings continue, the problem is with the cloud/app handshake.
Sound Trigger Test: If the camera has audio, clap loudly near it while watching the app’s live view. If the sound meter reacts but no motion event is created, the PIR is dead. If no sound reaction, the main CPU is locked up.

Step-by-Step Diagnostic Procedure

Step 1: Establish Network Connectivity State.

Action: Perform Local Ping Test while the app shows “Offline.”
Normal: Camera responds to pings. This indicates a cloud/app authentication issue. Restart the app, re-login.
Failure A (No ping response, IR lights on):* Wi-Fi module or main CPU fault. Proceed to Step 3.
Failure B (No ping response, IR lights off):* Power fault. Proceed to Step 2.

Step 2: Diagnose Power.

Action: Perform Power Supply Test. Also, try a different, known-good 5V/2A USB adapter with a barrel connector tip.
Normal: Voltage stable >5.0V under load. Camera boots with new adapter.
Failure A (Low voltage with original adapter):* Faulty power supply. Replace.
Failure B (Good voltage, camera still dead):* Faulty power regulation on camera’s main board. Board replacement required.

Step 3: Isolate Wi-Fi Module vs. Full Crash.

Action: Observe indicator light. Then, press the reset button with a paperclip for 10 seconds.
Normal: LED flashes rapidly, then camera reboots and rejoins network.
Failure A (No LED response to reset):* Full board crash. Main CPU or power system dead.
Failure B (LED responds but never rejoins Wi-Fi):* Likely failing Wi-Fi module. If possible, try setting up on a different 2.4GHz network as a test.

Step 4: Diagnose Motion Detection Failure.

Action: Ensure camera is online. Perform IR Sensor Test and Sound Trigger Test.
Normal: IR toggles correctly. Sound triggers event or shows on meter.
Failure A (IR doesn’t toggle, no motion):* Faulty PIR sensor or its conditioning circuit. Board replacement.
Failure B (IR toggles, no motion events):* Firmware or configuration fault. Factory reset. If problem returns, firmware is bugged.

Physical Layer Inspection

Barrel Connector: Check for a loose center pin, cracked solder inside the camera’s DC jack.
Main Board: If opened, look for:
- Bulging Capacitors: Near the power input and CPU.
- Water Damage: White or green corrosion, especially around the reset button, lens, or SD card slot.
- Burnt Wi-Fi Module: The small, square chip with silver shielding may be discolored.
PIR Sensor: A small, rectangular metal can with a plastic window. Ensure the window is clean and not cracked.

Electrical / Signal Verification

Power Rail Ripple: Use an oscilloscope to check the 3.3V rail on the main board. Excessive noise (>100mV) can cause CPU lock-ups.
PIR Sensor Output: With an oscilloscope, probe the output pin of the PIR sensor (refer to datasheet). Walking in front of it should produce a pulsed signal. A flat line indicates a dead sensor.

Reset and Recovery Behavior Mapping

Normal Reset: LED flashes amber rapidly during reset, then turns solid blue/white for setup mode.
Failed Reset (No LED): No power or dead board.
Failed Reset (LED flashes endlessly): Firmware corruption; stuck in boot loop.

False Fixes That Do Not Work

“Adjusting motion sensitivity zones”: If the PIR sensor is dead, no setting will make it detect heat-based motion.
“Updating your router’s firmware”: While generally good, it does not fix a failing Wi-Fi module inside the camera.
“Using a Wi-Fi extender”: If the camera’s own radio is failing, providing a stronger signal won’t help.

Confirmed Fix Scenarios

Symptom: Offline, IR lights on. Cause: Failing Wi-Fi module. Fix: Main board replacement. Verification: Camera maintains connection for 30+ days.
Symptom: Misses all motion, IR works. Cause: Dead PIR sensor. Fix: Main board replacement. Verification: Camera logs events for walking tests day and night.
Symptom: Goes offline every 12 hours. Cause: Under-powered adapter causing brownouts. Fix: Replace power supply with higher amperage (2A+) unit. Verification: Voltage stable at camera jack under load, uptime extends to weeks.
Symptom: Motion detection turns itself off. Cause: Corrupted configuration NVRAM. Fix: Factory reset. If it recurs, board replacement (faulty memory). Verification: Setting remains enabled.

Post-Fix Verification Checklist

Uptime: Monitor app status for 72 hours. Camera must remain online.
Event Logging: Conduct 5 motion tests per day (walk through view) for 3 days. All must appear in the event timeline.
Night Vision: Confirm IR LEDs activate in darkness and provide a clear, non-foggy image.
Alert Speed: From motion to phone notification should be under 10 seconds.

Escalation Threshold

Board Replacement Required: If diagnostics point to a failed Wi-Fi module, dead PIR sensor, or corrupted main CPU/flash memory. These are integrated on the main PCB.
Module Replacement Required: Not applicable in consumer all-in-one cameras.
Factory Repair Required: Not offered. Manufacturer provides replacement under warranty.
Unit Replacement Justified: If the camera is out of warranty and requires a main board replacement, or exhibits multiple simultaneous failure patterns (e.g., offline + no motion + corrupted video). The cost and effort exceed the value of a new unit.