Nut upsuser - Oct 2016 - Unable to find driver for a supported device

Hello everyone,

I have a Tripp-Lite UPS (smart1500rmxl2ua) I'm trying to get working with
nut.

This is a FreeBSD 10.3 box.  I've tried using the
usbhid-ups<http://networkupstools.org/docs/man/usbhid-ups.html> driver but
everytime I try to start up nut, I get this:

# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
No matching HID UPS found
Driver failed to start (exit status=1)

usbconfig sees the UPS:

# usbconfig
ugen0.1: <UHCI root HUB VIA> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=SAVE (0mA)
ugen3.1: <EHCI root HUB VIA> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=SAVE (0mA)
ugen2.1: <UHCI root HUB VIA> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=SAVE (0mA)
ugen1.1: <UHCI root HUB VIA> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=SAVE (0mA)
ugen0.2: <TRIPP LITE SMART1500RMXL2Ua TRIPP LITE> at usbus0, cfg=0 md=HOST
spd=LOW (1.5Mbps) pwr=ON (60mA)

Here's the ups.conf

# cat ups.conf
[TrippliteUPS]
driver=usbhid-ups
port=auto


 I've also tried the tripplite driver with no success.  Any ideas on what
I'm missing?

Nick Teague
Network Administrator
Smartfox Solutions
office: 1-877-301-9993
fax: 1-256-301-9299
www.smartfox.us
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161011/a64b5175/attachment.html>

> On Oct 11, 2016, at 1:35 PM, Nick Teague <nick.teague at smartfox.us>
wrote:
> 
> ugen0.2: <TRIPP LITE SMART1500RMXL2Ua TRIPP LITE> at usbus0, cfg=0
md=HOST spd=LOW (1.5Mbps) pwr=ON (60mA)
To determine the proper driver, would you please run the following usbconfig
command as root? Here's an example from my UPS:

# usbconfig -d ugen0.2 dump_device_desc

ugen0.2: <Evolution MGE UPS SYSTEMS> at usbus0, cfg=0 md=HOST spd=LOW
(1.5Mbps) pwr=ON (20mA)

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0110 
  bDeviceClass = 0x0000 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0008 
  idVendor = 0x0463 
  idProduct = 0xffff 
  bcdDevice = 0x0001 
  iManufacturer = 0x0001  <MGE UPS SYSTEMS>
  iProduct = 0x0002  <Evolution>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001 

Feel free to chop off the last few digits of the string after iSerialNumber, if
it returns something unique.

If idProduct is 0001 (not likely these days), you need tripplite_usb, otherwise
usbhid-ups is the correct driver.

The other prerequisite is configuring the permissions. I'm not sure if we
ever got this integrated into the FreeBSD ports installation procedure, but do
you have a "nut-usb.conf" file in /usr/local/etc/devd? If so, it
should configure the appropriate /dev/usb device node to be owned (or at least
group-writable) by the NUT user. A devd restart and/or pulling the USB cable
might be necessary.

The exact details for the above will depend on the procedure you followed to
install NUT (ports vs building from source), so let us know, and we can zero in
on the problem quickly.

-- 
Charles Lepple
clepple at gmail

# usbconfig -d ugen0.2 dump_device_desc
ugen0.2: <TRIPP LITE SMART1500RMXL2Ua TRIPP LITE> at usbus0, cfg=0 md=HOST
spd=LOW (1.5Mbps) pwr=ON (60mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0008
  idVendor = 0x09ae
  idProduct = 0x0001
  bcdDevice = 0x0001
  iManufacturer = 0x0001  <TRIPP LITE>
  iProduct = 0x0002  <TRIPP LITE SMART1500RMXL2Ua >
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001

I swapped over to the tripplite_usb and it's still doing the same thing.

# /etc/rc.d/devd restart
Stopping devd.
Starting devd.

# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.29 (2.7.4)
Warning: This is an experimental driver.
Some features may not function correctly.

No matching USB/HID UPS found
Driver failed to start (exit status=1)


I installed from ports.  I do have nut-usb.conf. 

# ls -la
total 32
drwxr-xr-x   2 root  wheel    512 Oct 11 11:23 .
drwxr-xr-x  22 root  wheel   1536 Oct 11 11:23 ..
-rw-r--r--   1 root  wheel  24007 Sep 27 11:35 nut-usb.conf

# pwd
/usr/local/etc/devd

Nick Teague
Network Administrator
Smartfox Solutions
office: 1-877-301-9993
fax: 1-256-301-9299
www.smartfox.us

________________________________________
From: Charles Lepple [clepple at gmail.com]
Sent: Tuesday, October 11, 2016 7:35 PM
To: Nick Teague
Cc: nut-upsuser at lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Unable to find driver for a supported device
> On Oct 11, 2016, at 1:35 PM, Nick Teague <nick.teague at smartfox.us>
wrote:
>
> ugen0.2: <TRIPP LITE SMART1500RMXL2Ua TRIPP LITE> at usbus0, cfg=0
md=HOST spd=LOW (1.5Mbps) pwr=ON (60mA)
To determine the proper driver, would you please run the following usbconfig
command as root? Here's an example from my UPS:

# usbconfig -d ugen0.2 dump_device_desc

ugen0.2: <Evolution MGE UPS SYSTEMS> at usbus0, cfg=0 md=HOST spd=LOW
(1.5Mbps) pwr=ON (20mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x0000
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0008
  idVendor = 0x0463
  idProduct = 0xffff
  bcdDevice = 0x0001
  iManufacturer = 0x0001  <MGE UPS SYSTEMS>
  iProduct = 0x0002  <Evolution>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001

Feel free to chop off the last few digits of the string after iSerialNumber, if
it returns something unique.

If idProduct is 0001 (not likely these days), you need tripplite_usb, otherwise
usbhid-ups is the correct driver.

The other prerequisite is configuring the permissions. I'm not sure if we
ever got this integrated into the FreeBSD ports installation procedure, but do
you have a "nut-usb.conf" file in /usr/local/etc/devd? If so, it
should configure the appropriate /dev/usb device node to be owned (or at least
group-writable) by the NUT user. A devd restart and/or pulling the USB cable
might be necessary.

The exact details for the above will depend on the procedure you followed to
install NUT (ports vs building from source), so let us know, and we can zero in
on the problem quickly.

--
Charles Lepple
clepple at gmail