2.8.2_1 blazer_usb, nutdrv_qx

[dennypage]

@LanterIT said in NUT Package (2.8.1 and above):

Does this have an influence on the behavior as long as the status is OL?

By default, NUT doesn't take action until the UPS declares a low battery, and battery voltage is reported as informational only. This is probably one reason why no-one has noticed the bug. Runtime is the same, although for most of the nutdrv_qx protocols, runtime isn't reported at all.

I'll put up a bug report and PR for the NUT folk later today or tomorrow. I don't know how long it will take for this to flow though to an a release on pfSense. In the interim you can use the last executable--the extra debug statements won't hurt anything.

Thank you for your patience and perseverance.

[dennypage]

@LanterIT NUT issue #2325.

[dennypage]

@dennypage said in NUT Package (2.8.1 and above):

@LanterIT NUT issue #2325.

The fix for accessing battery_voltage_reports_one_pack has been merged, and I expect it to be included in nut-devel snapshot.

I was hoping that the flag would simply be deleted, but the NUT maintainer seemed resistant to that. You will need to maintain the flag in your Extra Augments to driver section.