Spackler
Young grasshopper
- Apr 27, 2018
- 36
- 7
Send Pushover notifications with pictures and hyperlinks
- Thread starter jaydeel
- Start date
Are you sure about the attachment path? Most users don't use Drive C for clips and alerts storage. Is the path missing any space characters?
Better yet, attach a Windows File Explorer screenshot like this:
Better yet, attach a Windows File Explorer screenshot like this:
Last edited:
Spackler
Young grasshopper
- Apr 27, 2018
- 36
- 7
I changed the above code to hide my files but guess it doesnt matter. I changed this code to just add the macros in the code that was sending pictures and still no pictures. I have the HI-Res and UI3 but no picture in the push like when I do it without the macros.
-s --form-string "token=%996" --form-string "user=%997" --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="%998" --form-string "sound=%999" -F "attachment=@E:\BILogs\Alerts\&ALERT_PATH"
This works
-s --form-string "token=sadlkjaslkdfjalkdfj" --form-string "user=sadkjfalksdjfalskdjf" --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=phone" --form-string "sound=bugle" -F "attachment=@E:\BILogs\Alerts\&ALERT_PATH"
Last edited:
For clarity, I've added newlines to your command and compared it to mine. What jumps out is the extra double-quote in the
If this malformed argument came AFTER the attachment argument, the command might of sent a picture.
device= argument.If this malformed argument came AFTER the attachment argument, the command might of sent a picture.
Code:
YOURS...
https://api.pushover.net/1/messages.json
-s
--form-string "token=%996"
--form-string "user=%997"
--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="%998"
--form-string "sound=%999"
-F "attachment=@E:\BILogs\Alerts\&ALERT_PATH"
MINE...
https://api.pushover.net/1/messages.json
-s
--form-string "token=%996"
--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=%990"
-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"Spackler
Young grasshopper
- Apr 27, 2018
- 36
- 7
I am such an idiot. Please forgive me and thank you for your help. I cannot believe I did that.
It happens to us all. API's are really picky about syntax... so it's working now?
Spackler
Young grasshopper
- Apr 27, 2018
- 36
- 7
Yes it is. Thank you so much fo the help. Really is amazing all the push stuff.
I never edit long/complex commands directly in the Blue Iris interface. Instead, I edit & inpect them in a text/code editor, then copy/paste them to Blue Iris. As you discovered, it's easy to overlook typos.
Everything has been working great recently... I get consistent images through pushover using the script. However, over the last few days, i've noticed that the images being sent are not the ones for the triggering event. Instead I'm getting the same static image from hours earlier. What is odd, is that they are not consistent. I might get 3 or 4 images from minutes (or hours) prior, then one or two that are from a current trigger, then the next will be 3 or 4 hours old again.
For example, in the screenshot above, you can see three Pushover time-stamped alerts; 7:28, 7:30, and 7:33. The images, however, reflect 7:10, 7:30, and 7:10, respectively. Something is causing the pushover script to grab images other than the ones that were generated with the actual triggering event.
The result is that most of the images are stale and inaccurate. Has anyone else experienced this? I'm at a loss as to what is causing it. It'd be one thing is they were all the same image, but it seems to get its bearings for a bit, and then revert to the old image.
For example, in the screenshot above, you can see three Pushover time-stamped alerts; 7:28, 7:30, and 7:33. The images, however, reflect 7:10, 7:30, and 7:10, respectively. Something is causing the pushover script to grab images other than the ones that were generated with the actual triggering event.
The result is that most of the images are stale and inaccurate. Has anyone else experienced this? I'm at a loss as to what is causing it. It'd be one thing is they were all the same image, but it seems to get its bearings for a bit, and then revert to the old image.
Yes. For me, the database was damaged or corrupt because I was manually deleting DAT files (I now know better). First try a Compact/Reindex. But you may need to regenerate..
Easy peasy... I should have thought of that myself. I'll just delete and regenerate and see how we fair by morning. Much appreciated.
Well, I was hopeful that the delete/rebuild would resolve this issue but, alas, it did not...
I think there may be a bug in one of the more recent updates. My brother uses email notifications for some of his cameras and has complained that as of late the attached images are also stale. It's less frequent for him, but same issue where an older image is sent instead of the triggered event image.
If this is a server-related issue, I would think others would start reporting it by now, but maybe others haven't updated yet I'm running 5.9.9.55.
I think there may be a bug in one of the more recent updates. My brother uses email notifications for some of his cameras and has complained that as of late the attached images are also stale. It's less frequent for him, but same issue where an older image is sent instead of the triggered event image.
If this is a server-related issue, I would think others would start reporting it by now, but maybe others haven't updated yet I'm running 5.9.9.55.
Attachments
Not yet, but primarily because I'm not good at articulating the problem. And I feel like I'm wasting his time. It's not super critical and I assume that if it is a systemic problem someone will say something on my behalf 
I just sent Ken a "for a colleague" inquiry, asking if he's got any ideas... it seems he's looking at support emails this morning - he just responded to my .55 pssible bug message.Not yet, but primarily because I'm not good at articulating the problem. And I feel like I'm wasting his time. It's not super critical and I assume that if it is a systemic problem someone will say something on my behalf
Ken asks...
Is there a chance he is sending these from the Trigger tab instead of the Alert tab action set?
Thanks for the effort. No, these are being sent from the alert tab, just as described in your write up...
In fact, I didn't know you could push notifications/emails from the trigger tab.