similar to: Nut 2.2.0 also broke Belkin 1200 Universal UPS' as well.

Have had no issue until I ran apt-get dist-upgrade this morning: # /lib/nut/newhidups -u nut -DDDDDD auto Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '6' Checking device (0000/0000) (001/001) - VendorID: 0000 - ProductID: 0000 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 Trying to match device Device does not

# /lib/nut/newhidups -DDDDD -u nut /dev/usb/hiddev0 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) debug level is '5' Checking device (0665/5161) (001/003) - VendorID: 0665 - ProductID: 5161 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 BELKIN 550VA UPS BATTERY BACKUP Should I be using a different driver?

Mr. Selinger, I'm CCing you directly since it appears (insofar as I can tell) that you are one of the delelopers for the newhidups driver. This is the third time I've submitted this (hence the CC this time). Hopefully mailman takes it. I've tweaked my SPF records, and I'm hoping that was the problem. My sincere apologies if this has gone through and I just haven't seen it

I have a new Belkin F6C900-UNV. I see that it's not listed in belkin-hid.c The VendorID is 0x050d like all the Belkin UPSes, and the ProductID is 0x0900. I haven't had a chance to actually test the development version of nut yet, since I'm running Fedora Core 6, which still has nut 2.0.3. `newhidups -DD -a myups` gives the error of: Checking device (050D/0900) (001/002) - VendorID:

I have changed over to CentOS5 on some of our computers. I had been using Mandriva 2006 and the nut software worked using: driver = newhidups port = auto Using the same version of nut with the same config files on CentOS5, I get the following error output from 'upsdrvctl': Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No

I have changed over to CentOS5 on some of our computers. I had been using Mandriva 2006 and the nut software worked using: driver = newhidups port = auto Using the same version of nut with the same config files on CentOS5, I get the following error output from 'upsdrvctl': Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No

I'm setting up a cluster with multiple ups's using nut 2.2. The ups's are Belkin 1500 (ID 050d:0751) which don't appear to report a serial number. Is there any other way I can setup ups.conf with multiple of these ups over usb on Linux? If I just setup the vendor and product id's, every definition in ups.conf appears to match the first one, and therefore all of them but

# /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

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

On Tuesday 14 October 2014 08:19:02 Charles Lepple did opine And Gene did reply: > usbhid-ups Added that, but only get this at "sudo service nut start" gene at coyote:/etc/init.d$ sudo service nut start * Starting Network UPS Tools [ OK ]

Peter, Apparently, some Belkin UPSes still have problems with this. When we receive this report through the interrupt pipeline it is ignored (the special case in usbhid-ups.c) and even after that it looks like there are still some problems with it: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-July/003014.html Wouldn't it be an option to just to ignore this completely and

-> ups at p34 POWER ALERT on Sat Aug 25 07:40:01 EDT 2007 -> UPS belkin at localhost battery is low The last good version is 2.0.4, someone e-mailed me from this list before exactly why this happened it was about ignoring bad events from the usb-dev subsystem/kernel but I guess my question is this going to get fixed or should I stick with 2.0.4 as long as I can? Thanks. # ./usbhid-ups

Greetings all; Back to a thread I started back in May of 2008 I think. I never did get this belkin and nut to talking, so I thought I'd make another run at it. Trying to run the driver as the user gene, I'm getting this: --------------------------- [root at coyote ups]# su gene -c "/sbin/belkin -D -a myups" Network UPS Tools - Belkin Smart protocol driver 0.21 (2.2.2) debug

Package: nut Version: 2.0.5-3+b1 Running: Debian Testing Arch: x86_64 BUG: (the battery is relatively new (6mos) and there have been no recent power outages) Jul 28 04:29:44 p34 upsmon[2402]: UPS belkin at localhost battery is low Jul 28 05:13:15 p34 upsmon[2402]: UPS belkin at localhost battery is low Jul 28 05:14:05 p34 upsmon[2402]: UPS belkin at localhost battery is low FIX: (go back to

Greetings; Its unk because whats plugged in seems to be blocking the rear name plate. About all I can recall is that its big, 3 battery unit, rated somewhere north ob 1250 VA. Its an 050D:0751 Belkin. What driver should I use, and what file is that set in? The nut version presently and freshly installed is from the Ubuntu 10.04.4 LTS repo's. Probably old, but IIRC it also worked with

Hi Arjen My apologies fro drifting off topic in the other mailing list...:-) On the bottom of the Belkin UPS unit - is the model number: F6C120auUNV The "au" is for Australia I think. "man belkinunv" states that F6C120-UNV is supported - and I assumed that the "au" would not prevent this. I plugged in the USB to gather the information you requested. My intention

Hello, I'm using nut to control a Belkin F6C1500-TW-RK ups (vendor ID 050d, product ID 0751). I'm using the belkin driver and a serial connection for communications. The host computer is running Debian. I have things configured such that both my computer and the ups shut off when the battery level reaches a critical level, and everything seems to work fine up to this point. My problem

Hello, I'm using nut to control a Belkin F6C1500-TW-RK ups (vendor ID 050d, product ID 0751). I'm using the belkin driver and a serial connection for communications. The host computer is running Debian. I have things configured such that both my computer and the ups shut off when the battery level reaches a critical level, and everything seems to work fine up to this point. My problem

On Oct 12, 2014, at 8:28 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Its unk because whats plugged in seems to be blocking the rear name plate. > About all I can recall is that its big, 3 battery unit, rated somewhere > north ob 1250 VA. > > Its an 050D:0751 Belkin. > > What driver should I use, and what file is that set in? Looks like it is in usbhid-ups. If

Hello, all, I had been using NUT's Ubuntu package (64 bit) with no problems until upgrading to Ubuntu 11.04. Now, I get the following message when I try usbhid-ups: $ sudo /lib/nut/usbhid-ups -a mybelkin Network UPS Tools - Generic HID driver 0.35 (2.6.0) USB communication driver 0.31 Can't claim USB device [050d:1100]: could not detach kernel driver from interface 0: Operation not