Hello,
I own a Nest Doorbell (Battery) and have been experiencing repeated false negatives in motion detection, specifically with vehicles. This is not the first time — it has happened multiple times under similar conditions.
Scenario:
Camera is pointed directly at my driveway/parking spot.
Activity Zone covers 100% of the field of view.
All motion types enabled: People, Packages, Vehicles, Motion.
Wake-up Sensitivity: High.
Good lighting conditions, no obstructions.
Most recently, a car parked directly in front of the camera exited the spot, in full view.
The movement was directly in front of the lens, yet no event was detected — the history shows “No event detected” for that time frame.
Ironically, the camera has triggered for other vehicles in worse conditions (distance, speed, lighting).
This pattern strongly suggests the AI filtering in the Nest Doorbell (Battery) is discarding relevant events even with “Motion” enabled, which defeats the purpose of the feature for users who rely on complete event history.
Why this matters:
I need to ensure all significant movements are recorded, especially in a monitored area.
The current filtering is inconsistent — it repeatedly ignores clear, close events.
This is not due to Activity Zone, sensitivity, or power-saving mode. All are configured for maximum detection.
Request:
Please review the motion detection algorithm for the Nest Doorbell (Battery) to ensure that when “Motion” is enabled, events are recorded regardless of object classification confidence. Users should have the option to capture all motion in their defined zones without AI filtering out important activity.
I can provide timestamped video from another source showing the missed events, alongside the Nest Doorbell history.
Thank you, Ana
