[Nut-upsuser] Low Battery Problems

Mike Dillinger miked at softtalker.com
Fri Jun 26 21:05:22 BST 2020

>> *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. 

Hi Charles, et al,

Just to close the loop on this... Running the test has fixed the problem.  It's been a few days now and no more false LB warnings. I've returned the override.battery.charge.low setting to 60 as well and everything is fine.  Thanks a lot for your help.


More information about the Nut-upsuser mailing list