Send Pushover notifications with pictures and hyperlinks

Ok - I removed both and tested it in BI, but no dice. It triggered an alert image, and when I used the script in the cmd prompt, it did send the image. Here is the script with your edits: -s --form-string "token=XXXXX" --form-string "user=XXXXXX" --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" -F "attachment=@c:\BlueIris\Alerts\&ALERT_PATH"
 
Last edited:
I tried using the alert with msg.exe. When I use the basic script, I do get the message when I hit "test" - see the picture. But when I put the pushover script after it, nothing pops up, either when I hit "test" or trigger the camera from outside. I even tried inserting a specific, existing .jpg file in place of &ALERT_PATH, but again no message.
Screenshot (6).png
 
The developer (Joshua Stein) has just made two very nice updates to the Pushover Android App (see the screenshot below). Both extend functionality straight from the Android notification tray. The main benefit is that you don't need to open the app to view/manage some notifications!
  1. The first is a bug fix I requested. Now you can once again view GIFs from the Android notification tray.
  2. The second is a new feature I requested. Now you can silence individual repeating Emergency notifications from the Android notification tray.

Version 5.0.7 is currently available only in beta, so you'll need to sign up.
Try clicking this link from your Android device:
Sign in - Google Accounts


1784308793690.png
 
  • Like
Reactions: jrbeddow, anijet and looney2ns
My notifications via curl/pushover stopped abruptly. Was working find last night, tonight no bueno. Even triggering manually on BI nothing. However from PO web console, it does send test message - so I know the app-to-PO-server connection is working. I suspect something in BI is buggered.

ETA: When I enter curl + my string from BI's alert tab, I get no error, no confirmation. Just new command prompt. Interestingly, when I have my Home Assistant trigger BI for a different camera, I get the PO notification.... odd. Time to hunt down the differences.

ETA2: Figured it out... Somehow, maybe with one of the latest updates, my "location" was reset to middle of Kansas. I'm in middle-TN, so that pushed my sunset an hour past actual. BI was in daytime mode, and my alerts don't trigger unless it's night. Doh!
 
Last edited:
  • Like
Reactions: Flintstone61 and TonyR
erkme73 said:
My notifications via curl/pushover stopped abruptly. Was working find last night, tonight no bueno. Even triggering manually on BI nothing. However from PO web console, it does send test message - so I know the app-to-PO-server connection is working. I suspect something in BI is buggered
Click to expand...
The same thing happened to me. I self-host ntfy and I use access tokens to protect things. When my alerts stopped working I suspected a problem with BI but the problem ended up being an expired token. The way I found the issue was by dropping to a command prompt and running a curl command to send a test message. My command didn't work until I updated the access token. Point is that there's more ways to test.

It's been a long time since I used Pushover and I don't remember the syntax but if you can craft a basic curl command to send a small message through Pushover then it would be a good test. The parameters I use in BI contain a lot of variables and they will not work with a curl command at a command prompt.

To test ntfy I used something like

curl -H "Authorization: Bearer tk_5wujmbgstsesmmeqz5mwllbz878s5" -d "This is a test" myntfy.sh/mytopic

It's a basic command with no variables that should work at a command prompt as long as curl is installed, and the result should be a message being sent that reads This is a test. When I ran a similar command on my BI machine it failed until I updated the authorization token. Once the token was updated in BI as well then everything worked normally.

I have no idea what's causing your issue but this is how I diagnosed a similar issue.
 
  • Like
Reactions: looney2ns and erkme73
robpur said:
The same thing happened to me. I self-host ntfy and I use access tokens to protect things. When my alerts stopped working I suspected a problem with BI but the problem ended up being an expired token. The way I found the issue was by dropping to a command prompt and running a curl command to send a test message. My command didn't work until I updated the access token. Point is that there's more ways to test.

It's been a long time since I used Pushover and I don't remember the syntax but if you can craft a basic curl command to send a small message through Pushover then it would be a good test. The parameters I use in BI contain a lot of variables and they will not work with a curl command at a command prompt.

To test ntfy I used something like

curl -H "Authorization: Bearer tk_5wujmbgstsesmmeqz5mwllbz878s5" -d "This is a test" myntfy.sh/mytopic

It's a basic command with no variables that should work at a command prompt as long as curl is installed, and the result should be a message being sent that reads This is a test. When I ran a similar command on my BI machine it failed until I updated the authorization token. Once the token was updated in BI as well then everything worked normally.

I have no idea what's causing your issue but this is how I diagnosed a similar issue.
Click to expand...
Thanks for the thorough and quick reply. I figured mine out (added via edit)... BI had somehow changed my coordinates to middle of Kansas when I'm actually in middle-TN. That pushed my nighttime schedule back by an hour or so. It was pitch black outside, hogs at my trap, and zero notification. I've got my trap notifications starting at sunset. The clue was that BI was still reporting that it was on daytime profile.
 
You must log in or register to reply here.
Top Bottom