low battery events when no battery.*.low variables available

[xorbug]

low battery events when no battery.*.low variables available

[jimklimov]

Can't really say right now, perhaps the best approach would be to run an experiment with some load you are okay to have abruptly powered off (a lamp?)

As the NUT docs highlight, such hardware-backed warnings depend on hardware abilities (and the presence of protocol support to set values, if configurable, and that NUT contributors found a way to send such commands). Some dumber devices may have the low-battery status just raised by hardware at a factory-defined situation.

Gotta really look into sources to confirm the next statement, but I am under impression that an override...low setting can be interpreted by drivers and/or upsmon to trigger shutdowns at specified points. There were mailing list discussions to that effect, with a set-up using several dummy-ups drivers to relay info from a "physical device" driver with different overrides to initiate shutdowns at different times for loads of different criticality - their upsmons MONITOR different dummy devices.

[xorbug]

Thanks @jimklimov, I think I can have some test when I can disconnect my devices a bit then, and report back (even just for the records, if my individual case is not representative enough of anything).