apcupsd- Back UPS 650VA
-
I’m running apcupsd v3.14.14 monitoring a Back UPS 650VA. I’m using the USB cable that came with the UPS. I’m using mostly default settings with UPS Cable and UPS Type set to usb.
It’s generally working, but I don’t pull all the information off the UPS. Specifically, I don’t get:
- MODEL
- STATUS
- LINEV
- LOADPCT
- SENSE
- LOTRANS
- HITRANS
- BATTV
- NUMXFERS
- TONBATT
- CUMONBATT
- SERIALNO
- BATTDATE
- NOMINV
- NOMBATTV
Should I be using settings other than the generic usb settings? It looks like 3.14.14 is the most current version of apcupsd, but it looks like it was released in 2016. Perhaps the Back UPS 650VA is too new for it to detect?
Thoughts?
-
Is that a farly new UPS? There's a problem where newer models don't work properly with either APCUPSD or NUT, but an older UPS works fine with both. This is a FreeBSD problem, as both work fine in Linux. I had a thread about that a while ago.
-
FWIW, I use the NUT Package and I get a ton of info for my old APC. Maybe try that?
Variable Value battery.charge 100.0 battery.charge.low 5 battery.charge.restart 0.0 battery.date 2019-07-19 battery.runtime 864.0 battery.runtime.low 180 battery.voltage 27.4 battery.voltage.nominal 24.0 device.mfr APC device.model Back-UPS BR 800 device.serial 5B1238T04722 device.type ups driver.name apcupsd-ups driver.parameter.pollinterval 60 driver.parameter.port 192.168.0.20:3551 driver.parameter.synchronous no driver.version 2.7.4 driver.version.internal 0.04 input.frequency 60.0 input.sensitivity M input.transfer.high 138.0 input.transfer.low 97.0 input.transfer.reason Low line voltage input.voltage 123.0 input.voltage.nominal 120 output.frequency 60.0 output.voltage 120.0 output.voltage.nominal 120 ups.date 2019-12-11 ups.delay.shutdown 0 ups.delay.start 0 ups.firmware 9.o6 .D USB FW:o6 ups.id Q6600 ups.load 33.0 ups.mfr APC ups.mfr.date 2012-09-19 ups.model Back-UPS BR 800 ups.realpower.nominal 540.0 ups.serial 5B1238T04722 ups.status OL ups.temperature 29.2 ups.test.interval 0 ups.test.result NO ups.time 05:57:00 -
If it works with the old UPS, but not the new, it's the same problem I had. Apparently there was a protocol change with newer APC UPSs. Linux was updated for it, but apparently not FreeBSD.
-
I have a Back-UPS RS 1500G (BR1500G) from ~August 2018 and it works fine with apcupsd 3.14.14. I get all the expected fields, including the ones you list.
It's set with UPS Cable=usb, UPS Type=usb, and nothing in the device field.
Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!
Need help fast? Netgate Global Support!
Do not Chat/PM for help!
-
Mine is an APC BE600M1. I have the same model connected to both my pfSense firewall and my desktop system running openSUSE 15.1. The one connected to the desktop is working fine, complete with all the stats. The one connected to pfSense has a lot of missing stats.
Here's what it shows in pfSense:
APC : 001,032,0720
DATE : 2019-12-11 11:02:31 -0500
HOSTNAME : firewall
VERSION : 3.14.14 (31 May 2016) freebsd
UPSNAME : APC BE600M1
CABLE : USB Cable
DRIVER : USB UPS Driver
UPSMODE : Stand Alone
STARTTIME: 2019-12-11 10:56:58 -0500
MODEL :
STATUS :
LINEV : 0.0 Volts
LOADPCT : 0.0 Percent
BCHARGE : 100.0 Percent
TIMELEFT : 40.2 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME : 0 Seconds
SENSE : Unknown
LOTRANS : -1.0 Volts
HITRANS : -1.0 Volts
ALARMDEL : Always
BATTV : 0.0 Volts
NUMXFERS : 0
TONBATT : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000000
SERIALNO :
BATTDATE :
NOMINV : 0 Volts
NOMBATTV : 0.0 Volts
END APC : 2019-12-11 11:02:32 -0500Also, whether it works with a particular model would depend on when that UPS was designed, not built or purchased.
-
Thanks all. You’ve confirmed my suspicion that it’s an age thing. I have a Back UPS 550 that’s 10-15 years old. It works fine with apcupsd on another NetGate.
Does anyone know if this is fatal or a mere inconvenience? I do see values for both BCHARGE and TIMELEFT. Both of these, I believe, are what apcupsd key off of in a power failure when determining when it’s time to shut down. However, it looks like both of these are monitored in the event of a power failure, and if I’m not getting a value for STATUS, it may never monitor BCHARGE or TIMELEFT. Does anyone know?
I imagine from everyone’s response that there’s really nothing we can do for FreeBSD except hope the condition gets fixed.
Thanks.
-
I'm no expert on UPS, but my understanding is that some signal is sent by the UPS to the attached computer. I know that it's possible for one computer to send that signal to another, when there are multiple computers sharing a UPS. One computer does the monitoring and then tells the others.
PfSense running on Qotom mini PC
i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
UniFi AC-Lite access pointI haven't lost my mind. It's around here...somewhere...
-
@mbrossar said in apcupsd- Back UPS 650VA:
I do see values for both BCHARGE and TIMELEFT. Both of these, I believe, are what apcupsd key off of in a power failure when determining when it’s time to shut down. However, it looks like both of these are monitored in the event of a power failure, and if I’m not getting a value for STATUS, it may never monitor BCHARGE or TIMELEFT. Does anyone know?
Pull the power cord and find out :-)
Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!
Need help fast? Netgate Global Support!
Do not Chat/PM for help!
-
@jimp said in apcupsd- Back UPS 650VA:
Pull the power cord and find out :-)
Actually, I just did. I see the power fail was detected and some things like battery percent and minutes remaining are updating, but many other items are not displayed.
So, hopefully, the UPS will do it's job and cause a proper shut down when needed, even if those items are missing.
-
@JKnott said in apcupsd- Back UPS 650VA:
I'm no expert on UPS, but my understanding is that some signal is sent by the UPS to the attached computer. I know that it's possible for one computer to send that signal to another, when there are multiple computers sharing a UPS. One computer does the monitoring and then tells the others.
That's what I do. My Windows host has an APC BR800 USB that is monitored by the APCUPSD Windows port. My pfSense VM uses NUT (but using Remote APCUPSD client mode) and reads the host's UPS and subsequently relays the UPS status to my XigmaNAS which also uses NUT. But from what's been discussed, may be moot if FreeBSD doesn't read them right.
-
@JKnott said in apcupsd- Back UPS 650VA:
I know that it's possible for one computer to send that signal to another, when there are multiple computers sharing a UPS.
I do that on my edge firewall and a couple internal systems. I have the apcupsd package setup as a server, and the other instances use it as a
nettype device in apcupsd. It works fine, so long as your switch and anything else between the UPS-backed hosts are also on the same UPS.You could use a Pi or something else Linux-y you already have on the UPS as the server and have pfSense speak to that across the network.
Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!
Need help fast? Netgate Global Support!
Do not Chat/PM for help!
-
@jimp said in apcupsd- Back UPS 650VA:
You could use a Pi or something else Linux-y you already have on the UPS as the server and have pfSense speak to that across the network.
I would rather the FreBSD folks get up to speed on this. I shouldn't have to get more hardware to fix a problem in the software.
-
That's the ideal fix, but if you already happen to have things in place, then it is a fine workaround. I have several Pis already doing various tasks, I'm sure others do as well. And the Pi I use as a USB console mux is already on my UPS, for example. So I wouldn't say go out and buy a Pi, but if it's already there, why not.
-
@jimp LOL! I have been thinking this very thing and will probably do it. If I do, I’ll report back.
