Right... it would be a hit or a miss with BI detecting motion, but the Amcrest app had the motion alerts there...for some reason BI would not detect at times.Let's go back to your original complaint. You were saying that Motion Detection performance in BI with the AD410 was spotty. How is it right now?
I want this camera to detect everything, so I am probably doing to stay with current settings..
Thanks for your help.. I will check tomorrow to see if motion detection/alerts are better than before.
The rationale behind my suggestion was to maximize the AI features you have invested in. My bet is you will be very pleased with the Human Detection feature of the AD410 as it is the same as Smart Motion Detection feature on other Dahua cameras.Right... it would be a hit or a miss with BI detecting motion, but the Amcrest app had the motion alerts there...for some reason BI would not detect at times.
So I am hoping now would be better...but I have to wait until tomorrow since the cars are too far in the dark for the camera to pick up.
Almost. Go ahead and let BI/DS confirm the Human Detection (since you need it for vehicle detection anyway), but the triggering for Humans lies in the Camera where triggering for Vehicles will be configured in BI. Make sense?Oh I got it now.. so enable motion in BI and set remove "person" from the list because Human Detection will be done at the Amcrest app level.
That is what I suggest, yes.So this means I can disable Motion Detection in the Amcrest app and only enable Human Detection?
The interaction between Motion - Triggers - Alerts still needs work. That is why I suggested you NOT use Deepstack for now. Not until you are happy with the triggering.The motion is acting the same way as before. I completely missed my son going out this morning.. that motion didn't even register. So I checked the cancelled events and found a couple of cancelled events there
1. while he was walking away in the middle of the yard like 40-50 feet away.. it detected him as a person at 71% - cancelled
2. it detected the bus at 64% - cancelled.
See the emboldened part of your message - that is the triggering. Right now you are having trouble discerning between motion detection - triggering - and alerts. You are having this problem, in part, because you are only looking at the results AFTER Deepstack has processed them. AND - you have not made (or confirmed) the proper HUMAN DETECTION settings in the camera. Until you resolve these fundamental issues, you have no idea about the BI/DS reliability.The issue is not that much with the triggering...It's completely missing the motion altogether. Going out the door, the doorbell should detect as a person immediately as it does from time to time.
But other times like this morning, it completely missed it and only captured the motion when the "person" was 40-50 feet away.
The Zone is set to the entire screen. When it works, it works great...but what's happening is it just stops working whenever it wants...so it's not reliable.
See emboldened text .... How do you know that? Are you seeing the captures in the Amcrest app or elsewhere?What proper human detection setting? - the only option in the camera for human detection is sensitivity, zone and schedule. I have the sensitivity to HIGH and the camera itself is capturing the motion fine, every time... it's just that BI is not getting the info from the camera half the time.
Because the motion alerts are all in the Amcrest app, but not in BI... all motion alerts in the Amcrest app coincide with the other cameras that are in the same location.See emboldened text .... How do you know that?