oh ok.. and will that also test why BI is cancelling the motion?You asked if the issue was ONVIF. The test I outlined removes ONVIF from the equation and simplifies things by removing Deepstack. It focuses ONLY on the BI triggering mechanism.
oh ok.. and will that also test why BI is cancelling the motion?You asked if the issue was ONVIF. The test I outlined removes ONVIF from the equation and simplifies things by removing Deepstack. It focuses ONLY on the BI triggering mechanism.
oh ok.. and will that also test why BI is cancelling the motion?
Ok.. but I can't wrap my head around the fact that why this is only happening with this camera.. if I turn off all the other cameras and ONLY have the doorbell connected, it would behave the same way...so to me that would tell me is not an issue with overloading the router...but more of an issue with this particular camera and BI.As far as testing goes, you really ought to consider what @wittaj was saying about loads on your router and BI optimizations through substreams. You might find that some of the problem really does disappear if you can live with substreams for your multi-view screen.
Ok.. but I can't wrap my head around the fact that why this is only happening with this camera.. if I turn off all the other cameras and ONLY have the doorbell connected, it would behave the same way...so to me that would tell me is not an issue with overloading the router...but more of an issue with this particular camera and BI.
Having read through this thread, it seems to me that the BIG question is why is the trigger being cancelled when it has confirmed a person?
There may be other issues but this point should be a good place to start.
A good while ago I experienced a strange problem that drove me insane. I resolved it by deleting the camera and making a copy of a working camera and editing it with the new camera ip address etc. Never really got to the bottom of the issue but making a copy of a working camera resolved the problem.
My post was based on the OP's post:The issue was the interaction between the doorbell and Blue Iris and Deepstack. I don't think confirmed alerts were being cancelled.
If you do this. The camera in blue iris doesn't get any onvif alerts. It seems to only get them from the motion alerts from Amcrest.Remind me .... are you trying to detect people or vehicles or both? Or something else (cats, birds, etc.)?
For those who want to use the camera AI for Human detection, you should DESELECT Motion Detection and ONLY select Human Detection, which is done in the Amcrest app.
If I disable motion in Amcrest app and only turn on human ai in Amcrest I no longer get onvif alerts from my camera but the Amcrest app continues to work fine. Is this normal?Yes, the process is - Camera detects Motion - Camera determines if Motion is a Human (you are not using this, but you should) - If YES, Camera creates a Trigger Event - BI polls Camera for Trigger Events - BI passes Trigger Event images to DS for processing - If DS detects Object, DS sends ALERT - BI processes Alert and sends PUSH.
There are numerous ways to configure things, but that is essentially what you have working right now.
I suggest you try the following:
1. Use your camera's AI for Human detection. To do this, in the Amcrest app you disable Motion detection and ENABLE Human Detection. Then you will only get Trigger Events from the Camera which pass its AI filter.
2. Don't use DS AI for now. Just see if you are happy with the Human Detection performance of the Camera feeding those Trigger events to BI. If you are happy with them, it is less work for BI and you will get faster notifications.
Now, if you ALSO want notifications about vehicles, then other configuration settings are necessary, but start with simple and build on that.