Nut upsdev - Oct 2016 - [HCL] <CyberPower> <PR2200LCDRT2U> supported by <snmp-ups>

root at Monitor:/etc/nut# upsc ups1

Init SSL without certificate database

battery.runtime: 133200.00

battery.runtime.elapsed: 0.00

device.mfr: CYBERPOWER

device.model: PR2200LCDRT2U

device.serial: 1

device.type: ups

driver.name: snmp-ups

driver.parameter.pollfreq: 1

driver.parameter.pollinterval: 2

driver.parameter.port: 192.168.1.7

driver.parameter.snmp_version: v1

driver.version: 2.7.2

driver.version.data: cyberpower MIB 0.1

driver.version.internal: 0.72

ups.firmware: 4.500

ups.mfr: CYBERPOWER

ups.model: PR2200LCDRT2U

ups.serial: 1

ups.status: OL
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20161029/6d108cd7/attachment.html>

[please use Reply-All - this list does not modify the reply-to header]
> On Oct 29, 2016, at 2:37 PM, Francois Cukier <francois at fcmail.ca>
wrote:
> 
> root at Monitor:/etc/nut# upsc ups1
> Init SSL without certificate database
> battery.runtime: 133200.00
This runtime seems high. The driver multiplies the SNMP value by 60 - does 2220
seconds sound more reasonable?
> battery.runtime.elapsed: 0.00
> device.mfr: CYBERPOWER
> device.model: PR2200LCDRT2U
> device.serial: 1
> device.type: ups
> driver.name: snmp-ups
> driver.parameter.pollfreq: 1
> driver.parameter.pollinterval: 2
> driver.parameter.port: 192.168.1.7
> driver.parameter.snmp_version: v1
> driver.version: 2.7.2
> driver.version.data: cyberpower MIB 0.1
> driver.version.internal: 0.72
> ups.firmware: 4.500
> ups.mfr: CYBERPOWER
> ups.model: PR2200LCDRT2U
> ups.serial: 1
> ups.status: OL
Does ups.status track the power state? (OL/OB/OB+LB)

Also, have you had a chance to do any shutdown testing?

Thanks for sending this.