Send Pushover notifications with pictures and hyperlinks

Let's try these two things first:
  1. What's the typical size of your camera's alert JPGs? If over 2.5MB, then they are rejected by the Pushover API. If this appears to be the issue, then the solution might be my pushover_resize script.
  2. If not #1, then try checking setting 'Wait for process to complete' on the 'Run a program' action in the 'On alert' action set.
Ok - just confirmed through multiple alerts that selecting the setting 'Wait for process to complete' did not resolve my issue.
 
Check out these posts for background on Blue Iris' short-lived temporary JPGs:
first
second

They matter if you are NOT saving high-res JPGs or creating AI markup images.
Thanks - I am creating high res JPGs and I am creating the AI markup images, so seems that doesn't apply to me then?

1730759419368.png
 
Ugh. I've just parsed your command syntax. Everything appears to be in order.


Correct.
I looked at the first post that you linked (here) where the user was having a similar issue, but I don't think that applies, since I have the defaults checked on the record tab of this particular camera (and all my other cameras sync with this one). Please let me know if that's not correct though.

1730759666289.png
 
Try my 'msg.exe' trick... Insert the following 'Run a program' action before the pushover curl action.

This should pop up a window that shows the expanded macros, so that you can confirm that the JPG path in the curl command is as you expect.

Here's the 'Parameters' field text * /TIME:5 DB=&ALERT_DB, PATH=&ALERT_PATH
Increase the TIME value if you want the window to stay open longer.

1730759724011.png
 
Last edited:
  • Like
Reactions: JNDATHP
Thanks - just tested and it seems to be coming back correctly

View attachment 206395

When I look in the alerts folder, the jpg file in this PATH is the correct JPG.
Very good.

As an experiment, you might try removing the argument --form-string "device="%998"
Maybe it's expanding to a funky value that's screwing up the command syntax.

EDIT - you can inspect this macro in the msg.exe command as well.
 
  • Like
Reactions: TonyR
Very good.

As an experiment, you might try removing the argument --form-string "device="%998"
Maybe it's expanding to a funky value that's screwing up the command syntax.

EDIT - you can inspect this macro in the msg.exe command as well.
Bingo! that was it! I removed that and it works.

I will do some more testing later tonight as to what the issue actually was, but for now I'm just glad it's working. Thanks so much!
 
  • Like
Reactions: jaydeel
Well I broke down and tried something new.
I used the description at the beginning of this post and used word pad to paste my " parameters" string together with my API and USER key, and Device name.
I put the App on my iphone.
I also did a FAFO with the Windows App on my desktop PC, ,,,, unneeded as i found out from @wittaj.
Anyway, I hit the lightning bolt test icon, and it sent a notification to my phone.
Yippee.

Im running CP AI on a couple cams. so it asked for an AI alert type, so I put Car, Person
I'm just trying it out on the LPR cam 1st.
I get about 500 alerts or more a day on the counter in the BI mobile app. As a commercial vehicle operator, I cannot have my phone blowing up with pushover notifications out the ass.
Even if I get the notification, I cannot use my phone to retrieve it while in motion. So I have all notifications silenced on my phone.

FFS my old Nightowl DVR, was horrid, When it did work ( the App) I think we bogged down the local Verizon tower with 100 notifications to 2 phones every time the wind blew. I think they fuckin blocked it after awhile as a DDoS Attack LOL.
The Amcrest NVR was no better. I had to turn off notifications because my phone was blowing up all day.
Hopefully this will quell the clutter.
thanks again
 

Attachments

  • IMG_4087.png
    IMG_4087.png
    1.7 MB · Views: 15
  • Like
Reactions: looney2ns