[Nut-upsdev] Setting up charge/voltage based shutdowns
Jim Klimov
jimklimov+nut at gmail.com
Sun Aug 6 16:39:45 BST 2023
Hello all again,
While looking at https://github.com/networkupstools/nut/issues/2014 I
understood that I am
not sure if currently NUT has a standard way of triggering a shutdown based
on remaining charge
or runtime, if a device/driver lacks a `battery.charge.low` setting but has
readings for the values
themselves.
Such an ability rings a bell to me, but maybe it is specific to some
drivers and is not
something ubiquitous - as being in the driver (and/or upsmon/upssched?)
core codebase?
So there are a few questions stemming from this:
* Can a user currently (on NUT 2.8.0) set up battery percentage based
shutdowns
when the "low" variable is missing in the driver/device? (Suggestions in
the ticket
linked above are welcome)
* Does it make sense to add something like this (if missing) to be
consistent on
un-capable devices? Or is it already there but too buried in code or docs?
* Would anyone step up to make this setup easy for newcomers (even if it
means "just"
finding a chapter in the docs/FAQ and making it better exposed, perhaps
in the Wiki),
or more so if design and coding are due? ;)
Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20230806/1265b945/attachment.htm>
More information about the Nut-upsdev
mailing list