[Nut-upsuser] Overriding battery.runtime.low

[Peter Bishop]

Thanks for that, Charles. The "ignorelb" setting did exactly what I needed. Although, as it turns out, I didn't need it :-/ I'm new to NUT so this is a new install and I didn't know that the driver would actually shutdown the UPS; this is why the power ran out before the shutdown of my remote systems had completed. By disabling that functionality, the original 5 mins was sufficient. I don't need the UPS shutdown functionality, I just need everything cleanly shutdown before the battery runs out. 

Thanks again.

> On 24 Feb 2021, at 14:03, Charles Lepple <clepple at gmail.com> wrote:
> 
> On Feb 24, 2021, at 4:02 AM, Peter Bishop via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote:
>> 
>> I have an APC BR1500GI and want to run my devices for the longest possible period. Consequently I want to use the battery.runtime.low setting, sufficient to allow my devices to shutdown. The APC has a setting of 5 minutes for this purpose but I want to change this to 10 minutes, so have added the “override.battery.runtime.low = 600” setting to the ups.conf file. However, this override doesn’t appear to be causing the NUT setup to initiate a shutdown.
>> 
>> Does the “override.battery.runtime.low” work for this purpose or does it just change the value being displayed by upsc? If it’s the latter, is there a way to achieve the override for the low battery setting? For testing purposes I changed this value to “2500”, switched off the mains, and monitored the “battery.runtime” value. It dropped below “2500” (and remained there) but the “battery is low” message was never generated.
> 
> The override.* settings can cover both cases. If you just provide override.battery.runtime.low, you are just replacing what is sent from the driver to upsd, and then on to clients like upsc. (In particular, this doesn't send any settings adjustments back to the UPS.) Since upsmon is watching ups.status for the UPS-provided LB bit (by default), this isn't sufficient to modify shutdown behavior.
> 
> The subtle difference in examples like this:
> 
>   https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-lists.debian.net%2Fpipermail%2Fnut-upsuser%2F2020-August%2F011977.html&data=04%7C01%7C%7C09b7427293084d87c1a208d8d8ccec7a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637497721942032252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yG%2BP5BARevtBvoJ2vjYvg11sCJgWG8p6Gr1dNxTrnUs%3D&reserved=0
> 
> is the use of "ignorelb" in concert with "override.battery.runtime.low".
> 
> I also ran across this thread while looking up info on the BR1500GI:
> 
>   https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-lists.debian.net%2Fpipermail%2Fnut-upsuser%2F2020-November%2F012172.html&data=04%7C01%7C%7C09b7427293084d87c1a208d8d8ccec7a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637497721942032252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CGNtzukW%2FPj8dZSKI6br6VPwjzx2Z9bwGcFVhTmTNCI%3D&reserved=0
> 
> I don't think we resolved the shutdown issue (or got debug logs to dig deeper).
> 
>> 
>> Required information:
>> 
>>                OS: Linux **** 5.4.83+ #1379 Mon Dec 14 13:06:05 GMT 2020 armv6l GNU/Linux
>>                NUT version: 2.7.4-8
>>                NUT installation: package
>>                UPS: APC BR1500GI
> 
> Thanks, appreciate the info!
> 
>> 
>> Thanks.
>> _______________________________________________
>> Nut-upsuser mailing list
>> Nut-upsuser at alioth-lists.debian.net
>> https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-lists.debian.net%2Fcgi-bin%2Fmailman%2Flistinfo%2Fnut-upsuser&data=04%7C01%7C%7C09b7427293084d87c1a208d8d8ccec7a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637497721942032252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DbHwKj%2FdmBvqsS6w3DPEKWZcXewixzXbtIwPBVN1wpQ%3D&reserved=0
>