search for: apcs01

I got around to unplugging my UPS and I found it doesn't last nearly as long as estimated. Is the "upsmon[1446]: UPS desktop_ups at localhost battery is low" logged when "battery.runtime:" = "battery.runtime.low: 120"? Does any make better batteries that don't go down faster when they get old? battery.charge: 100 battery.charge.low: 10

...test.battery* instant commands: https://networkupstools.org/docs/user-manual.chunked/apcs02.html (I don't know if test.panel.start is exactly the same.) More detailed status is typically reported in the "ups.test.result" variable: https://networkupstools.org/docs/user-manual.chunked/apcs01.html (The driver should pick up on this and also include "RB" (replace battery) in "ups.status", but again, this is hard to test.) James: in your case, this might be due to your APC model not showing the full set of variables over the standard USB HID interface. (Search the we...

https://alioth.debian.org/tracker/?func=detail&atid=411544&aid=311678&group_id=30602 I wanted to do it somewhat more flexibly/elegantly, so this is what I've been thinking about (or rather sitting on mostly implemented piece, still needing some testing though): - any variable that may include multiple data, would be (during runtime) split into appropriate *.N.* sets; for