Andy10
Posts: 19
Joined: Fri Sep 05, 2014 11:01 pm

APCUPSD on Raspi to send email on loss of power

Fri Sep 19, 2014 3:20 am

Hoping someone has run into this before and can help. My plan was to plug my Raspberry Pi which is setup as a 24/7 server with raspian 3.12.22+ into a UPS and have it email me when it lost power and when power came back. Bought a cheap APC UPS with a USB port and plugged it in. Downloaded and installed APCUPSD following the instructions here->

http://www.anites.com/2013/09/monitoring-ups.html

It appears that apcupsd is working fine. I can get wall messages when I unplug the UPS and it will successfully shutdown and reboot my Pi, but it isn't emailing me when it does so. Hoping this is something simple somewhere that I just need to add a line to tell it to do something extra but I am neither a Linux nor a python expert so I'm not sure what I'm doing wrong at this point.

This is what I get when I run apcaccess that is making me think that apcupsd is working fine:

Code: Select all

 $apcaccess
APC      : 001,034,0869
DATE     : 2014-09-19 02:43:30 +0000
HOSTNAME : raspberrypi
VERSION  : 3.14.10 (13 September 2011) debian
UPSNAME  : RPiUPS
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2014-09-19 01:16:16 +0000
MODEL    : Back-UPS ES 600G
STATUS   : ONLINE
LINEV    : 118.0 Volts
LOADPCT  :   0.0 Percent Load Capacity
BCHARGE  : 068.0 Percent
TIMELEFT :  89.1 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 180 Seconds
SENSE    : High
LOTRANS  : 092.0 Volts
HITRANS  : 139.0 Volts
ALARMDEL : 30 seconds
BATTV    : 13.5 Volts
LASTXFER : No transfers since turnon
NUMXFERS : 0
TONBATT  : 0 seconds
CUMONBATT: 0 seconds
XOFFBATT : N/A
STATFLAG : 0x07000008 Status Flag
SERIALNO : 4B1345P29769
BATTDATE : 2013-11-08
NOMINV   : 120 Volts
NOMBATTV :  12.0 Volts
FIRMWARE : 905.W1 .D USB FW:W1
END APC  : 2014-09-19 02:44:19 +0000

This is the pertinent part of apcupsd.events file in /var/log
2014-09-19 01:12:46 +0000 Power failure.
2014-09-19 01:12:52 +0000 Running on UPS batteries.
2014-09-19 01:15:53 +0000 Reached run time limit on batteries.
2014-09-19 01:15:53 +0000 Initiating system shutdown!
2014-09-19 01:15:53 +0000 User logins prohibited
2014-09-19 01:15:55 +0000 apcupsd exiting, signal 15
2014-09-19 01:15:55 +0000 apcupsd shutdown succeeded
2014-09-19 01:16:17 +0000 apcupsd 3.14.10 (13 September 2011) debian startup succeeded

and here is /var/log/messages
Sep 19 01:12:46 raspberrypi kernel: [ 2584.736661] usb 1-1.2: USB disconnect, device number 6
Sep 19 01:12:46 raspberrypi kernel: [ 2584.736698] usb 1-1.2.1: USB disconnect, device number 7
Sep 19 01:12:46 raspberrypi kernel: [ 2584.958567] usb 1-1.2.2: USB disconnect, device number 8
Sep 19 01:15:54 raspberrypi shutdown[3604]: shutting down for system halt
Sep 19 01:16:14 raspberrypi kernel: imklog 5.8.11, log source = /proc/kmsg started.
Sep 19 01:16:14 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1856" x-info="http://www.rsyslog.com"] start
Sep 19 01:16:14 raspberrypi kernel: [ 0.000000] Booting Linux on physical CPU 0x0


This is my apcupsd.conf file->

Code: Select all

## apcupsd.conf v1.1 ##
# 
#  for apcupsd release 3.14.10 (13 September 2011) - debian
#
# "apcupsd" POSIX config file

