Nut upsuser - Jul 2019 - Trouble getting Roline/Powercom UPS recognized

Hi all,

I’m new to NUT and have some trouble getting my new UPS to work.
Since the HCL listed Powercom UHID models as „green“ I thought buying
a Roline (German rebranded Powercom) model would be a good idea.

The OS is FreeBSD:

FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0
r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019     root at
nemesis:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64
amd64

This is the device:

ugen0.6: <POWERCOM Co.,LTD HID UPS Battery> at usbus0
uhid0 on uhub0
uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.02, addr
5> on usbus0

This is the driver version:

root at freenas-pmh[~]#  /usr/local/libexec/nut/usbhid-ups -V
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33

Came bundled with the FreeNAS installation.

ups.conf:

root at freenas-pmh[~]# cat /usr/local/etc/nut/ups.conf 
[roline]
    driver = usbhid-ups
    port = /dev/uhid0
    desc = “"

Debug output:

root at freenas-pmh[~]#  /usr/local/libexec/nut/usbhid-ups -DD -a roline
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
   0.000000	debug level is '2'
   0.000746	upsdrv_initups...
   0.001256	Checking device (0D9F/0004) (/dev/usb//dev/ugen0.6)
   0.193552	- VendorID: 0d9f
   0.193573	- ProductID: 0004
   0.193579	- Manufacturer: unknown
   0.193582	- Product: unknown
   0.193586	- Serial Number: unknown
   0.193589	- Bus: /dev/usb
   0.193592	- Device release number: 0002
   0.193598	Trying to match device
   0.193608	Device matches
   0.261466	Unable to get HID descriptor (Unknown error)
   0.261487	HID descriptor length 996
   0.328756	Unable to get Report descriptor: Input/output error
   0.328821	Checking device (05E3/0610) (/dev/usb//dev/ugen0.5)
   0.330192	- VendorID: 05e3
   0.330204	- ProductID: 0610
   0.330209	- Manufacturer: unknown
   0.330214	- Product: USB2.0 Hub
   0.330217	- Serial Number: unknown
   0.330221	- Bus: /dev/usb
   0.330224	- Device release number: 3298
   0.330229	Trying to match device
   0.330238	Device does not match - skipping
   0.330256	Checking device (0557/2419) (/dev/usb//dev/ugen0.4)
   0.330301	- VendorID: 0557
   0.330307	- ProductID: 2419
   0.330310	- Manufacturer: unknown
   0.330314	- Product: unknown
   0.330317	- Serial Number: unknown
   0.330321	- Bus: /dev/usb
   0.330324	- Device release number: 0100
   0.330327	Trying to match device
   0.330333	Device does not match - skipping
   0.330347	Checking device (0557/7000) (/dev/usb//dev/ugen0.3)
   0.330385	- VendorID: 0557
   0.330390	- ProductID: 7000
   0.330394	- Manufacturer: unknown
   0.330397	- Product: unknown
   0.330400	- Serial Number: unknown
   0.330404	- Bus: /dev/usb
   0.330407	- Device release number: 0000
   0.330411	Trying to match device
   0.330416	Device does not match - skipping
   0.330430	Checking device (05E3/0610) (/dev/usb//dev/ugen0.2)
   0.331621	- VendorID: 05e3
   0.331633	- ProductID: 0610
   0.331637	- Manufacturer: unknown
   0.331640	- Product: USB2.0 Hub
   0.331643	- Serial Number: unknown
   0.331646	- Bus: /dev/usb
   0.331650	- Device release number: 3298
   0.331653	Trying to match device
   0.331659	Device does not match - skipping
   0.331677	Checking device (0000/0000) (/dev/usb//dev/ugen0.1)
   0.331733	- VendorID: 0000
   0.331741	- ProductID: 0000
   0.331745	- Manufacturer: 0x8086
   0.331748	- Product: XHCI root HUB
   0.331752	- Serial Number: unknown
   0.331755	- Bus: /dev/usb
   0.331758	- Device release number: 0100
   0.331762	Trying to match device
   0.331767	Device does not match - skipping
   0.331780	No appropriate HID device found
   0.331789	No matching HID UPS found

I’m a bit puzzled by the fact that it probes all ugen devices when the
device to use (uhid0) is explicitly configured …

Any help greatly appreciated.

Thanks,
Patrick

On Jul 16, 2019, at 3:52 AM, Patrick M. Hausen wrote:
> The OS is FreeBSD:
> 
> FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0
r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019     root at
nemesis:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64
amd64
> 
> This is the device:
> 
> ugen0.6: <POWERCOM Co.,LTD HID UPS Battery> at usbus0
> uhid0 on uhub0
> uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.02, addr
5> on usbus0
There may be an issue with the uhid driver binding to the device. I can't
remember which versions of FreeBSD this affects, though.
> This is the driver version:
> 
> root at freenas-pmh[~]#  /usr/local/libexec/nut/usbhid-ups -V
> Network UPS Tools - Generic HID driver 0.41 (2.7.4)
> USB communication driver 0.33
> 
> Came bundled with the FreeNAS installation.
This driver is using the libusb-0.1 API through FreeBSD's emulation layer
(since they implement a different API that is closer to libusb-1.0).

We have another branch that uses the libusb-1.0 API:
https://github.com/networkupstools/nut/issues/300
> ups.conf:
> 
> root at freenas-pmh[~]# cat /usr/local/etc/nut/ups.conf 
> [roline]
>    driver = usbhid-ups
>    port = /dev/uhid0
>    desc = “"
As mentioned here:
https://networkupstools.org/docs/man/usbhid-ups.html#_implementation

"The driver ignores the "port" value in ups.conf."

The problem is that libusb does not provide a way to open a specific device by
pathname, and if it did, it would need a generic USB device node (like the
/dev/ugen* names shown at the end of the "Checking device" log
messages) rather than a USB HID device node. Instead, if you have multiple
UPSes, see the previous section in the man page.

We recommend putting something like "port = auto" in the configuration
file.
> Debug output:
> 
> root at freenas-pmh[~]#  /usr/local/libexec/nut/usbhid-ups -DD -a roline
> Network UPS Tools - Generic HID driver 0.41 (2.7.4)
> USB communication driver 0.33
>   0.000000	debug level is '2'
>   0.000746	upsdrv_initups...
>   0.001256	Checking device (0D9F/0004) (/dev/usb//dev/ugen0.6)
>   0.193552	- VendorID: 0d9f
>   0.193573	- ProductID: 0004
>   0.193579	- Manufacturer: unknown
>   0.193582	- Product: unknown
>   0.193586	- Serial Number: unknown
>   0.193589	- Bus: /dev/usb
>   0.193592	- Device release number: 0002
>   0.193598	Trying to match device
>   0.193608	Device matches
>   0.261466	Unable to get HID descriptor (Unknown error)
>   0.261487	HID descriptor length 996
>   0.328756	Unable to get Report descriptor: Input/output error
This is the case where the libusb-1.0 API might provide better error messages.
These might be related to permissions - check to see if the /dev/ugen0.6 node is
writable by the NUT user/group. (There should be a devd.conf file installed
under /usr/local to make this work.)
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Hi all,
> Am 16.07.2019 um 15:33 schrieb Charles Lepple <clepple at gmail.com>:
> There may be an issue with the uhid driver binding to the device. I
can't remember which versions of FreeBSD this affects, though.
Unloaded the kmod - did not change anything. But I will configure
devd not to load uhid.ko ever, just to be sure. You are implying Ithe uhid
driver
should not be present, correct?
> We have another branch that uses the libusb-1.0 API:
https://github.com/networkupstools/nut/issues/300
I will compile and try this one and report back.
> This is the case where the libusb-1.0 API might provide better error
messages. These might be related to permissions - check to see if the
/dev/ugen0.6 node is writable by the NUT user/group. (There should be a
devd.conf file installed under /usr/local to make this work.)
I’m running my tests as root. The device is rw-rw——, root, uucp.

Kind regards
Patrick