- Detection zone misconfigured
- Sensitivity too low
- Policy overridden after update
Problem Description
Motion events are visible but detections do not trigger notifications/recording logic as expected.
Symptoms
- No motion events
- Late detections
- One camera unaffected
Recognize these? Here's what usually causes it.
Common Causes
- Detection zone misconfigured
- Sensitivity too low
- Policy overridden after update
Most fixes happen in the first 3 steps.
Do not over-tighten zones so much that real events are excluded.
Tools & Requirements
Step-by-Step Solution
Inspect zone geometry
Ensure detection zones cover true activity areas.
Tune sensitivity safely
Adjust sensitivity and retrigger thresholds incrementally.
Validate with controlled tests
Trigger known movement and confirm detection-to-record pipeline.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the sensor still misses events after repositioning, check whether a scheduled 'home' or 'away' mode is overriding the sensitivity setting silently.
Maintain separate zone profiles for day/night lighting conditions.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Detection zone misconfigured
- Sensitivity too low
- Policy overridden after update
Before you go — try one of these (they fix most cases).
Need More Help? UniFi Protect Support
Note: The contact information below connects you directly to UniFi Protect's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.