#
# ========= General configuration parameters ============
#

# UPSNAME xxx
#   Use this to give your UPS a name in log files and such. This
#   is particulary useful if you have multiple UPSes. This does not
#   set the EEPROM. It should be 8 characters or less.
# Added ups name of RasPiUPS ANG 8-23-2014
#UPSNAME
UPSNAME RPiUPS

# UPSCABLE <cable>
#   Defines the type of cable connecting the UPS to your computer.
#
#   Possible generic choices for <cable> are:
#     simple, smart, ether, usb
#
#   Or a specific cable model number may be used:
#     940-0119A, 940-0127A, 940-0128A, 940-0020B,
#     940-0020C, 940-0023A, 940-0024B, 940-0024C,
#     940-1524C, 940-0024G, 940-0095A, 940-0095B,
#     940-0095C, M-04-02-2000
#
# commented out this and add usb line below ANG 8-23-2014  
#UPSCABLE smart
UPSCABLE usb

# To get apcupsd to work, in addition to defining the cable
# above, you must also define a UPSTYPE, which corresponds to
# the type of UPS you have (see the Description for more details).
# You must also specify a DEVICE, sometimes referred to as a port.
# For USB UPSes, please leave the DEVICE directive blank. For
# other UPS types, you must specify an appropriate port or address.
#
# UPSTYPE   DEVICE           Description
# apcsmart  /dev/tty**       Newer serial character device, appropriate for 
#                            SmartUPS models using a serial cable (not USB).
#
# usb       <BLANK>          Most new UPSes are USB. A blank DEVICE
#                            setting enables autodetection, which is
#                            the best choice for most installations.
#
# net       hostname:port    Network link to a master apcupsd through apcupsd's 
#                            Network Information Server. This is used if the
#                            UPS powering your computer is connected to a 
#                            different computer for monitoring.
#
# snmp      hostname:port:vendor:community
#                            SNMP network link to an SNMP-enabled UPS device.
#                            Hostname is the ip address or hostname of the UPS 
#                            on the network. Vendor can be can be "APC" or 
#                            "APC_NOTRAP". "APC_NOTRAP" will disable SNMP trap 
#                            catching; you usually want "APC". Port is usually 
#                            161. Community is usually "private".
#
# netsnmp   hostname:port:vendor:community
#                            OBSOLETE
#                            Same as SNMP above but requires use of the 
#                            net-snmp library. Unless you have a specific need
#                            for this old driver, you should use 'snmp' instead.
#
# dumb      /dev/tty**       Old serial character device for use with 
#                            simple-signaling UPSes.
#
# pcnet     ipaddr:username:passphrase:port
#                            PowerChute Network Shutdown protocol which can be 
#                            used as an alternative to SNMP with the AP9617 
#                            family of smart slot cards. ipaddr is the IP 
#                            address of the UPS management card. username and 
#                            passphrase are the credentials for which the card 
#                            has been configured. port is the port number on 
#                            which to listen for messages from the UPS, normally 
#                            3052. If this parameter is empty or missing, the 
#                            default of 3052 will be used.
#
# commentd out next two lines and added following lines ANG 8-24-2014 
#UPSTYPE apcsmart
#DEVICE /dev/ttyS0
UPSTYPE usb
#DEVICE


# POLLTIME <int>
#   Interval (in seconds) at which apcupsd polls the UPS for status. This
#   setting applies both to directly-attached UPSes (UPSTYPE apcsmart, usb, 
#   dumb) and networked UPSes (UPSTYPE net, snmp). Lowering this setting
#   will improve apcupsd's responsiveness to certain events at the cost of
#   higher CPU utilization. The default of 60 is appropriate for most
#   situations.
POLLTIME 120

# LOCKFILE <path to lockfile>
#   Path for device lock file. Not used on Win32.
LOCKFILE /var/lock

# SCRIPTDIR <path to script directory>
#   Directory in which apccontrol and event scripts are located.
SCRIPTDIR /etc/apcupsd

