Support for DIGITUS OnLine USV-System DN-170094

[uvolmer]

I'm a new owner of the UPS above. nut works in general with this device using the nutdrv_qx driver.
But sadly the battery.charge is zero and the battery voltage is wrong.

I found some reports regarding other products from this vendor with similar behavior but to solutions for me.

I tried both the 2.8.4 version and the current master branch.

/opt/nut/bin/upsc digitus1@localhost
battery.charge: 0
battery.runtime: 0094
battery.voltage: 2.25
battery.voltage.high: 39.00
battery.voltage.low: 31.20
battery.voltage.nominal: 36.0
device.mfr: Digitus
device.model: DN-17
device.serial:
device.type: ups
driver.debug: 0
driver.flag.allow_killpower: 0
driver.name: nutdrv_qx
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 0000
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0001
driver.state: quiet
driver.version: 2.8.4.826-826+g41daedfab
driver.version.data: Megatec 0.09
driver.version.internal: 0.48
driver.version.usb: libusb-0.1 (or compat)
input.current.nominal: 7.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 236.9
input.voltage.fault: 234.9
input.voltage.nominal: 220
output.voltage: 229.9
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: V002B000D0
ups.load: 18
ups.productid: 0000
ups.serial:
ups.status: OL
ups.temperature: 21.0
ups.type: online
ups.vendorid: 0001

[jimklimov]

You can try your luck with different explicitly specified protocol options for the driver, maybe some other would read it better (in particular, find a battery.charge elsewhere)?..

The battery.voltage here seems to be reported per cell (6 ~2V cells usually make up a nominally 12V PbAc assembly, and you may have 3 of those). Check the docs about override.battery.packs=N and battery_voltage_reports_one_pack.