Action trigger URLs -> programming a delay after sending each one of them to BI

[balqosz]

Hi VorlonCD!

Is it possible to add a small delay between sending urls to BI?
I'm having problems sending trigger and flagalert=2 commands. If sending them through AITool, BI doesn't mark the alert, it remains without confirmation, until a new alert is sent to BI again... but then again, this new alert keeps without confirmation until a new alert is received... and so on. So the first alert in the list is always without confirmation (not showing it at least until the next alert)

So I tried a simple batch file (.bat) as external program from AItool, and it is working as expected, it flags the alert inmediatly. I show you the batch file content below:

"C:\Program Files (x86)\cURL\bin\curl.exe" "http://127.0.0.1:9955/admin?trigger&camera=mycam&user=####&pw=####"
timeout /t 1
"C:\Program Files (x86)\cURL\bin\curl.exe" "http://127.0.0.1:9955/admin?flagalert=2&camera=mycam&user=#####&pw=####"

As you see, there is a "1 second timeout" between commands. It works. The alert is being flagged almost instantly. Maybe a smaller value works too, perhaps 200ms, I don't know.

Or maybe there is a hidden setting in json file to try?

Thank you!

[johnseybert]

I see this behavior as well and wasn't sure what was going on or how to duplicate it to troubleshoot. Seemed random at times. Good to know you were able to track it down!

[VorlonCD]

So flagalert=2 and trigger both in the same URL doesnt work? What is 2 vs 1? why use 2?

[balqosz]

I was using all in one url, but I was having problems so began to investigate why it was happening.
I saw the same behaviour when sending the url through the web browser. But then, I tried separated urls in the web browser, and it worked. Then the final step was that a small delay was needed, because sending the all-in-one url in two steps without a delay, had the same behaviour as sending one url.

(one url) http://127.0.0.1/....&trigger&flagalert=2 ===? FAIL

(two urls) http://127.0.0.1/....&trigger and then http://127.0.0.1/...&flagalert=2 ===> FAIL

(two urls + delay) http://127.0.0.1/....&trigger / 1 sec delay / and then http://127.0.0.1/...&flagalert=2 ===> OK

Maybe a BI bug?

[aesterling]

I read the info below on page 214 of the Blue Iris help file PDF. Do we know if these commands have changed in a recent release? Or is that unrelated to this problem?

x = 0 mark the most recent alert as canceled (if not previously confirmed).
x = 1 mark the most recent alert as flagged.
x = 2 mark the most recent alert as confirmed.
x = 3 mark the most recent alert as flagged and confirmed.
x = -1 reset the flagged, confirmed, and cancelled states