ZM 1.37.61 - ONVIF event messages issues.
Re: ZM 1.37.61 - ONVIF event messages issues.
Did your camera recover in the end?
Re: ZM 1.37.61 - ONVIF event messages issues.
No, there has been a new firmware released that doesn't work at all, in ZM or ODM.
Re: ZM 1.37.61 - ONVIF event messages issues.
They have provided a new beta. 1.2.10 build 250120 rel 45083n at least throws no errors. Time will tell if I actually get events.
Re: ZM 1.37.61 - ONVIF event messages issues.
Yup motion events working again.
Re: ZM 1.37.61 - ONVIF event messages issues.
ONVIF events still not working at my end:
2/21/25, 12:58:09 PM GMT zmc_m1 3420440 ERR Failed to get ONVIF messages! 8 (null) zm_monitor.cpp 1978
2/21/25, 12:58:07 PM GMT zmc_m1 3420440 INF Triggered off ONVIF zm_monitor.cpp 2004
2/21/25, 12:58:09 PM GMT zmc_m1 3420440 ERR Failed to get ONVIF messages! 8 (null) zm_monitor.cpp 1978
2/21/25, 12:58:07 PM GMT zmc_m1 3420440 INF Triggered off ONVIF zm_monitor.cpp 2004
Re: ZM 1.37.61 - ONVIF event messages issues.
I recently merged some code that logs the xml if a failure happens.
I've seen tons of those error 8. ALso lots of error 6. Currently everything working well for me though.
I've seen tons of those error 8. ALso lots of error 6. Currently everything working well for me though.
Re: ZM 1.37.61 - ONVIF event messages issues.
Yeah strange, not for me, Gets a motion alarm, doesn't go any further.
2/21/25, 3:34:57 PM GMT zmc_m1 3428379 INF C500: 3400 - Capturing at 14.25 fps, capturing bandwidth 140603bytes/sec Analysing at 1.71 fps zm_monitor.cpp 1934
2/21/25, 3:34:50 PM GMT zmc_m1 3428379 INF C500: 3300 - Capturing at 14.36 fps, capturing bandwidth 124932bytes/sec Analysing at 1.87 fps zm_monitor.cpp 1934
2/21/25, 3:34:43 PM GMT zmc_m1 3428379 INF C500: 3200 - Capturing at 14.24 fps, capturing bandwidth 148576bytes/sec Analysing at 1.71 fps zm_monitor.cpp 1934
2/21/25, 3:34:37 PM GMT zmc_m1 3428456 ERR Failed to get ONVIF messages! 8 (null) zm_monitor.cpp 1978
2/21/25, 3:34:36 PM GMT zmc_m1 3428379 INF C500: 3100 - Capturing at 14.25 fps, capturing bandwidth 120807bytes/sec Analysing at 1.85 fps zm_monitor.cpp 1934
2/21/25, 3:34:34 PM GMT zmc_m1 3428456 INF Setting ClosesEvent zm_monitor.cpp 2008
2/21/25, 3:34:34 PM GMT zmc_m1 3428456 INF Triggered off ONVIF zm_monitor.cpp 2004
2/21/25, 3:34:34 PM GMT zmc_m1 3428456 INF Got Motion Alarm!
2/21/25, 3:34:57 PM GMT zmc_m1 3428379 INF C500: 3400 - Capturing at 14.25 fps, capturing bandwidth 140603bytes/sec Analysing at 1.71 fps zm_monitor.cpp 1934
2/21/25, 3:34:50 PM GMT zmc_m1 3428379 INF C500: 3300 - Capturing at 14.36 fps, capturing bandwidth 124932bytes/sec Analysing at 1.87 fps zm_monitor.cpp 1934
2/21/25, 3:34:43 PM GMT zmc_m1 3428379 INF C500: 3200 - Capturing at 14.24 fps, capturing bandwidth 148576bytes/sec Analysing at 1.71 fps zm_monitor.cpp 1934
2/21/25, 3:34:37 PM GMT zmc_m1 3428456 ERR Failed to get ONVIF messages! 8 (null) zm_monitor.cpp 1978
2/21/25, 3:34:36 PM GMT zmc_m1 3428379 INF C500: 3100 - Capturing at 14.25 fps, capturing bandwidth 120807bytes/sec Analysing at 1.85 fps zm_monitor.cpp 1934
2/21/25, 3:34:34 PM GMT zmc_m1 3428456 INF Setting ClosesEvent zm_monitor.cpp 2008
2/21/25, 3:34:34 PM GMT zmc_m1 3428456 INF Triggered off ONVIF zm_monitor.cpp 2004
2/21/25, 3:34:34 PM GMT zmc_m1 3428456 INF Got Motion Alarm!
Re: ZM 1.37.61 - ONVIF event messages issues.
Sorry just merged and pushed it.
Re: ZM 1.37.61 - ONVIF event messages issues.
Excellent, much further this time, it's starting the detection phase, only its staying in alarm state.
2/26/25, 6:52:29 PM GMT zmeventnotification 3532757 INF |----> FORK:C500 (1), eid:173943 Sending event_start notification over FCM
2/26/25, 6:52:28 PM GMT zmc_m1 3532653 ERR Failed to get ONVIF messages! 8 (null)
2/26/25, 6:52:27 PM GMT zmeventnotification 3532757 INF |----> FORK:C500 (1), eid:173943 use hooks/start hook not being used, going to directly send out a notification if checks pass
2/26/25, 6:52:27 PM GMT zmeventnotification 3532630 INF PARENT: New event 173943 reported for Monitor:1 (Name:C500) Continuous[last processed eid:]
2/26/25, 6:52:25 PM GMT zmc_m1 3532655 INF C500: 1820 - Gone into alarm state PreAlarmCount: 0 > AlarmFrameCount:1 Cause:ONVIF
2/26/25, 6:52:29 PM GMT zmeventnotification 3532757 INF |----> FORK:C500 (1), eid:173943 Sending event_start notification over FCM
2/26/25, 6:52:28 PM GMT zmc_m1 3532653 ERR Failed to get ONVIF messages! 8 (null)
2/26/25, 6:52:27 PM GMT zmeventnotification 3532757 INF |----> FORK:C500 (1), eid:173943 use hooks/start hook not being used, going to directly send out a notification if checks pass
2/26/25, 6:52:27 PM GMT zmeventnotification 3532630 INF PARENT: New event 173943 reported for Monitor:1 (Name:C500) Continuous[last processed eid:]
2/26/25, 6:52:25 PM GMT zmc_m1 3532655 INF C500: 1820 - Gone into alarm state PreAlarmCount: 0 > AlarmFrameCount:1 Cause:ONVIF
Re: ZM 1.37.61 - ONVIF event messages issues.
Are the events closing in ONVIF events back to Zoneminder from your C520?
Re: ZM 1.37.61 - ONVIF event messages issues.
I don't know, havn't been paying attention.
My logs have gotten a lot quieter lately from the ONVIF event detection.... not sure if I've solved it or broken it.
My logs have gotten a lot quieter lately from the ONVIF event detection.... not sure if I've solved it or broken it.
Re: ZM 1.37.61 - ONVIF event messages issues.
No, the event isn't ending. I recently put some new code in there to handle cameras that don't send close events... but apparently it isn't working.
Re: ZM 1.37.61 - ONVIF event messages issues.
I get a response of -1 which apparently is EOF. SO I am adding code to kill the alarm if we get EOF. Should help.
Re: ZM 1.37.61 - ONVIF event messages issues.
Excellent, can you let me know when you have added the updated code?
I'll test on the C500 and give the results.
Many thanks.
I'll test on the C500 and give the results.
Many thanks.