If that's true then person detection on the camera is fooled by a flapping piece of black fabric which is pretty gawdawful.
With proper tuning of cameras, IVS rules, and or BI motion detection, it can be pretty darn accurate. But it takes some time to dial everything in properly.One thing I'm realising is that the detection is not good for triggering recordings. I've been testing for a few days to trigger when motion is detected and it misses a lot of post/during movement when someone parks a car for a few seconds and then step out after 10-15 seconds for example. It misses a ton of footage, so I guess constant recording with motion alerts may be the best way for me. I was hoping to save on storage by not having as much footage written to disk, but I guess there is no good balance between detecting, recording footage and disk space used.
The balance is to use substreams and record 24/7 substream and then mainstream on triggers.
With proper tuning of cameras, IVS rules, and or BI motion detection, it can be pretty darn accurate. But it takes some time to dial everything in properly.
I have two cameras in my back yard that trigger on BI motion only, not recording 24/7. And after proper tuning of the BI motion, it never misses a capture.
But you have to spend some time to get it dialed in.
The only reason I'm using BI motion detection on those two cameras is because those cameras do not have AI IVS.Did you have IVS for those cameras before using BI for motion detection? How is the additional CPU load looking like?
I'm thinking about for the time being just getting a couple of very large HDDs and leaving 24/7 until I learn more, Maybe that is cheaper than getting hardware to cope with additional load of software detection?