# PWRFAILDIR <path to powerfail directory>
#   Directory in which to write the powerfail flag file. This file
#   is created when apcupsd initiates a system shutdown and is
#   checked in the OS halt scripts to determine if a killpower
#   (turning off UPS output power) is required.
PWRFAILDIR /etc/apcupsd

# NOLOGINDIR <path to nologin directory>
#   Directory in which to write the nologin file. The existence
#   of this flag file tells the OS to disallow new logins.
NOLOGINDIR /etc


#
# ======== Configuration parameters used during power failures ==========
#

# The ONBATTERYDELAY is the time in seconds from when a power failure
#   is detected until we react to it with an onbattery event.
#
#   This means that, apccontrol will be called with the powerout argument
#   immediately when a power failure is detected.  However, the
#   onbattery argument is passed to apccontrol only after the 
#   ONBATTERYDELAY time.  If you don't want to be annoyed by short
#   powerfailures, make sure that apccontrol powerout does nothing
#   i.e. comment out the wall.
ONBATTERYDELAY 6

# 
# Note: BATTERYLEVEL, MINUTES, and TIMEOUT work in conjunction, so
# the first that occurs will cause the initation of a shutdown.
#

# If during a power failure, the remaining battery percentage
# (as reported by the UPS) is below or equal to BATTERYLEVEL, 
# apcupsd will initiate a system shutdown.
BATTERYLEVEL 5

# If during a power failure, the remaining runtime in minutes 
# (as calculated internally by the UPS) is below or equal to MINUTES,
# apcupsd, will initiate a system shutdown.
MINUTES 3

# If during a power failure, the UPS has run on batteries for TIMEOUT
# many seconds or longer, apcupsd will initiate a system shutdown.
# A value of 0 disables this timer.
#
#  Note, if you have a Smart UPS, you will most likely want to disable
#    this timer by setting it to zero. That way, you UPS will continue
#    on batteries until either the % charge remaing drops to or below BATTERYLEVEL,
#    or the remaining battery runtime drops to or below MINUTES.  Of course,
#    if you are testing, setting this to 60 causes a quick system shutdown
#    if you pull the power plug.   
#  If you have an older dumb UPS, you will want to set this to less than
#    the time you know you can run on batteries.
TIMEOUT 0

#  Time in seconds between annoying users to signoff prior to
#  system shutdown. 0 disables.
ANNOY 300

# Initial delay after power failure before warning users to get
# off the system.
ANNOYDELAY 60

# The condition which determines when users are prevented from
# logging in during a power failure.
# NOLOGON <string> [ disable | timeout | percent | minutes | always ]
NOLOGON disable

# If KILLDELAY is non-zero, apcupsd will continue running after a
# shutdown has been requested, and after the specified time in
# seconds attempt to kill the power. This is for use on systems
# where apcupsd cannot regain control after a shutdown.
# KILLDELAY <seconds>  0 disables
KILLDELAY 0

#
# ==== Configuration statements for Network Information Server ====
#

# NETSERVER [ on | off ] on enables, off disables the network
#  information server. If netstatus is on, a network information
#  server process will be started for serving the STATUS and
#  EVENT data over the network (used by CGI programs).
NETSERVER on

# NISIP <dotted notation ip address>
#  IP address on which NIS server will listen for incoming connections.
#  This is useful if your server is multi-homed (has more than one
#  network interface and IP address). Default value is 0.0.0.0 which
#  means any incoming request will be serviced. Alternatively, you can
#  configure this setting to any specific IP address of your server and 
#  NIS will listen for connections only on that interface. Use the
#  loopback address (127.0.0.1) to accept connections only from the
#  local machine.
NISIP 127.0.0.1

# NISPORT <port> default is 3551 as registered with the IANA
#  port to use for sending STATUS and EVENTS data over the network.
#  It is not used unless NETSERVER is on. If you change this port,
#  you will need to change the corresponding value in the cgi directory
#  and rebuild the cgi programs.
NISPORT 3551

