Alerts tab

Details the major steps to configure and deploy Blue Iris.
Start with Onboarding Checklist article.
1. Setup Windows to work well with Blue Iris.
2. Connecting IP cameras.
3. Setting up Storage and Recordings.
4. Configuring your home or office network for Remote Access via a web browser or the phone apps.
5. Creating Triggers and Alerts.
6. Setting up AI with DeepStack
7. Creating Schedules and Profiles
Post Reply
Posts: 90
Joined: Thu Jul 11, 2019 9:52 pm

Alerts tab

Post by varghesesa »


This article goes under the covers of the Alerts tab. This article / webinar is part of the Triggers / Recordings / Alerts series where we go deep into one of the most popular features of Blue Iris (BI), the ability to define motion triggers -> instruct BI to record when cameras trigger -> send corresponding alerts.

If you prefer to listen instead of read, watch the webinar associated with this article, The Alerts Tab webinar.

We also have an overview "Triggers and Alerts webinar" for those who are new to BI. See our onboarding playlist in the YouTube channel.

Blue Iris Mental Model

[webinar discussion at 3:18]

One way to think about Blue Iris is a software engine (server) that processes inputs/sensors from the outside world (Triggers) and makes sense of them by sending the appropriate Alerts.

triggers-and-alerts_optimized.png (15.73 KiB) Viewed 13130 times

It's important to map the mental model into the BI dialogs and features. The triggers in the mental image come straight from the Trigger sources and zones controls in the Alerts tab.

trigger settings.PNG
trigger settings.PNG (57.38 KiB) Viewed 13127 times

Furthermore, the Alerts list comes straight from the Action Set seen frequently throughout the application.

action set.png
action set.png (55.18 KiB) Viewed 13128 times

The other large component of BI functionality is connecting / managing cameras and recording moments of interest.

bi-model_optimized.png (16.81 KiB) Viewed 13124 times

This article is focused on the most common scenario, i.e. creating motion triggers and sending alerts to yourself, i.e. Push notifications to the mobile app, SMS messages and/or Email alerts.

common alerts.PNG
common alerts.PNG (76.74 KiB) Viewed 13118 times

Alerts Tab - Controls

[webinar discussion at 8:11]

As stated earlier, the Trigger sources and zones section of the Alerts tab is what controls the wiring (activation) of triggers. This is how the software determines which triggers can generate alerts.

alerts tab wiring.PNG
alerts tab wiring.PNG (80.83 KiB) Viewed 13117 times

Triggers / Recordings / Alerts Model

[webinar discussion at 10:23]

The model below is very important to understand in terms of what is really going on behind the scenes with the BI software / logic. The image also maps the model to the BI user interface. Once this mapping is understood, it becomes very easy to understand what BI is doing based on the visual affects in the user interface.

triggers recordings model.png
triggers recordings model.png (107.36 KiB) Viewed 13115 times

Triggers vs Alerts

[webinar discussion at 18:35]

Because the word trigger and alert have similar meanings in the English language, sometimes it is confusing to know the difference between a motion trigger vs an alert.
A motion trigger is a moment in time that BI considers important based on your motion settings.
However, every motion trigger may not lead to an alert. The most obvious example is when you turn on AI. AI is another layering of filtering that determines whether the moment in time that BI considered important due to motion settings is still important based on AI analysis. If the AI returns "nothing found" for the motion trigger, an alert will not be sent (usually, based on default settings). However, the motion trigger is still recorded in the database as a motion trigger event.

triggers vs alerts.PNG
triggers vs alerts.PNG (107.99 KiB) Viewed 13109 times

Alerts Tab Uncovered

[webinar discussion at 21:29]

Most users have re-triggers off. Usually, once you have been alerted, you do not care to get re-triggered in close proximity to the original trigger because you have already been notified and if the alert were of importance you are probably already paying attention to the camera.

If somebody approaches your front door, you want the camera to trigger and send an alert.
However, if the person stands still for 2s and then raises his hand to scratch his head while waiting at the door, do you really want to be re-triggered? Or are you already paying attention to the camera based off of the first alert? Most users are already paying attention and do not want to be continuously alerted on the same "event".
But there may be cases where re-triggers are of value so the option is there.

re-triggers.png (59.05 KiB) Viewed 13105 times


Allow disarm time by delaying alerts

[webinar discussion at 24:11]

disarm timer.png
disarm timer.png (66.45 KiB) Viewed 13103 times

Wait until triggered at least

[webinar discussion at 26:21]

wait until triggered.png
wait until triggered.png (69.89 KiB) Viewed 13101 times

Minimum time between alerts

[webinar discussion at 29:55]

minimum time.png
minimum time.png (64.63 KiB) Viewed 13100 times

Minimum/max time since trigger

[webinar discussion at 31:38]

min-max timers.png
min-max timers.png (74.31 KiB) Viewed 13099 times
Post Reply