[Nut-upsuser] ups.test.result meaning

Charles Lepple clepple at gmail.com
Sun Nov 1 03:13:19 GMT 2020

On Oct 31, 2020, at 8:13 PM, Rick Dicaire <kritek at gmail.com> wrote:
> On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com <mailto:tadawson at tpcsvc.com>> wrote:
> I'm going to guess that since your test runtime of 305 is very close to the low limit of 300, that's the warning. Not yet a fail, but very, very close. 

unfortunately, we don't get a ton of information back from the UPS about battery test results, so Tim's assessment is likely the explanation.

(Your UPS is literally sending back "2" for the test result, which maps to that message: https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L352 <https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L352> . That's part of the USB HID PDC standard - if there are other vendor-specific results returned by CyberPower UPSes, we aren't yet aware of them.)

> I tried setting 
> override.battery.runtime.low = 60

The override.* settings are basically used in upsd to replace the values that the driver sends through upsd to clients like upsc and upsmon. The values don't go back down through the driver to the UPS hardware (the intent is to mask bad values sent in the other direction).

In order to change a value stored in the UPS, you can use upsrw on the value. (Related: many CyberPower UPS models require the shutdown/startup timer  values to be rounded up to the next multiple of 60 seconds.)

The one case where you can set override.battery.runtime.low and change the shutdown behavior is when you also set the "ignorelb" option. (I don't see that listed in the driver.parameter.* section of the upsc output.) If you were not having any luck changing that variable with upsrw to affect the shutdown threshold, you could use "ignorelb" to let upsd determine when to send the shutdown command to the UPS (instead of just sending it when the UPS reports LB). https://networkupstools.org/docs/man/ups.conf.html#_ups_fields <https://networkupstools.org/docs/man/ups.conf.html#_ups_fields>

> in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to report only OL.
> I initiated another test.battery.start.quick.
> Same kind of result:
> battery.charge: 31
> battery.charge.low: 10
> battery.charge.warning: 20
> battery.mfr.date: CPS

It is still possible that the battery is old, and needs to be replaced. The usual guideline is 3-5 years for a lead-acid battery in an UPS.

Note that this is a case where you can stash the date you changed out the battery by overriding the "battery.mfr.date: CPS" variable's value with an actual date.

> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20201031/5c9c34dd/attachment.html>

More information about the Nut-upsuser mailing list