[Nut-upsuser] Low Battery event not occurring

Charles Lepple clepple at gmail.com
Sat May 14 11:52:18 UTC 2016

> battery.charge: 3
> battery.charge.low: 10
> battery.charge.warning: 30
> battery.runtime: 93
> battery.temperature: 32.9
> battery.type: PbAC
> battery.voltage: 46.4
> battery.voltage.nominal: 48.0

Is it possible that battery.charge is really 30% rather than 3%?

The 3016 protocol models have issues with scaling on some of the voltages and frequencies. You can see this by killing the driver, and restarting it with '-DDD'. If you want to mail that log to the list, please gzip it first. Also, only about the first minute would be necessary.

> device.mfr: Tripp Lite
> device.model: TRIPP LITE SMART2200RM2UN
> device.serial: nunyabiznis

Pretty sure the letters in the serial numbers are uppercase :-)

Given how many of the model names are reused for very different hardware, it can be helpful to see at least the first few digits of a serial number, but in this case, I don't think we have too many other reports of this hardware to go on. The closest ones seem to be: http://networkupstools.org/ddl/Tripp_Lite/SMART2200RMXL2U.html

> If I understand the NUT process correctly, it looks for this LB status in order to create the POWERDOWNFLAG.  "In upsmon.conf, add a POWERDOWNFLAG directive with a filename. upsmon will create this file when the UPS needs to be powered off during a power failure when low battery is reached."

That is correct. You can also configure NUT drivers to ignore the UPS's LB flag and synthesize it from battery.charge or battery.runtime: http://networkupstools.org/docs/man/ups.conf.html (search for 'ignorelb')

Charles Lepple
clepple at gmail

More information about the Nut-upsuser mailing list