Jim Klimov via Nut-upsdev writes:
> 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`
My view is that this rests at the upsmon side. Each monitor would look at the status and decide to act as per its own configuration. Sent from my iPhone with iTyposOn Aug 6, 2023, at 5:25 PM, Jim Klimov wrote:From my understanding, alone with other NUT behaviors it would not.Even if NUT
>From my understanding, alone with other NUT behaviors it would not.
Even if NUT drivers already do (or are changed to) react to the actual
charge/runtime going below this setting to fabricate an LB status, this as
a driver setting/override would have immediate effect on all clients like
`upsmon`
Hi Jim,
I was thinking about setting different values for each device , so the first
system has higher values and shutdowns
earlier:override.battery.charge.lowoverride.battery.runtime.low
Won’t it work ?
Best Regards,Strahil Nikolov
On Sunday, August 6, 2023, 7:41 PM, Jim Klimov via Nut-upsdev
