search for: battery_charge_level

...e, there are a few `setval()` hits, namely: * adelsystem_cbi.c: "BVAL_HIALRM_I", * al175.c: "BATTERY VOLTAGE STATUS", * asem.c: "charge_percentage >= hb_threshold (default 75)", * generic_modbus.c: "usually ... charging state > 85%", * pijuice.c: "battery_charge_level > HIGH_BATTERY_THRESHOLD (macro 75)" * similarly in hwmon_ina219.c added by PR https://github.com/networkupstools/nut/pull/2430 that started this discussion The first one seems to be about an alarm, the second - not sure, and the rest are about passing a threshold with no apparent implicat...

...hits, namely: > > * adelsystem_cbi.c: "BVAL_HIALRM_I", > * al175.c: "BATTERY VOLTAGE STATUS", > * asem.c: "charge_percentage >= hb_threshold (default 75)", > * generic_modbus.c: "usually ... charging state > 85%", > * pijuice.c: "battery_charge_level > HIGH_BATTERY_THRESHOLD (macro 75)" > * similarly in hwmon_ina219.c added by PR > https://github.com/networkupstools/nut/pull/2430 that started this > discussion > > The first one seems to be about an alarm, the second - not sure, and the > rest are about passing a thresh...

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > During discussion at > https://github.com/networkupstools/nut/pull/2430#discussion_r1592317940 I > found that while `nut-names.txt` documents the `battery.charge.low` as the > "Remaining battery level when UPS switches to LB (percent)", there is no > counterpart as `battery.charge.high`.

...> * adelsystem_cbi.c: "BVAL_HIALRM_I", > > * al175.c: "BATTERY VOLTAGE STATUS", > > * asem.c: "charge_percentage >= hb_threshold (default 75)", > > * generic_modbus.c: "usually ... charging state > 85%", > > * pijuice.c: "battery_charge_level > HIGH_BATTERY_THRESHOLD (macro 75)" > > * similarly in hwmon_ina219.c added by PR > > https://github.com/networkupstools/nut/pull/2430 that started this > > discussion > > > > The first one seems to be about an alarm, the second - not sure, and the > > r...