search for: openups_scale_vbat_fun

..._in, v_bat, v_out, i_ltc; +static int on_input; static char openups_scratch_buf[20]; @@ -129,9 +131,9 @@ static const char *openups_off_fun(double value); static const char *openups_scale_vin_fun(double value); static const char *openups_scale_vout_fun(double value); -/* static const char *openups_scale_vbat_fun(double value); */ -static const char *openups_scale_ccharge_fun(double value); -static const char *openups_scale_cdischarge_fun(double value); +static const char *openups_scale_vbat_fun(double value); +static const char *openups_scale_input_current_fun(double value); +static const char *openups_sca...

Hi, I've been checking out NUT with an OpenUPS board over the last couple of weekends, and have noticed that it doesn't seem to report sensible values. This lead me to investigate usbhid-ups and delve into various issues. As mentioned in a github issue, one of the problems is with the report descriptor - dumping this from the usbhid-ups debug output and picking through it reveals that

...+static const char *openups_online_fun(double value); +static const char *openups_nobattery_fun(double value); +static const char *openups_off_fun(double value); + +static const char *openups_scale_vin_fun(double value); +static const char *openups_scale_vout_fun(double value); +static const char *openups_scale_vbat_fun(double value); +static const char *openups_scale_ccharge_fun(double value); +static const char *openups_scale_cdischarge_fun(double value); +static const char *openups_temperature_fun(double value); + +static info_lkp_t openups_charging_info[] = { + {0, NULL, openups_charging_fun} +}; + +static inf...