apc ups commlost

Started by JediFonger, July 20, 2026, 04:49:40 PM

Previous topic - Next topic
OPNsense 26.7-amd64
^running latest

any tips on gettin APC UPS battery connected via usb online? have os-nut & apcupsd installed but i got:
APC      : 001,017,0434
DATE     : 2026-07-16 00:46:52 -0400 
HOSTNAME : router.localdomain
VERSION  : 3.14.14 (31 May 2016) freebsd
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2026-07-16 00:46:44 -0400 
STATUS   : COMMLOST

usbconfig doesn't see it. on a windows box off the same connection it works perfectly fine. any tips?

I haven't made the switch to OPNsense 26.7 yet.

Was Apcupsd communicating with the UPS just prior to the upgrade to 26.7?

Have you ruled out the USB port by plugging the cable in to other USB ports on OPNsense firewall?

Have you ruled out the USB cable by using another known working cable?

Another test is to disable Apcupsd and configure NUT to monitor the UPS using the UPS Type 'USBHID-Driver' and see if it is able to communicate with the UPS.

i honestly can't remember because i this setup is new and i coulda sworn it worked? maybe, but i was plugging it in at the same time i was upgrading to 26.7. maybe i dreamt it, i dunno if there logs to check.

it's not the UPS/cable because i can take my w11 laptop plug it in and everything is detected and APC UPS software can see it everything works 100% fine.

currently os-nut tool service isn't running, i assume it's supposed to run? i dunno. i haven't ever gotten this to work yet, but i suspect usbconfig not detecting the ups is probably a big issue.

Quote from: lmoore on Today at 05:27:49 AMI haven't made the switch to OPNsense 26.7 yet.

Was Apcupsd communicating with the UPS just prior to the upgrade to 26.7?

Have you ruled out the USB port by plugging the cable in to other USB ports on OPNsense firewall?

Have you ruled out the USB cable by using another known working cable?

Another test is to disable Apcupsd and configure NUT to monitor the UPS using the UPS Type 'USBHID-Driver' and see if it is able to communicate with the UPS.

Quote from: JediFonger on Today at 06:58:36 AMcurrently os-nut tool service isn't running, i assume it's supposed to run?

- This may be the cause of os-nut service not running on you system - https://github.com/opnsense/plugins/issues/5387
- Apply a patch to 26.7 to fix an OPNsense display issue affecting NUT - https://forum.opnsense.org/index.php?topic=52380.msg270981#msg270981

In the past, I did find that when apcupsd initiated a shutdown of OPNsense, it would simply halt the system rather than power it off. If your UPS was commanded to got to sleep/hibernate x number of seconds after shut down, you might be alright, otherwise, if the utility power returns before the UPS has gone off and the UPS is not configured to power-cycle itself after such an event, one would need to forcibly power-cycle the OPNsense box as even a PS2 keyboard is useless at this point - see https://github.com/opnsense/plugins/issues/5383.

My OPNsense test box is currently off as I have other test machines on the bench. It will be a few days at least before I can perform any tests with OPNsense.

If either of the two issues in GitHub are at play and affecting you, you'd be better off disabling Apcupsd and using NUT and the USB driver mentioned earlier.