search for: 10kv

...t is that "battery.voltage" and "battery.charge" were not always reported correctly with nutdrv-qx driver (might be handled better by blazer drivers though), and the overrides tried by issue posters did not help them with original state of NUT codebase. I tried it on three ups: 10kv online, 3kv online, 2kv offline. all the battery.voltage are fine and the same value as 2.7.4. the battery.charge report of 10kv and 3kv are fine. but 2kv is wrong. with 2.7.4 the 2kv battery.charge is reporting 100. but the new code is reporting 67. details below: 10KV: ./nutdrv_qx -a ftups -d1 N...

...t is that "battery.voltage" and "battery.charge" were not always reported correctly with nutdrv-qx driver (might be handled better by blazer drivers though), and the overrides tried by issue posters did not help them with original state of NUT codebase. I tried it on three ups: 10kv online, 3kv online, 2kv offline. all the battery.voltage are fine and the same value as 2.7.4. the battery.charge report of 10kv and 3kv are fine. but 2kv is wrong. with 2.7.4 the 2kv battery.charge is reporting 100. but the new code is reporting 67. details below: 10KV: ./nutdrv_qx -a ftups -d1 N...

Cheers, One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 The gist of it is that "battery.voltage" and "battery.charge" were not always reported correctly with nutdrv-qx driver (might be handled better by blazer drivers though), and the overrides