# If you want the last few EVENTS to be available over the network
# by the network information server, you must define an EVENTSFILE.
EVENTSFILE /var/log/apcupsd.events

# EVENTSFILEMAX <kilobytes>
#  By default, the size of the EVENTSFILE will be not be allowed to exceed
#  10 kilobytes.  When the file grows beyond this limit, older EVENTS will
#  be removed from the beginning of the file (first in first out).  The
#  parameter EVENTSFILEMAX can be set to a different kilobyte value, or set
#  to zero to allow the EVENTSFILE to grow without limit.
EVENTSFILEMAX 20

#
# ========== Configuration statements used if sharing =============
#            a UPS with more than one machine

#
# Remaining items are for ShareUPS (APC expansion card) ONLY
#

# UPSCLASS [ standalone | shareslave | sharemaster ]
#   Normally standalone unless you share an UPS using an APC ShareUPS
#   card.
UPSCLASS standalone

# UPSMODE [ disable | share ]
#   Normally disable unless you share an UPS using an APC ShareUPS card.
UPSMODE disable

#
# ===== Configuration statements to control apcupsd system logging ========
#

# Time interval in seconds between writing the STATUS file; 0 disables
STATTIME 0

# Location of STATUS file (written to only if STATTIME is non-zero)
STATFILE /var/log/apcupsd.status

# LOGSTATS [ on | off ] on enables, off disables
# Note! This generates a lot of output, so if         
#       you turn this on, be sure that the
#       file defined in syslog.conf for LOG_NOTICE is a named pipe.
#  You probably do not want this on.
LOGSTATS off

# Time interval in seconds between writing the DATA records to
#   the log file. 0 disables.
DATATIME 0

# FACILITY defines the logging facility (class) for logging to syslog. 
#          If not specified, it defaults to "daemon". This is useful 
#          if you want to separate the data logged by apcupsd from other
#          programs.
#FACILITY DAEMON

#
# ========== Configuration statements used in updating the UPS EPROM =========
#

#
# These statements are used only by apctest when choosing "Set EEPROM with conf
# file values" from the EEPROM menu. THESE STATEMENTS HAVE NO EFFECT ON APCUPSD.
#

# UPS name, max 8 characters 
#UPSNAME UPS_IDEN

# Battery date - 8 characters
#BATTDATE mm/dd/yy

# Sensitivity to line voltage quality (H cause faster transfer to batteries)  
# SENSITIVITY H M L        (default = H)
#SENSITIVITY H

# UPS delay after power return (seconds)
# WAKEUP 000 060 180 300   (default = 0)
#WAKEUP 60

# UPS Grace period after request to power off (seconds)
# SLEEP 020 180 300 600    (default = 20)
#SLEEP 180

# Low line voltage causing transfer to batteries
# The permitted values depend on your model as defined by last letter 
#  of FIRMWARE or APCMODEL. Some representative values are:
#    D 106 103 100 097
#    M 177 172 168 182
#    A 092 090 088 086
#    I 208 204 200 196     (default = 0 => not valid)
#LOTRANSFER  208

# High line voltage causing transfer to batteries
# The permitted values depend on your model as defined by last letter 
#  of FIRMWARE or APCMODEL. Some representative values are:
#    D 127 130 133 136
#    M 229 234 239 224
#    A 108 110 112 114
#    I 253 257 261 265     (default = 0 => not valid)
#HITRANSFER 253

# Battery charge needed to restore power
# RETURNCHARGE 00 15 50 90 (default = 15)
#RETURNCHARGE 15

# Alarm delay 
# 0 = zero delay after pwr fail, T = power fail + 30 sec, L = low battery, N = never
# BEEPSTATE 0 T L N        (default = 0)
#BEEPSTATE T

# Low battery warning delay in minutes
# LOWBATT 02 05 07 10      (default = 02)
#LOWBATT 2

