Are you using the 'device' argument in the API call?
--form-string "device=YOUR_PUSHOVER_DEVICE_NAME(S)_HERE"Send Pushover notifications with pictures and hyperlinks
- Thread starter jaydeel
- Start date
Yep I am, that was the problem. Working now.Forgot all about that.
Thank you jaydeel as always!
MIchael
Hopefully you don't have to edit the 'On alert' actions for multiple Profiles for multiple cameras. That can become quite tedious (and error prone).
Forgot all about that.
Thank you jaydeel as always!
MIchael
This is why I use macros to the store the value of the 'device' argument (and Push credentials, and 'sound').
You just change the macro value in the Registry, then you're done!
This is covered at the end of post #1 (section Future Proofing).
Last edited:
So I've just tried to get this working on my BI install and nothing seems to be happening when I try the test via the cmd.
Running on Windows 11, curl 8.13.0, BI 5.9.9.64
This is the parameter field details. Note I've created the reg keys manually as standard String Values (ala REG_SZ).
-s --form-string "token=%996" --form-string "user=%997" --form-string "message=<b>&CAM</b> &MEMO" -F "attachment=@C:\BlueIris\Alerts\&ALERT_PATH" --form-string "device="%998" --form-string "sound=%999"
When I try the cmd line test, it simply does nothing at all. No errors, no noti nada. Just goes back to the prompt. I tried doing it directly, with replacing the macro numbers with the actual tokens and still nada.
Doing a test on the Pushover website works fine so my mobile can receive the notification no issues, just nothing from my server. Adding --verbose doesn't do anything either.
Any ideas on why it doesn't do anything at all??
Running on Windows 11, curl 8.13.0, BI 5.9.9.64
This is the parameter field details. Note I've created the reg keys manually as standard String Values (ala REG_SZ).
-s --form-string "token=%996" --form-string "user=%997" --form-string "message=<b>&CAM</b> &MEMO" -F "attachment=@C:\BlueIris\Alerts\&ALERT_PATH" --form-string "device="%998" --form-string "sound=%999"
When I try the cmd line test, it simply does nothing at all. No errors, no noti nada. Just goes back to the prompt. I tried doing it directly, with replacing the macro numbers with the actual tokens and still nada.
Doing a test on the Pushover website works fine so my mobile can receive the notification no issues, just nothing from my server. Adding --verbose doesn't do anything either.
Any ideas on why it doesn't do anything at all??
This argument has a misplaced double-quote. Remove the 2nd one.
--form-string "device="%998"
thanks for pointing that out.Update. OK I managed to get it working via the cmd prompt. For reference, I made the mistake of using the specific command mentioned as is, complete with the Blue Iris macro Alert path!
Once I replaced &ALERT_PATH with the specific filename, the command worked fine.
Only issue now is that it doesn't work with proper alerts via BI. I currently have both BI push notifications and a Run Action for Pushover enabled for the camera.
If I walk in front of the camera, I get the BI notification eventually but nothing from Pushover. It's like the BI &ALERT_PATH doesn't resolve properly. Is there a way to check this and see what it is set to?
Update #2
OK managed to get it mostly working i think. Seems like it didn't like using the custom macros for the token and user values. Replacing those with the actual values and removing the unneeded bits like devices and sounds, it finally resolved the alert folder/file and seems to be working now.
Tried the extra alert to add it to the BI log but that still doesn't work so some issues remain
Last edited:
Try my msg.exe trick to view live macro values from Blue Iris actions.
Feel free to DM your problematic Action Parameter field entries. It's probably just another syntax issue.
Managed to get it working for the most part. It's a basic set up at the moment where the only thing that works is a simple Pushover message with an image. This is mainly what I wanted though so anything else is just gravy
Would be nice to get the logging to BI to work though. This is the URL string I have in the field for the 'Configure Web Request or MQTT' alert but it never works. I added the username and password but not sure if it's needed or not
INTERNAL_IP&PORT/admin?log=pushover%%20notification%%20attempted:%%20&CAM%%20[&MEMO]&level=0&user=USERNAME&pw=PASSWORD
I just tested this Action and code from a Preset 'On call' Action. It works just fine. Here's an example:Managed to get it working for the most part. It's a basic set up at the moment where the only thing that works is a simple Pushover message with an image. This is mainly what I wanted though so anything else is just gravy
Would be nice to get the logging to BI to work though. This is the URL string I have in the field for the 'Configure Web Request or MQTT' alert but it never works. I added the username and password but not sure if it's needed or not
INTERNAL_IP&PORT/admin?log=pushover%%20notification%%20attempted:%%20&CAM%%20[&MEMO]&level=0&user=USERNAME&pw=PASSWORD
In this context, the
&MEMO macro is blank because the preset action was not triggered by an alert.You don't need the credentials if you have an entry like
^192.168.1.* in Settings > Web server > Advanced > Limit access by IP address.Below is a screenshot showing my preset configuration, and also my actual entry in the 'Configure Web Request' action:
192.168.1.3:8600/admin?log=pushover%%20notification%%20attempted:%%20&CAM%%20[&MEMO]&level=999(For readers who are not aware, the double percents
%% are required In Blue Iris Actions to generate an actual percent character.)
Last edited:
OK I see where I went wrong there as I had the log alert in the main Alert tab not the PTZ Preset one. Adding it there got it sort of work. Though I had to have in both main Alert and the PTZ Preset.
I added in the IP to the Web Server settings as mentioned as well so removed the username/password from the url.
Thanks heaps for the assist with this
Side note, I don't have the Level column in my logfile view in BI at all either and can't find any settings to change it. Is it only in the actual file itself?
Sorry, I did not mean to imply that the Preset action was required. I used it only as a test vehicle, as I sometimes find presets more convenient for testing actions vs the Alert Action Set. The main reason is that I can test actions on-demand, instead of getting up and walking in front of the camera to trigger the action.
Icons replace the level number in the Blue Iris messages log. Blue Iris pre-defined level values (see the list below) have icons. Custom level values do not.
I like to use custom values because it improves filtering when inspecting a logfile. Ken told me once that any value over 10 was safe to use, and that there was no maximum value. For example, I use '911' to flag serious messages for some of my applications.
Pre-defined logfile level numbers include:
0=informational, 1=warning, 2=error,
3=triggered/re-triggered/alerted,
4=disk allocation OK; 'signal restored'
7=new version available,
10=login/logout
NOTE: This list is self-generated (not provided by Ken) and may not be exhaustive; it's just a collection of entries I've observed.
Last edited:
Thanks for clarifying. It's working now with the PTZ Preset and the Alert one so I'm happy to leave it as is
Actually I've just run into an issue with this config.
With the global webserver set with the 'Limit access by IP' and the parameter ^192.168.1.* added, I can no longer connect to the web client from another PC on the same network. I get a HTTP Server 503 error which seems like the logfile add Alert action locks the LAN webserver port and prevents any other access. I can access via the android app though so external access works fine. It would seem like the Alert action doesn't release the port after sending the message (or keeps it open for ages).
Removing the '^192.168.1.*' value makes the webclient work again on LAN but then the Add to Log Alert action doesn't work.