I updated my BI to 5.4.6.4 as it had listed this release as the most recent stable release and had added Deepstack BVR test/tuning options. After I upgraded, the cameras I had setup to trigger Deepstack analysis using Dahua's IVS weren't triggering.
To troubleshoot, I ran Deepstack analysis on the clips of me walking by the cameras. Deepstack correctly identified me as a person (and one image as a dog with quite a high certainty, but this was using night settings).
Next, I disabled Deepstack from the trigger and analysis and tried to trigger the alert just using IVS (like I had before I started using Deepstack). No trigger in my alerts.
After that, I pulled up my 5231 in IE tab and had my wife walk in front of the camera using live view and rules visible. Sure enough, IVS was firing like it should have.
Went back and downgraded BI back to 5.4.6.3 (luckily have kept the downloads), reenabled Deepstack off IVS triggers, and everything worked again.
Did anyone else have this issue in 5.4.6.4? It may have been fixed in 5.4.7.1, but I don't upgrade to the latest updates, usually just latest critical or highly-stable update. I'll reach out to the developer if anyone else had this issue, and although I feel like I have mostly ruled out user error, I have not completely ruled it out (may have missed a new setting).
To troubleshoot, I ran Deepstack analysis on the clips of me walking by the cameras. Deepstack correctly identified me as a person (and one image as a dog with quite a high certainty, but this was using night settings).
Next, I disabled Deepstack from the trigger and analysis and tried to trigger the alert just using IVS (like I had before I started using Deepstack). No trigger in my alerts.
After that, I pulled up my 5231 in IE tab and had my wife walk in front of the camera using live view and rules visible. Sure enough, IVS was firing like it should have.
Went back and downgraded BI back to 5.4.6.3 (luckily have kept the downloads), reenabled Deepstack off IVS triggers, and everything worked again.
Did anyone else have this issue in 5.4.6.4? It may have been fixed in 5.4.7.1, but I don't upgrade to the latest updates, usually just latest critical or highly-stable update. I'll reach out to the developer if anyone else had this issue, and although I feel like I have mostly ruled out user error, I have not completely ruled it out (may have missed a new setting).