search for: _ups_fields

...thresholds for the UPS, so theoretically the UPS will send the LB signal when the battery voltage goes lower than 10.40 Volts. Also, if battery.charge works, you can use "ignorelb" if you want to shut down at another level of charge: http://www.networkupstools.org/docs/man/ups.conf.html#_ups_fields > ups.delay.shutdown: 30 > ups.delay.start: 180 These timers are in seconds. You will want to verify this, but according to those values, the UPS will shut off its output 30 seconds after the shutdown signal (so you need to make sure that your OS shutdown takes less time than that). Does &...

01.12.2014, 06:18, "Charles Lepple" <clepple at gmail.com>: > On Nov 29, 2014, at 7:32 AM, Victor Porton <porton at narod.ru> wrote: >> ?On Debian Linux jessie: >> >> ?After buying an UPS and installation of nut-server and nut-client at my PC and configuring the ports and the protocol, do I need to adjust time and/or percentage parameters, to be sure my

On Thursday 29 October 2020 22:12:00 Charles Lepple wrote: > On Oct 28, 2020, at 9:56 PM, Gene Heskett <gheskett at shentel.net> wrote: > > Which looks very incomplete to me. OTOH, its not a very big UPS but > > neither is the pi. I have tested that, and it shuts off long before > > it outouts a LB signal. > > Which part looks incomplete, the variables or the

On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote: > I'm going to guess that since your test runtime of 305 is very close to > the low limit of 300, that's the warning. Not yet a fail, but very, very > close. > I tried setting override.battery.runtime.low = 60 in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to report only

...ever gets picked up. As you have seen, the "default.*" and "overwrite.*" names are not actual variables: they are configuration options to change what is returned from upsc. That is why you get VAR-NOT-SUPPORTED. reference: http://www.networkupstools.org/docs/man/ups.conf.html#_ups_fields Also, I don't think there is a way for a PDC HID UPS to communicate that it can only handle certain discrete values for a variable (although there is support for contiguous ranges). That information would need to come from the manufacturer's specifications, and the Eaton/MGE document in th...

...UPS, so theoretically the UPS will send the LB signal when the battery voltage goes lower than 10.40 Volts. > > Also, if battery.charge works, you can use "ignorelb" if you want to shut down at another level of charge: > > http://www.networkupstools.org/docs/man/ups.conf.html#_ups_fields >> ?ups.delay.shutdown: 30 >> ?ups.delay.start: 180 > > These timers are in seconds. You will want to verify this, but according to those values, the UPS will shut off its output 30 seconds after the shutdown signal (so you need to make sure that your OS shutdown takes less time t...

...I get the shutdown to occur early, say when the battery is 50% to play it safe You didn't mention the output of upsrw (which has a few settings for controlling when "LB" is set), but you can also synthesize the low battery event: http://www.networkupstools.org/docs/man/ups.conf.html#_ups_fields and search for "ignorelb" > and just test and make sure that nut is even sending a command to shutdown and why it isn't happening? For your particular situation of one UPS and one master system, this should shut the system down without waiting for the "OB LB" status: h...

...the data flows with > override.*: > > > 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. > > https://networkupstools.org/docs/man/ups.conf.html#_ups_fields > > -- > Charles Lepple > clepple at gmail > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240310/307eeaf7/attachment.htm>

On Mar 9, 2024, at 5:16?PM, chribonn at duck.com wrote: > > 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 at 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

*Platform: Proxmox VE 8.1.4NUT version: Network UPS Tools upsstats 2.8.0* I configured Proxmox and I can pull up the UPS stats. Typing in `*upsrw -l cyberpower at localhost*` I get the following: *[battery.charge.low]Remaining battery level when UPS switches to LB (percent)Type: STRINGMaximum length: 10Value: 10[battery.runtime.low]Remaining battery runtime

.... As long as the UPS isn't turning off on its own (that is, NUT is telling it to turn off), and the reported charge or runtime values are reliable, you can tell NUT to use its own thresholds for shutdown: "ignorelb" under UPS Fields: https://networkupstools.org/docs/man/ups.conf.html#_ups_fields > >> Even the larger UPSes tend to return a lot of read-only values, and >> only provide a few knobs for shutdown-related settings. > > So I note running those cmds on this 1500wa APC under this desk. > Disappointing... The APC protocol situation is a different rant ent...

Hi all, I've been doing some searching, but I am not able to find what I'm looking for so I'm hoping someone here might be able to help. I have NUT installed and connected to my UPS, although not configured to do anything yet. I have 2 clusters that I need to shutdown in a specific order to make sure it is all powered down correctly - I know it probably needs to happen through the

Hey Charles, Looks like after take out default.input.transfer.low, upsrw script *DOES* work, the only thing for Eaton 3S 500 is that it is only accept certain voltage values for input.transfer.low, 84v and 96v are two of them. Otherwise the value never gets picked up. Thank you for all your help Shen On Thu, Jun 5, 2014 at 12:07 PM, Shen Chuan <shen at minutekey.com> wrote: > Hey

HI thanks for replying and helping. I've now ran the UPS down a few times from full charge to test and I don't think it's the batteries or a problem with the UPS itself. I can watch it go from 100% right down to 1% over 20 minutes etc and then the power gets so low that everything just powers off! I think it's down to Nut not actually shutting down my server that is my problem...

On 2/20/2014 6:55 AM, Charles Lepple wrote: > On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > >> Worse, however, is if there's a power failure right near the end of >> the 2-days-off cycle. That happened to me last week - it was a >> short duration 15 second loss - and the upscode2 driver decided it >> needed to issue a forced shutdown. >> >>