If your phone buzzes every time a car drives past or a tree branch moves, you've already turned off the notifications — which means your security camera is now a security camera you've stopped looking at. That's worse than useless. Here's how to fix it properly instead of just muting the problem.
Why False Alerts Happen
Every camera has a motion sensor that works by one of two methods: pixel difference detection (comparing frames to spot changes) or PIR (passive infrared, detecting body heat movement). Cheap cameras often use pixel difference only, which means anything that changes pixels — shadows, headlights sweeping across a wall, a leaf blowing — triggers a recording.
Better cameras layer PIR on top of pixel detection, and the best ones add AI classification (person vs. vehicle vs. animal vs. "background noise"). Understanding which type you have tells you which fixes will actually help.
Step 1: Draw Accurate Motion Zones
Every decent app lets you define zones where motion detection is active. This is the single highest-impact change you can make. Draw your zones to exclude:
- Public sidewalks and streets (cars and pedestrians constantly trigger)
- Trees and bushes that move in wind
- Areas where shadows sweep across during sunrise/sunset
- Neighbor's driveways, front doors, or commonly-used paths
For a front door camera, your zone should cover the area immediately in front of the door and the walkway leading up to it — not the street, not the tree to the left. I tightened my front camera zone to a 60% smaller area than the default and cut false alerts by about 80% in a single evening.
Be precise. Most apps use a grid or polygon drawing tool. Take 5 minutes to do it right. Most people accept the default zone that covers the entire frame, which is exactly why they get 40 alerts per day.
Step 2: Adjust Sensitivity the Right Way
Sensitivity controls how much pixel change is required to trigger recording. High sensitivity catches everything — including bugs near the lens at night (a huge source of false alerts with IR cameras). Low sensitivity misses slow-moving or distant subjects.
Start at the manufacturer's default, then:
- If you're getting alerts for wind-blown vegetation: reduce sensitivity by 20%
- If you're missing people who walk through slowly: increase by 10-15%
- If night alerts are dominated by flying insects near the lens: reduce night sensitivity separately if the app allows it (Eufy and Reolink both offer day/night sensitivity controls independently)
Don't go below 50% sensitivity on your primary security cameras unless you understand the tradeoff. You're not just eliminating nuisance alerts — you're also raising the threshold for what the camera will actually capture.
Step 3: Enable AI Detection If Your Camera Supports It
If your camera supports person/vehicle/animal classification, turn it on and filter notifications to person-only or person + vehicle. This is the most effective fix for most people.
How it works: The camera still records everything that triggers motion, but it only sends you a notification when the AI classifies the trigger as a person or vehicle. A tree branch blowing triggers recording but no alert. Your cat crossing the yard triggers recording but no notification. A person at your front door triggers both.
Cameras with good AI detection (in my experience):
- Eufy cameras with HomeBase 3: very accurate person detection, decent vehicle detection
- Google Nest: best-in-class, especially with Aware subscription for familiar face detection
- Reolink RLC-810A: person and vehicle detection is good, animal detection occasionally tags bushes
- Wyze Cam v4: person detection is reliable on the free tier now, which was a nice update
What doesn't work well: Wyze and Reolink occasionally classify large shadows as people at night. If your IR illuminator is casting strong shadows from branches, the AI can be fooled. Fix the underlying lighting issue rather than lowering sensitivity further.
Step 4: Set Activity Schedules
You don't need motion alerts from your own driveway camera between 7am and 8pm if you're home during those hours. Use activity schedules (every major app supports these) to limit notifications to times you're actually away or asleep.
My setup:
- Front door camera: alerts all day (small zone, accurate detection)
- Driveway camera: alerts only between 10pm-6am and when I set "away" mode
- Backyard camera: alerts only 11pm-5am (a raccoon at 2pm is not a security concern)
This reduces alert volume dramatically without compromising actual security coverage. The cameras still record continuously — you're just turning off the interruptions when they're least useful.
Step 5: Fix the Night Insect Problem
This one frustrated me for months before I figured it out. IR night vision creates a warm light source that attracts moths and spiders. A moth three inches from the lens looks like a massive white streak across the frame. Each one triggers a recording. In summer, this can generate 50+ "events" per night on a single camera.
Fixes that actually work:
- Reposition the camera so the IR LEDs aren't pointing toward shelter areas where insects congregate
- Use white LED color night vision instead of IR — insects are less attracted to white light than IR wavelengths and you can set the LED to activate on motion only
- Clean the camera housing monthly — spider webs directly on the lens cause continuous false triggers that look like noise or glare
- Add a dryer sheet near (not on) the camera mounting point in summer — the scent deters spiders from building webs near the lens. Sounds insane, works well
None of this is in any official documentation. I learned it from a security installer friend and it saved me hours of reviewing bug footage.
Step 6: Check Your Notification Cooldown Settings
Most cameras have a cooldown period between notifications — typically 30 seconds to 5 minutes. If your camera sends an alert, then another alert 45 seconds later for the same ongoing event, your cooldown is too short.
Set notification cooldown to 3-5 minutes for outdoor cameras. For indoor cameras watching a stationary area (front door interior), 1-2 minutes is usually fine. This doesn't affect recording — you'll still capture the full event — it just batches the alert to once per incident rather than once per motion re-trigger.
Eufy's app calls this "notification cooldown." Reolink calls it "interval." Wyze calls it "cool down period." Ring calls it "Motion Frequency" and offers Light, Standard, and Frequent options — use Standard or Light.
What to Do If Nothing Helps
If you've tightened zones, enabled AI detection, adjusted sensitivity, and you're still drowning in false alerts, the problem might be camera placement. Common placement mistakes:
- Camera facing directly into morning or afternoon sun (lens flare constantly re-triggers)
- Camera pointed at a heavily-trafficked public area with no realistic zone to exclude
- Camera too close to an air vent, fan outlet, or HVAC unit (temperature variation confuses PIR)
- Camera indoors aimed at a window (reflections and moving car lights through glass)
Move the camera before adjusting more settings. The right position with default settings usually outperforms a bad position with perfectly-tuned settings.
The Bottom Line
Spend 20 minutes with your camera's app: tighten the motion zones, enable AI person detection, set a 3-minute notification cooldown, and create a schedule for daytime alerts when you're home. That's the fix for 90% of people complaining about false alerts. Do it today, not when you get annoyed enough to turn the whole thing off.
A camera you stopped watching isn't protecting you.
Where to Buy
Affiliate links — if you buy through these links, I may earn a small commission at no extra cost to you.