Camera triggers in BI every minute on the 11 second mark

[AlwaysSomething]

I have a one camera in BI that triggers every minute on the 11 second mark. I'll also get some random ones on the 01 seconds mark but they are not every minute.

Here is a screenshot to hopefully help you understand.



BI is version 5.9.4.11 x64 (7/21/2024)
Not the latest but running well since I upgraded it months ago.

I only caught this because it's a new camera for LPR and I have been struggling with the night capture so decided for the Canceled alerts to "Remain on the alerts list" so I can view the captures quicker. When it triggers it's sending my CPU to 100% so would like to fix this.

Since this is night time and for LPR the images are black unless a vehicle goes by. Also looked at my other "overview" cam and nothing is going on every minutes when this is triggering. I only had one other camera set to "Remain on the alerts list" since it was also a new camera for LPR (different angle) and that one is not having this problem.

I cloned the camera and and set the clone for regular motion detection to see if there is something my eyes are missing but the clone is not triggering at all (unless valid like a car drives by).

Anyone ever experience this?

Steps I've tried so far to resolve:
1. Disable the camera and enable again.
2. Change the "Remain on the alerts list" to "Move to canceled alerts list". Camera is still triggering so put it back to "Remain..."
3. Shutdown BI and then restart. The actual service, not just the GUI.
4. Restart the entire PC (bare bones install)
5. Checked the Watchdog tab and only checked item is the default "Detect loss of video signal".
6. Checked the logs and don't see anything.

I watched the alerts list (since these 2 LPR cameras are the only ones set to "Remain..") and no other cameras are alerting. The other camera set for "Remain.." is not behaving like this and the BI settings were identical (as far as my eyes can see).

I'm stumped.

One last bit of info, besides these 2 cams for LPR I have one other camera cloned that I am using to compare CPAI versus the cam's AI with ONVIF. I do not have any problems with those either. Like I said, I watched the alerts list so none of my other cams are doing this.

Last option I can think of would be to remove the camera and and add it back in again but hate to have to add it all in again. Plus, hoping if there is a resolution it will help the next person.

Thanks.

 

[wittaj]

Yeah sounds like a delete the camera and add back.

Before I got to you saying it was a clone I thought maybe you had iframes way different than the FPS and you were getting the iframe to trigger because of a pulse in the image.

 

[AlwaysSomething]

I just double checked the camera status in BI to be safe and Key is 1.

I'll wait till tomorrow morning if no other responses and then I'll delete and add back in

 

[jrbeddow]

Before you go to the trouble of deleting and re-adding the camera, is there any chance that the triggering is coming from BI motion detection reacting to the changing digits on the real-time clock display (directly from the camera feed)? Ask me how I know...yeah, I had to chase this one down too and essentially block out this region of the screen using the zone "painting" tools. It can happen if your trigger contrast setting is sufficiently low and the target size setting is also quite small.

Just one thing to check before moving on to more drastic methods.

 

[AlwaysSomething]

Yea

Before you go to the trouble of deleting and re-adding the camera, is there any chance that the triggering is coming from BI motion detection reacting to the changing digits on the real-time clock display (directly from the camera feed)? Ask me how I know...yeah, I had to chase this one down too and essentially block out this region of the screen using the zone "painting" tools. It can happen if your trigger contrast setting is sufficiently low and the target size setting is also quite small.

Just one thing to check before moving on to more drastic methods.

How do you know? Yeah I think I read that somewhere once (maybe your original thread LOL).

So the triggering stopped when I checked this morning. I did use a zone but turned it off during my troubleshooting of the LPR AI so that is a possibility. I also set the Min Obj Size really small because at night the only thing showing is the plate which is tiny. Between the two changes that could be the reason.

I'm going to check again at night and see if it comes back. I'll do some tweaking and post an update.

 

[AlwaysSomething]

So checked at night and no longer triggering.

However....

Since I'm still tweaking my LRP I have been looking at the dat files and noticed the mask it was using was not what I had set. It was a previous version. I removed the mask and then created it again. I checked a new dat file after the recreating and it is correct now and still no triggering. So bottom line is it may have been the camera's time timestamp triggering the motion.

 

[jrbeddow]

If you still have any of the alerts from the period where it was triggering "inexplicably", you could go back and rewatch them in the BI console with all of the testing and tuning overlays turned on (right click when viewing, turn on all motion and trigger overlays). This should confirm if it really was the timestamp acting as the motion trigger. Not really a necessity if this is no longer occuring, but just satisfying to know with certainty.