Send Pushover notifications with pictures and hyperlinks
- Thread starter jaydeel
- Start date
Another simpler idea... stop the BI server, then try manually finding and removing any stubborn temp*.jpg files in the Alerts folder... Before you delete them, you might check their properties/attributes to determine if there's anything unusual/unexpected... Blue Iris should update the database when you restart the service.
If you cannot find any old temp*.jpg files, then this a sign that Blue Iris is managing them as expected. They should not persist after the Action set is fully executed.
Also, have I asked if you've enabled 'Wait for process to complete (up to 30 seconds)' in the Run a program action? This setting ensures that the fresh temp*.jpg persists for the duration of the Pushover run action. More here.
Last edited:
Thanks for the detailed instructions and explanation. I went the route of stopping the service and examining the alerts folder. In it, I found no temp in any of the file names.
The naming syntax was odd to me, with each file name having a suffix of -1.jpg or -3.jpg:
I'm not quite sure what would cause that. I've opened several of these files and verified that the images are all unique and the time stamp overlay on the image matches the file name.
I DID NOT have the "wait 30 seconds" option enabled on the Run Action dialog box. I just enabled it for both cameras and both users who are receiving these images. I should know by morning whether the duplication/stale images have been resolved.
I will report back in the AM. Thanks!
ETA: I verified that I have enough storage space under the alerts folder. I'm at 100GB and auto delete after 2 days - so no chance I would come close to running out of room.
The naming syntax was odd to me, with each file name having a suffix of -1.jpg or -3.jpg:
I'm not quite sure what would cause that. I've opened several of these files and verified that the images are all unique and the time stamp overlay on the image matches the file name.
I DID NOT have the "wait 30 seconds" option enabled on the Run Action dialog box. I just enabled it for both cameras and both users who are receiving these images. I should know by morning whether the duplication/stale images have been resolved.
I will report back in the AM. Thanks!
ETA: I verified that I have enough storage space under the alerts folder. I'm at 100GB and auto delete after 2 days - so no chance I would come close to running out of room.
I should have asked this earlier. It might explain why you are seeing the TEMP file when using the msg.exe trick... Do you use multiple profiles? If so, make sure the following setting is enabled for all of them. It is Profile-dependent.
For managed storage folders in Blue Iris, most of us disable 'Limit clip age'. The oldest files are then automatically deleted as space is needed. And most of the allocated space is used. You can monitor this in the log file.
Last edited:
I know - and that's how I have it set up for new clips. However, I have 64 cameras that all record alert images. That results in massive number of alert images which I felt affected stability - so I trimmed it an wanted to make sure there was no added workload.
Wow! That's the maximum number of cameras supported by Blue Iris.
Have you verified that the Alerts folder, which I believe you said you've allocated 1GB, even contains 2 days of alert JPGs?
Last edited:
There are two days of jpgs in each camera folder, but only for the cameras for where I specified to save JPG. That's only a handful of cameras at this point, since most save to the database. I have the path for the jpgs set to prefex a folder for each camera to keep the number of files in a given folder limited to a single camera.
Yeah, I know. I have way more than 64 cameras, but Ken said it's a definite hard limit. I even offered to pay him a King's ransome to make it higher... But no go. I'm debating whether I should setup another BI machine, but the logistics of having them integrated on one display is what's keeping me from trying.
For now I have to delete (not just disable) the cameras I'm least likely to use.
Interesting. Your screenshot from the msg.exe trick (below), does not show a subfolder prefix on the TEMP JPG (i.e., \camera\temp*.jpg).
Probably intentional so there's never a question where it's located.
Have you verified that the TEMP JPGs are actually created?
I found a way to monitor this in real time - using NirSoft utility FolderChangesView - see this link for the details.
Probably intentional so there's never a question where it's located.
Have you verified that the TEMP JPGs are actually created?
I found a way to monitor this in real time - using NirSoft utility FolderChangesView - see this link for the details.
If I monitor the directory for the given camera when I do a "trigger now", I can immediately see the new file appear in that directory - but it's not a temp. It's the full .jpg file that remains unchanged well after the trigger has resolved.
The top file is the one it created. What's interesting is that the file nomenclature shows *-0.jpg on some, *-1.jpg on another, and *-3.jpg on yet another. I wonder if that suffix is in place of the "temp" name. Either way, the file names do not change - even after a refresh.
The top file is the one it created. What's interesting is that the file nomenclature shows *-0.jpg on some, *-1.jpg on another, and *-3.jpg on yet another. I wonder if that suffix is in place of the "temp" name. Either way, the file names do not change - even after a refresh.
Interestingly, my record tab shows "use default" for the jpg path, yet each image is in it's own camera folder. My video clip path is not default, and I explicitly have &CAM\&CAM.%Y%m%d_%H%M%S. Without the double &CAM, it will put all clips in one directory. So "use default" for jpgs must pull from the custom folder I'm using for video...
z