ONVIF event types?

S4nDr0

Young grasshopper
Aug 7, 2025
37
20
Bulgaria
Hello,

I am trying to reconfigure my cameras to use their built-in detection. So far I was using CPAI, right now I am at latest BI and have been using the built-in AI for a few days, however I noticed that I get some stutter that is present even in recordings if there are many simultaneous cameras triggering and processing by AI. From what I've read the built-in detection of the cameras (especially newer ones?) is very good, and it is not necessary to use external AI confirmations, so I am trying to set that up...

As per my initial setup - I have set up IVS rules with tripwires/intrusion zones, and enabled smart detection for humans/vehicles (and animals where it's supported). I also am getting ONVIF events on BI and disabled Motion Zones. Problem is however that cameras seem to be triggering from motion only - I see that the events appear to be default (and same) on all cameras (Camera Settings -> Motion/Trigger -> ONVIF/camera events -> configure) , however I see that there are many that are for motion and enabled by default such as IsMotion=True , IsMotion=1, Event=MotionDetected and so on. Is there any documentation which I can check so that I know which ones should be enabled/disabled and so on, as I want alerts only for detection of human/vehicle/animal, not for motion (I am already recording 24/7 so alerts are not tied to recording).

The cameras are different models - I have a one of each Color4M-T, IPC-B54PRO-Z4E, and a Reolink POE doorbell. I also have a few of each IPC-T54PRO-AS, IPC-T54PRO-ZE. Each camera is installed via find/inspect, and ONVIF events are properly fetched - I've been using them until now for the AI tool to verify alerts, however without it - I get a lot of false positives as the default rules in ONVIF configuration seem to alert for motion as well.
 
Make sure MD and SMD are turned off in the camera.

Also, BI has a tendency to turn on MD so the hack is to make it the lowest sensitivity and just one little block and a small schedule so that it doesn't impact the triggers.
 
  • Like
Reactions: S4nDr0
Ok, it seems it was this... there are so many options and it makes it kind of hard to navigate - so I left IVS rules active, and deactivated SMD/MD on the camera - for now I don't have any false positives, we'll see if it results in false negatives though :)) Thanks for the help!
 
Unfotunately now I get no alerts at all. Is it necessary to have "event linkage" to the IVS? Currently there's no event linkage (it was snapshot by default but I removed it as they don't have their own storage) I see there's an option for Alarm Out port however I am not sure if that's the same - it could be for the siren or something as there's a time frame 10-300 seconds?
 
Alarm out is for one of the wires.

There is a bug with some cams that event linkage needs to be on even if no SD card is present.
 
Tried adding event linkage -> snapshot to all cams as it was by default, but I still get no alerts. I got just 1 alert for sound as I also enabled those for sound intensity change, but no alerts for visual detections. Currently I have:

1. Acupick disabled
2. MD disabled
3. SMD disabled
4. Drawn tripwire and intrusion zones - both directions, and both appear + cross for the intrusion zone -> default (full time) schedule for both, and target filter human, motor vehicle, animal. Sensitivity is at 8 which should be high enough.
5. BI is set up as before - no AI/Motion detection etc. just ONVIF events for alerts.

What I noticed that on the cameras I have IVS -> Global config (didn't notice it's on all cams until now, I thought it was just on the Color4M) and there's Large Scale AI models which is enabled - should I disable this or research into it and set it up properly? There seems to be some calibration with vertical / horizontal lines etc.
 
Folks have determined they had worse detection with large scale AI models enabled.

But before we go too much further down the BI rabbit hole, we need to confirm the cameras are actually triggering.

Since you don't have an SD card in it, you will have to have the camera GUI up live with IVS lines drawn and BI up at same time and wait for a car or person to go by and see if the IVS is actually triggered - the line and box around the object will turn red.

Confirm that is the case, and if so, then post screenshots of your BI settings.

If the camera isn't triggering, then post screenshots of your field of view and camera GUI settings.
 
  • Like
Reactions: looney2ns
Ok, I managed to check this, cameras are triggered - the tripwires start flashing and blinking, however it appears that the proper event type is not sent to/fetched by BlueIris. Since I've made the change I've been getting only audio alerts so these seem to be working fine. The ONVIF configuration in BlueIris is default - whatever it set up when I added the cameras. I am not sure why/how is the audio alert working as I see no specific "audio onvif event" in the list, but it is working.

Here are the settings for one of the cameras, others are identical except that "license plate capture" is not enabled on them but that doesn't make any difference (I am (was) using it on this camera only). Also for the motion zones - I've tested with both checked and unchecked, currently they are enabled as in the screenshot, but I have not set them up.

p.s. added a quick screenshot of the triggered image as well, this is just what I caught but before that I saw people moving on the road as well and it got flashy on them, too, but I didn't think of screenshotting it.
settings.jpg
 
Last edited:
That all looks right.

Hit the find/inspect tab and post what shows up in the pop-up window - I wonder if there is an ONVIF password issue.
 
  • Like
Reactions: S4nDr0 and Bruce_H
OK, finally solved. It appears that the issue was with the configuration. Once I hit find/inspect it re-detected stuff, and added new Stream profiles, also changed the ONVIF Source: to 00000. When I initially set up the cameras, I used find/inspect and then set up password, set default stream profiles and added the path behind as it was specified in guides that I read.. It appears you need to hit Find/inspect once more after the correct IP/username/password are set, and it fetches the necessary settings now that the password is set in the field.

Thanks a lot for the help. Now I just need to figure out how to better my rules, and make them more specific as it was with CPAI/Blueiris' built-in AI where it showed a human/vehicle/animal icon. Right now they just use the ONVIF event infor such as "RuleEngine/FieldDetector/ObjectsInside" but I guess that's a topic for another discussion :)

config.jpg
 
Awesome!

While this thread deals with using spotter cams, it mentions how to change "RuleEngine/FieldDetector/ObjectsInside" to whatever you want it to be!


 
  • Like
Reactions: S4nDr0
Thanks for all the help. I think I finally got the setup right at least from detection stand point. What I opted for is to use both AI and IVS - I depends on IVS for the detections as this results in a lot less (actually none so far) false positives. Then I enabled AI and "Confirm alerts with AI" however I selected to post Always (not to cancel alerts if they are not confirmed, and use low confidence 50%). This way each processed alert is still sent as it was already confirmed by the cameras themelves (not motion sensors) however I also get the nice animal/human/car icons and highlights on what was detected. I think that's best of both worlds. I also added MikeLud's custom AI models since the newest version of BI supports it, and I think detection is pretty good and CPU usage hovers around 20-30%, considering I am using a very old CPU (i7 4790).

Previously I got like 90% CPU usage when there were many alerts for example with heavy fog/snow/rain as the MD/SMD seems to have been activating very often and the AI processing was going wild. Right now even through a heavy fog last night - CPU usage was ok. I do have a GPU and have offloaded what I could to it - AI, NVDEC, etc but it was still taking a toll on the CPU.