Need help setting up BI5 text alerts.

Yes BI has a log file. Go to the Blue Iris Status. You probably have to check the log to file box to get more details and then pull up the .txt files.

I don’t think the logfile includes any entries for Blue Iris Actions

However, you can create your own log file using the ‘Run a program or write to a file’ action.

For an example, see the screenshot below. Add this action to the same action set as the curl action.

This won’t tell you if the curl action failed, but it will show the curl command string as attempted, including expanding any macros.

If you want to try this:
1. Edit the file path to your liking.
2. Add the curl action’s Parameters field text to this action’s Parameters field. Be sure to terminate it with ‘\n’ to create new lines.



EDIT 5/19: I'm now using a Parameters string like the following. This provides a time stamp for each line in the log file - making it more useful.

What do you mean terminate it with ‘\n’ to create new lines.?

Does this make it clearer?


otherwise the action will append each event to a single line In the fille.

EDYY said:

What do you mean terminate it with ‘\n’ to create new lines.?

Click to expand...

Instead of a continually running single line like this, the \n will break the line where inserted.

i.e, :

Instead of a continually running single line, the \n
will break the line where inserted like this

@jaydeel the curl command works from a cmd prompt as long as I don’t add the -F

I am not getting any temp*.jpg files in my alerts folder.

Blue Iris 5.8.4.5

[@jaydeel the curl command works from a cmd prompt as long as I don’t add the -F

I am not getting any temp*.jpg files in my alerts folder.

Blue Iris 5.8.4.5

Click to expand...

This happens when the attachment file does not exist.

I don’t see the actual command are trying to use from the cmd prompt, so it’s not possible for me to debug it.
Here are some scenarios…

1. Your file path contains a Blue Iris macro (macros expand only when used from Blue Iris actions)
   -F "attachment=@D:\BlueIris\Alerts\&ALERT_PATH"
2. Your file path has an errant space character (e.g., between ‘Blue’ and ‘Iris’)
   -F "attachment=@D:\Blue Iris\Alerts\DW1.20240208_160000.2019036.5-0.jpg"
3. Your argument is lacking the ‘@‘ character
   -F "attachment=D:\Blue Iris\Alerts\DW1.20240208_160000.2019036.5-0.jpg"

Are you sure the temp*.jpg files are not being created? If you are monitoring the Alerts folder using File Explorer, it will not refresh fast enough. Try using the utility FileChangesView (download).