[Nut-upsuser] Battery runtime not displaying

[Michal Soltys]

On 2013-06-14 23:16, ML mail wrote:
> Thanks for the help, with the apcsmart-old driver it works again! Didn't
> notice my UPS is now so "old" ;-)
>
> Here is the output of upsc with apcsmart-old driver:
>
> battery.alarm.threshold: 0
> battery.charge: 100.0
> battery.charge.restart: 00
> battery.date: 11/22/06
> battery.packs: 001
> battery.packs.bad: 000
> battery.runtime: 540
> battery.runtime.low: 120
> battery.voltage: 53.73
> battery.voltage.nominal: 048
> device.mfr: APC
> device.model: Smart-UPS RT 2000 XL
> device.serial:
> device.type: ups
> driver.name: apcsmart-old
> driver.parameter.pollinterval: 2
> driver.parameter.port: /dev/ttyS7
> driver.version: 2.6.4
> driver.version.internal: 2.1
> input.frequency: 49.98
> input.quality: FF
> input.sensitivity: A
> input.transfer.high: 253
> input.transfer.low: 161
> input.transfer.reason: simulated power failure or UPS test
> input.voltage: 233.2
> input.voltage.maximum: 233.2
> input.voltage.minimum: 233.2
> output.voltage: 229.3
> output.voltage.nominal: 230
> ups.delay.shutdown: 020
> ups.delay.start: 000
> ups.display.language: E
> ups.firmware: 416.7.I
> ups.firmware.old: 5YI
> ups.id: UPS_IDEN
> ups.load: 063.0
> ups.mfr: APC
> ups.mfr.date: 11/22/06
> ups.model: Smart-UPS RT 2000 XL
> ups.serial:
> ups.status: OL
> ups.temperature: 034.6
> ups.test.interval: 1209600
> ups.test.result: NO
>
> and here with apcsmart driver:
>
> battery.charge: 100.0
> battery.voltage: 53.73
> device.mfr: APC
> device.model: Smart-UPS RT 2000 XL
> device.serial:
> device.type: ups
> driver.name: apcsmart
> driver.parameter.pollinterval: 2
> driver.parameter.port: /dev/ttyS7
> driver.version: 2.6.4
> driver.version.internal: 3.04
> input.voltage: 233.2
> output.voltage: 229.3
> ups.firmware: 416.7.I
> ups.load: 063.0
> ups.mfr: APC
> ups.model: Smart-UPS RT 2000 XL
> ups.serial:
> ups.status: OL
> ups.temperature: 034.6
>

The "new" output is extremely terse, suggesting that it failed some 
regex check and went back to barebone essentials in panic. Anything in 
logs ?

If you could start the driver manually with

apcsmart -DDDDDDDDD -a <id>

and send me output, that would likely shed some light on the issue.

Thanks.