Re: [Nut-upsuser] CyberPower CST150UC: Question re: battery.runtime.low configuration settings

2024-04-24 Thread tim.o via Nut-upsuser
On 4/24/24 18:06, Charles Lepple wrote: My guess is that if you sent 520, upsc would return 8 (for a revised maximum of 511 seconds). If not, the UPS is even weirder than most  As you found, the ignorelb option is available to work around limitations in the UPS shutdown logic. I can confirm

Re: [Nut-upsuser] CyberPower CST150UC: Question re: battery.runtime.low configuration settings

2024-04-24 Thread Charles Lepple via Nut-upsuser
On Apr 24, 2024, at 3:45 PM, tim.o via Nut-upsuser wrote: >> Have you tried any other values? 3600 is hex 0xe10, and 16 is 0x10, so it is >> quite possible the UPS is using an 8-bit field to store battery.runtime.low. >> I'm guessing the maximum is going to be 255. >> > I am not sure I

Re: [Nut-upsuser] CyberPower CST150UC: Question re: battery.runtime.low configuration settings

2024-04-24 Thread tim.o via Nut-upsuser
Unfortunately, the SUCCESS response is just saying that upsrw was able to send that request to upsd (i.e. the username/password were correct). As you saw, the real proof is in what you read back from upsc. Ah, gotcha. Have you tried any other values? 3600 is hex 0xe10, and 16 is 0x10, so it

Re: [Nut-upsuser] CyberPower CST150UC: Question re: battery.runtime.low configuration settings

2024-04-24 Thread Charles Lepple via Nut-upsuser
> On Apr 23, 2024, at 3:51 PM, tim.o via Nut-upsuser > wrote: > > The value changed to battery.runtime.low: 16, instead of 3600. I don't > understand why, because executing the command resulted in SUCCESS. Unfortunately, the SUCCESS response is just saying that upsrw was able to send that