similar to: Vertiv UPS

Hello, I was able to get the Vertiv/Liebert UPS (Vertiv Liebert PSA5 1500VA 900W - PSA5-1500MT120) to start working with NUT and "usbhid" driver, but would appreciate help to get it to work properly. Here's the output from the "upsc" command for a Cyberpower UPS I have: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS

Bruce Pleat via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > Here's the (far less lengthy) output for the Vertiv Liebert: > > device.mfr: Vertiv Co > device.model: Liebert PSA5 > device.serial: 22223106602D04C > device.type: ups > driver.name: usbhid-ups > driver.parameter.pollfreq: 30 > driver.parameter.pollinterval: 2 >

> On Sep 14, 2020, at 9:12 PM, Joe Reid <jreid at vnet.net> wrote: > > rPi3 running current Buster. I get this far: > > # upsc networkups > Init SSL without certificate database > battery.charge: 100 > battery.charge.warning: 30 > battery.runtime: 2891 > battery.type: PbAC > device.mfr: Vertiv Co > device.model: Liebert PST5 > device.type: ups >

rPi3 running current Buster.  I get this far: # upsc networkups Init SSL without certificate database battery.charge: 100 battery.charge.warning: 30 battery.runtime: 2891 battery.type: PbAC device.mfr: Vertiv Co device.model: Liebert PST5 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid:

Hello The page https://networkupstools.org/ddl/Liebert/PSA_1500.html don't contain all information about UPS series PSA. First, the variable "*device.serial*" is dummy, it is always empty , and "*ups.serial*" also always empty. Second, configuration file for the all UPS "PSA" contain these lines: [PSA] ??? driver = "usbhid-ups" ?? ?port =

Just a note: recent PRs are naturally not in 2.8.0 release (April 2022), but would be in eventual 2.8.1 Jim On Sun, Jan 15, 2023, 00:51 Bruce Pleat <bpleat at gmail.com> wrote: > Part of what made my life harder is nut-scanner isn't in the package. > > Once I get a chance, I'll update to 2.8, but that'll be a little while off. > (Any clue how to get 2.8 included in

Part of what made my life harder is nut-scanner isn't in the package. Once I get a chance, I'll update to 2.8, but that'll be a little while off. (Any clue how to get 2.8 included in the package provider for my Raspberry Pi is presumably beyond the scope of this list, but if someone knows and wants to let me know, I wouldn't complain...) On Sat, Jan 14, 2023 at 3:12 PM Jim

Thanks! FWIW if you do get to test new code, https://github.com/networkupstools/nut/pull/1811 adds warnings for situations like yours. Would be great to check if it works actually, with many "same-serial" devices :) Jim On Sat, Jan 14, 2023, 23:39 Bruce Pleat <bpleat at gmail.com> wrote: > Thank you, looks like the regex idiosyncracy might have been the issue. > > My

Hi, Back in 2011, it was reported that Liebert PSA devices persist in reporting OB (On Battery) when using usbhid-ups regardless of the actual state. Pier Paolo did some work (2011) which reportedly solved the issue. However, that doesn't seem to have reached mainstream and I now face the same problem. I'm using NUT 2.6.3 with a new Liebert PSA 1500Va that only ever reports OB and

Likely because 2.6.3 is not a current release. 2.7.2 (or 3?) is rhe current version, and it makes little sense to backport changes. Nut is a trivial compile . . . 'Use the source, Luke . . .' - Tim On October 17, 2014 6:05:35 PM CDT, Derek Harding <derek at lagham.org.uk> wrote: >Hi, > >Back in 2011, it was reported that Liebert PSA devices persist in >reporting OB

hello I found the Nut project by chance and I wanted to know if it will serve my purpose. work with several brands of UPS (Eaton, CM, APC, Vertiv (Emerson)). I want to know if I could change parameters, update UPS battery and firmware, etc? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Thank you, looks like the regex idiosyncracy might have been the issue. My current file: [sl] driver = usbhid-ups port = auto desc = "CyberPower UPS SL" product = "SL.*" productid = 0501 vendorid = 0764 #model = "SL Series" [ab] driver = usbhid-ups port = auto desc =

Another Update: I had to reboot my server today. After the reboot, I had the exact same problem as before without the usb hub. Since I already had the ups connected and communicating, I decided to try to figure out how to fix it. Here is what worked for me using the usb 2.0 hub sudo upsd ?c stop sudo upsdrvctl stop sudo upsdrvctl start sudo upsd Everything connected up and was

I guess it's kind of a natural response on my part, working professionally in software. T-Shooting step one: Get current and see if the problem persists. If it does,then step rwo: debug. 2+ years is forever in software, noting that 2.6.3 was mid 2012 . . . - Tim On October 17, 2014 9:38:15 PM CDT, Charles Lepple <clepple at gmail.com> wrote: >On Oct 17, 2014, at 8:31 PM, Tim Dawson

On Oct 17, 2014, at 8:31 PM, Tim Dawson <tadawson at tpcsvc.com> wrote: > Likely because 2.6.3 is not a current release. 2.7.2 (or 3?) is rhe current version, and it makes little sense to backport changes. Tim, It's possible that these changes didn't make it in. I admit that would be my knee-jerk reaction to seeing an older version number, but the last occurrence of

I downloaded latest source and it compiles ok but the original usbhid-ups.c is unchanged. Pier changed other files, too, and I don't know the changes needed. Simply substituting the modified (as per 2011) usbhid-ups gives a failed connection to the ups. So I have tried a little. I'll uninstall 2.6.3 and try to install 2.7.2 from a fresh compile. Thanks for the responses so far :-) --

So, regarding wildcards (globs) vs. regular expressions, the latter being used for such matches, I believe (did not check now) the config sections should look like this: [cp] driver = usbhid-ups port = auto desc = "CyberPower UPS CP" model = "CP685AVR-G" vendorid = "0764" product = "CP.*" Note the

Barry, I have had success with NUT on Debian and an EATON 5E2000IUSB-AU 5E 2000VA/1200W UPS With 3 x OUTLETS which I believe is good value. I would believe the the EATON ?5E 1500VA/900W UPS With 3 x OUTLETS would work just as well. The 1500VA also uses the same batteries as the 2000VA so I would believe it would run its raited load longer than 2000VA. My eight drive RAID driver uses less that

Hello again. Back in the day (2007) I wrote a USB-capable driver for my Masterguard/Phoenixtec UPSes (in case you locally archived this list, this very mail is a reply to a rather long thread from then), which I used ever since. However, the world has been going on since then and I need to get away with the old 2.0.4 binaries currently in use. These boxes (I use two A3000-19 and two A700-19) are

Thank you both for answering. I tried with and without the "-x" as the manual wasn't clear enough to me. I tried with and without wildcards (e.g., "*SL*", "*SL Series*", "SL Series" for that one). I tried other permutations before asking for help here. ("model" throws an error, "-x model" doesn't, which was confusing) I am not