Motion Detection Sensitivity and Zone Settings (V380 Pro WiFi)

How motion detection works on V380 Pro cameras

V380 Pro WiFi cameras typically detect motion using one or both methods:

Video-based detection (pixel change)
The camera compares frames and triggers when enough pixels change. This is common on most indoor/outdoor Wi-Fi cameras.
PIR sensor detection (heat movement)
Some models include a PIR sensor that reacts to warm bodies moving across its field. PIR usually reduces false alerts but has its own limits (range, angle, and sensitivity to weather conditions).

In the app, both types usually appear under “Alarm,” “Motion Detection,” “Detection,” or “Alarm Settings.” Even if your camera has PIR, the app may still offer video-based sensitivity controls.

What you can control (and why it matters)

Motion alerts can be made useful or unbearable depending on four core settings:

Detection switch
Turns motion alarms on/off.
Sensitivity
Determines how easily motion triggers. Too high = constant notifications. Too low = missed events.
Detection zone / area
Lets you select where motion is allowed to trigger (for example, only the doorway, not the street).
Schedule
Limits detection to certain hours (for example, nighttime only).

A good setup balances all four. Sensitivity alone is rarely the full solution.

Where to find Motion Detection settings in the Android app

The menu names vary by V380 Pro version and camera model, but the path usually looks like one of these:

Device list → tap your camera → Settings (gear icon) → Alarm Settings → Motion Detection
Live View screen → Settings → Alarm / Detection
Device Settings → Alarm → Motion / Human / Sound detection

Common labels you may see:

Motion Detection
Alarm Detection
Alarm Setting
Detection Setting
Smart Detection
Humanoid / Human Detection
Alarm Zone / Area / Region
Alarm Time / Schedule

If you can’t find them, check both the Live View overlay menus and the main device settings page.

Step-by-step: Enable motion detection

Open V380 Pro on Android.
Select the camera and enter Live View.
Open Settings (usually a gear icon).
Go to Alarm Settings or Detection.
Turn on Motion Detection (or Alarm Switch).
Save/apply changes if the app prompts you.

After enabling, do a quick test: wave a hand in front of the camera and see if an alarm indicator appears (some versions show an icon, a banner, or a short beep).

Sensitivity: what it really controls

Sensitivity is the trigger threshold. With video-based detection, the camera decides that “enough pixels changed” to count as motion.

Typical sensitivity options:

Low / Medium / High
A numeric scale (for example 1–10 or 1–100)

How to interpret results:

If small lighting changes (shadows, TV flicker) trigger alarms, sensitivity is too high.
If a person walking through the scene does not trigger, sensitivity is too low or the zone is wrong.

Recommended starting point

Indoors: Medium
Then adjust based on pets, fans, and lighting.
Outdoors: Low to Medium
Outdoor scenes have more “natural motion” (trees, rain, insects, headlights).

A reliable calibration routine (fast and effective)

Use this workflow instead of guessing:

Set sensitivity to Medium.
Turn on motion alarms.
Walk through the target area at normal speed (doorway, gate, hallway).
Check whether you get an event/notification.
If it misses you, increase sensitivity one step.
If it triggers without you (wind, shadows), decrease sensitivity one step.
Repeat twice and stop. Over-tuning usually makes it worse.

Keep in mind: changing the zone often reduces false alarms more effectively than lowering sensitivity.

Detection zones: make motion detection smarter, not louder

A detection zone (also called region/area) is the part of the image that is allowed to trigger motion.

Typical zone styles:

Grid selection (you tap squares to enable/disable detection)
Draw-a-rectangle (select one or more rectangles)
“All area” vs “Custom area”

Step-by-step: Set a motion detection zone

Open the camera’s Alarm Settings / Motion Detection menu.
Find Alarm Zone / Detection Area / Region.
Choose Custom (if available).
Select only the areas that matter:
- Doorway
- Gate
- Cashier counter
- Hallway entrance
Exclude areas that cause noise:
- Roads with passing vehicles
- Tree branches and bushes
- Moving curtains
- TV screens
- Reflective surfaces that catch headlights
Save/apply.

Zone design tips that dramatically reduce false alarms

Avoid the sky and bright background edges
Sky brightness shifts can trigger motion easily.
Avoid glossy floors or windows
Reflections move like “motion” to the algorithm.
Keep the zone tight
A smaller detection region lets you use slightly higher sensitivity without constant false alerts.
Don’t include busy areas “just in case”
That turns your camera into a notification generator.

Scheduling: stop alerts when you don’t need them

Most V380 Pro setups allow an alarm schedule (sometimes called “Alarm Time,” “Arming Schedule,” or “Plan”).

Common scheduling patterns

Night-only monitoring
For example, detect motion from 10 PM to 6 AM.
Work-hours monitoring
Detect motion in a shop after closing.
Full-time monitoring
Use zones and low sensitivity to keep it sane.

Step-by-step: Set a schedule

Open Motion Detection settings.
Find Alarm Time / Schedule / Plan.
Enable scheduling (if there’s a switch).
Select the days and time blocks you want active.
Save/apply.

If your app supports multiple time blocks per day, use them:

One for daytime
One for nighttime
This can help handle different lighting conditions and different types of motion in the scene.

Smart detection options (if your camera supports them)

Some V380 Pro camera models include extra detection types that can make alarms more meaningful:

Human / Humanoid detection
Prioritizes human shapes and reduces alerts from trees or shadows.
Sound detection
Triggers on loud noises (use carefully; it can be very sensitive indoors).
Tamper detection
Alerts if the camera is covered or moved.
Motion tracking / Auto tracking
The camera follows movement (useful for monitoring, but can increase movement in the scene and sometimes trigger additional alarms).

Best practice:

If Human detection exists and works reliably on your model, use it as the primary trigger for push notifications.
Keep basic motion recording enabled if you want a complete event history, but limit notifications to “human” events when possible.

Notification behavior: align detection with what gets recorded

Motion detection often controls multiple outcomes:

Push notifications to your Android phone
Local recording to SD card triggered by motion
Cloud event recording (if enabled)
Alarm sound/light (siren/spotlight on certain models)
Snapshot capture

These can be controlled separately on some app versions. For example, you might:

Record events to SD card on motion
Send push notifications only for human detection
Disable siren to avoid disturbing neighbors

If your app offers separate toggles such as:

“Alarm Recording”
“Push Notification”
“Alarm Sound”
Adjust them to match your goal.

Suggested setups (real-world templates)

Template A: Indoor home camera (living room) with pets

Goal: catch people, reduce pet triggers.

Motion Detection: On
Sensitivity: Low to Medium
Zone: exclude floor area where pets roam; focus on doorways and mid-height zones
Schedule: optional, or night-only if you’re home during day
Human detection: On (if available)
Push notifications: On, but keep them limited to key hours

Extra tip:
If pets climb furniture, keep the zone higher (upper half of the frame) so pet motion is less likely to trigger.

Template B: Outdoor front gate facing street

Goal: detect entry at gate, ignore passing cars.

Motion Detection: On
Sensitivity: Low
Zone: gate area only; remove road and sidewalk
Schedule: full-time or night-only
Human detection: On (if available)
IR/night vision: ensure glare is controlled so the image stays clear at night

Extra tip:
Headlights sweeping across the scene are a huge false-alarm source. Tight zones help more than sensitivity reduction.

Template C: Small shop / office after hours

Goal: reliable intrusion alerts.

Motion Detection: On
Sensitivity: Medium
Zone: entrances, windows, cashier area
Schedule: only after business hours + weekends
Push notifications: On
Alarm recording: On to SD card or cloud
Siren: optional (consider neighbors)

Extra tip:
Use two time blocks if lighting changes significantly between evening and late night.

Troubleshooting: too many false alarms

Cause 1: Moving objects in the detection zone

Examples: curtains, ceiling fans, trees, flags.

Fix:

Exclude those areas with a custom zone.
Lower sensitivity one step only after zoning is correct.

Cause 2: Lighting changes

Examples: TV flicker, car headlights, sunlight shifting shadows.

Fix:

Remove bright windows from the zone.
Don’t include reflective floors.
At night, avoid aiming through glass with IR enabled.

Cause 3: Insects and spider webs (night)

IR light attracts insects and highlights webs, creating constant triggers.

Fix:

Clean the camera face regularly.
Position the camera away from corners where webs form.
Reduce IR glare and avoid placing IR close to a wall.
Tighten the zone so only the entry area triggers.

Cause 4: Rain and swaying foliage outdoors

Fix:

Lower sensitivity.
Exclude trees/hedges.
Consider human detection if available.

Troubleshooting: motion detection doesn’t trigger at all

Cause 1: Motion Detection switch is off

Fix:

Confirm the master alarm/motion toggle is enabled.
Some versions have two toggles: “Alarm” and “Motion.” Both may need to be on.

Cause 2: Schedule blocks are empty or set to inactive hours

Fix:

Set schedule to full-day temporarily for testing.
Then reapply your preferred schedule.

Cause 3: Zone excludes the area where you’re testing

Fix:

Temporarily set zone to “All.”
Test again.
Rebuild a custom zone after confirming it works.

Cause 4: Sensitivity too low for the scene

Fix:

Increase sensitivity one step.
Test by walking closer to the camera, then at normal distance.

Cause 5: Camera view is too wide or subject is too far

Fix:

Reposition the camera so the target area fills more of the frame.
Motion algorithms detect better when the subject occupies more pixels.

Troubleshooting: alerts are delayed or inconsistent

Possible causes:

Weak Wi-Fi at the camera
Router congestion
Phone background restrictions
Cloud relay delays in remote viewing environments

Fixes:

Improve Wi-Fi signal near the camera.
Disable battery optimization for V380 Pro on Android.
Allow background data and notifications.
Reboot the camera and router if events suddenly become late.

Best practices to keep motion alerts reliable long-term

Re-check zones after repositioning the camera
Even a small angle change can include the street or window again.
Use “zone first, sensitivity second”
Zoning solves most false alerts without missing real motion.
Separate “recording” from “notifying” if the app allows it
Record broadly, notify narrowly.
Keep the lens and housing clean
Dirt and water spots at night can look like motion.
Update firmware only when stable
Unstable power during updates can cause weird behavior afterward.

Quick tuning checklist

Motion detection enabled
Schedule set correctly (or temporarily full-day for testing)
Sensitivity set to Medium as baseline
Custom zone excludes roads, trees, windows, fans, TVs
Human detection enabled if available
Android app allowed to run in background (battery optimization disabled)
Test by walking through the zone at normal speed, day and night

This approach produces alerts that feel intentional: fewer distractions, more meaningful events, and better recordings when something actually matters.