Hello,

I have been a TP-Link customer for over 20 years and currently use several Tapo devices:

• Doorbell D210

• 2 × C113 cameras

• Active cloud subscription (plan for up to 10 devices)

The hardware works correctly. The issue is clearly related to the software/firmware logic.

Problem summary

Motion-triggered recordings are inconsistent and frequently miss critical parts of events.

Observed behavior (occurs repeatedly):

1.    Delayed recording start (trigger delay): Recording starts several seconds after motion begins. Example: a delivery person arrives, but only the moment when they are leaving is captured.

2.    Events not recorded at all: Clear motion events sometimes generate no recording.

3.    Premature event termination: Recording stops while the person or object is still present.

4.    Missing post-event recording: The full exit is not captured (e.g., a vehicle leaving).

5.    Inconsistent behavior: Performance varies significantly under similar conditions.

Important technical detail

This issue occurs in both Cloud recording and Local microSD recording. This completely rules out internet latency or cloud-related issues. The problem is strictly related to:

• Motion detection logic.

• Pre/post event buffering.

• Internal event handling in firmware.

Technical assessment

Based on the observed behavior, the issue appears to be caused by high trigger latency and an insufficient pre-event buffer. I have compared this behavior with other competitors' products under the same conditions, and the trigger latency in Tapo is significantly higher, especially on the D210.

Current configuration

• Motion sensitivity: Maximum.

• Detection zones: Configured and active.

• Recording duration: Set to maximum allowed.

• Network: 1Gb Cox connection, low latency, stable.

Request

Please confirm if there are planned firmware updates to improve pre/post event buffering and detection reliability. I am planning to expand my system with at least 4 additional cameras, but this recording reliability issue must be resolved first.

Best regards,

Yury