# UPS Output voltage when running on batteries
# The permitted values depend on your model as defined by last letter 
#  of FIRMWARE or APCMODEL. Some representative values are:
#    D 115
#    M 208
#    A 100
#    I 230 240 220 225     (default = 0 => not valid)
#OUTPUTVOLTS 230

# Self test interval in hours 336=2 weeks, 168=1 week, ON=at power on
# SELFTEST 336 168 ON OFF  (default = 336)
#SELFTEST 336

And finally my changes to the onbattery and offbattery files->

onbattery

Code: Select all

#!/bin/sh
#
# This shell script if placed in /etc/apcupsd
# will be called by /etc/apcupsd/apccontrol when the UPS
# goes on batteries.
# We send an email message to root to notify him.
#

# commented out everything below here and added new lines below
#ANG 8-23-2014
#SYSADMIN=root
#APCUPSD_MAIL="mail"

#HOSTNAME=`hostname`
#MSG="$HOSTNAME Power Failure !!!"
#
#(
#   echo "Subject: $MSG"
#   echo " "
#   echo "$MSG"
#   echo " "
#   /sbin/apcaccess status
#) | $APCUPSD_MAIL -s "$MSG" $SYSADMIN
#exit 0



# Added this new script from http://www.anites.com/2013/09/monitoring-ups.html
#  ANG 8-23-2014


#!/usr/bin/env python

import smtplib
import email.mime.text
import syslog

syslog.openlog('[UPS]')
def log(msg):
    syslog.syslog(str(msg))

GMAIL_ADDRESS = '[email protected]'
GMAIL_PASSWORD = 'MyPassword'

from_email = GMAIL_ADDRESS
to_emails = ["[email protected]"]  # email address

msg_subject = "ALERT: UPS Power Failure"
msg_text = "Auto Notification"

log(msg_subject)

msg = email.mime.text.MIMEText(msg_text)
msg['Subject'] = msg_subject
msg['From'] = from_email
msg['To'] = ", ".join(to_emails)
s = smtplib.SMTP_SSL('smtp.gmail.com', '465')
s.login(GMAIL_ADDRESS, GMAIL_PASSWORD)
s.sendmail(from_email, to_emails, msg.as_string())
s.quit()


offbattery

Code: Select all

#!/bin/sh
#
# This shell script if placed in /etc/apcupsd
# will be called by /etc/apcupsd/apccontrol when the    
# UPS goes back on to the mains after a power failure.
# We send an email message to root to notify him.
#
# commented out original and added new below  
# ANG 8-23-2014

#SYSADMIN=root
#APCUPSD_MAIL="mail"

#HOSTNAME=`hostname`
#MSG="$HOSTNAME Power has returned"
#
#(
#   echo "Subject: $MSG"
#   echo " "
#   echo "$MSG"
#   echo " "
#   /sbin/apcaccess status
#) | $APCUPSD_MAIL -s "$MSG" $SYSADMIN
#exit 0


#  Added new code here based on  http://www.anites.com/2013/09/monitoring-ups.html
# ANG 8-23-2014


#!/usr/bin/env python

import smtplib
import email.mime.text
import syslog

syslog.openlog('[UPS]')
def log(msg):
    syslog.syslog(str(msg))

GMAIL_ADDRESS = '[email protected]'
GMAIL_PASSWORD = 'MyPassword'

from_email = GMAIL_ADDRESS
to_emails = ["[email protected]"]  # email address

msg_subject = "OK: UPS Power Recovered"
msg_text = "Auto Notification"

log(msg_subject)

msg = email.mime.text.MIMEText(msg_text)
msg['Subject'] = msg_subject
msg['From'] = from_email
msg['To'] = ", ".join(to_emails)
s = smtplib.SMTP_SSL('smtp.gmail.com', '465')
s.login(GMAIL_ADDRESS, GMAIL_PASSWORD)
s.sendmail(from_email, to_emails, msg.as_string())
s.quit()



I tested these by running them directly -> $python onbattery and I get the email fine.

