@smiticans - You get a pushover email address that can be used to send pushes to the pushover app, so you would simply put that email address into the UPSs.
@smiticans - You get a pushover email address that can be used to send pushes to the pushover app, so you would simply put that email address into the UPSs.
https://api.pushover.net/1/glances.json -s --form-string "token=REDACTED" --form-string "user=REDACTED" --form-string "text=hello world"
Yeah but are the pushes coming from the API or pushover email option?
I use only the API option, and I see this on occasion as well… i‘d estimate 1-5 times every 100 notifications… and it appears to be device-dependent.Has anyone noticed the images not coming through sometimes. Just seemed to start happening last night and today... Weird....
I use only the API option, and I see this on occasion as well… i‘d estimate 1-5 times every 100 notifications… and it appears to be device-dependent.
For example, it just happened on a notification from a script and the image was MIA on my Android device, but arrived just fine on an iPhone and my iPad.
Interesting!@jaydeel do you know how I would generate an emergency priority alert 2 so that it keeps ringing until read? I have successfully trigger a priority one alert by adding --form-string priority=1 but the emergency alert requires retry and expire parameters as well.
https://api.pushover.net/1/messages.json -s --form-string "token=YOUR_TOKEN_HERE" --form-string "user=YOUR_USER_KEY_HERE" --form-string "message=priority #1 message<br>(should be red)" --form-string "html=1" --form-string "priority=1"
--form-string "priority=1"
https://api.pushover.net/1/messages.json -s --form-string "token=YOUR_TOKEN_HERE" --form-string "user=YOUR_USER_KEY_H[ICODE]ERE" --form-string "message=PRIORITY #2 message<br>Requires 2 parameters:<br>1) 'retry=sec' [at least 30] sec , and <br>2) 'expire=sec' [less 3 hrs]" --form-string "html=1" --form-string "priority=2" --form-string "retry=30" --form-string "expire=300"
--form-string "priority=2" --form-string "retry=30" --form-string "expire=300"
--form-string "sound=MY_ANNOYING_SOUND"
https://api.pushover.net/1/receipts/YOUR_RECEIPT_HERE.json?token=YOUR_TOKEN_HERE
{
"status":1,
"acknowledged":0,
"acknowledged_at":0,
"acknowledged_by":"",
"acknowledged_by_device":"","
last_delivered_at":1652391742,
"expired":0,
"expires_at":1652391952,
"called_back":0,
"called_back_at":0,
"request":"5290df0d-491c-409e-afa0-cb65927630b1"
}
{
"status":1,
"acknowledged":1,
"acknowledged_at":1652391793,
"acknowledged_by":"YOUR_USER_KEY",
"acknowledged_by_device":"galaxy-s21",
"last_delivered_at":1652391772,
"expired":0,
"expires_at":1652391952,
"called_back":0,
"called_back_at":0,
"request":"1763f824-7d7e-4750-b1aa-e531a460759a"
}
No to repeating a sound. Yes to uploading alternate sounds.The pushover alert tones are very short. Is there a way to get them to keep ringing the entire time or say 10 seconds? Would uploading a 10-30 second alert tone work?
For whatever reason on my Blue Iris system the space exists in my path. So it works for me. Regardless, I’ve gone ahead and edited the op, as this may be causing others trouble.(btw the code in the op still has the space between "Blue Iris" in the path which wont work unless changed to blueiris with no space)
-F "attachment=@D:\BlueIris\Alerts\&ALERT_PATH"
I'm just checking in to see if any workarounds were ever discovered for the "database compaction leading to dead links" issue were ever found. I am sort of "revisiting" this Pushover notifications subject, after spending some time with using the (frankly awful) official Android BI app. UI3 is so vastly superior, I wish I could use it all the time, and with working links directly from notifications. This works great, but I am trying to get away from having to manually run the database maintenance (which breaks the links), or automatic, which will do the same thing daily, etc...This is one of the reasons I like having the hyperlink in the message... even if the notification image is MIA, can still get the alert jpg.
(that is, until the database is compacted; when this happens all the hyperlinks go stale because the alert database pointers are rebuilt).