Send Pushover notifications with pictures and hyperlinks
- Thread starter jaydeel
- Start date
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"
--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"
-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"
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?
I am saving jpgs in a Jpgs folder. Should I use that instead of the Alerts folder?
if you mean this setting, these JPGs are stored in the Alerts folder.
You should use the path is assigned the Alerts folder in the Settings > Storage folder...
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..
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 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.
MakingCoffee
n3wb
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.
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.
I realize the original post is dense, so all reminders help.
Excerpt from the API Syntax Reference Guide in post #1.
THANK YOU! I cant tell you how many times I went over the syntax line by line --- I never notices the @ before the alert path. That was it. Now I'm getting the alert JPGs.I realize the original post is dense, so all reminders help.
Excerpt from the API Syntax Reference Guide in post #1.
View attachment 212505
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:
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?"
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?"
Sybertiger
Known around here
Well this is weird, BI stopped sending pushover alert today for some reason. Still within my 10,000 free limit. A test directly from the pushover.net website works. Any clue where the issue may be? No changes made to BI or the computer in over a year. I've been using pushover for alert successfully for 3 years.
Are you using the curl command method in a Blue Iris run-a-program action? Or one of my Powershell scripts?
EDIT: I just simultaneously tested three methods (curl + bi_gif_tool.ps1 + pushover_resize.ps1). All are working at my end. On multiple cameras.
Last edited:
Sybertiger
Known around here
Using the curl method. Have not changes anything regarding how this works in forever. It just stopped working all of a sudden. I can see BI+DS are processing the alerts as normal. It's not like that other problem when DS times out and therefore no alert is sent.
Is it possible that the image size has been borderline and today is too large? ... when I get a minute, I'll check the API for any changes.