Any help at all would be seriously appreciated. I've been up one side and down the other of the man pages and googled my butt off and if my solution is there I can't find it!

I'm hoping if nothing else someone might be able to point me in the right direction...

I also just posted a comment on the page where I found the initial directions but the post was from a year ago so I'm not sure I'll get any help there.

Also tried ->
https://help.ubuntu.com/community/apcupsd
https://wiki.debian.org/apcupsd

And of course->
http://www.apcupsd.com/manual/manual.html

If you can help, thank you.
if you can commiserate and let me know I'm not the only one in this boat even better!

Andy10
Posts: 19
Joined: Fri Sep 05, 2014 11:01 pm

Re: APCUPSD on Raspi to send email on loss of power

Fri Sep 19, 2014 11:38 am

This was also a helpful post and got me to the point I'm at now->

http://www.raspberrypi.org/forums/viewt ... 29&t=14447

Andy10
Posts: 19
Joined: Fri Sep 05, 2014 11:01 pm

Re: APCUPSD on Raspi to send email on loss of power

Mon Oct 13, 2014 12:48 pm

So the key thing I didn't include here was the APCCONTROL script. I had a friend take a peek at it for me and he immediately saw what my mistake was (DOH!). Turns out either the installed default does not include calls to the onbattery or offbattery scripts, or I changed it somewhere along the way trying to trouble shoot and didn't catch it later. The basic solution was to add this code under on batter or off battery:

Code: Select all

 if [ -f /etc/apcupsd/offbattery ] ; then
                python  /etc/apcupsd/offbattery
        fi

Here is my final APCCONTROL file:

Code: Select all

#!/bin/sh
#
# Copyright (C) 1999-2002 Riccardo Facchetti <[email protected]>
#
#  for apcupsd release 3.14.10 (13 September 2011) - debian
#
# platforms/apccontrol.  Generated from apccontrol.in by configure.
#
#  Note, this is a generic file that can be used by most
#   systems. If a particular system needs to have something
#   special, start with this file, and put a copy in the
#   platform subdirectory.
#

#
# These variables are needed for set up the autoconf other variables.
#
prefix=/usr
exec_prefix=${prefix}

APCPID=/var/run/apcupsd.pid
APCUPSD=/sbin/apcupsd
SHUTDOWN=/sbin/shutdown
SCRIPTSHELL=/bin/sh
SCRIPTDIR=/etc/apcupsd
WALL=wall

#
# Concatenate all output from this script to the events file
#  Note, the following kills the script in a power fail situation
#   where the disks are mounted read-only.
# exec >>/var/log/apcupsd.events 2>&1



#
# This piece is to substitute the default behaviour with your own script,
# perl, or C program.
# You can customize every single command creating an executable file (may be a
# script or a compiled program) and calling it the same as the $1 parameter
# passed by apcupsd to this script.
#
# After executing your script, apccontrol continues with the default action.
# If you do not want apccontrol to continue, exit your script with exit 
# code 99. E.g. "exit 99".
#
# WARNING: the apccontrol file will be overwritten every time you update your
# apcupsd, doing `make install'. Your own customized scripts will _not_ be
# overwritten. If you wish to make changes to this file (discouraged), you
# should change apccontrol.sh.in and then rerun the configure process.
#
if [ -f ${SCRIPTDIR}/${1} -a -x ${SCRIPTDIR}/${1} ]
then
    ${SCRIPTDIR}/${1} ${2} ${3} ${4}
    # exit code 99 means he does not want us to do default action
    if [ $? = 99 ] ; then
	exit 0
    fi
fi

case "$1" in
    killpower)
	echo "Apccontrol doing: ${APCUPSD} --killpower on UPS ${2}" | ${WALL}
	sleep 10
	${APCUPSD} --killpower
	echo "Apccontrol has done: ${APCUPSD} --killpower on UPS ${2}" | ${WALL}
    ;;
    commfailure)
	echo "Warning communications lost with UPS ${2}" | ${WALL}
    ;;
    commok)
	echo "Communications restored with UPS ${2}" | ${WALL}
    ;;
