similar to: NUT with Cyber Power 700 AVR

Hi, I've installed Nut 2.0.5 on a RedHat 9 box. I have a GeekSquad 1500 UPS. (GeekSquad is a BestBuy brand) I've found out that it's actually a CyberPower 1500 AVR LCD. I'm using it with the serial cable. I'm unable to get it working with any of the drivers provided with NUT. I've tried cpsups, cyberpower and powerpanel. here's the output of the different drivers

I also am wondering if the message about libusb driver missing might be the real problem. Checking my system, I see this: =================== [root at mythtv dev]# ll /dev/bus/usb/001 total 0 crw-rw-r--+ 1 root root 189, 0 Nov 9 08:21 001 crw-rw-r--+ 1 root root 189, 1 Nov 9 08:21 002 crw-rw-r--+ 1 root root 189, 2 Nov 9 08:21 003 crw-rw-r--+ 1 root dialout 189, 3 Nov 10 09:43 004

*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

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 >

Can you try starting the driver with higher debug verbosity to see more details, e.g. add `debug_min = 6` to the `ups.conf` section, or stop the auto-starting driver attempts and run the driver program with CLI options? * https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity With `upsdrvctl` driven attempts, you may also be in conflict with a generated `nut-driver at

Hi Recently i bought a MicroDoWell BP50, and with it followed a USB 2 serial converter. When i plug it into my 2.6.19 kernel, dmesg shows hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:04.2-2 usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver So, i figured i should use usbhid-ups,

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

Thanks for the tip, Jim. I just figured out what is going on. The system is now working. ==> This one is on me. <== The root cause was the specification of the bus number in the ups.conf file. Here is what it looks like now: ============ [cyberpower] driver = "usbhid-ups" port = "auto" vendorid = "0764" productid =

I'm trying to get a CyberPower PP1100 working with NUT on a Fedora 16 system and not having much luck. Kernel: 3.4.4-4.fc16.x86_64 #1 SMP Thu Jul 5 20:01:38 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux NUT (installed from Fedora RPM): nut-client-2.6.4-1.fc16.x86_64 nut-2.6.4-1.fc16.x86_64 libusb: libusb-devel-0.1.3-9.fc16.x86_64 libusb1-1.0.9-0.6.rc1.fc16.x86_64

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

Great! Regarding libusb and nut-scanner, I think the *.so (exact) symlinks are part of *-devel packages. This was solved in NUT recently (maybe after 2.8.2 release already) by detecting and stashing the basename of realpath of the library present during build, so the exact *.so.X.Y.Z would be also tried. Also, nut-scanner now (in 2.8.2 IIRC) should not suggest the volatile bus/busport/device

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 >

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

I know others have seen this before, I just never saw any real resolution to it. I am not a programmer, or at the least a very bad one, so I don't think this is something I can do properly myself. I have a Cyberpower 1500 AVR rack mount that worked good, except for the output voltage listing, with an older version of NUT (I don't remember the version of NUT, but the O/s was Fedora

Hi there First a big thank you to all nut developers. I tried the 2.0.4 as well as the 2.0.5-pre1 versions with my CyberPower OP1000E connected to a serial to USB converter. All I got was the following: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5-pre1 Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5-pre1) Warning: This is an

Hello, I've had this same model CyberPower connected to a linux server and a freebsd server. [root at sensor003 menon]# lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus

Hello! I got my hands on a CyberPower 1500AVRT, and i'm trying to get it connected to my Gentoo machine. I've followed all the basic guides on setting up NUT and UPS' but have had no luck. My current ups.conf is: [cyberpower-gentoo] driver = cyberpower port = /dev/ttyS0 desc = Workstation Upon running /etc/init.d/upsd start or upsdrv start I get: * Starting

Hi, Nut version 2.2.2, Opensuse 11.0 using serial connection using Cyberpower cable. Have 2 servers connected directly using serial. Looking for a way to get this ups and nut to work together. Have tried with powerpanel and cyberpower and they both do not like to talk to the ups. The upsd fails to start. Can somebody guide me to what I do wrong or how I can find the issue. The port is