search for: cyperpower

I've been using nut with a serial device for a while, but today I tried hooking up this new CyberPower 685 unit via newhidups--since it seemed better supported over USB than serial, based on reading the list archives and cvs logs. Unfortunately, I can't connect to it. My system sees the device: uhid1: CPS UPS BF700, rev 1.10/0.01, addr 2, iclass 3/0 ... and I have chmodded all

I'm playing with a new CentOS 8 with a cyperpower OR500 (a smaller sibling to the OR700) plugged in via USB. GNOME sees the UPS... but NUT does not (even if I shut down gnome). > [root at delp ups]# upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.4 > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communicat...

Can upsmon be set to shutdown the system immediately upon sensing a power failure? I just installed nut on my Debian Squeeze system, connected it to a Cyperpower ups and edited /etc/nut/ups.conf and upsmon.conf. On system reboot upsd and upsmon were started. I would like an immediate orderly system shutdown and power down upon a power failure. I pulled the power plug and the system continued running on battery power. After several minutes I restored...

On Mar 27, 2020, at 11:51 PM, Ben Kamen <ben at benkamen.net> wrote: > > I'm playing with a new CentOS 8 with a cyperpower OR500 (a smaller sibling to the OR700) plugged in via USB. > > GNOME sees the UPS... but NUT does not (even if I shut down gnome). > >> [root at delp ups]# upsdrvctl start >> Network UPS Tools - UPS driver controller 2.7.4 >> Network UPS Tools - Generic HID driver 0.41...

...5 min of battery then things should reset. I tried many web on-line examples and docs. but can't get it working. I would be grateful for help. I would like the most simple, understandable way to do it. I'll cite my files and info below. Thank You so much. Unbuntu 12.04 Server, nut 2.6.3, Cyperpower CP1500AVRLCD, no slaves just the one server PC. nut.conf MODE=standalone ----- ups.conf: [cyberpower-1500] driver = usbhid-ups port = auto ----- upsd.conf: LISTEN 127.0.0.1 3493 LISTEN ::1 3493 ----- upsd.users: [monuser] password = xxxxx allowfrom = local upsmon master ----...

I'm looking at switching from an APC UPS to a different brand after having had my third SU3000RM in a row blow up power transistors. I'm looking at the Cyperpower PR3000LCDRTXL2U. I see the PR3000E and the PR6000LCDRTXL5U listed as supported, but not the PR3000LCDRTXL2U. Howeverit seems likely that if the PR6000LCDRTXL5U is supported, the PR3000LCDRTXL2U ought to work as well. I've been running apcupsd, but if I go with the CyberPower unit I'll be...

Greetings: I'm evaluating two replacements for UPS upgrades to my dept. Because the CyberPower OP650 has been retired, we are evaluating the CyberPower600VA and the CyperPower 1000AVRLCD. We will be evaluating others. Initial configuration and communications are established via the usbhid-ups driver, the gambit of tests are all passed with the exception of one. I seem to be failing the power race test. As I understand it the power race test happens when mains is los...

...psdrvctl[519]: [network-ups] unhandled ASN 0x5 received from .1.3.6.1.4.1.3808.1.1.1.2.2.2.0 Feb 15 17:47:52 delta snmp-ups[576]: Startup successful UPS.CONF ======== maxretry = 3 [network-ups] driver = snmp-ups port = 172.16.20.30 snmp_version = v2c community = cybernut pollfreq = 15 desc = "CyperPower OR1500LCDRTXL2U" UPSC OUTPUT ======== root at delta:/etc/nut# upsc network-ups at localhost Init SSL without certificate database battery.runtime: 262800.00 battery.runtime.elapsed: 0.00 device.mfr: CYBERPOWER device.model: OR1500LCDRTXL2U device.serial: REDACTED SERIAL NUMBER device.type: u...

I've not been able to connect to my ups using NUT 2.7.4 or NUT 2.8.0. 2.7.4 was installed as a package, 2.8.O was compiled from source. I've messed with permissons, everything is root:root and has the approprate read/execute permissons. I've tried two differnt UPS(es) APC & CyperPower. I'm running PI OS (Raspbian) on a Raspberry Pi3 model B. The port 3493 is open (UFW). I can reach the Pi on the network from another machine on port 3493 (using upsstats.cgi). The usbhid-ups driver starts up. But the ups is initally connected, but somehow gets lost. Next comes the message con...