ZM 1.37.61 - ONVIF event messages issues.

[Primed73]

Did your camera recover in the end?

[iconnor]

No, there has been a new firmware released that doesn't work at all, in ZM or ODM.

[iconnor]

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.

[iconnor]

Yup motion events working again.

[Primed73]

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

[iconnor]

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.

[Primed73]

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!

[iconnor]

Sorry just merged and pushed it.

[Primed73]

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

[Primed73]

Are the events closing in ONVIF events back to Zoneminder from your C520?

[iconnor]

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.

[iconnor]

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.

[iconnor]

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.

[Primed73]

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.

[abg]

Hi,

noticed the discussion here and considered to pop in, hopefully I can help with testing and ask some questions - just let me know if I'm not welcomed

Back in February I bought 2 TAPO C520WS V1 both running currently a beta firmware provided for testing by TP-Link. Apparently I have a newer FW version than what I saw presented here, namely 1.2.10 Build 250228 Rel.35704n and it's my second beta FW I received from TP-Link.
Long story short - I bought these cameras and noticed the white LEDs (smart mode lighting) are playing crazy, they start and stay on for 10 seconds then due to some bad conditional checking in the firmware the camera "believes" it's daylight and turns them off without switching to IR. After 10 more seconds it turns them on again until the end of the movement detection event A burglar can easily run away in complete darkness for 10 seconds.
They partially resolved the issue because originally after the movement detection event the cameras didn't even switch back to IR.
I discussed this with them on the TP-Link forum and they opened a ticket for me - got the rest of the exchange privately on E-Mail - here I was posting as panda11:
https://community.tp-link.com/en/smart- ... Id=1489674

Now, on topic. I managed to integrate these cameras from the very beginning in the latest Home Assistant (HAOSS) together with ONVIF functionality - that's pan/tilt control and receiving events (motion (person) detection) . I chose these cameras because I knew they are 100% supported in Home Assistant and also found references about them in both MotionEye & ZoneMinder sources.
My goal from the very beginning was to use the camera intelligence for detection/configuration (Android Tapo app locally) and a SW solution for recordings storage, remote live viewing and pan/tilt controls. Home Assistant has some nice integration (Frigate for instance) but I found ZoneMinder a better/simpler solution for my needs and zmNinja is exactly what I was looking after.

I struggled a while to get ZoneMinder latest master (v1.37.66) from 27.04.2025 built and installed - the whole Saga here:
viewtopic.php?t=33916

And now I'm stuck with the ONVIF configuration/functionality. I can control the cameras from the ZM web GUI - pan/tilt for instance, but after I press the direction buttons too many times (5-10) the ZM log is getting flooded with ONVIF errors, mainly saying that ZM cannot connect to the camera anymore.
In the ZM GUI ONVIF section I only added values in the ONVIF_URL , ONVIF_EVENTS_PATH (/Events), Username, Password, ONVIF_Alarm_Text (MotionAlarm) and set ONVIF_Event_Listener on Enabled. Just as a side note - if I enable SOAP WSA COMPLIANCE I get related errors in the ZM log, something ending with 8 and then with 1.
And unfortunately I don't receive any events in ZM - I triggered manually movement detection in front of the cameras. However, these movement detection events are showing up in Home Assistant, which is running on the same system in a VirtualBox VM (my choice - couldn't secure docker (it's an over complicated mess) and I dropped it in favor of VirtulaBox).

Finally some questions:
- I don't really understand how these ONVIF events are communicated and if somehow I interfere with HomeAssitant running on the same host/IP. I can disable Home Assistant ONVIF - don't really need it if ZM can do pan/tilt without filling the log with errors. Is there any conflict?

- do I need to perform some additional steps/configuration in ZM in order to receive these ONVIF alarms and trigger the recording? Is ZM compatible (able to communicate) with the TAPO C520WS over ONVIF?

- I run now ZoneMinder latest master (v1.37.66) from 27.04.2025 because I couldn't build the normal latest release - source code is incomplete (doesn't contain the submodules). I'd be happy to test/compile other versions or exact git snapshots if I'm instructed how to obtain them together with the related submodules. It takes around 10 minutes to build ZoneMinder on the system I run it now. Is this version I'm running now stable/error free or should I try some other release? Please advise.