UPS Load and Battery Charge always zero using nutdrv_qx

[LucasTor]

UPS Load and Battery Charge always zero using nutdrv_qx

[jimklimov]

Technically, it could also be the driver. There were some changes about calculating or otherwise determining battery charges and runtimes, running up to NUT 2.8.1 I think. I'm on the road now; check the reference trail from #1279 and #1652 tickets...

Are you in position to re-try with the older NUT release that you were using, to see if it really is our regression?

Also, am I right that here you use a serial-port connection (not USB)? Did you before?

[LucasTor]

Thanks @jimklimov, that was it, just changed the docker image to 2.8.0-r4, and now I have data for the load and battery percentage back

I am using USB for it, just as before

Here is another upsc log, in case that helps with debugging

battery.charge: 100
battery.voltage: 13.40
battery.voltage.high: 26.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.mfr: TS SHARA 230727
device.model: Sen 2U  15
device.type: ups
driver.name: nutdrv_qx
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/serial/by-id/usb-STMicroelectronics_STM32_Virtual_ComPort_00000000001A-if00
driver.parameter.synchronous: auto
driver.version: 2.8.0
driver.version.data: Megatec 0.06
driver.version.internal: 0.32
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 100.0
input.frequency: 60.0
input.frequency.nominal: 60
input.voltage: 223.0
input.voltage.fault: 223.0
output.voltage: 115.0
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: V01030503A
ups.load: 13
ups.status: OL
ups.temperature: 27.0
ups.type: offline / line interactive

[jimklimov]

Well, the UPS/firmware is not broken - that's good news :)

Figuring out why we lost the info in 2.8.1 is gonna be a head-scratcher...

Are you by chance in position to build NUT from source and test the current master code base (in case some of the changes after 2.8.1 fixed this bit)? https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests outlines how to build and test drivers right from the build workspace, without necessarily changing your OS installed variant of NUT.

Or at least to run that 2.8.1 container with a higher debug verbosity, check https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity for suggestions in this regard...

[LucasTor]

Hey! Sorry for the delayed response, had a busy day today, I will read through the instructions on how to build from source, and let you know if I have any luck getting the missing data from the UPS
By the way, can I build it on an M1 Mac? As I plan on doing on my work PC instead of my homelab server

[jimklimov]

Macs should work too, as far as compilation goes at least - each NUT iteration of the past couple of years is tested on CircleCI Mac environments. There were some recently posted issues (search by label) regarding some XML manifests for further OS integration. Don't have one, so that's as much as I can elaborate.