Question for anyone that knows.
So I have my trigger and cancel alert URLs setup and working now.
I have my alerts set to re-trigger after 3 seconds unless active still and my image set to capture every 3.5 seconds.
The issue I have is sometimes the trigger image does not match the AI image because of delay processing or the fact that BI may only show one on the alert but it took 2 images.
For example BI takes snap, adds to thumbnail, while AI is processing another image is taken. The first image ends up as canceled because say a car JUST started into scene so motion was hit but not enough for AI to know it's a car. The second image knows it's a car so now it triggers. Well BI only made the one entry despite 2 images so when it triggers the email is the first image with maybe nothing in it of enough value. Funny part now is the alert is cleared from timeline due to the cancel but flagged cause I'm still using flags for trigger at the moment but this is because the same issue, multiple images but 1 entry in BI.
Anyway I know in the example you could just modify the motion to require being in the view more before trigger but that was just my example. It happens in other cases where you wouldn't want to do this so trying to understand if my times need to be adjusted or some way to make BI use all the images and not just the one etc.
What am I doing wrong or can I change to improve this? I only want multiple images in case the first misses. I may see if Ken can set an image time limit too (for times when it is constant motion I don't need non-stop alerts and maybe dynamic mask don't help since it can move a lot). Like mowing the yard and being lazy to not want to disable alerts. Well I can get hundreds of emails LOL. I only need 1 if it's a legit one and still part of the same alert but that's another issue.
Thanks!
I have the same problem you described. I think it could be improved if BI didn't use &flag=0 to cancel an alert, but instead use a dedicated tag. Meaning, it could work like this instead...
&flag=1 would add a flag to the alert
&flag=0 would remove the flag from the alert
and then use a separate command like...
&valid=0 would cancel the alert
&valid=1 would remove the "cancel" (mark it confirmed)
This would allow AI Tool to confirm or cancel an Alert in BI, but also allow it to "change its mind" and toggle the Alert's status based on what's found in the next image, as long as it's during the current triggered state.
So in your example, the first image only has a small portion of the car visible so AI Tool finds nothing relevant and would fire the cancel URL (which includes &valid=0) to cancel the alert in BI. But then AI Tool processes the second image with the entire car visible in the frame, so this time AI Tool would fire the trigger URL (which includes &valid=1) so it would no longer be marked "Canceled" in BI. This avoids having an alert that's marked as both flagged and canceled due to multiple images like you described.
BI could achieve the same thing with the current "flag" workflow if the states were mutually exclusive, meaning both "flag" and "canceled" couldn't be active at the same time. However, I like using flags for other purposes, so that's another reason to use a dedicated tag that doesn't rely on flags.
I still have a strange issue with the mask though, when I draw anything the image zooms in and I can't zoom back out to draw more masking
