Not really sure what this article will become. Right now, I am using it as a placeholder for gotchas based on tickets associated with the action map and creating alerts.
Gotcha 2: Email/SMS alerts are not working
Global settings -> Users tab.
Make sure the user is allowed access to BI during the appropriate profiles.
Confirm alerts are being sent from the server
Furthermore, confirm the Alert is sent soon after BI senses motion. The gap between the MOTION event and the Alert should not be more than 1-2s.
Log states alerts are sent: Issue with Alert settings
If the logs state alerts are being sent, then you can be confident your global permissions and motion triggers are set correctly to generate an alert.
The issue must reside with your alert settings.
If you are only sending one type of alert, e.g. an email notification, create an SMS alert to try and isolate the issue. Does the other alert work?
If only the SMS notification is working, I would look very closely at my email alert settings.
If only the email notification is working, I would look very closely at my SMS alert settings.
If both alerts are not working, the issue is probably with the email server setup since both alerts rely on the email server.
Global settings -> Email servers.
Easy to check if SMS and Email alerts are being processed correctly by BI.
Simply login to your email server.
Go to the sent folder.
If you see sent emails to your cellular provider (for an SMS text) or to the email address specified in the Email alert settings, BI processed the alert correctly.
BI emails are easy to spot because the subject starts with Blue Iris.
If you do not see any BI sent emails, your email server is not setup correctly.
Log states alerts are NOT sent: Issue with Server settings (Permissions or Trigger settings)
If the logs state NO alerts are being sent, then you can be confident there has to be an issue with permissions via the Global settings or your Motion triggers do not generate an alert.
One common mistake is the Profiles for the alert are NOT active for the Profile you are testing.
Camera settings -> Alerts tab -> On Alert.
- Are the cameras working? See Camera Stream Optimization article.
- Are you still receiving motion triggers? The Alerts tab in the Clips List will tell you! If not, there is a problem with the Trigger tab.
- If the motion trigger is present, there is a problem with the Alerts tab.
If you do not know how to debug alerts, watch the Triggers and Alerts webinar. The information is also available in the Alerts and Actions section of Help (Testing the Action Set).
Gotcha 1: Alert images
Alert images are the images that are associated with SMS and Email alerts.
Push notifications also provide Alert images.
The issue is often users want the Alert Image, i.e. the Trigger image to be in high resolution and sometimes it appears as a low resolution image.
The thumbnail image which is actually stored in the database and associated with the Alert is 240px.
In earlier versions of 5.x, the thumbnail image was 480px, but the increased size really did not add much value, but did eat up database storage so was changed back to 240px.
To get higher resolution main stream Alert images, select Hi-res JPEG files for Add to alerts list:. Camera settings -> Trigger tab.
If your camera has dual streams and Hi-res JPEG is selected (as stated above), but the alert image is not the higher resolution, the issue is often the main stream does not have a key frame.
The fix is creating a pre-trigger buffer.
A 5s pre-trigger buffer is always a good practice. Camera settings -> Record tab.
A pre-trigger buffer assures at least one key frame exists for the main stream.
A 5s pre-trigger buffer assumes your kfps is at least greater the 0.2 (1/5).
If the above two fixes do not resolve the issue, right click on an alert -> Open containing folder.
Is the corresponding JPEG the correct resolution? 240p is what's in the database. However if there's a hi-res JPEG file, this should be served instead.
If the Open containing folder selection is greyed out, then there is an issue.
- The most obvious cause is you did not set Add to alerts list = Hi-res JPEGfiles
- OR There is an issue with the setup of the Alerts folder (image below), folder permissions or something else.
Check the log for errors, in particular Storage errors.
Note on email alerts
Email alerts provide many more options.
The Motion leading-edge image will always come from the sub stream.
The Trigger leading-edge, aka the Alert image, will only be high-res if you select Hi-res JPEG (as stated above) AND the main stream has a key frame in the buffer (thus, the need for a pre-trigger buffer as stated above).
The Additional images will always be hi-res (if you have a main stream key frame in the buffer).
Finally, the Email alert dialog also provides quality controls (default is 50/50).