Nut upsuser - Jun 2009 - upsmon says ONBATT when status: TRIM

Hi,

I've been getting emails from upsmon saying:

 Subject: UPS PW5125 at localhost notification: ONBATT

 UPS PW5125 at localhost on battery

But then the machines on the UPS stay on for hours; we haven't got
that kind of runtime, more like 10-20 minutes.

After a few occurrences, it now happened at a time where I could log
in to see in real time what is happening and:

$ upsc PW5125 | grep status
ups.status: TRIM

So there is no risk of the UPS running out of battery power :) Not
sure if it is on battery or not, but even if it is on battery, the
battery is being recharged concurrently, so, well, no human
intervention needed.

Could the upsmon email in this case be tweaked to be clearer?
Something like

 Subject: UPS PW5125 at localhost notification: TRIM

 UPS PW5125 at localhost trimming input line power

My NOTIFYCMD is just

 #! /bin/sh
 echo "$*" | mailx -s "UPS ${UPSNAME} notification:
${NOTIFYTYPE}" EMAIL

In case the rest of upsc is useful:

ambient.temperature: 52
battery.charge: 95
battery.runtime: 1003
battery.voltage: 52.26
driver.name: bcmxcp
driver.parameter.baud_rate: 9600
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.2.2
driver.version.internal: 0.14
input.frequency: 50.00
input.voltage: 240
output.current:  3.2
output.frequency: 50.00
output.phases: 1
output.voltage: 209
output.voltage.nominal: 230
ups.firmware: Cont:01.01 Inve:01.01
ups.load:  45.6
ups.model: PW5125     1500VA
ups.power.nominal: 1500
ups.serial: UY044A0405
ups.status: TRIM

> Hi,
Hi Lionel,
>
> I've been getting emails from upsmon saying:
>
>  Subject: UPS PW5125 at localhost notification: ONBATT
>
>  UPS PW5125 at localhost on battery
>
> But then the machines on the UPS stay on for hours; we haven't got
> that kind of runtime, more like 10-20 minutes.
>
> After a few occurrences, it now happened at a time where I could log
> in to see in real time what is happening and:
>
> $ upsc PW5125 | grep status
> ups.status: TRIM
>
This is fixed in a later release of the driver.

From change log:
Wed Jan 14 21:45:10 UTC 2009 / Kjell Claesson <kjell.claesson at
epost.tidanet.se>

  - drivers/bcmxcp.c: Changed status info to include OL with BYPASS, BOOST,
TRIM.
    Add some more meters like power and current.nominal (max).

And also if you upgrade to a later release you have load segment control
and some more info from the PW5125 you run. 

Like this:

~ $ upsc pw5115         
ambient.temperature: 28            
ambient.temperature.high: 70       
battery.charge: 98                 
battery.runtime: 2060              
battery.voltage: 26.95             
driver.name: bcmxcp                
driver.parameter.baud_rate: 9600   
driver.parameter.pollinterval: 2   
driver.parameter.port: /dev/ttyS0  
driver.parameter.shutdown_delay: 10
driver.version: 2.4.1              
driver.version.internal: 0.21      
input.frequency: 49.65
input.frequency.high: 54
input.frequency.low: 46
input.frequency.nominal: 50
input.transfer.boost.high: 207
input.transfer.high: 266
input.transfer.low: 171
input.transfer.trim.low: 243
input.voltage: 234
input.voltage.nominal: 230
outlet.1.delay.shutdown: -1
outlet.1.delay.start: 1
outlet.1.id: 1
outlet.1.status: On
outlet.2.delay.shutdown: -1
outlet.2.delay.start: 2
outlet.2.id: 2
outlet.2.status: On
output.current:  0.0
output.current.nominal:  4.5
output.frequency: 49.65
output.phases: 1
output.voltage: 234
output.voltage.nominal: 230
ups.beeper.status: enabled
ups.firmware: Cont:02.03 Inve:02.03
ups.load:   0.0
ups.model: PW5125     1000VA
ups.power: 0
ups.power.nominal: 1000
ups.serial: GB282A0427
ups.status: OL

Regards
Kjell