Worked with Ken and found that the trigger URL to override the current image for the SMS is &trigger&jpeg=<PATH>
Found that using
@Chris Dodge AI tool, and the original
@GentlePumpkin, the trigger does not work on sending the image.
If you manually take out the URL that was attempted from the AI log, and put it in the browser it works just fine.
This also only works for the non-MergeImageAnnotations image file, so the original one captured and sent to AI. (not sure why the MergeImageAnnotations one wont work)
I am going to run some PCAPS if I cant find a way to get BI at a higher log level, to see if there is a difference on the receiving of the URL
Thoughts on a possible fix out the w.o log review.
If the merge step could be combined with the copy to file step and make a file in a directory then move to the trigger step.
This way you could just hard code the file being called on the trigger URL rather than a variable.
There could be a timing issue if multiple alerts come in though.
Right now the copy to folder happens after the trigger step is done, so we would not be able to call the copied file for the trigger url
Code:
[14.10.2020, 09:58:02.037]: DetectObjects> 10.13.13.70:89 - (5/6) Performing alert actions:
[14.10.2020, 09:58:02.679]: MergeImageAnnotations> Merged 2 detections in 656ms into image C:\Users\ADMINI~1\AppData\Local\Temp\2\Cam5.20201014_095800883.jpg
[14.10.2020, 09:58:02.684]: CallTriggerURLs> -> trigger URL called: http://XX/admin?camera=Cam1&trigger&jpeg=E:\aiinput\Cam5.jpeg&user=XX&pw=XX, response: 'signal=green profile=1 lock=0 camera=Garage1HD_rtsp '
[14.10.2020, 09:58:02.767]: Trigger> Copying image to network folder...
[14.10.2020, 09:58:02.769]: CopyImage> File copying from C:\Users\ADMINI~1\AppData\Local\Temp\2\Cam5.20201014_095800883.jpg to E:\aiinput\Cam5.jpg
[14.10.2020, 09:58:02.771]: Trigger> -> Image copied to network folder.