similar to: Cyber Power System CP1500 AVR UPS: changing battery.charge.low value

On Mon, 4 Mar 2024, Alan C. Bonnici via Nut-upsuser wrote: > Platform: Proxmox VE 8.1.4 > NUT 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: STRING >

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

Thanks Charles for the clarification. If NUT cannot control it then removing it would, IMO add value. On Sun, 10 Mar 2024 at 00:14, Charles Lepple < clepple_at_gmail.com_chribonn at duck.com> wrote: > 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

Very good point. I hope to write a beginners guide -- more like adopting my notes --on NUT. 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

Wow :-) I'll have a read through it. On Sun, 10 Mar 2024 at 15:54, Roger Price < roger_at_rogerprice.org_chribonn at duck.com> wrote: > On Sun, 10 Mar 2024, Alan via Nut-upsuser wrote: > > > Very good point. I hope to write a beginners guide -- more like > adopting my > > notes --on NUT. > > I did the same thing, 131 pages, at >

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 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 reported. Two observations are that once a variable setting

2008/4/10, David Erosa <david.erosa at gmail.com>: > Public bug reported: > > Binary package hint: nut > > After updating to last nut package (2.2.1-2.1ubuntu6), the megatec_usb > driver seems to be working, except for the charge percentage: > > $ /lib/nut/megatec_usb -DDDDD -a SAI > ... > Checking device (0665/5161) (001/007) > - VendorID: 0665 >

Hi, Rsync 3.0.7 and Cygwin 1.7.1 hangs at random instances. This does not happen always and does not happen at all locations. I can reproduce the problem. Others are having similar problems. Can someone please guide me one what I can do to report such problems? Regards, Alan

I've been running the Debian packaged 2.4.3 for a while, working find. When 2.6.0-1 just pushed through to debian, things have stopped working :( I checked what had been the usual suspects in past problems, namely permissions problems in /dev/bus/usb, but all seems in order: $ lsusb ... Bus 009 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS $ ls -l /dev/bus/usb/009/002

I recently purchased a Cyber Power 700 AVR UPS. I installed it just fine and wanted to install NUT to monitor the unit. I searched the mailing list and found a similar post. However, the distro used in that post was different and the unit was slightly different (900 AVR). My server is running Debian Lenny. The Cyber Power UPS is connect to one of the serial ports using the cable that came with

Nut Developers, I have unsuccessfully tried to solve a problem with the voltage value on my Cyber Power UPS CP1000AVRLCD. Something is wrong with the battery voltage calculation. It always reads around 20 volts with that's nuts (pardon the pun). Right now: battery.voltage : 20.3 You can take a look for yourself at http://www.3111skyline.com/nutindex.html Is there a parameter I can check

Citeren "David C. Rankin" <drankinatty at suddenlinkmail.com>: > Discharged battery.voltage: > > 17.4 Volts - (indicated on shutdown, discharging battery.charge 77%) > 16.9 Volts - (indicated on shutdown, discharging battery.charge 51%%) > 16.6 Volts - (indicated on shutdown, discharging battery.charge 33%) > > -- Shutdown Occurred at < 3% -- Battery

Hello, I am using Nut 2.8.0 (2.8.0-7 packages) Debian 'Bookworm' in it's Devuan form 'Daedalus'. When I look at my Eaton (ex-MGE Powerware) E5115 UPS boxes in NUT 'upsstats" I am confused by the battery readings. Under the 'System' column I can click on the link and obtain a GUI with a few meters. The NUT 'upsstats' battery voltage meter for these

The (2.2.1) upshid-ups driver reports battery.temperature rather than ups.temperature. Here's a quick patch to have it show up in the status page... --- clients/upsstats.c.DIST 2008-03-04 09:15:40.000000000 +0000 +++ clients/upsstats.c 2008-03-04 09:16:20.000000000 +0000 @@ -787,6 +787,11 @@ return 1; } + if (!strcmp(cmd, "BATTTEMP")) { +

Hello Jeff, `upsstats` by itself only relays and renders the information provided by a NUT data server (upsd) and the NUT driver for the device. So you can revise the specific reported values with e.g. `upsc` command-line client to be sure. What I think happens here is that the driver uses a `battery.voltage.low/nominal/high` group of readings which does not match the hardware circumstances

Hi, I'm currently using a Belkin UPS ( http://www.belkin.com/au/IWCatProductPage.process?Product_Id=137904) with nut, and my notify script doesn't receive a low battery warning. I receive ONBATT and ONLINE, but not any battery low message. I've run upsmon -D and I've seen it polls the ups.status property. The problem seems to be that this UPS doesn't put LB (I guess that

I'm sorry about a wrong place to address, because my problem most likely is in a hardware, not the NUT software. I had tried to contact the MGE support team, but got no answer. I have purchased the MGE Ellipse 650 UPS, and after testing it with the Linux/NUT package (v. 2.0, mge-shut driver) found out that the battery.charge indicator and related things (battery.lifetime, low battery signal)

Hi, Right now my UPS has "battery.charge.low" set to 30. I think thats pretty silly, I'd like it to be alot lower. Its a read only variable so I can't modify it. I can't find a setting in a conf file to override it. Did I miss it? Thanks, Tuc

Hello! I have Megaline 5000 UPS, which I need to monitor via RS232 interface. I'm using "metasys" driver, and everything is Ok, but I can't see battery charge. From command line and cgi-interface I can see battery voltage, input and output voltage and load of UPS in %. But there is nothing about battery charge and remaining time (when on-battery). Is there any chance to see

Hi all! I have a nut 2.4.1 on FreeBSD 7.1 i386. UPS model is IPPON smart smart power pro 2000. When i try to see battery charge, in output it have not such variable, and i can't control other servers (Win2k3 + WinNUT) because they not knows about current battery charge. How i can solve that problem? Thanks! upsc IPPON at localhost:54672 --------------------------- battery.voltage: 27.50