@Solla-topee Video clips sent. Thank you very much for your interest.

Solla-topee wrote

  @CUNEYT 

Hi,
1. I find the following information from the provided videos. Please check if it's correct: on your Synology Surveillance Station, when event detection is set to Tapo C225, the beginning of the movement was not recorded on the Synology side. However, this phenomenon didn't occur when event detection is set to Surveillance Station.
 
If so, to verify the reported phenomenon lies with the Tapo C225 or Synology, you may also need technical support from Synology. Alternatively, a workaround is to enable pre-recording on the Synology Surveillance Station, for example, pre-recording for 10 seconds, and see if that helps.

Recording | Surveillance Station - Synology Knowledge Center

 

2. Although the camera doesn't detect events when switching between day/night modes, the switching time is very short and usually doesn't affect the detection function. Please confirm when the Tapo C225 switches from night mode to day mode (or vice versa), and a movement occurs simultaneously, whether you will receive the corresponding detection notification on your phone? Does the corresponding detection video clip store on the SD card?

 

 

  @Solla-topee 

1. Correct. I also tried 10 seconds pre-recording but it did not changed anything. But I can test with increasing it to 15-20 seconds if it helps. 

The problem is, the camera doesn't detect events when switching between day/night modes and it does not send a movement occured signal to Synology. If Synology does not get that signal it cannot add pre-recording time to beginning. If you watched the clips you can clearly see that a full 11 seconds missing at the beginning of the Synology clip. That 11 second movement exists at the begining of the camera's clip recorded on the sd card. 

You say that the switching time is very short but it takes about 10-11 seconds and after that delay the camera starts to fallow the events again.

2. Of course yes, Corresponding clip stores on the SD card. I have sent you that clip taken from the sd card.

When event detection is set to Synology instead of Tapo C225, everythinj works as expected.

Best regards.

Critical Security Vulnerability: No ONVIF Trigger During Mode Transition (11-Seconds Blind Spot)

"I have tested your suggestion regarding the pre-recording buffer, and I must report that it DOES NOT solve the underlying security flaw. My detailed tests have revealed a critical vulnerability in the Tapo C225's firmware:

1. The Deafness Period: Contrary to your claim that the transition is 'very short', in a real-world dark environment, the Day/Night switch takes approximately 10 to 11 seconds.

2. Missing ONVIF Trigger: During these 11 seconds, while the camera is adjusting its image, it completely fails to send any ONVIF motion trigger to the NAS. The video stream continues, but the 'Motion Detected' signal is suspended.

3. The 9-Second Failure Scenario: If an intruder enters the room, triggers the light, and leaves the frame within 9 seconds (while the camera is still in transition), the camera NEVER sends a trigger. There is no recording on the NAS side.

4. Pre-recording is Useless Without a Trigger: Since the NAS (Synology) never receives a 'Start Recording' signal from the camera, it doesn't matter if the pre-recording buffer is set to 15 or 30 seconds; the NAS will never save the footage to the disk. The entire event is lost.

This is not a minor delay; it is a total loss of security during a 11-second window. The camera prioritizes image adjustment over its primary function: motion alerting. I am requesting an urgent firmware investigation to ensure ONVIF triggers are prioritized even during mode transitions.

Best regards.

  @Solla-topee 

Thank you for your detailed response.

I appreciate the explanation regarding the SD card recordings. However, the core of the issue is not the camera's internal recording, but the ONVIF 'Motion Detected' trigger latency sent to external NVR systems like Synology.

Your statement, "The camera doesn't detect events during day/night mode switching to prevent false detection," actually confirms my finding. If the camera intentionally suspends detection during this transition (which lasts about 11 seconds in my environment), it explains why Synology receives no signal to start recording.

Since Synology Surveillance Station relies entirely on the ONVIF signal from the camera to trigger its own recording when set to 'Camera' detection mode, any suspension or delay on the camera side makes the NVR recording incomplete.

I would like your tech team to investigate the following:

1. ONVIF Signal Suspension: Why is the ONVIF alert process completely halted during the 11-second image adjustment?

2. Trigger Latency: Even after the switch is complete, there seems to be a significant delay before the 'Motion Detected' signal is broadcasted via ONVIF.

I have already switched my detection method to 'Surveillance Station' (server-side analysis) as a workaround, which proves that the video stream is available, but the camera's internal trigger is failing to communicate the event in time.

I look forward to hearing from your tech team regarding a firmware-level improvement for ONVIF trigger prioritization during mode transitions.

Best regards.

  @Solla-topee 

Thank you for the update. Just to clarify, I am already in direct contact with System Engineer Yurik regarding this specific issue.

Yurik has acknowledged the technical nature of the delay and has already escalated the case to the senior engineering team under Ticket ID: TKID260338021.

The '1-second switch' mentioned doesn't account for the sensor's exposure adjustment period, which is where the 11-second ONVIF trigger latency occurs in my tests. I am now waiting for the senior tech team's analysis on why the Tapo App can notify me immediately while the ONVIF signal remains delayed during this transition.

I will share the findings once the engineering team provides a technical resolution.

Best regards.

Hi Yurik and the Tech Team,

I have completed my final diagnostic tests regarding the 11-second ONVIF delay on the Tapo C225. The results clearly isolate the issue to the camera's internal firmware processing.

Final Diagnostic Findings:

1. Eliminating Hardware/Mode Variables: I locked the camera to Permanent Night Mode to remove the 'day/night switching' and 'mechanical IR-cut filter' variables. Even with NO switching or exposure adjustment involved, the ONVIF Event Trigger still lags by 11 seconds.

2. Server-side Validation: I tested the system using Server-side (NVR) Motion Detection instead of the camera's internal trigger.

   • Result: The recording starts INSTANTLY as soon as the light is switched on.

   • Conclusion: This proves that the RTSP/ONVIF video stream is being sent by the C225 without any latency. The NVR receives the visual data in real-time.

3. App vs. ONVIF Contrast: During these same events, the Tapo App on my smartphone notifies me immediately. This confirms the camera's processor is detecting the motion in real-time but failing to broadcast the ONVIF signal simultaneously.

Final Technical Conclusion: The hardware, sensor, and video streaming of the C225 are working perfectly. However, there is a firmware-level bottleneck in the ONVIF Event Service. The camera validates motion internally for its own App but delays the standardized ONVIF 'Motion Detected' flag by ~11 seconds.

As a security product, this 11-second 'blind spot' in NVR logging is a critical flaw. Please provide these findings to the Senior Engineering team for a firmware-level optimization of ONVIF broadcast priority.

I have side-by-side video recordings showing the exact moment the light is switched on in Permanent Night Mode. The visual evidence clearly shows the immediate stream availability versus the 11-second delay in the ONVIF trigger. I am ready to share these files with the engineering team upon request.

Best regards.