#
# powerout, onbattery, offbattery, mainsback events occur
#   in that order.
#
    powerout)
    ;;
    onbattery)
	echo "Power failure on UPS ${2}. Running on batteries." | ${WALL}
# added if  ; then statement to call offbattery file in python from Mike 10-9-2014
        if [ -f /etc/apcupsd/offbattery ] ; then
                python  /etc/apcupsd/offbattery
	fi
    ;;
    offbattery)
	 echo "Power restored on UPS ${2}. No longer running on batteries." | ${WALL}
# added if  ; then statement to call offbattery file in python from Mike 10-9-2014
	if [ -f /etc/apcupsd/offbattery ] ; then
		python	/etc/apcupsd/offbattery
	fi
    ;;
    mainsback)
	if [ -f /etc/apcupsd/powerfail ] ; then
	   printf "Continuing with shutdown."  | ${WALL}
	fi
    ;;
    failing)
	echo "Battery power exhaused on UPS ${2}. Doing shutdown." | ${WALL}
    ;;
    timeout)
	echo "Battery time limit exceeded on UPS ${2}. Doing shutdown." | ${WALL}
    ;;
    loadlimit)
	echo "Remaining battery charge below limit on UPS ${2}. Doing shutdown." | ${WALL}
    ;;
    runlimit)
	echo "Remaining battery runtime below limit on UPS ${2}. Doing shutdown." | ${WALL}
    ;;
    doreboot)
	echo "UPS ${2} initiating Reboot Sequence" | ${WALL}
	${SHUTDOWN} -r now "apcupsd UPS ${2} initiated reboot"
    ;;
    doshutdown)
	echo "UPS ${2} initiated Shutdown Sequence" | ${WALL}
	${SHUTDOWN} -h now "apcupsd UPS ${2} initiated shutdown"
    ;;
    annoyme)
	echo "Power problems with UPS ${2}. Please logoff." | ${WALL}
    ;;
    emergency)
	echo "Emergency Shutdown. Possible battery failure on UPS ${2}." | ${WALL}
    ;;
    changeme)
	echo "Emergency! Batteries have failed on UPS ${2}. Change them NOW" | ${WALL}
    ;;
    remotedown)
	echo "Remote Shutdown. Beginning Shutdown Sequence." | ${WALL}
    ;;
    startselftest)
    ;;
    endselftest)
    ;;
    battdetach)
    ;;
    battattach)
    ;;
    *)	echo "Usage: ${0##*/} command"
	echo "	     warning: this script is intended to be launched by"
	echo "	     apcupsd and should never be launched by users."
	exit 1
    ;;
esac
It was definitely one of those can't see the forest through the trees moments...

tomeurp
Posts: 1
Joined: Sat Jun 17, 2017 4:00 pm

Re: APCUPSD on Raspi to send email on loss of power

Sat Jun 17, 2017 4:11 pm

Hello,

This has been really helpful because I know almost nothing about programming and have been able to modify the onbattery script so that the raspberry calls me using a VoIP account and plays a pre-recorded message whenever the UPS starts running on battery, which is pretty convenient since an email could be easily missed. However, this comes with a drawback... whenever there is a small fluctuation in the mains power, I receive a phone call, which pisses me off if it happens in the middle of the night and when I receive the call, power is already back.

Would anybody be able to help me in inserting, lets say, a 30 seconds delay to the onbattery script, then checking again if the ups is still running on batteries, and if so, call me, but abort the calling and the sending of emails if power has already returned and the ups is no longer running on batteries?

I imagine inserting a 30 seconds delay would be enough, with no need for a second check of the apc status if I, somehow, managed the offbatery script to kill the onbattery process if this one's already running, but it could be risky because if, say, the power goes down, then returns, then dies again, unless all processes are perfectly synced, the offbattery could kill both onbattery processes and never receive an alert on a real power failure.

Thank you so much in advance.

Return to “Other projects”