<html><head></head><body><div dir="ltr">Very good point. I hope to write a beginners guide -- more like adopting my notes --on NUT.<div><br></div><div>I could summarise your point that technically one should only override settings that NUT can act upon (like those settings that control Low Battery or, as stated in the documentation if the reported value is known to be incorrect. Overriding a variable that is out of scope for NUT (as with upd.delay.start) only leads to false depictions of facts; the reading would not match what will actually happen.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 10 Mar 2024 at 00:21, Charles Lepple <<a href="mailto:clepple_at_gmail.com_chribonn@duck.com">clepple_at_gmail.com_chribonn@duck.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mar 9, 2024, at 6:14 PM, Charles Lepple <<a href="mailto:clepple@gmail.com" target="_blank">clepple@gmail.com</a>> wrote:<br>
> <br>
> On Mar 9, 2024, at 5:16 PM, <a href="mailto:chribonn@duck.com" target="_blank">chribonn@duck.com</a> wrote:<br>
>> I used the override.ups.delay.start = -1 in nut.conf and this is now being reported.<br>
<br>
The ups.conf man page describes the direction that the data flows with override.*:<br>
<br>
> Use with caution! This will only change the appearance of the variable to the outside world [read: clients connected to upsd], internally in the UPS the original value is used.<br>
<br>
<a href="https://networkupstools.org/docs/man/ups.conf.html#_ups_fields" rel="noreferrer" target="_blank">https://networkupstools.org/docs/man/ups.conf.html#_ups_fields</a><br>
<br>
-- <br>
Charles Lepple<br>
clepple@gmail<br>
<br>
<br>
</blockquote></div>
</body></html>