similar to: HCL Cyberpower CPS-850AVRLCD supported by usbhid

[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

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

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 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:

Cyber Power Systems CP600LCD https://www.cyberpowersystems.com/product/ups/cp600lcd/ upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2220 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS CP600 device.type: ups driver.name: usbhid-ups

Cyber Power Systems AVRG750U https://www.cyberpowersystems.com/product/ups/avrg750u/ upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 15360 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 24.0 battery.voltage.nominal: 24 device.mfr: CPS device.model: AVRG750U device.serial: <REDACTED> device.type: ups

Cyber Power Systems CP1000PFCLCD = upsc output = attached = Shutdown results = I experienced a genuine power outage shortly after setup. The 1 master system and the 1 slave system both shutdown successfully. The master shutdown before the slave (*not* a bug report; I may not have this configured correctly yet). The UPS was not powered off by the master. I don't know if the UPS

I didn't want to sign up for the nut-devs list or create a git account just to provide this information, so I hope posting this info here is OK... I just bought a Cyber Power Systems EC750G UPS for use as a spare. Here are some info for it: ========================= upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime:

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 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:

Hope it's not too rude to just drop this here for y'all... Checking device (0764/0501) (001/005) - VendorID: 0764 - ProductID: 0501 - Manufacturer: CPS - Product: UPS AE550 - Serial Number: unknown This one and their 485 don't provide a load measurement -- the Windows drivers kick it onto battery for a timed period and measure the drain to guess the runtime -- apparently all their

It looks like the CyberPower Cyber Power Systems CP685AVR supported by usbhid-ups has a favorable device dump linked to the Devices Dumps Library page here: http://networkupstools.org/ddl/Cyber_Power_Systems/CP685AVR.html However, it is not listed anywhere on the Hardware Compatibility List (HCL) page here: http://networkupstools.org/stable-hcl.html This appears to be an omission on the HCL

The battery was replaced in December and the output from upsc was: $ upsc desktop_ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1020 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS CP850AVRLCD device.type: ups driver.name: usbhid-ups

On Oct 25, 2020, at 11:52 AM, Robert Stocker <kneadtoknow at gmail.com> wrote: > > Init SSL without certificate database > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPS > battery.runtime: 15690 > battery.runtime.low: 300 > battery.type: PbAcid > battery.voltage: 24.0 > battery.voltage.nominal: 24 I

[please use Reply-All - this list does not modify the reply-to header] > On Nov 23, 2016, at 10:30 AM, Craig STCR <craig.stcr1 at gmail.com> wrote: > > It looks like the CyberPower Cyber Power Systems CP685AVR supported by > usbhid-ups has a favorable device dump linked to the Devices Dumps > Library page here: > >

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)

On 2018-12-16 8:04 a.m., Charles Lepple wrote: > On Dec 15, 2018, at 10:32 PM, James <bjlockie at lockie.ca> wrote: >> >> My UPS has an LCD that says the battery is 100% and the estimated run time is 12min. >> The uspc has similar results. >> The problem is when line power is lost the UPS batter goes to 0% very quickly (seconds). >> >> It charged to 85%

I would like to solicit some feedback re: the battery.runtime.lowconfiguration settings through NUT. I was able to set the value using the 'upsrw' command but when I did a 'upsc' the configuration seems incorrect. Please see below for details. Thank you OS name and version: ?? ?Description:??? Debian GNU/Linux 12 (bookworm) ?? ?Release:??????? 12 ?? ?Codename:?????? bookworm

I switched my desktop with my raspberry pi because I thought my desktop ups had a larger capacity. Now the ups.load of each is not what it was (it should be). The battery.runtime is better for my desktop (it's supposed to be worse) and my raspberry pi is worse (I hoped for hours better). What am I seeing? I switched them for longer raspberry pi time and the APC battery is getting old. :-)

Hi NUT: We propose adding HID usage for "Temperature" to the NUT source code file cps-hid.c (driver: USBHID-UPS(8)<https://networkupstools.org/docs/man/usbhid-ups.html>) so that UPS temperature information can be displayed in the UPS status list. After conducting internal tests, we confirmed that inserting the following code: { "ups.temperature", 0, 0,