No known issues with Action set 'Run a program' actions. Confirm the Blue Iris 6 service is running with your account (not local service).
Last edited:
Send Pushover notifications with pictures and hyperlinks
- Thread starter jaydeel
- Start date
I am using notifications sent to Pushover as well, and those notifications worked with the new version without any changes.
It's been a while since I've played with this - a testament to how well it's worked for me over the last year or two. I recently went to add a couple more cameras to the pushover notification and I'm struggling to get the custom sound to come through on the android app. All is working as it should except the sound is the default pushover ding sound. My script is a c/p from a working camera, using the parms for the new cam. I'm getting proper image and alert text, but only the default app sound.
If I choose a built in sound (i.e. bugle, bicycle, tugboat, etc) those do come through correctly. But none of the uploaded custom sounds will play on my cameras. Did something change with the pushover API?
If I choose a built in sound (i.e. bugle, bicycle, tugboat, etc) those do come through correctly. But none of the uploaded custom sounds will play on my cameras. Did something change with the pushover API?
I got it resolved thanks to Grok of all places 
I had it scan this entire thread and focus on my last post. It determined that my mid-grade phone (moto stylus g 2024) has known issues with prioritizing the audio pathway for custom audio vs. built-in sounds and adding the flag
to the script should resolve. Wouldn't you know it, it worked!
So if anyone is struggling to get custom audio to push through, but built-in sounds do work, consider adding that high-priority flag!
I had it scan this entire thread and focus on my last post. It determined that my mid-grade phone (moto stylus g 2024) has known issues with prioritizing the audio pathway for custom audio vs. built-in sounds and adding the flag
Code:
--form-string "priority=1"to the script should resolve. Wouldn't you know it, it worked!
So if anyone is struggling to get custom audio to push through, but built-in sounds do work, consider adding that high-priority flag!
I have been successfully using Pushover and this method for well over three years, but noticed that (starting roughly six months ago) I no longer receive the "&MEMO" portion of the alert. I haven't changed the formatting of my Pushover curl command at all over this period, but I don't receive the details of the type of alert (AI confidence percentages, objects detected, etc). It's not really a big problem, but I'd like to know what changed and what I might be able to do about it. Did Ken possibly change something that has gone unnoticed by most users?
My Pushover curl command for reference:
My Pushover curl command for reference:
Code:
https://api.pushover.net/1/messages.json -s --form-string "token=REDACTED" --form-string "user=REDACTED" --form-string "message=<b>&CAM</b> &MEMO <a href='&LAN/alerts/&ALERT_DB?fulljpeg'>Hi-Res</a> <a href='&LAN/ui3.htm?rec=&ALERT_DB'>UI3</a>" --form-string "html=1" -F "attachment=@D:\BlueIris\Alerts\&ALERT_PATH"I setup pushover notifications maybe a year or so ago and it's been working great. In the last 6 months or so, I don't see the image unless I swipe down to refresh in the app (Sometimes twice).
Any ideas?
Any ideas?
I'm not seeing this, and for each alert I use execute both a curl run-a-program action (fast) and a slower Powershell run-a-program action (using my GIF tool).
Your syntax looks fine. Here's yours compared to one of mine (I'm showing them multi-line because I think it makes it easier to spot errors.)
Code:
YOURS...
https://api.pushover.net/1/messages.json
-s
--form-string "token=REDACTED"
--form-string "user=REDACTED"
--form-string "message=<b>&CAM</b> &MEMO <a href='&LAN/alerts/&ALERT_DB?fulljpeg'>Hi-Res</a> <a href='&LAN/ui3.htm?rec=&ALERT_DB'>UI3</a>"
--form-string "html=1"
-F "attachment=@D:\BlueIris\Alerts\&ALERT_PATH"
MINE...
https://api.pushover.net/1/messages.json
-s
--form-string "token=%995"
--form-string "user=%997"
--form-string "message=<b>&CAM</b> &MEMO <a href='&WAN/alerts/&ALERT_DB?fulljpeg'>JPG</a> <a href='&WAN/ui3.htm?rec=&ALERT_DB'>UI3</a>"
--form-string "html=1"
--form-string "device=%991"
-F "attachment=@D:\BlueIris\Alerts\&ALERT_PATH"
--form-string "sound=%992"
--form-string "priority=2"
--form-string "retry=30"
--form-string "expire=300"
--form-string "tags=a=BI,c=&CAM,g=Front"Maybe it matters that I've abbreviated my ONVIF descriptions to short names like "LD/C" because the &MEMO field in the database is limited to max length of 35 characters (for full explanation, see this post).
Hmm...yes, in situations (certain cameras and/or schedules) where I'm using ONVIF triggers exclusively, the MEMO portion does come through on the Pushover alert, but not at all on camera schedules that use a combined BI motion (with the new built-in AI) alongside ONVIF triggers, or even on the same cameras when using a schedule that exclusively uses the BI motion with AI confirmation. Yeah, I know...a complicated and probably rare setup. The thing is, at night, it's hard to beat the amazing capabilities of Dahua 5442 cameras (S2) and IVS rules, but they still miss some things, particularly animals, thus my desire to utilize both methods, at least at night.