The camera is Chinese, which very strangely generates ONVIF events.
The strange thing is that after publishing a discovery event, an event about the end of discovery is immediately published.
In this case, the event about the end of detection is published constantly with an interval of approximately 1 second! and so on ad infinitum. This is probably not the most correct camera algorithm.
Perhaps as a result of this, ZM records very rarely, i.e. For approximately 50 events, only one can be registered.
Permanent entries in the logs:
Code: Select all
3/19/24, 5:02:20 PM GMT+3 zmc_m14 5771 INF Triggered off ONVIF zm_monitor.cpp 1901
3/19/24, 5:02:20 PM GMT+3 zmc_m14 5771 INF Got Motion Alarm! zm_monitor.cpp 1891
3/19/24, 5:02:20 PM GMT+3 zmc_m14 5617 INF Clone of HeroSpeed_2Mp: 11600 - Capturing at 20.03 fps, capturing bandwidth 523298bytes/sec Analysing at 0.00 fps zm_monitor.cpp 1831
3/19/24, 5:02:15 PM GMT+3 zmc_m14 5617 INF Clone of HeroSpeed_2Mp: 11500 - Capturing at 20.00 fps, capturing bandwidth 539743bytes/sec Analysing at 0.00 fps zm_monitor.cpp 1831
3/19/24, 5:02:10 PM GMT+3 zmc_m14 5771 INF Triggered off ONVIF zm_monitor.cpp 1901
3/19/24, 5:02:10 PM GMT+3 zmc_m14 5771 INF Got Motion Alarm! zm_monitor.cpp 1891
3/19/24, 5:02:10 PM GMT+3 zmc_m14 5617 INF Clone of HeroSpeed_2Mp: 11400 - Capturing at 20.24 fps, capturing bandwidth 523407bytes/sec Analysing at 0.00 fps zm_monitor.cpp 1831
3/19/24, 5:02:05 PM GMT+3 zmc_m14 5617 INF Clone of HeroSpeed_2Mp: 11300 - Capturing at 19.76 fps, capturing bandwidth 519619bytes/sec Analysing at 0.00 fps zm_monitor.cpp 1831