Hello, I am having a heck of a time with false low battery alarms right now. It has been going on for the last couple of months. I originally started getting them with a UPS that was 1-2 years old so I thought it was time to change it out and buy a new one. I'm still getting the false alarms with the brand new one. The status is "OL LB" which is strange to me. I have a CyberPower 1500VA running on Debian (testing) Linux connected via USB. This was also the same model I had before, so I've used this for a long time with no problems until recently. I have tried to play with the low battery settings in ups.conf to no avail. Here is my ups.conf as of now: [myups1] driver = usbhid-ups port = auto vendorid = 0764 desc = "CyberPower 1500VA" pollinterval = 10 ignorelb override.battery.charge.low = 60 override.battery.charge.warning = 80 override.battery.runtime.low = 600 Here is some information regarding my system. $ uname -a Linux rockenfield 5.6.0-2-amd64 #1 SMP Debian 5.6.14-1 (2020-05-23) x86_64 GNU/Linux $ dpkg --list | grep -E "\bnut" ii nut 2.7.4-12 all network UPS tools - metapackage ii nut-client 2.7.4-12 amd64 network UPS tools - clients ii nut-server 2.7.4-12 amd64 network UPS tools - core system $ systemctl --lines=0 status nut-client.service nut-server.service nut-monitor.service nut-driver.service ● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-06-15 10:46:21 PDT; 2 days ago Main PID: 1741 (upsmon) Tasks: 2 (limit: 18777) Memory: 4.8M CGroup: /system.slice/nut-monitor.service ├─1740 /lib/nut/upsmon └─1741 /lib/nut/upsmon ● nut-server.service - Network UPS Tools - power devices information server Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-06-15 10:46:21 PDT; 2 days ago Main PID: 1738 (upsd) Tasks: 1 (limit: 18777) Memory: 1.4M CGroup: /system.slice/nut-server.service └─1738 /lib/nut/upsd ● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-06-15 10:46:21 PDT; 2 days ago Main PID: 1741 (upsmon) Tasks: 2 (limit: 18777) Memory: 4.8M CGroup: /system.slice/nut-monitor.service ├─1740 /lib/nut/upsmon └─1741 /lib/nut/upsmon ● nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor preset: enabled) Active: active (running) since Mon 2020-06-15 10:46:20 PDT; 2 days ago Main PID: 1680 (usbhid-ups) Tasks: 1 (limit: 18777) Memory: 1.3M CGroup: /system.slice/nut-driver.service └─1680 /lib/nut/usbhid-ups -a myups1 $ upsc myups1 Init SSL without certificate database battery.charge: 100 battery.charge.low: 60 battery.charge.warning: 80 battery.mfr.date: CPS battery.runtime: 1530 battery.runtime.low: 600 battery.type: PbAcid battery.voltage: 24.0 battery.voltage.nominal: 24 device.mfr: CPS device.model: LX1500GU device.serial: DAGJY2000603 device.type: ups driver.flag.ignorelb: enabled driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 10 driver.parameter.port: auto driver.parameter.synchronous: no driver.parameter.vendorid: 0764 driver.version: 2.7.4 driver.version.data: CyberPower HID 0.4 driver.version.internal: 0.41 input.voltage: 119.0 input.voltage.nominal: 120 output.voltage: 136.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 30 ups.mfr: CPS ups.model: LX1500GU ups.productid: 0501 ups.realpower.nominal: 900 ups.serial: DAGJY2000603 ups.status: OL ups.test.result: No test initiated ups.timer.shutdown: -60 ups.timer.start: -60 ups.vendorid: 0764 Any help is greatly appreciated. I have some automation (openHAB, system scripts, etc) that react accordingly. I'm also getting trampled on console sessions will wall messages. Thanks! -MikeD
> On Jun 18, 2020, at 12:39 PM, Mike Dillinger wrote: > > ups.test.result: No test initiatedI’d recommend a battery test. Starting the test via the front panel should be sufficient, or you might be able to do it with upscmd. This should let the UPS firmware discharge the battery a bit, and see how long it should last. Conceptually, “OL LB” is not inconsistent- it means the UPS has AC power, but the battery state of charge is reading low (as might happen after the UPS restarts after an extended power failure) . You might have a CPS unit where the battery voltage returned to NUT is hard-coded to 24.0 V, which is annoying, but should not affect internal decisions about shutdown. Example: https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html and https://github.com/networkupstools/nut/issues/459#issuecomment-325163688 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200622/6162af67/attachment.html>
On Monday 22 June 2020 08:19:15 Charles Lepple wrote:> > On Jun 18, 2020, at 12:39 PM, Mike Dillinger wrote: > > > > ups.test.result: No test initiated > > I’d recommend a battery test. Starting the test via the front panel > should be sufficient, or you might be able to do it with upscmd.from man pi at rpi4:~ $ upscmd -l myups Instant commands supported on UPS [myups]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper beeper.off - Obsolete (use beeper.disable or beeper.mute) beeper.on - Obsolete (use beeper.enable) load.off - Turn off the load immediately load.off.delay - Turn off the load with a delay (seconds) load.on - Turn on the load immediately load.on.delay - Turn on the load with a delay (seconds) shutdown.return - Turn off the load and return when power is back shutdown.stayoff - Turn off the load and remain off shutdown.stop - Stop a shutdown in progress test.battery.start.deep - Start a deep battery test test.battery.start.quick - Start a quick battery test test.battery.stop - Stop the battery test pi at rpi4:~ $ upscmd myups test.battery.start.quick Username (pi): Password: Unexpected response from upsd: ERR ACCESS-DENIED Looking at /etc/nut/uspd.users, I (me, pi) should be able to do that. ??? Some help plz.> This should let the UPS firmware discharge the battery a bit, and see > how long it should last. > > Conceptually, “OL LB” is not inconsistent- it means the UPS has AC > power, but the battery state of charge is reading low (as might happen > after the UPS restarts after an extended power failure) . You might > have a CPS unit where the battery voltage returned to NUT is > hard-coded to 24.0 V, which is annoying, but should not affect > internal decisions about shutdown. Example: > https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html > and > https://github.com/networkupstools/nut/issues/459#issuecomment-3251636 >88Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
> *From:* Charles Lepple [mailto:clepple at gmail.com] > *To:* Mike Dillinger <miked at softtalker.com> > *Cc:* nut-upsuser at alioth-lists.debian.net > *Date:* Monday, June 22, 2020, 5:19 AM PDT > *Subject:* [Nut-upsuser] Low Battery Problems > > I’d recommend a battery test. Starting the test via the front panel should be sufficient, or you might be able to do it with upscmd. > > This should let the UPS firmware discharge the battery a bit, and see how long it should last. > > Conceptually, “OL LB” is not inconsistent- it means the UPS has AC power, but the battery state of charge is reading low (as might happen after the UPS restarts after an extended power failure) . You might have a CPS unit where the battery voltage returned to NUT is hard-coded to 24.0 V, which is annoying, but should not affect internal decisions about shutdown. Example: https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html and https://github.com/networkupstools/nut/issues/459#issuecomment-325163688 >Thanks for the information. I did initiate a deep test and it finished successfully. I spent a fair amount of time look at this issue this weekend and ended up lowering override.battery.charge.low from 60 to 40 and the problem went away. I haven't had any of the "OL LB" warnings since changing that threshold which has not been the case for a while now. I think I'll try bumping override.battery.charge.low back up to 60 after running the test that you suggested and see how that works out. Thanks again! -MikeD