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

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

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

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 >

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 >

*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

Thank Charles. I've bookmarked this and will try to experiment a bit. On Mon, 3 Jun 2024, 04:33 Charles Lepple via Nut-upsuser, < nut-upsuser_at_alioth-lists.debian.net_chribonn at duck.com> wrote: > On Jun 2, 2024, at 12:14?PM, Roger Price wrote: > > > >> Is the comment about offdelay (in red) correct / can this line be > eliminated?. > > > > My

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

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 >

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

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

I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id: 0764:0501, UPS.PowerSummary.Voltage reports 26.6 for the 24V batteries so when the 0.667 battery scale is applied that goes down to 17.7V. upsc output: battery.charge: 100

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

On 6/4/2017 4:46 PM, Charles Lepple wrote: [snip] >> 4) when I went down to 95 volts, the "AVR" kicked in to boost the >> voltage without going to battery. This was indicated by a "click" from >> the UPS and an indication on the UPS display. > > In non-explore mode, does the driver report the AVR status? (No need to set things back up if you have

I was getting: "Can't claim USB device [0764:0501]: could not detach kernel driver from interface 0: Operation not permitted" so I manually installed the udev rules the source (I installed the Gentoo ebuild). I am now getting: # upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using

On Tuesday 21 January 2020 19:52:01 Charles Lepple wrote: > sudo lsusb -v -d 0764:0501 copious output, containing this: idVendor 0x0764 Cyber Power System, Inc. idProduct 0x0501 CP1500 AVR UPS bcdDevice 0.01 iManufacturer 3 CPS iProduct 1 CP625HGa I take it that this is evidence they don't follow the spec to the letter.

On Jun 3, 2017, at 2:21 PM, Mike <the.lists at mgm51.com> wrote: > > On 5/30/2017 10:47 PM, Charles Lepple wrote: >> On May 22, 2017, at 11:13 AM, Mike <the.lists at mgm51.com> wrote: >>> >>> On 5/21/2017 10:39 AM, Charles Lepple wrote: > [snip] > >> Even though the CPS sub-driver has been written already, I would like to take a look at the

Trying to configure multiple UPS on one Raspberry Pi 4 (Bullseye). Issue: Whenever more than one is plugged in, one shows as all - as in "upsc x" for all of them shows identical information for one UPS rather distinct for each plugged in. OS: /proc/version = "Linux version 5.10.103-v7l+ (dom at buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU

On 5/30/2017 10:47 PM, Charles Lepple wrote: > On May 22, 2017, at 11:13 AM, Mike <the.lists at mgm51.com> wrote: >> >> On 5/21/2017 10:39 AM, Charles Lepple wrote: [snip] > Even though the CPS sub-driver has been written already, I would like to take a look at the raw "explore" mode output: > >