similar to: Support removed for newer Belkin 1200 VA UPS?

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

Bus 003 Device 002: ID 050d:1100 Belkin Components # /lib/nut/usbhid-ups -a belkin Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-) No matching HID UPS found Hmm best to stick with 2.0.4. Justin.

Bus 003 Device 002: ID 050d:1100 Belkin Components # /lib/nut/usbhid-ups -a belkin Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-) No matching HID UPS found Hmm best to stick with 2.0.4. Justin.

I have a Belkin F6H500ukUNV ups that I am attempting to get working under nut, however it does not appear to be detected by nut, I'm assuming that I need to feed some information back to you guys to get it included in the database somwhere. I've included (what I can think might be) the relivant outputs. Please let me know if you require anything else. dmesg output /sbin/newhidsups

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 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:

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

I almost had nut_2.0.5-3_i386.deb (from http://packages.debian.org/unstable/admin/nut - installed via dpkg, not via repository) working: * problems with getting it to come up during boot * monitoring via knutclient was OK * shutdown on low battery worked adequately, if not quite as described) and newhidups suddenly stopped talking to my Belkin F6C550-AVR . It's only been in use for a

Hi, is there a way to use my Belkin F6H650 on the USB port? I already installed usbhid-support, but neither the hidups worked (reports "/dev/usb/hiddev0 is not a UPS") nor genericups with upstype=7 and the hiddev set as device ("ioctl TIOCMSET: Invalid argument") worked. I have installed the debian sarge package of nut 2.0.1 (2.0.1-4) Regards, Philipp

Hi, I bought a Belkin Active Battery Backup UPS (http://www.belkin.com/uk/activebattery/) yesterday with a USB port and hoped it would work with nut. The device will show up in /proc/bus/usb/devices as a Cypress Semiconductor USB to Serial. It creates /dev/hiddev0 (and this disappears when the UPS is unplugged). I've tried using belkin, belkinunv, usbhid-ups and megatec_usb. I've tried

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 ran into the following issue today and would like some feedback from the group. Setup: I am using a MGE Pulsar Evolution 2200 UPS connected through a Belkin (F5U218-MOB) 4-Port USB Hub. Scenario: The newhidups subdriver_matcher function calls belkin_subdriver->belkin_claim. The belkin_claim function in belkin-hid.c matches the VendorID of the hub to Belkin's VendorID (0x050d), causing

I just noticed the following curious behavior when using newhidups with upsdrvctl and two different USB devices: My ups.conf contains two devices, both using newhidups: [belkinusb] driver = newhidups port = auto desc = "Belkin UPS, USB interface" vendorid=050d [mgeusb] driver = newhidups port = auto desc = "MGE UPS, USB

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

Hello everyone! If this message was posted twice, my apologies. I'm having issues with my webmail today... I am using the testing version of NUT from SVN at changeset 582. I have successfully created a stub for newhidups driver for my Dynex DX-800U UPS, but I am completely lost on the customization of it. I've followed the hid-subdrivers.txt instructions and I understand I need to

Hi, I am new to this list, so I apologize if I make any mistakes in posting. I am trying to set up nut with my Tripp Lite SMART 1200LCD. I looked on the compatability page, and some Tripp Lite models were supported, so I decided to try out mine. I have tried both USB and serial connections, and neither have worked. I am just wondering if this is a problem with nut supporting my model, or

Hello world; been using nut atop Debian GNU/Linux (sid) for about two years by now, my configuration broke as I upgraded the machine this morning (headin' for kernel 2.6 to have full support for the new GBE NIC included). I read through the UPGRADE.gz instructions provided with the Debian packages and tried to fix things according to the instructions pointed out there, but things still just

Hello NUT ! In order to fill info structure I'm putting in the drivers, I need to gather a lot of information. The information I need, at best, is : - For each USB UPS, the pair VendorID ProductID - For each pair Driver/UPS supported, how was made the driver ? By the manufacturer, by reverse engineering, ... - Who contributed to which driver - Who is the "maintener" of each driver

I'm sure I'm missing something, but I can't seem to get NUT working on FreeBSD. bryce at tahiti[/usr/local/etc/nut]>cat ups.conf [belkin] driver = usbhid-ups port = auto vendorid = 050d #productid = 0751 bryce at tahiti[/usr/local/etc/nut]>s /usr/local/libexec/nut/usbhid-ups -DDDDD -a belkin Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31