Hi Charles, The posting at https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 references ups.delay.start and suggests setting it to -1.
upsrw -l pve1@localhost listed this as modifiable but any attempt at modifying the value failed. I used the *override.ups.delay.start = -1* in nut.conf and this is now being reported. Two observations are that once a variable setting is overridden, *upsrw -w* will not show these values. Is it by design? Below is the output from *upsc *for the Cyber Power System CP1500 AVR Init SSL without certificate database battery.charge: 100 battery.charge.low: 70 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 6000 battery.runtime.low: 900 battery.type: PbAcid battery.voltage: 26.0 battery.voltage.nominal: 24 device.mfr: CPS device.model: Value2200E device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0501 driver.parameter.synchronous: auto driver.parameter.vendorid: 0764 driver.version: 2.8.0 driver.version.data: CyberPower HID 0.6 driver.version.internal: 0.47 driver.version.usb: libusb-1.0.26 (API: 0x1000109) input.transfer.high: 0 input.transfer.low: 0 input.voltage: 241.0 input.voltage.nominal: 230 output.voltage: 243.0 ups.beeper.status: disabled ups.delay.shutdown: 300 *ups.delay.start: -1* ups.load: 0 ups.mfr: CPS ups.model: Value2200E ups.productid: 0501 ups.realpower.nominal: 1320 ups.status: OL ups.test.result: No test initiated ups.timer.shutdown: -60 ups.timer.start: -60 ups.vendorid: 0764 Regards, Alan On Fri, 8 Mar 2024 at 15:02, Charles Lepple via Nut-upsuser < nut-upsuser_at_alioth-lists.debian.net_chrib...@duck.com> wrote: > On Mar 8, 2024, at 7:07 AM, Roger Price <ro...@rogerprice.org> wrote: > > > > Perhaps setting lowbatt = 50 in ups.conf would help. > > Roger, good point. > > That option is missing in the usbhid-ups man page, so I logged an issue to > remind us to fix that: https://github.com/networkupstools/nut/issues/2356 > > Since I am used to fighting the Cyber Power Systems shutdown timers, I > automatically assumed it was a similar issue where the UPS accepts the > value then ignores it. > > Alan, your shutdown timers might need to be multiples of 60 seconds (I see > 20 and 30 for ups.delay.shutdown and ups.delay.start, respectively), and > that might not even be enough. Discussion: > https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 > and https://github.com/networkupstools/nut/issues/625 > > -- > Charles Lepple > clepple@gmail > > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
