Re: [Nut-upsuser] UNSUBSCRIBE
On 20.03.24 15:08, Tim Reimers KA4LFP via Nut-upsuser wrote: I did try to do that several days ago, got the email, confirmed my desire to unsubscribe, and wad told that my "request would soon be acted upon" Yet I continue to get these messages. - Are you sure you are subscribed from this address and you aren't getting mail forwarded from somewhere? - down on the page you have "Nut-upsuser list run by ..." with address where someone capable of unsubscribing you I'd love to have just a way to receive only message chains where I either started the question or am contributing. I don't need to see ALL the comms on the list, however this old-school mailing list doesn't seem to have that modern capability as a Groups.io or Google Group, etc would have. Thanks, Tim Morse Code: The original digital mode. On Wed, Mar 20, 2024, 1:59 PM Matus UHLAR - fantomas wrote: On 20.03.24 10:46, Tim Reimers KA4LFP via Nut-upsuser wrote: >Subject: [Nut-upsuser] UNSUBSCRIBE at the bottom of each mail is a link to page where you can get unsubscribed. >https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser Note that in order not to unsubscribe random people, you will get confirmation e-mail and you must confirm the action. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. It's now safe to throw off your computer. ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] CyberPower PR3000LCDRTXL2U and NUT 2.8.0 - mute?
On Thu, Mar 21, 2024 at 1:09 PM Phil Stracchino via Nut-upsuser < nut-upsuser@alioth-lists.debian.net> wrote: > On 3/21/24 14:00, Greg Oliver via Nut-upsuser wrote: > > All I can say is definitely replace the batteries if you are going to > > keep using it. The CyberPower(s) I have had in the past all have the > > battery check that cannot be turned off and when the batteries are > > actually "dead" the unit will kill the load to everything every time it > > runs the check. Just FYI. > > Yeah, definitely planning on replacing the batteries. Just trying to > mute the alarm in the meantime. > > And probably going to suck it up and buy new battery packs instead of > buying new SLA batteries and rebuilding them, because Cyberpower's > battery "trays" are ghastly. I've seen thicker plastic on > notions-counter blister packs. I know it is probably not good practice, but I always cut the speaker wires in all of my UPS units. I only have them to keep watching TV and internet when the storms (or something else) causes outages. It is hard to watch TV when the beep is constantly going :) On the other hand, it is also hard to know when the batteries are going to fail without the beep. > > -- >Phil Stracchino >Babylon Communications >ph...@caerllewys.net >p...@co.ordinate.org >Landline: +1.603.293.8485 >Mobile: +1.603.998.6958 > > > ___ > Nut-upsuser mailing list > Nut-upsuser@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser > ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] CyberPower PR3000LCDRTXL2U and NUT 2.8.0 - mute?
On 3/21/24 14:00, Greg Oliver via Nut-upsuser wrote: All I can say is definitely replace the batteries if you are going to keep using it. The CyberPower(s) I have had in the past all have the battery check that cannot be turned off and when the batteries are actually "dead" the unit will kill the load to everything every time it runs the check. Just FYI. Yeah, definitely planning on replacing the batteries. Just trying to mute the alarm in the meantime. And probably going to suck it up and buy new battery packs instead of buying new SLA batteries and rebuilding them, because Cyberpower's battery "trays" are ghastly. I've seen thicker plastic on notions-counter blister packs. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] CyberPower PR3000LCDRTXL2U and NUT 2.8.0 - mute?
On Thu, Mar 21, 2024 at 12:23 PM Phil Stracchino via Nut-upsuser < nut-upsuser@alioth-lists.debian.net> wrote: > I have a CyberPower PR3000LCDRTXL2U with a BP48V75ART2U expansion > chassis, which I am monitoring using NUT 2.8.0 (on Gentoo Linux). TThe > UPS appears to be telling me that the batteries need replacement due to > age. CyberPower support has confirmed that for me and told me how i > should be able to mute the alarm from the front panel until I can > replace the batteries, but it doesn't appear to be working. > > I can send the PR3000LCDRTXL2U a beeper.disable or beeper.mute via > upscmd, and upsc dutifully reports ups.beeper.status: disabled, but it > keeps beeping. > > Anyone else with a PR3000LCDRTXL2U have any useful tips? > All I can say is definitely replace the batteries if you are going to keep using it. The CyberPower(s) I have had in the past all have the battery check that cannot be turned off and when the batteries are actually "dead" the unit will kill the load to everything every time it runs the check. Just FYI. > -- >Phil Stracchino >Babylon Communications >ph...@caerllewys.net >p...@co.ordinate.org >Landline: +1.603.293.8485 >Mobile: +1.603.998.6958 > ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] CyberPower PR3000LCDRTXL2U and NUT 2.8.0 - mute?
I have a CyberPower PR3000LCDRTXL2U with a BP48V75ART2U expansion chassis, which I am monitoring using NUT 2.8.0 (on Gentoo Linux). TThe UPS appears to be telling me that the batteries need replacement due to age. CyberPower support has confirmed that for me and told me how i should be able to mute the alarm from the front panel until I can replace the batteries, but it doesn't appear to be working. I can send the PR3000LCDRTXL2U a beeper.disable or beeper.mute via upscmd, and upsc dutifully reports ups.beeper.status: disabled, but it keeps beeping. Anyone else with a PR3000LCDRTXL2U have any useful tips? -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] There is no voltage information
Thanks again.
So one more bit (other than indeed different libusb versions) that could
potentially come into play is bitness - armv7l builds are 32-bit, right?
One idea from here is to have you run the driver programs directly with
high debug verbosity, e.g. `usbhid-ups -DD -s Liebert` to compare the
two walls of text (at some debug level it spews byte data seen from
libusb); this might be more convenient to proceed with as a github issue.
Another idea, if you would be comfortable building NUT from source, would
be to check if NUT v2.8.0 (and/or current git master) mis-behaves similarly
if built in the Debian 11 32-bit environment against libusb-0.1. So to
dissect if the issue is between NUT 2.7.4 and 2.8.0 or in the OS
environment/dependencies somehow. This can get you started:
https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests
(take care to `configure --with-usb=libusb-0.1 ...`) - notably, you won't
have to *install* this build over what have you in the OS to just test the
newly built driver.
Jim
On Thu, Mar 21, 2024 at 7:18 AM Juan Carlos Fischer <
juancarlos.fisc...@gmail.com> wrote:
> Hello!
>
> NUT 2.7.4
> Raspberry Pi 4 Model B Rev 1.5 8 GB"Raspbian GNU/Linux 11
> (bullseye)" Linux raspberrypi 5.15.32-v7l+ #1538 SMP Thu Mar 31
> 19:39:41 BST 2022 armv7l GNU/Linux
>
> pi@raspberrypi:~ $ sudo ldd /lib/nut/usbhid-ups
>
> linux-vdso.so.1 (0xbec53000)
> /usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so =>
> /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6f83000)
> libusb-0.1.so.4 => /lib/arm-linux-gnueabihf/libusb-0.1.so.4 (0xb6f4e000)
> libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6f22000)
> libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6dce000)
> /lib/ld-linux-armhf.so.3 (0xb6f98000)
>
> NUT 2.8.0
> Raspberry Pi 4 Model B Rev 1.5 8 GB "Debian GNU/Linux 12 (bookworm)" Linux
> raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023
> aarch64 GNU/Linux
>
> pi@raspberrypi:~ $ sudo ldd /lib/nut/usbhid-ups
>
> linux-vdso.so.1 (0x007f9051c000)
> libusb-1.0.so.0 => /lib/aarch64-linux-gnu/libusb-1.0.so.0
> (0x007f9041)
> libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x007f9026)
> /lib/ld-linux-aarch64.so.1 (0x007f904df000)
> libudev.so.1 => /lib/aarch64-linux-gnu/libudev.so.1 (0x007f9021)
> libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0
> (0x007f901e)
>
> Best regards,
> -jcf
>
>
> On Wed, Mar 20, 2024 at 5:10 PM Jim Klimov
> wrote:
>
>> Thanks.
>>
>> Can you please also check (e.g. with ldd `which usbhid-ups`) which
>> `libusb` variant (1.0 or 0.1) was the 2.7.4 version of the driver running
>> with?
>> I wonder if the two generations of that library got something
>> differently?..
>>
>> The commit I mentioned -
>> https://github.com/networkupstools/nut/commit/207fed2282 - which added
>> the exponent checks, was from 2012 and should be in 2.7.4 as well :-\
>>
>> Checked: it is -
>> https://github.com/networkupstools/nut/blob/v2.7.4/drivers/belkin-hid.c#L157-L194
>>
>> Are the two tests running on otherwise the same HW/OS setup?
>>
>> Jim
>>
>>
>> On Wed, Mar 20, 2024 at 9:01 PM Juan Carlos Fischer <
>> juancarlos.fisc...@gmail.com> wrote:
>>
>>> Hello!
>>> Thanks for answering.
>>> This is the result using version 2.7.4:
>>>
>>> Network UPS Tools - UPS driver controller 2.7.4
>>> Network UPS Tools - Generic HID driver 0.41 (2.7.4)
>>> USB communication driver 0.33
>>> Using subdriver: Belkin/Liebert HID 0.17
>>>
>>> battery.charge: 100
>>> battery.charge.low: 38
>>> battery.charge.warning: 38
>>> battery.type: PbAc
>>> battery.voltage: 13.9
>>> battery.voltage.nominal: 12.0
>>> device.mfr: Emerson Network Power
>>> device.model: LiebertPSA
>>> device.serial:
>>> device.type: ups
>>> driver.name: usbhid-ups
>>> driver.parameter.bus: 001
>>> driver.parameter.pollfreq: 30
>>> driver.parameter.pollinterval: 2
>>> driver.parameter.port: auto
>>> driver.parameter.productid: 0001
>>> driver.parameter.synchronous: no
>>> driver.parameter.vendorid: 10AF
>>> driver.version: 2.7.4
>>> driver.version.data: Belkin/Liebert HID 0.17
>>> driver.version.internal: 0.41
>>> input.frequency: 50.0
>>> input.voltage: 221.8
>>> output.voltage: 222.6
>>> ups.load: 8
>>> ups.mfr: Emerson Network Power
>>> ups.model: LiebertPSA
>>> ups.productid: 0001
>>> ups.serial:
>>> ups.status: OL CHRG
>>> ups.vendorid: 10af
>>>
>>> Regards,
>>>
>>> Juan Carlos
>>>
>>> On Wed, Mar 20, 2024 at 4:22 PM Jim Klimov
>>> wrote:
>>>
Hello,
For clarity: what changed with the move from NUT v2.7.4 to 2.8.0 -
the warnings "became reported", or the highlighted values became zeroes
(and were valid non-zero numbers with older NUT - so a regression)?
It seems the message is specific to the subdriver and comes from
commit 207fed2282 and a change to the method involved was just recently
experimentally proposed in
