I’ve got a couple of LINUX servers and a Synology NAS on my Cyber Power 1350 UPS. I’d like to monitor the battery level and OUTAGES. I can use the little pushbutton on the front to poke through the status OR I can install NUT and monitor my UPS with a cool webpage and much better statistics! I’m going the webpage route!
Setting up NUT on Raspberry
Image an SD card and do the usual set up steps. Check my GUIDE if you have questions. I changed the hostname to “ups” to identify my new server. Plug a USB cable into the UPS and into the Raspberry. Check your connection with “lsusb”, literally “list USB devices”:
pi@ups:~ $ lsusb Bus 001 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@ups:~ $
Looks good. I see my UPS at the top of the list. Now install the monitoring software:
apt-get update && apt-get install nut nut-client nut-server
This is the Network UPS Tools package or “NUT” for short. Nice to have real-world tools in the Raspberry repositories for easy installs! w00t!
NUT Configuration
First, let’s add the connection and the UPS to the config in /etc/nut/ups.conf. I like to add my stuff right at the bottom so I can find it quickly in the future. Add the following “stanza”:
[servers] driver = usbhid-ups port = auto desc = "CyberPower CP1350 AVR UPS"
Hopefully, YOUR UPS is like mine and works well with the usbhid-ups driver. The name can be whatever suits your fancy. Put it in [square] brackets. The desc(ription) is also completely up to you. I would say, try the auto settings–otherwise, you can look up your model here.
Next, we need to setup upsmon. Again, I’m just going to add what I need to the end of the file. The first line shows the format. You can include it as a comment for future reference. :
# MONITOR <system> <powervalue> <user> <password> ("master"|"slave")
MONITOR ups@localhost 1 monuser secret master
The system is the name that we configured in the last bit. Powervalue of 1 is fine for home use. Username and password are at your discretion. (Mine are based on the hardcoded credentials that a Synology NAS uses.) “master” because the UPS is attached directly to this device through the USB cable. The clients will be defined as “slave”.
This same “user” is then added to /etc/nut/upsd.conf. At the very bottom of the file, add:
[monuser] password = secret upsmon master
Finally, set the mode of how this whole thing will function. Edit /etc/nut/nut.conf and change the last line:
MODE=netserver
The Big Restart
Now, let’s restart these processes and see if we can connect. I’m going to just reboot. That will ensure that all the config files got saved and the unit files are all enabled. Once the Raspberry comes back up, try to connect with UPSC and the name of your UPS:
root@ups:~# upsc servers@localhost Init SSL without certificate database battery.charge: 53 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 490 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.7 battery.voltage.nominal: 12 device.mfr: CPS device.model: CP 1350C device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: CyberPower HID 0.4 driver.version.internal: 0.41 input.transfer.high: 140 input.transfer.low: 90 input.voltage: 123.0 input.voltage.nominal: 120 output.voltage: 123.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 33 ups.mfr: CPS ups.model: CP 1350C ups.productid: 0501 ups.realpower.nominal: 298 ups.status: OL CHRG ups.test.result: Done and warning ups.timer.shutdown: -60 ups.timer.start: 0 ups.vendorid: 0764 root@ups:~#
UPS Web Server
YAY! It works! Now, to install the web component, as promised! First, install the webserver and the NUT web stuff:
apt install apache2 nut-cgi
Edit /etc/nut/hosts.conf to allow CGI scrips access to the monitor. Add one line to the bottom of the file:
MONITOR servers@localhost "Server UPS"
Enable CGI in apache and restart the web server:
root@ups:/etc/nut# a2enmod cgi Your MPM seems to be threaded. Selecting cgid instead of cgi. Enabling module cgid. To activate the new configuration, you need to run: systemctl restart apache2 root@ups:/etc/nut# systemctl restart apache2 root@ups:/etc/nut#
Now, you just need to convince apache that you really, really want to turn on CGI by uncommenting the following in /etc/nut/upsset.conf:
### I_HAVE_SECURED_MY_CGI_DIRECTORY
…and you should be able to hit the webpage:
http://ups.local/cgi-bin/nut/upsset.cgi
Do you remember the username and password that we configured for upsmon? You’re going to need it here! Once you’re logged in, you can take a look at your status, or actually issue commands to the UPS! (No wonder it’s password protected!) Another page that comes with the package is here:
http://ups.local/cgi-bin/nut/upsstats.cgi
Next post, we look at configuring the client or “slave” systems. This allows the upsmon process to send shutdown commands to the servers that are plugged into this UPS and do an orderly shutdown instead of crashing when the lights go out!
Thanks. Works like a charm. Never realised my Eaton 3S 850 UPS was able to share this much data. Any idea if this data can be shared with InfluxDB / Grafana? When possible, what would be the route in general?
How would you monitor two UPSes, on different USB ports on the same Raspberry Pi? I can monitor one UPS, but not the other. Both are Tripplite SmartUPS Pro boxes.
Just add a second line to each of the config files for that second UPS:
hosts.conf:MONITOR ups@localhost “Downstairs UPS”
hosts.conf:MONITOR 2Dups@localhost “Upstairs UPS
upsmon.conf:MONITOR ups@localhost 1 monuser secret master
upsmon.conf:MONITOR 2Dups@localhost monuser secret master
Hi John,
Where’s that 2nd article, in which you share that info with your servers for an orderly shutdown? That is precisely the problem that led me to find your article. 2 Servers plugged into the same UPS which only has 1 USB cable out. I have several Rpi’s laying about doing nothing, and this sounds like an elegant and useful purpose for one of them!
Best Regards,
Robert
Yeah, I need to address how to config the servers as clients of NUT!
Stay tuned.
I finally figured it out: https://www.howtoraspberry.com/2021/05/how-to-configure-an-orderly-shutdown/
Thanks so much for this great article. How could you make it send an email if it went from mains to battery power?
Just add an email command in upssched. Here’s the article: https://www.howtoraspberry.com/2021/05/how-to-configure-an-orderly-shutdown/
Request for followup post – How to send alerts via email.
Loss of power, power restored, discharging low battery etc would all be real useful.
Thanks!
It’s finally online: https://www.howtoraspberry.com/2021/05/how-to-configure-an-orderly-shutdown/
Wonderful article and everything worked perfectly for me. I mounted a small Pi Zero W on the side of my CyberPower SL series with this NUT config on Raspbian Lite.
Quick Question: Do you think the AC/DC adapter that comes with the Pi is necessary, or could I replace it with a short USB to micro-USB cable to one of the USB charger ports on my UPS?
I noticed the power adapter that came with the Pi Zero Vilros case is labeled for 2.5A output, while the USB charger ports on the CyberPower UPS are labeled for 2.4A output.
Disregard this comment. I easily determined that the USB ports are battery supported and work fine to power the Pi.
I would like to offer a few clarifications for your consideration to this excellent blog post…
In the statement: “This same “user” is then added to /etc/nut/upsd.conf. At the very bottom of the file, add:”
I think that should read: “/etc/nut/upsd.conf”
The statement: “Next, we need to setup upsmon. Again, I’m just going to add what I need to the end of the file.”
I think it would be more clear if it read: “Next, we need to setup /etc/nut/upsmon.conf. Again, I’m just going to add what I need to the end of the file.”
The statement: “The system is the name that we configured in the last bit.”
I think it would be more clear if it read: “The system is the hostname that we configured in the first bit.”
Consider telling users:
When NUT installs itself, it sometime fails to give group read access perms to the NUT services to the config folder. In the /etc/nut folder, enter the cmd: chmod 644 *
And, the following was important for me to get the companion iPhone app working, UPS Power Monitor (by Dariusz Niklewicz https://apps.apple.com/us/app/ups-power-monitor/id1500563567)…
NUT is picky about your needing to specify ALL of the interfaces it needs to listen on, the default local interfaces config doesn’t cut it for some client apps. So, in /etc/nut/upsd.conf file, add the following:
LISTEN 127.0.0.1 3493
LISTEN ::1 3493
LISTEN ups 3493 # locally resolved ip
LISTEN ups.local 3493 # externally resolved ip
Oops, error in my corrections…
In the statement: “This same “user” is then added to /etc/nut/upsd.conf. At the very bottom of the file, add:”
I think that should read: “/etc/nut/upsd.users”
I did end up having to do the following adjustments for my CyberPower UPS. …might be worth mentioning? …especially if users experience the ‘Stale Data’ ups connection error.
https://raspberrypi.stackexchange.com/posts/72926/revisions
Yeah, definitely worth a mention if people have trouble. Thanks, David!
Hello, great article.
When I browse to upsset.cgi and issue a command eg. Start Quick Battery Test, I get an error saying ‘ERR ACCESS-DENIED’.
Is there something I’ve missed?
Double-check your username and password setup in ‘upsd.users’.
Thanks for the guide. Everything is working fine until the webpage, under UPS Web Server. I’m trying to navigate to https://ups.local/cgi-bin/nut/upsset.cgi, but it doesn’t load. “Site can’t be reached.”
Not getting past the second step due to NUT failing with
Fatal error: unstable configuration
Driver failed to start (exit status=1)
Network UPS Tools – Generic contact-closure UPS driver 1.36 (2.7.4)
UPS type: APC Back-UPS (940-0020B/C cable)
unable to open auto: No such file or directory
Btw, I wanted my Pi Zeros to simply text me with state changes of my NUT monitored UPSs but, I found setting up mail and forwarding through a service kind of unwieldly. So, I just subscribed to textbelt.com for ~ $10 per yr for a lot of msgs, and it just takes a simple curl command. 🙂 I.e:
/bin/upssched-cmd
DATUM=`/bin/date`
UPSHOST=`/bin/hostname`
PHONE=”[phone #]”
TEXTBELT='[textbelt.com key]’
…
onbatterypower)
logger -t upssched-cmd “UPS went on battery power at this time”
MSG=$(echo “$DATUM:\nUPS [$UPSHOST] is using BATTERY !!”)
curl -X POST https://textbelt.com/text \
–data-urlencode phone=”$PHONE” \
–data-urlencode message=”$MSG” \
-d key=$TEXTBELT
;;
…
backonlinepower)
logger -t upssched-cmd “UPS reports power is back”
…
I have two identical APC XS1500 power supplies usb connected to my pi-4. I have the most current version of nut server/client installed and separate configuration entries for each UPS in ups.conf and upsmon.conf. When I run upsc apc1500-1 or apc1500-2 I get the output from the SAME UPS every time. I also see these messages on syslog. Any ideas how to uniquely identify each ups in the config?
Sep 21 18:25:32 upspi1 usbhid-ups[991]: libusb_get_interrupt: error submitting URB: Device or resource busy
Sep 21 18:25:32 upspi1 usbhid-ups[991]: Got disconnected by another driver: Device or resource busy
Sep 21 18:25:32 upspi1 kernel: [ 1416.663512] usb 1-1.3: usbfs: process 991 (usbhid-ups) did not claim interface 0 before use
I’ve never run into that. Maybe a solution can be gleaned from here: https://serverfault.com/questions/994338/how-can-i-fix-my-ups-repeatedly-disconnecting-and-reconnecting