similar to: USBHID-UPS not detecting USB UPS even though options match

> On Jun 21, 2020, at 5:34 PM, Stephen Walker-Weinshenker wrote: > > product = "OL1500RTXL2U" > serial = "XXXXXXXXXXXX" > vendor = "CyberPower Systems" > bus = "001" Generally we only recommend including these extra parameters if there are multiple UPSes on one host, and you need to distinguish between them. Is it

Everything runs fine for several hours, then communication is lost and nut doesn't reestablish communication on its own. Running sudo upsdrvctl stop then sudo upsdrvctl start reestablishes communication. OS Version: Linux piaware 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux Nut Version: 2.7.2-4 Nut Installation Method: apt Device: CyberPower PR1500LCD Uses ? ? Generic

CyberPower Systems PR6000LCDRTXL5U http://www.cyberpowersystems.com/products/ups-systems/smart-app-ups/pp-series/PR6000LCDRTXL5U.html I had to create the following udev rule (on RHEL6): ATTR{idVendor}=="0764", ATTR{idProduct}=="0601", MODE="664", GROUP="dialout" Shutdown testing successful. UPS comes back online after turning off. # upsc battery.charge:

Dear Rod, thanks for writing. Good work! I am no longer an active NUT developer, so I am forwarding your message to the NUT developers list. NUT developers: probably this device can be added permanently. Also, should the MAINTAINERS file perhaps be replaced by a pointer to the mailing lists? It seems fairly outdated anyway. Cheers, -- Peter R. W. Rodolico wrote: > > I think I have the

CyberPower OR700LCDRM1U (http://www.cyberpowersystems.com/products/ups-systems/smart-app-ups/rackmount-lcd/OR700LCDRM1U.html) upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 6000 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 14.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS OR700

sending to the list for posterity. > On Oct 27, 2016, at 6:43 AM, Raymond Day wrote: > > Thank you. > > Looked like that worked. > > I put your code in /etc/nut/nut.conf just at the end of that file. > > Then did. > > upsdrvctl start > > upsc serverups > > Got this date back: > > battery.charge: 100 > battery.charge.low: 10 >

Summary ======= I have encountered problems with the nut shutdown sequence using the directory structure in the packages for Fedora Core 4. These problems occur when the /var file system is mounted as a separate volume. I have done some investigation and think that I have an answer, but I need verification from someone who has more experience from nut on a wider variety of systems. I want to

Begin forwarded message: > From: James Erickson <jimerickso at gmail.com> > Date: August 10, 2009 2:50:52 PM EDT > To: Charles Lepple <clepple at gmail.com> > Subject: Re: [Nut-upsuser] CyberPower OR2200 > > On Sun, Aug 09, 2009 at 06:38:32PM -0400, Charles Lepple wrote: >> >>> From: James Erickson >>> Date: August 9, 2009 6:17:51 PM EDT

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

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 switched a while back to a Cyberpower PR3000LCDRTXL2U UPS with an external battery chassis. We've lost power twice since I installed it, and both times, the UPS has killed power to everything while still indicating 80% capacity before NUT has even initiated shutdown on anything. Here's what upsc reports on it right now: battery.charge: 100 battery.charge.low: 35

So I just bought one of these fabulous CyberPower UPS devices from BestBuy hoping I could control it with my machine. Luckily, I found NUT! I've got the SVN sources and compiled and installed them but I haven't been able to get it to recognize the usb AE550. When I plug the usb cable in I see this in syslog: Feb 6 22:36:56 mythbox kernel: usb 1-1: new low speed USB device using

UPS - CYBERPOWER CPS DX600E upsc usb at localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1650 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 4.8 battery.voltage.nominal: 12 device.mfr: CPS device.model: DX600E device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

CyberPower Battery Backup with Surge Protection, model LE825G Appears to function properly with the driver listed on the HCL for the Cyber Power Systems ups 2 685AVR USB (usbhid-ups). Tested with shutdown mode "UPS Goes On Battery" with a 5 second timer and the system successfully shutdown as expected. upsc output: upsc ups battery.charge: 100 battery.charge.low: 10

CyberPower Value 1500ELCD-RU root at ubuntu:/home/oper# upsc myups at localhost battery.charge: 87 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 5220 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 16.5 battery.voltage.nominal: 24 device.mfr: CPS device.model: Value1500E device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq:

Cyberpower CPS850avrlcd https://www.cyberpowersystems.com/product/ups/cp850avrlcd/ shutdown sequence: UNTESTED upsc output: _____  sudo upsc cp-ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1230 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS

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 have had a similar problem to many other people for the last few months with my Cyberpower UPS. It was working properly after reboot about one in five times; the rest of the time it would endlessly disconnect and reconnect, according to syslog messages. The latest I was able to find towards a solution is http://www.mail-archive.com/nut-upsuser at lists.alioth.debian.org/msg06671.html The root

hi. why choose 1.4? correctly 1.3 FreeBSD hq.local 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #1: Tue Jul 31 19:48:36 MSK 2012 root at hq.local:/sys/amd64/compile/HQ amd64 ugen1.3: <DELL> at usbus1 uhid0: <DELL Dell UPS Rack 1920W HV, class 0/0, rev 1.10/1.00, addr 3> on usbus1 root at hq: # usbconfig ugen0.1: <EHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps)

[shutdown sequence] I have tested and verified the shutdown sequence works. [manufacturor] https://www.cyberpowersystems.com/product/ups/ec350g/ mbeisser at nas:~$ upsc ups Init SSL without certificate database battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1575 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 9.3