usbhid-ups: Complete the onlinedischarge_log_throttle_hovercharge option support
#2423
Labels
bug
impacts-release-2.8.2
Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)
USB
Milestone
Comments
jimklimov
added
bug
USB
impacts-release-2.8.2
jimklimov
added a commit
to jimklimov/nut
that referenced
this issue
May 2, 2024
…rge_log_throttle_*charge [networkupstools#2215, networkupstools#2423] Signed-off-by: Jim Klimov <[email protected]>
jimklimov
added a commit
to jimklimov/nut
that referenced
this issue
May 2, 2024
…rge_log_throttle_hovercharge setting [networkupstools#2215, networkupstools#2423] Signed-off-by: Jim Klimov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that during work on #2215 / #2216 something transpired that in currently committed code there is a C and config (string) variable of
onlinedischarge_log_throttle_hoverchargeand its handling in code, but no actual setting from the string into the number.Note: do not confuse with the also introduced
onlinedischarge_log_throttle_chargewhich allows to report only changes of thecurrent_chargeand not spam on cycles where it remains same as before.The text was updated successfully, but these errors were encountered: