similar to: Nut problems with Centos and Belkin UPS

I looked through the faq, but couldn't find an answer to this. I'm trying to configure nut-2.0.4-26 on SuSE linux 10.2. In ups.conf, I have [myups] driver = belkinunv port = /dev/undefined desc = "Local UPS" I'm trying to find out what the port should be set to. lsusb shows: Bus 001 Device 005: ID 050d:0980 Belkin Components Device Descriptor: bLength

Hello, http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-September/003137.html http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-July/003014.html http://permalink.gmane.org/gmane.comp.monitoring.nut.user/2552 I still have this problem: $ dpkg -l | grep -i nut ii nut 2.2.0-2 The core system I thought this bug was fixed :( syslog:Dec 10

Hi, I have several Belkin UPSes here that I'm trying to connect through USB. I just downloaded 2.2.0, but unfortunately I'm getting error messages. All testing was done as root. The driver says (full output is attached): ---SNIP--- eta nut # ./usbhid-ups -x productid=0750 -DDD -a belkin <...cut...> Checking device (050D/0750) (003/007) - VendorID: 050d - ProductID: 0750 -

I just moved my UPS over from serial to USB and found that I needed to add it to the hotplug USB list to make things work. Belkin F6C120-UNV - Bus 002 Device 004: ID 050d:0912 Belkin Components It seems to be working OK on 2.0.4 with newhidups. Attached is a patch which I think should add the appropriate device id's in the right places to the trunk code. Jon -------------- next part

Just a little tiny detail : ============================================================================== > --- trunk/scripts/hotplug/libhid.usermap (original) > +++ trunk/scripts/hotplug/libhid.usermap Fri Aug 25 19:18:19 2006 > @@ -21,5 +21,7 @@ > libhidups 0x0003 0x09ae 0x1003 0x0000 0x0000 0x00 0x00 0x00 0x00

Hi everyone, I have a belkin ups that was bought around 2 months ago. It seems like the driver doesn't like the UPS, although on the website it's listed as supported. This is on a gentoo system with nut 2.2.1 . megatec_usb output: ---------SNIP---------- digamma nut # ./megatec_usb -a belkinm -DDDDDD Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb] Carlos Rodrigues

Greetings; I have the newest nut (nut-2.2.2-4.fc10.i386) from fedora 10 repos) installed and this ups (from lsusb -vv): Bus 001 Device 006: ID 050d:0751 Belkin Components Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0

Hi, I'm new in the list and I'm having a little bit trouble to put the megatec_usb to work. I've been using NUT for a while with the apc and megatec driver (serial), with no problem. The server is a Ubuntu 8.04.2 with NUT version 2.2.1-2.1ubuntu7.2, the default package version in this ubuntu release. I've configured the ups.conf as follows: [sms] driver = megatec_usb

Hi, I'm new in the list and I'm having a little bit trouble to put the megatec_usb to work. I've been using NUT for a while with the apc and megatec driver (serial), with no problem. The server is a Ubuntu 8.04.2 with NUT version 2.2.1-2.1ubuntu7.2, the default package version in this ubuntu release. I've configured the ups.conf as follows: [sms] driver = megatec_usb

Bonjour, Je souheterais utilis? la version qui permet le '-x generic',mais je ne sais pas ou la recuperer car ca devrait solutionner mon probleme (cf mail ci-dessous) DaneZ _____ From: DaneZ [mailto:david.guillotte@danez.no-ip.org] To: arnaud.quette@mgeups.com Sent: Sat, 08 Jul 2006 23:24:06 +0200 Subject: Fw: INFOSEC 500 XP en USB _____ Bonjour Arnaud, Je me

Hi all, I?ve a UPS Liebert GXT3 500-3000VA with USB port. I?ve install NUT version 2.2.2 from repository packages for Debian Lenny. Linux kernel 2.6.26 I?ve try to use usbhid-ups driver in ups.conf [liebert] driver=usbhid-ups port=/dev/usb/hiddev0 Debian get the usb: # lsusb -v Bus 001 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive UPS Device Descriptor: bLength

Ok guys I get this errors: Network UPS Tools ? UPS driver controller 2.4.1 Network UPS Tools ? Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 No matching HID UPS found my ups.conf is: [ap1000] driver = usbhid-ups port = auto I?ve also tried to set a specific usb port and change driver. My ups is a AMACROX 1000 http://www.amacrox.com//english/01_product/02_01detail.aspx?pdid=46

I used a brazilian UPS from "TS-Shara" which uses the megatec serial protocol and it works perfectly. Now I have another one from the same brand (TS-Shara) and it uses a USB cable. I found the following: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0483 ProdID=0035 Rev= 2.00 S:

So, I have this Mustek Powermust 600USB (no serial port) here temporarily. It seems to be a hid device. The output from "lsusb -v" and "newhidups -DDDDD" (with "generic" and "vendorid=06da") are (respectively): ----------------------------------------------------------------------------------------------- Bus 001 Device 002: ID 06da:0003 Phoenixtec Power

I have an UPS, that claims to be IPPon Back Power Pro 700. I'm trying to connect it using USB. lsusb -v says: Bus 1 Device 3: ID 06da:0003 Phoenixtec Power Co., Ltd Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0

>> >> The output was also not as big as you made it out to be. > > Well, I didn't expect the driver to fail *that* badly :-) > > Assuming the UPS is still at /dev/ugen4.2, can you try the following command? (Probably needs to be run as root, with the driver stopped.) > > usbconfig -u 4 -a 2 dump_curr_config_desc Here is output of the command. Thank you for

# /lib/nut/megatec_usb -a myups Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] No supported devices found. Please check your device availability with 'lsusb' and make sure you have an up-to-date version of NUT. If this does not help, try running the driver with

On 06/19/2017 05:33 PM, Charles Lepple wrote: > On Jun 19, 2017, at 4:27 AM, Manuel Wolfshant wrote: >> 1.014501 [D2] Unable to get HID descriptor (Pipe error) >> 1.014511 [D3] HID descriptor length (method 1) -1 > So at this point in the logs, the kernel USB HID driver is detached from the UPS HID interface (until the UPS USB cable is unplugged and reattached). If

Hi, Sometime ago [ June 2018 ] I posted a message about getting trying to get NUT to work with a Power Shield Defender 1200VA UPS. This model appears in the HCL at https://networkupstools.org/stable-hcl.html That UPS reported the following when queried using 'lsusb' on an iMac running macOS [ 10.15 ] Bus 001 Device 008: ID 0665:5161 Cypress Semiconductor USB to Serial Device Descriptor:

I recently purchased a UPS from http://www.microcenter.com/product/470131/5E_1,100W_2,200VA_6-Outlet_UPS It's sold as an Eaton 5E 1,100W 2,200VA 6-Outlet UPS SKU: 147140 Mfr Part #: 5E2200USB-LA UPC: 743172064875 "The Eaton 5E is an essential line interactive UPS that provides cost effective and reliable power protection against power outages and bad power quality. Thanks to its small