Cameras without internet - lack or delayed motion detection (NTP present, date time correct)
Hi,
I have 6 cameras (2xC110, 4xC320), latest firmware, HW1/2 versions of C320ws. In each I have microSD card for local recording, enabled motion detection, WiFi enabled too, cloud account enabled in app, correct date and time. When I have enabled whole communiction to WAN on router, motion detection work correctly. When I have no interrnet, or I disable WAN communication except NTP port 123, or when I disable whole WAN and I use local router NTP server (include Intercept NTP client requests option), or local Synology NAS NTP server, motion detection lack or records are delayed. So in iOS Tapo.app I see records, but without any movement and I know (I watching online stream), that realy someone was present, or I don't see record from that movement.
I use Synology Surveillance Station too and I can see, that when internet is blocked (with, or without NTP port 123 blocked), or when using local NTP servers, Surveillance station not receiving motion detection trigger from cameras, or if receive trigger, motion is not present in record, or only end of motion is present (delayed start and early end of recording).
In each kombination of settings I have correct date and time in video streams, it is same, as on router, same as on Synology NAS, same as on Windows PC. I do restart of each camera after setting is changed, router is rebooted too. Only when I have not correct time is, when I blocked NTP on WAN and have disabled local NTP server (so no NTP is present in enviroment).
Based on this, it seams, that NTP port 123 is not that problem and motion detection problem is based on something else. I read somewhere, that one userchange on his firewall method from drop to reject, but this now I can't (I use router firewall, not on Synology). It is blocking method problem, or I need to enable some others port, or it is because of cloud/internet blocking?
I found threads with similar problems, but not so complex testing and no local NTP present.
Thanks.
Hi.
1) + 2) Can't tell, maybe camera making detection "correctly" and with/without Synology connected, or blocked internet detection is same, so when camera not detect movement, it was not based on something with NTP/internet, only it was not detected because of optical problems. Witnout Synology connected I can't test Synology recognizing of camera motion detections.
I tested camera latest 24h without internet and local NTP with enabled Intercept NTP client requests option on router, so datetime was correct. Camera make 27 detection, 2 detection, was not triggered by camera. From that 27 triggered detections 10 detections was not recognized by Synology Surveillance Station, so only on SDcard/in Tapo.app I found video.
3) I attaching PDF with part of log. It contains camera start, NTP synchronisation and log before and after motion detection at 08:33:04. Next motion detection start at 09:18:12. This 2 detections was not recongized by Synology Surveillance Station, but in camera and Tapo.app I can see video. When I investigate records, that was correctly recognized by Synology, delay was sometimes 3 seconds, so, when motion detection was at 10:00:00, Synology record start at 09:59:58, but based on Synology settings, start was expected at 09:59:55. Sometimes was delay shorter, sometimes correct, sometimes longer.
In log you can see some time shift too. Not only first NTP sync, but you can see time shift after correct NTP sync too, where time is going back, then to front:
<4>1970-01-01 01:00:07[NVMP]Main progress start ...
<4>2024-06-05 07:43:55[SYSTEM]System time is calibrated by FW build time.
<4>2024-06-05 07:43:57[STM]new current time: 1736839577
<4>2025-01-14 08:27:17[SYSTEM]System time is calibrated by SD card.
<2>2025-01-14 08:27:31[SNTPC]recived from 747408000.
<2>2025-01-14 08:27:31[SNTPC]set time: 1736839617
<4>2025-01-14 08:26:57[CloudIot]req ntp err
<4>2025-01-14 08:26:57[SYSTEM]System time is calibrated by SNTP.
<4>2025-01-14 08:26:57[STM]record_plan new rec type:(time)
<4>2025-01-14 08:26:58[STM]gop time error, start_time: 1736839651, end_time: 1736839618
<4>2025-01-14 08:27:00[STM]time jump, gop start_time: 1736839618, stopped time: 1736839651
Thanks.
