Arjen de Korte wrote: > > 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.
Perhaps we should lower the debug level of that particular set of error messages to 0? It seems to be useful even when not debugging. > 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 > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser > _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
