Help debugging - motion found, person:89%, no alert

[TD22057]

For the most part I've been very happy with deepstack and how it's been working. But I'm never sure it really captures everything and this morning I had a great example. My wife went for an early walk and triggered 2 out of the 3 cameras she passed through. But one camera showed no alerts this morning. This camera has worked fine triggering alerts before (night and day) with DS so I don't think there is a settings problem (at least not one that prevents it from working at all). I'm running BI 5.4.9.18 w/ the latest DS. Camera's are Dahua 2MP w/ 25FPS, substream's synced, Key=1.00.

Here's a screen shot showing post-processing. You can see that BI identified the motion (orange line in the timeline), with DS analysis mode turned on, it found the person at 89% confidence. But no alert was generated at all. The log is also completely empty around this time. When I do BI->Status->Log, I don't even see the logs for the alerts that were generated on the other cameras at this time.

• Any ideas how I can debug this?
• Do I need to do something to get more logging?
• Why didn't the other cameras which did trigger alerts show up in the logs?

Any ideas would be greatly appreciated, TD

 

[wittaj]

Keep in mind that real time DeepStack and Analysis after the fact are two different things. We will always get Deepstack to pick-up on analysis.

Your CPU looks low so I don't think it is a timed out issue.

You need to open the full BI log (option down at bottom of the Log page) and see with the ms times are for Deepstack and see if it even triggered for this camera at that time and what happened (nothing found or -100 error).

Are you have BI save alerts for ones not confirmed by DS? If so, did it get an alert that was cancelled for this event? It could very well be BI motion itself didn't pick her up due to either motion settings or contrast issues that it struggled with at this viewpoint.

 

[TD22057]

Thanks. I didn't have the log "save to file" box checked so there isn't any file to open. I've fixed that and will have to wait to see if the problem repeats.

Deepstack run times at other points in the log are on the 100-200ms order with a couple on the high side at 400ms.

re: Are you have BI save alerts for ones not confirmed by DS? I

Not quite. I do have log events that say "alert cancelled" when nothing was found. Those look normal - something changed in the image but no person was there. In this case, there is nothing in the log at all. The time line image shows an orange bar/line where BI found motion. But DS didn't find anything and the log was empty. So since the BI timeline shows that orange line at the time she walks through the frame, I'm assuming that BI found the motion just fine and either DS didn't run or maybe had an error of some kind.

Another thing I think is strange in the logs is that for many items, I'll see what I would think is normal: camera reports "MOTION_A" message, then a DS message saying "alert cancelled" or "person 75%". But I also see a bunch of cases where the camera says "MOTION_A" and then nothing - no alert was generated and no DS message either way. There are also cases where I just see a DS message saying "alert cancelled" without a camera motion message in the logs. There are also cases where alerts and clips were generated (correctly) and nothing shows in the log screen at all.

Maybe if the saved log file has more details than the log screen (is that true?) it will be more helpful.

 

[wittaj]

I think the Motion_A and nothing means that DeepStack was down for some reason - are you using CPU or GPU version? It might be a good idea to uninstall and reinstall DeepStack in the event something corrupted as BI has done updates.

 

[JonSnow]

i've just started with Deepstack and am seeing the same on some alerts, when checking the dat file for Cam A it processed two image with both having +70% person detection yet was set to "Nothing Found". Then a few minutes later when BI triggered again it detected and processed person detection perfectly.

When checking Cam B which overlooks my driveway I sometimes get "Nothing Found" when passing my parked cars or if the car door is open and i am behind it from the cams view its detected as a static object.

I have also just enable "Save to File", but is there a way to go back and process or correct a failed detection?

 

[TD22057]

To follow up with this: I can't really explain what I think was strange in the log files. I did check the saved image folder and look at the images. There was only one picture of the event that it missed. That pic seemed clear enough but who knows why it didn't register. Since I have a lot of CPU head room, I changed the BI motion settings to trigger on 0.3 seconds of motion (faster than I had it) and reduced the DS processing time from every 750ms to 500ms. So far that has worked a lot better and I don't think I've missed any events. My theory is that sending more images to DS gives it more chance to identify people.

 

[dz93]

To follow up with this: I can't really explain what I think was strange in the log files. I did check the saved image folder and look at the images. There was only one picture of the event that it missed. That pic seemed clear enough but who knows why it didn't register. Since I have a lot of CPU head room, I changed the BI motion settings to trigger on 0.3 seconds of motion (faster than I had it) and reduced the DS processing time from every 750ms to 500ms. So far that has worked a lot better and I don't think I've missed any events. My theory is that sending more images to DS gives it more chance to identify people.

You might also want to try to disable "Use main stream if available" under Artificial Intelligence in the trigger tab. For me, when this option is enabled, for some reason blue iris can't send the images every 500ms like I had it set and so it was dropping images and resulted overall in reduced detections from deepstack.

 

[Fubduck]

When I upgraded from 5.4.7.11 to 5.4.9.18, I was not seeing alerts for some of my cameras in the alerts list.

Long Story short, the Alerts Tab was not configured properly for the cameras.
It was set to- Fire when: This camera is triggered, but the Trigger sources and zones box was not checked.