<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On Oct 31, 2020, at 8:13 PM, Rick Dicaire <<a href="mailto:kritek@gmail.com" class="">kritek@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <<a href="mailto:tadawson@tpcsvc.com" class="">tadawson@tpcsvc.com</a>> wrote:<br class=""></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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. <br class=""></blockquote><div class=""><br class=""></div></div></div></div></blockquote><div>Rick,</div><div><br class=""></div><div>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.</div><div><br class=""></div><div>(Your UPS is literally sending back "2" for the test result, which maps to that message: <a href="https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L352" class="">https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L352</a> . 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.)</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div class="">I tried setting </div><div class=""><font face="monospace" class="">override.battery.runtime.low = 60</font></div></div></div></div></blockquote><div><br class=""></div><div>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).</div><div><br class=""></div><div>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.)</div><div><br class=""></div><div>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). <a href="https://networkupstools.org/docs/man/ups.conf.html#_ups_fields" class="">https://networkupstools.org/docs/man/ups.conf.html#_ups_fields</a></div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div class=""><font face="arial, sans-serif" class="">in ups.conf, and waited for the UPS to reach 100% charge, and </font><font face="monospace" class="">ups.status </font><font face="arial, sans-serif" class="">to report only </font><font face="monospace" class="">OL.</font></div><div class=""><font face="monospace" class=""><br class=""></font></div><div class=""><font face="arial, sans-serif" class="">I initiated another </font><font face="monospace" class="">test.battery.start.quick</font><font face="arial, sans-serif" class="">.</font></div><div class=""><font face="arial, sans-serif" class="">Same kind of result:</font></div><div class=""><font face="arial, sans-serif" class=""><br class=""></font></div><div class=""><font face="monospace" class="">battery.charge: 31<br class="">battery.charge.low: 10<br class="">battery.charge.warning: 20<br class="">battery.mfr.date: CPS<br class=""></font></div></div></div></div></blockquote><div><br class=""></div><div>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.</div><div><br class=""></div><div>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.</div><br class=""><blockquote type="cite" class=""><div class="">_______________________________________________<br class="">Nut-upsuser mailing list<br class=""><a href="mailto:Nut-upsuser@alioth-lists.debian.net" class="">Nut-upsuser@alioth-lists.debian.net</a><br class="">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</div></blockquote></div><br class=""></body></html>