Nut upsdev - Aug 2007 - Nut 2.2.0 also broke Belkin 1200 Universal UPS' as well.

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.

Justin Piszcz wrote:
> 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.
No. Just run the driver in debug mode and you'll see what you have to do
to start it again. Previously, the belkin-hid driver would only match
the vendorid, but since there are also Belkin USB devices that are not
an UPS, we included the productid in this match too. The productid 1100
was added after we released nut-2.2.0, so you need to specify this in
either 'ups.conf'

[belkin]
	driver = usbhid-ups
	port = auto
	productid = 1100

or on the startup commandline

	/lib/nut/usbhid-ups -a belkin -x productid=1100

Apparently you've missed the note about this in the UPGRADING document
(where the usbhid-ups was still named newhidups):
> Changes from 2.0.4 to 2.0.5:
> 
>  - users of the newhidups driver: the driver is now more strict about
>    refusing to connect to unknown devices. If your device was
>    previously supported, but fails to be recognized now, add
>    'productid=XXXX' to ups.conf. Please report the device to the
NUT
>    developer's mailing list.
Best regards, Arjen

On 8/26/07, Arjen de Korte <nut+users at de-korte.org>
wrote:
> Previously, the belkin-hid driver would only match
> the vendorid, but since there are also Belkin USB devices that are not
> an UPS, we included the productid in this match too. The productid 1100
> was added after we released nut-2.2.0, so you need to specify this in
> either 'ups.conf'
I see this was added to the trunk in r1029:

   http://boxster.ghz.cc/projects/nut/changeset/1029

Arnaud and Arjen,

Should we apply that changeset to branches/Testing or are all of the
usbhid-ups changes intended to go into 2.2.1?

-- 
- Charles Lepple