Difference between revisions of "SMS Notifications"

From ZoneMinder Wiki
Jump to navigationJump to search
 
(18 intermediate revisions by the same user not shown)
Line 6: Line 6:
You can get images from the alarm embedded in the text (covered in install steps).
You can get images from the alarm embedded in the text (covered in install steps).


The following is tested for 1.30, and 1.34.
The following is used in 1.36 / Debian 10 and newer.


== Installation ==
== Installation ==
Line 15: Line 15:


=== MSMTP Specific Install ===
=== MSMTP Specific Install ===
Debian 10 should use MSMTP.
Debian 10 and newer should use MSMTP.
  apt-get install msmtp msmtp-mta mutt
  apt-get install msmtp msmtp-mta mutt
Add a working config to /etc/msmtprc (see below for resources on this)
echo "hello" | msmtp -a default user@email.com


=== Testing the email ===
=== Testing the email ===
Line 24: Line 22:
First test via terminal outside of ZM. Confirm it is working there. Example configurations and calls can be found at: https://wiki.debian.org/msmtp and https://wiki.archlinux.org/index.php/MSMTP (for msmtp).
First test via terminal outside of ZM. Confirm it is working there. Example configurations and calls can be found at: https://wiki.debian.org/msmtp and https://wiki.archlinux.org/index.php/MSMTP (for msmtp).


Once you get a working /etc/msmtprc configuration, try:
echo "hello" | msmtp -a default user@email.com
Watch out for the following:
* Make sure app-armor is disabled for msmtp. The following commands will help: apt install apparmor-utils and then aa-disable /etc/apparmor.d/usr.bin.msmtp
=== Testing the email in Zoneminder ===
Then:
Then:
# run a filter in the background (see tips below) or execute.  
# run a filter in the background (see tips below) or execute.  
Line 34: Line 39:
=== Tips ===
=== Tips ===


* Free email services limit how many emails you are allowed to send through SMTP. It helps to disable cron emails.
* Free email services may limit how many emails you are allowed to send.


* Always make filters for 1 (or low number) results. If you fail to do this, you could try to send dozens of emails.
* Always make filters for 1 (or low number) results. If you fail to do this, you could try to send dozens of emails.
Line 42: Line 47:
* If when testing the filter execute, the 'execute' button becomes unclickable, uncheck then recheck the email option.
* If when testing the filter execute, the 'execute' button becomes unclickable, uncheck then recheck the email option.


<pre>
* If you send email as someone other than root you may need to include the user in revaliases.
#watch "tail -n 30000 /var/log/syslog | grep sSMTP | tail"
</pre>
 
* When testing use a background filter, and watch the logs. Filters run every 60 seconds by default.


* If you send email as someone other than root, make sure he is in /etc/ssmtp/revaliases
* test email attachments with one of these:
 
* test emails with  
<pre>
<pre>
cat file | mail -s "subject" destination@email.com
OR
echo "some text" | mail -s "subject destination@email.com
FOR ATTACHMENTS:
echo hello | mail -A /dir/to/attachment.log -s "email with file" destination@email.com
echo hello | mail -A /dir/to/attachment.log -s "email with file" destination@email.com
OR
Also try mutt (slightly different)
mutt -a /dir/to/attachment.log -s "email with file" -- destination@email.com
mutt -a /dir/to/attachment.log -s "email with file" -- destination@email.com
echo "test" | mutt -d 5 -s "Test Email" user@email.com -a /tmp/file_attachment
</pre>
</pre>


* make sure email is checked off in filters. It gets unchecked easily.
* make sure email is checked off in filters.  


