Send Pushover notifications with pictures and hyperlinks

I also tried the message test shown above and this is the result

DB=@-1, PATH=temp_Drive_0.jpg
 
I'd suggest removing these unused entries as well:
--form-string "device=YOUR_PUSHOVER_DEVICE_NAME(S)_HERE"
--form-string "sound=YOUR_PUSHOVER_SOUND_HERE"
 
Sorry user is there - I deleted it when I deleted the pertinent info

-s --form-string "token=xxxxxxxxxxxxxxxxxxxxxxxx" --form-string "user=xxxxxxxxxxxxxxxxxxxxxxxxxxxx" --form-string "message=<b>&CAM</b> &MEMO <a href='&WAN/alerts/&ALERT_DB?fulljpeg'>Hi-Res</a> <a href='&WAN/ui3.htm?rec=&ALERT_DB'>UI3</a>" --form-string "html=1" --form-string "device=YOUR_PUSHOVER_DEVICE_NAME(S)_HERE" --form-string "sound=YOUR_PUSHOVER_SOUND_HERE" -F "attachment=@I:\Alerts\&ALERT_PATH"
 
George M said:
I also tried the message test shown above and this is the result

DB=@-1, PATH=temp_Drive_0.jpg
Click to expand...
Is 'Drive' the short name of the camera you are testing?

Blue Iris creates a temp JPG when you are not saving hi-res JPGs (Alert tab) or using 'Burn mark-up mark-up on alert images' (unchecked on the AI configuration tab).

These temp files are short-lived; therefore the URL links using them are ephermeral. They will not work, or will show the wrong image immediately after a new alert is created.

More here, here, and here.

EDIT: The 3rd link above has this 'paraphrased' suggestion ... In the Run a program/Write to file Alert action, try checking 'Wait for process to complete (up to 30 seconds)'. This prevents the action set from completing while the curl command is still transmitting the temporary image to the push service.
 
Last edited:
Drive is the cam name. I'll read the other links
I am saving jpgs in a Jpgs folder. Should I use that instead of the Alerts folder?
 
George M said:
Drive is the cam name. I'll read the other links
I am saving jpgs in a Jpgs folder. Should I use that instead of the Alerts folder?
Click to expand...
if you mean this setting, these JPGs are stored in the Alerts folder.

1736817551433.png


You should use the path is assigned the Alerts folder in the Settings > Storage folder...

1736817692299.png
 
OK, thats I;/Alerts
I was also saving jpgs in another folder on the Record page. I guess I don't need to do that..
 
So have you tried this yet?

In the Run a program/Write to file Alert action, try checking 'Wait for process to complete (up to 30 seconds)'. This prevents the action set from completing while the curl command is still transmitting the temporary image to the push service.​
 
I did check that.
I appreciate your help on this. I'm being yelled at because the family is going to dinner. I'll have to leave but maybe I can connect with you tomorrow.
 
I was having issues with alerts being sent after changing the path to where the alerts are being saved. While typing this up I now see that I should have looked at this first... however...

If alerts should be workings, but aren't through PushOver, I was able to test via cmd.exe and then deleting arguments until I got a response back there. Essentially, my path to the image was incorrect as a SPACE was in the original path, but not the new path... Deleting the path from the cmd.exe test showed it very quickly. Hope this helps someone else.
 
  • Like
Reactions: jaydeel
MakingCoffee said:
I was having issues with alerts being sent after changing the path to where the alerts are being saved. While typing this up I now see that I should have looked at this first... however...

If alerts should be workings, but aren't through PushOver, I was able to test via cmd.exe and then deleting arguments until I got a response back there. Essentially, my path to the image was incorrect as a SPACE was in the original path, but not the new path... Deleting the path from the cmd.exe test showed it very quickly. Hope this helps someone else.
Click to expand...
I realize the original post is dense, so all reminders help. :p

Excerpt from the API Syntax Reference Guide in post #1.
1737402126434.png
 
  • Like
  • Love
Reactions: looney2ns and MakingCoffee
Hi, I'm testing Pushover notifications, and based on my observations, executing the curl command via a Blue Iris action does not always guarantee successful execution when sending an attachment using the &ALERT_PATH macro.

The issue is that, paradoxically, Blue Iris operates too quickly and call the curl command before the alert image file (&ALERT_PATH) is actually available in the filesystem, since its creation takes some time. As a result, every so often, the curl command fails with the error: curl: (26) Failed to open/read local data from file/application The worst part is that we won’t even be aware of this failure because Blue Iris does not log the output of executed commands.

The issue comes down to a few hundred milliseconds between the creation of the image file and the execution of curl. In 99% of cases, this works fine, but I’ve personally experienced situations where we can’t be certain—eventually, a notification just won’t go through.

For now, I’ve worked around this by calling a .bat script first. The script ensures that the alert image file (from &ALERT_PATH) is available in the filesystem before Blue Iris executes curl commands. However, I don’t think this is the best solution. Ideally, Blue Iris itself should verify that the files exist before triggering the command.

Has anyone else encountered this issue? Do you have any better solutions?"
 
kredka1410 said:
Hi, I'm testing Pushover notifications, and based on my observations, executing the curl command via a Blue Iris action does not always guarantee successful execution when sending an attachment using the &ALERT_PATH macro.

The issue is that, paradoxically, Blue Iris operates too quickly and call the curl command before the alert image file (&ALERT_PATH) is actually available in the filesystem, since its creation takes some time. As a result, every so often, the curl command fails with the error: curl: (26) Failed to open/read local data from file/application The worst part is that we won’t even be aware of this failure because Blue Iris does not log the output of executed commands.

The issue comes down to a few hundred milliseconds between the creation of the image file and the execution of curl. In 99% of cases, this works fine, but I’ve personally experienced situations where we can’t be certain—eventually, a notification just won’t go through.

For now, I’ve worked around this by calling a .bat script first. The script ensures that the alert image file (from &ALERT_PATH) is available in the filesystem before Blue Iris executes curl commands. However, I don’t think this is the best solution. Ideally, Blue Iris itself should verify that the files exist before triggering the command.

Has anyone else encountered this issue? Do you have any better solutions?"
Click to expand...
This is a known problem and there is a fix. See here and here.

Basically you need to check the option 'Wait for process to complete' in In the Alert's 'Run a program' action.

This was introduced ~8/21/2023, so you'll need to be running a version of Blue Iris after this date.
 
You must log in or register to reply here.
Top Bottom