search for: pleat

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 the package provider for my Raspberry > Pi is...

...gt; 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 current file: >> [sl] >> driver = usbhid-ups >> port = auto >> desc = "CyberPower UPS SL" >>...

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 current file: > [sl] > driver = usbhid-ups > port = auto > desc = "CyberPower UPS SL" > product = "SL.*"...

...of NUT > lookup, so prone to change with re-plugging of other devices. For > libusb-1.0 API this should be the non-zero hardware-related port number (if > supported by HW/OS/drivers) by default (or iteration counter if OS does not > tell). > > On Sat, Jan 14, 2023 at 8:16 PM Bruce Pleat <bpleat at gmail.com> wrote: > >> 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 >> S...

...t just the iteration counter of NUT lookup, so prone to change with re-plugging of other devices. For libusb-1.0 API this should be the non-zero hardware-related port number (if supported by HW/OS/drivers) by default (or iteration counter if OS does not tell). On Sat, Jan 14, 2023 at 8:16 PM Bruce Pleat <bpleat at gmail.com> wrote: > 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...

Bruce Pleat via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > I'm using the latest updates to OS and running the latest apt nut packages > in the dist (2.7.x?). Debian 11 has 2.7.4. That's old; 2.8.0 was released in spring of 2022. And git master has a lot of improvemen...

...lock Speed=3.700GHz Processor L2 cache=512KB Processor L3 cache=4.96.KB ?Device Information Primary Hard Drive={none} MiniCard SSD Device=128GB HDD TW0TBURJ550553CC1419 Dock eSATA Device={none} Video Controller=Intel HD Graphics Video BIOS Version=2177v14 Video Memory=64MB What's happend? pleate tell me the why decided above problem. tanabe

...s for command-libe specification of such > parameters. In config file it is just key=value. For these matchers they > are generally regexes (not shell globs). Please do RTFM :) > > Jim > > On Sat, Jan 14, 2023, 01:11 Greg Troxel <gdt at lexort.com> wrote: > >> Bruce Pleat via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> >> writes: >> >> > I'm using the latest updates to OS and running the latest apt nut >> packages >> > in the dist (2.7.x?). >> >> Debian 11 has 2.7.4. >> >> That's old;...

...to configs should help. Also `-x` is for command-libe specification of such parameters. In config file it is just key=value. For these matchers they are generally regexes (not shell globs). Please do RTFM :) Jim On Sat, Jan 14, 2023, 01:11 Greg Troxel <gdt at lexort.com> wrote: > Bruce Pleat via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > writes: > > > I'm using the latest updates to OS and running the latest apt nut > packages > > in the dist (2.7.x?). > > Debian 11 has 2.7.4. > > That's old; 2.8.0 was released in spring of 202...

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 > d...

aotheoverlord wrote: > > > Maybe I missed it, but could you tell us which version of PowerBuilder you are using? PowerBuilder 7... I tried to compile the application in PowerBuilder 6, but it doesn't works.

I''ve been getting increasing resistance from helpers who prefer Subversion over CVS. I feel that it''s slowing down development. So, done. Mailing lists, releases, news will still be at Rubyforge. Bug tracking will likely move to the new repository soon as well. The new repository is at: http://code.whytheluckystiff.net/ Checkout RedCloth from

Trying to configure multiple UPS on one Raspberry Pi 4 (Bullseye). Issue: Whenever more than one is plugged in, one shows as all - as in "upsc x" for all of them shows identical information for one UPS rather distinct for each plugged in. OS: /proc/version = "Linux version 5.10.103-v7l+ (dom at buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU

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

Greetings people; The section of drakeconf that pclos uses has two problems. First is several screens full of complaints about deprecated syntax in "/etc/udev/rules.d/70-nut-usbups.rules" at each reboot. So I pulled the current 2.5 svn trunk, then found I was missing quite a few build tools needed here that aren't used when building a kernel, currently running a 32 bit

I'm trying to Compile/Package and then (on a different box) Config/Run 2.8.1. Both boxes are Raspberry Pi 4b on Bullseye with a generic USB UPS. -- I'm trying to get nut running on my Raspberry (bullseye/11). (I'd also love to share a working 2.8.1 for Raspberry with the world, but...) I compiled the latest code from git: version 2.8.1-774-g963abbd87 I compiled it on one system

Hi, I didn't see in the HCL any Vertiv support. The specific unit I'm considering is: ( https://www.amazon.com/gp/product/B07BYD6RLN) - "Vertiv Liebert PSA5 1500VA 900W line-Interactive UPS with AVR Technology and Battery Backup, 10 outlets and Three-Year, Full Unit Replacement Warranty (PSA5-1500MT120)" Has anyone worked with this (or even UPS from Vertiv) and had success (or