* service zoneminder restart after changes (NOTE: this wasn't required for just setting email settings in ZM options 07/2020).
* service zoneminder restart may be needed after changes (depends upon ZM version)


* test setting off alarms by clicking 'force alarm' in the monitor view, then unclick to remove alarm.
* test setting off alarms by clicking 'force alarm' in the camera monitor view, then unclick to remove alarm.


* make one dedicated email alert account if you want multiple users to receive alerts. There is a patch in the forums to add multiple recipients.
* If you find false alerts with motion detection, consider using either ZMES, or passing the event to an object detection based script.
 
* It's tough to use Motion detection for alerts with IR active.. You might be best off using a device with ZMTrigger, or the cameras built in motion detection if night IR is used... False alerts appear when a camera switches from Day lens to IR.


* Always double check the filters are right, AFTER you save them.
* Always double check the filters are right, AFTER you save them.
Line 76: Line 68:
* Once an email has been sent for an event, that event is marked and an email for it '''won't be sent again'''[https://forums.zoneminder.com/viewtopic.php?f=8&t=7774&p=27386&].
* Once an email has been sent for an event, that event is marked and an email for it '''won't be sent again'''[https://forums.zoneminder.com/viewtopic.php?f=8&t=7774&p=27386&].


====SSMTP Specific Tips====
* Cron may require setting an environment variable of EMAIL=sendingaddress@email.com in the crontab
 
* ssmtp.conf has issues with special characters in AuthPass. Do not use special characters for your password.
 
* Add DEBUG=yes to ssmtp.conf to see full email logs in syslog
 
* If SSMTP is unable to connect, there may be a two minute timeout before it reports unable to connect. If it seems like ssmtp has frozen, wait before closing out of it, if you want its logs.
 
* Don't forget to change revaliases as needed. it should match ssmtp.conf
 
* Expert: Manually test email server connections with something like
<pre>
openssl s_client -debug -starttls smtp -crlf -connect smtp.emailprovider.com:465
then continue with
EHLO hostname
AUTH
etc...
</pre>
 
* ssmtp supports only auth login, and cram-md5. If you have digest-md5 or auth plain at your email server it will likely not work. Test manually using the commands above to verify this.
 
* Test ssmtp manually with $ssmtp -vvvvv email@address.com < msg.txt ([https://wiki.archlinux.org/index.php/SSMTP#Sending_email example message]) (though DEBUG=yes has more information)
 
* SSMTP is lacking some authentication methods and is abandoned as of 07/2020, therefore MSMTP is recommended.
<br>
<br>
<br>
 
====MSMTP Specific Tips====
 
* MSMTP has been tested to work as an alternative to SSMTP (but configured identically) in Debian Buster / Devuan 3.
* Apparmor can impede msmtp logging on Buster (07/2020).
* msmtp can use mutt to send attachments. (ssmtp above was setup with mailutils). See below:
 
Compare these cronjobs
 
'''ssmtp/mailutils:'''
<code>0 1 1 * * echo hello  | mail -A /cameras/report.log -s "ZM Report Log"  user@email.com</code>
 
'''msmtp/mutt    :'''
<code>0 1 1 * * echo hello  | mutt -a /cameras/report.log -s "ZM Report Log" -- user@email.com</code>
<br>
<br>
<br>


=== Example Filter ===
=== Example Filter ===


For monitoring on the weekend you might have
See [[Filters]]
 
<pre>
date/time greater than or equal to -1 minute AND
alarm frames greather than or equal to 1 AND
Weekday equal to Saturday OR
Weekday equal to Sunday AND
alarm frames greater than or equal to 1 AND
date/time greater than or equal to -1 minute
</pre>
 
Notice that you must include all parameters for each group/set individually when there is an OR.


== Send email if only on a certain runstate (Filter on Run States) ==
== Send email if only on a certain runstate (Filter on Run States) ==
Line 146: Line 84:
== Send email if a part of ZM goes offline ==
== Send email if a part of ZM goes offline ==


For any serious deployment you will want to monitor ZM in case it goes offline, or a hdd fails. While it's possible to use a separate system for this (e.g. https://en.wikipedia.org/wiki/Comparison_of_network_monitoring_systems), you can also simply have email alerts in cron. Here is an example script that can watch two hdds (adjust as needed) and the status of ZM and Mysql.
For any serious deployment you will want to monitor ZM in case it goes offline, or a hdd fails. While it's possible to use a separate system for this (e.g. https://en.wikipedia.org/wiki/Comparison_of_network_monitoring_systems), you can also simply have email alerts in cron. Here is an example script that can watch two hdds (adjust as needed) and the status of ZM and Mysql.  
<pre>
<pre>
#!/bin/bash
#!/bin/bash
Line 162: Line 100:
echo "ZM_Status" | mutt -s "ZM Status" destination@email.com -a /root/zm_up_log
echo "ZM_Status" | mutt -s "ZM Status" destination@email.com -a /root/zm_up_log
</pre>
</pre>
This script can be run in crontab as often as you wish.
This script can be run in crontab as often as you wish. It should also be easy to filter the script to email only if something is out of the ordinary. In fact, let's do that next.


== Send email if HDD Fails ==
<pre>
#!/bin/bash
# 20 * * * *  root /root/hdderror.sh (this script)
# must run as root for access to dmesg in debian
# chmod +x
LOGFILE=/root/file.log
SUBJECT="e.g. Home Camera System HDD Error"
echo "" > $LOGFILE
# any text of "error" with regards to sda,sdb, etc that isn't a remount
dmesg | grep -e sda -e sdb -e sdc -e sdd -e sde | grep -i error | grep -v remount >> $LOGFILE
#returns 1 if nothing
if [ $? -eq 0 ]; then
#send email
  echo "HDD Error..." | mutt -s $SUBJECT destination@email.com -a $LOGFILE
else
  echo "do nothing"
fi
</pre>
== Basic ZM Server Monitor ==
These would go in /etc/crontab
<pre>
1 0 * * 1 root dmesg | tail -10 > /tmp/hdd_report
2 0 * * 1 root lsblk  >> /tmp/hdd_report
3 0 * * 1 root ls -lt /videos/ >> /tmp/hdd_report
4 0 * * 1 root df -h >> /tmp/hdd_report
5 0 * * 1 root echo "zm server" | mutt -s "zm server" user@email.com -a /tmp/hdd_report
</pre>


==Resources==
==Resources==

Latest revision as of 04:41, 9 September 2023

These instructions are to assist with email or text message setup.

For SMS, You setup email to point to a text gateway. Setup a filter that monitors the cameras for alarms, and when an alarm is set off you have it send an email to the text gateway (or email address). Simple.

You can get images from the alarm embedded in the text (covered in install steps).

The following is used in 1.36 / Debian 10 and newer.

Installation

Follow How to get ssmtp working with Zoneminder.

There are two ways to send emails in options - email. One is sending a short email, and one is designed for longer messages. In the code (as of 1.30 lines 818 and 918), in zmfilter.pl these are correspondingly sub SendEmail and sub SendMessage. They are distinct functions. SSMTP/MSMTP support is in SendEmail but not in SendMessage.

MSMTP Specific Install

Debian 10 and newer should use MSMTP.

apt-get install msmtp msmtp-mta mutt

Testing the email

First test via terminal outside of ZM. Confirm it is working there. Example configurations and calls can be found at: https://wiki.debian.org/msmtp and https://wiki.archlinux.org/index.php/MSMTP (for msmtp).

Once you get a working /etc/msmtprc configuration, try:

echo "hello" | msmtp -a default user@email.com

Watch out for the following:

  • Make sure app-armor is disabled for msmtp. The following commands will help: apt install apparmor-utils and then aa-disable /etc/apparmor.d/usr.bin.msmtp

Testing the email in Zoneminder

Then:

  1. run a filter in the background (see tips below) or execute.
  2. Enable logging on /var/log/zm folder.
  3. tail the ZMFilter log and syslog.
  4. to initiate an alarm (if alarms are used to test emails), use 'force alarm' on the monitor screen. That is, view a camera, and click force alarm.

You should see SSMTP send an email on the syslog (or try) and the zmfilter log will report the trigger.

Tips

  • Free email services may limit how many emails you are allowed to send.
  • Always make filters for 1 (or low number) results. If you fail to do this, you could try to send dozens of emails.
  • When you make the filter you want the 'current' alarms. You don't want old events. This is accomplished with a Date/Time greater than or equal to -1 minute.
  • If when testing the filter execute, the 'execute' button becomes unclickable, uncheck then recheck the email option.
  • If you send email as someone other than root you may need to include the user in revaliases.
  • test email attachments with one of these:
echo hello | mail -A /dir/to/attachment.log -s "email with file" destination@email.com
mutt -a /dir/to/attachment.log -s "email with file" -- destination@email.com
echo "test" | mutt -d 5 -s "Test Email" user@email.com -a /tmp/file_attachment
  • make sure email is checked off in filters.
  • service zoneminder restart may be needed after changes (depends upon ZM version)
  • test setting off alarms by clicking 'force alarm' in the camera monitor view, then unclick to remove alarm.
  • If you find false alerts with motion detection, consider using either ZMES, or passing the event to an object detection based script.
  • Always double check the filters are right, AFTER you save them.
  • Once an email has been sent for an event, that event is marked and an email for it won't be sent again[1].
  • Cron may require setting an environment variable of EMAIL=sendingaddress@email.com in the crontab

Example Filter

See Filters

Send email if only on a certain runstate (Filter on Run States)

Notifications are easy if you want alarms emailed between a static time, for example between 12AM and 6AM. If you have a situation where you may not want the alarms to send you text messages on occasion, you can filter on run states.

Starting from (ZM > 1.30.4) you can set filters based on run states, which means you can change the run state at any desired time (using Cron, or manually), and only if a runstate matches the filter will SMS be sent.

Note that in the author's opinion, run states can become unwieldy for large installations. It's best used with smaller setups only.

Send email if a part of ZM goes offline

For any serious deployment you will want to monitor ZM in case it goes offline, or a hdd fails. While it's possible to use a separate system for this (e.g. https://en.wikipedia.org/wiki/Comparison_of_network_monitoring_systems), you can also simply have email alerts in cron. Here is an example script that can watch two hdds (adjust as needed) and the status of ZM and Mysql.

#!/bin/bash
/etc/init.d/zoneminder status > /root/zm_up_log
echo "" >> /root/zm_up_log
/etc/init.d/mysql status >> /root/zm_up_log
ps -Ao user,fname,pmem | grep -e zmc -e zma | grep -v zmaudit >> /root/zm_up_log
echo "" >> /root/zm_up_log
echo "" >> /root/zm_up_log
lsblk >> /root/zm_up_log
echo "" >> /root/zm_up_log
echo "" >> /root/zm_up_log
dmesg | grep -e sda -e sdb >> /root/zm_up_log

echo "ZM_Status" | mutt -s "ZM Status" destination@email.com -a /root/zm_up_log

This script can be run in crontab as often as you wish. It should also be easy to filter the script to email only if something is out of the ordinary. In fact, let's do that next.

Send email if HDD Fails

#!/bin/bash
# 20 * * * *   root /root/hdderror.sh (this script)
# must run as root for access to dmesg in debian
# chmod +x 

LOGFILE=/root/file.log
SUBJECT="e.g. Home Camera System HDD Error"

echo "" > $LOGFILE

# any text of "error" with regards to sda,sdb, etc that isn't a remount
dmesg | grep -e sda -e sdb -e sdc -e sdd -e sde | grep -i error | grep -v remount >> $LOGFILE
#returns 1 if nothing

if [ $? -eq 0 ]; then
#send email
  echo "HDD Error..." | mutt -s $SUBJECT destination@email.com -a $LOGFILE
else
  echo "do nothing"
fi

Basic ZM Server Monitor

These would go in /etc/crontab

1 0 * * 1 root dmesg | tail -10 > /tmp/hdd_report
2 0 * * 1 root lsblk  >> /tmp/hdd_report
3 0 * * 1 root ls -lt /videos/ >> /tmp/hdd_report
4 0 * * 1 root df -h >> /tmp/hdd_report
5 0 * * 1 root echo "zm server" | mutt -s "zm server" user@email.com -a /tmp/hdd_report

Resources