similar to: NUT USB Delayed Communication

Hello, On one hand, sorry to hear that higher polling frequency in upsmon did not help. On another, question is if the driver gets the info (online state and its changes) from device quickly enough. Initially I meant for you to also try if the "pollonly" flag (in each device section of ups.conf for usbhid-ups instances) would make a difference?.. I'd expect data-transfer interrupts

Good evening folks, So I configured NUT on a Raspberry Pi 4 both UPS are connected over USB however the switch from AC Power to Battery seems to be delayed on the NUT communication would anyone have any ideas? The Pi Reports that the UPS is on battery around 30 seconds later I think this delay is long. I have tested it on a physical computer and the detection is around 5 to 6 seconds with

Good afternoon, So been trying to figure out a problem i am encountering with NUT and two APC 1000 UPS's that's connected via USB, First off it somewhat works well kind of, Pull the power to either UPS and it's slow at responding but finally detects it however the other problem is that after a few days NUT just stops reporting that the Power has been off. Here is what I've

Laurent Taieb via Nut-upsuser wrote on 3/9/23 9:25 AM: > > Hi NUT Users, > > One of my APC UPS is having battery issue and apparently we cannot > change battery in that UPS. (not super green?) > > I have purchased an EATON UPS and added the ref in ups.conf > > When restarting the driver, I got this error > > >0.030612[D2] Checking device 2 of 10 (0463/FFFF)

On Thursday, March 9th, 2023 at 8:34 AM, Dan Langille via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: >> The UPS has been defined in ups.conf as: >> >> [myups3] >> >> driver : usbhid-ups >> >> port = auto >> >> vendorid = 0463 >> >> productid = ffff >> >> desc = "5S" >> >> bus

Hello all, I have been having a problem with upsmon on Fedora 24 on boot. NUT is configured as a netclient to a Raspbian NUT server. After boot up upsmon repeatedly says "connect failed: No such host". It is not able to connect at all until the service is bounced. This seems to indicate a name resolution problem but shouldn't this auto correct once name resolution is working properly

Also, just in case - are you in a virtualized environment? Is there (intentional or not) USB pass-through to the UPSes? My hint is, we had cases where a host or guest grabbed the device but it was not apparent from the part of system running NUT. Jim On Fri, Mar 24, 2023, 23:23 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Sounds like some other program is holding the port. Have

Thanks Larry, I tried. Got the following traces and the driver doesn?t start. 1.036797 [D2] - VendorID: 0463 1.036812 [D2] - ProductID: ffff 1.036826 [D2] - Manufacturer: unknown 1.036840 [D2] - Product: unknown 1.036872 [D2] - Serial Number: unknown 1.036912 [D2] - Bus: 002 1.036942 [D2] - Device: unknown 1.036965 [D2] - Device

Sounds like some other program is holding the port. Have you stopped other NUT drivers for the device (e.g. via auto-resuscitating services) before starting this one? Does udev, ugen or similar facility have the configuration to hand off this device to NUT run-time user? (BTW, if you are now testing a custom build - was it configured to use same accounts as pre-packaged variant)? On Fri, Mar 24,

The "unknown" fields mean the driver did not get that piece of information from libusb. In case of Manufacturer/Product which are unknown in the later post, but known in the first, I suppose you had another driver running, or the kernel still owned it (udev misbehavior, not handing it off after reconnections, etc.) and so exclusive access was not given to the new (currently reporting)

I'm attempting to get a HP R1500 G2 UPS working with Solaris 10 connected via USB. Thanks to Arnaud's patch to drivers/tripplite-hid.c found at http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-February/005887.html things mostly work. upsc ups01 shows a couple of things that don't look quite right. [....] battery.temperature: -234.1 [....] ups.alarm: No battery installed!

Hi. I'm looking for a way to configure an Eaton Powerware 5125 under Debian Squeeze (amd64) with USB port. Can someone help me? Find attached bellow my settings: # cat /etc/nut/ups.conf ... [ups01] driver = bcmxcp_usb port = /dev/bus/usb/002/003 desc = "Powerware 5125" # ls -la /dev/bus/usb/002/003 crw-rw-r-- 1 root nut 189, 130 Nov 21 11:45 /dev/bus/usb/002/003 #

tisdagen den 16 december 2014 15.36.29 skrev Frantz de Germain: > Hello, Hi Frantz, > > I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. > I've got the message : > > "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of > this message)" > > I've been looking for "pollonly" in

On Sat, 17 Sep 2016, Yevgeniy Kuksenko wrote: > Hello all, I have been having a problem with upsmon on Fedora 24 on boot. NUT is configured as a netclient to a Raspbian NUT server. After boot up upsmon > repeatedly says "connect failed: No such host". It is not able to connect at all until the service is bounced. This seems to indicate a name resolution > problem but

2010/10/18 Michael Eitelwein > Hi Arnaud > Hi Michael, > Yes, did test it without success. > can you please post the first 20 seconds running blazer_usb in debug mode, ie: $ sudo /lib/nut/blazer_usb -DDD -a cyberpower aside from fixing the megatec situation, ensuring that you'll be able to run the replacement is also to be considered ;-) now, for the megatec issue, we need

Hello I currently run a few samba servers one being used as a PDC. Today I added a user to the domain and for some reason I can not get it to connect to any of the shares but "home" on the file server. % smbclient -U gregi //server3/public Password: Domain=[HYDRIX-MALVERN] OS=[Unix] Server=[Samba 3.0.28] tree connect failed: NT_STATUS_ACCESS_DENIED However I can connect with : $

Hi all, Have been using Nut on Linux for over ten years now and find it brilliant. Thanks. Just upgraded to 2.4.2 and have the 5 or 6 models of UPS's that we use (apcsmart, megatec, mge-shut, surgemax, digitus) all working including the MGE Pulsar Evolution 1100 on a USB connection using the usbhid-ups driver. Running on SLES9. Old but we still have a few servers out there running

Hello, I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. I've got the message : "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message)" I've been looking for "pollonly" in the usbhid-ups man page, but it didn't help me. Could someone explain me what does this means exactly ? What are

Sergey, I?m no expert on this but I have been reading the driver code, trying to sort out bigger problems with the OpenUPS driver! I can make 2 observations that I can?t check out myself : ?beeper.disable? was previously ?beeper off? - and ?beeper.enable? was ?beeper.on?. Not sure if it?s worth trying the old versions? If your UPS doesn?t wait for LB, could this be because there is another

On Wed, 18 Oct 2017, Drew Plaster wrote: > MASTER SYSTEM > > nut.conf > MODE=netserver > > ups.conf > [TOPAPC] > driver = usbhid-ups > port = auto > pollonly > serial = "IS1309002707" > desc = "TOPAPC" > [MIDAPC] > driver = usbhid-ups > port = auto > pollonly > serial =