<div dir="ltr"><div>Hello,</div><div><br></div><div>Looking at logged NUT issue discussions like <a href="https://github.com/networkupstools/nut/issues/475">https://github.com/networkupstools/nut/issues/475</a>, <a href="https://github.com/networkupstools/nut/issues/483">https://github.com/networkupstools/nut/issues/483</a> and <a href="https://github.com/networkupstools/nut/issues/646">https://github.com/networkupstools/nut/issues/646</a> I see people did have success with models named similar to yours. So generally it should be supported, with "liebert-hid" or better with "mge-hid" subdriver according to reports... But then there were also users for whom it did not work, and those for whom it disconnected after a few hours (causing a Stale Data problem).</div><div><br></div><div>I would suggest first ruling out systemic issues (device node permissions vs. user the driver runs as, some kernel quirks?, possibly a libusb version mismatch - official NUT releases only offered libusb-0.1 compatibility and solutions for libusb-1.0 were not merged yet, but there are branches on GitHub to try if you would - linked from issue #300). Those "no route to host" and "no such file" lines look most incorrect.</div><div><br></div><div>Does `nut-scanner` also fail to find and connect to the device?</div><div><br></div><div>Do you have udev or similar system that might grab the device and not let NUT have it?<br></div><div><br></div><div>You can also try to pick configuration options in ups.conf section for your device, or via `-x` CLI options while you experiment on command line, such as to try setting the subdriver to use, or the `usb_set_altinterface=1` so that the NUT driver tells libusb to disconnect other consumers from the device, if I read the docs correctly.</div><div><br></div><div>Finally, it feels feasible that like some other recent devices, this one might have a new revision where USB HID is not exposed on "interface 0" - there is a PR open at <a href="https://github.com/networkupstools/nut/pull/1044">https://github.com/networkupstools/nut/pull/1044</a> to handle other interface numbers, so far for a couple of known devices where that is needed.</div><div><br></div><div>Jim<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 18, 2021 at 2:42 PM Detlef via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-family:Verdana;font-size:12px"><div>
<p>I need help to find a way to start the usbhid-ups driver successfully, i always get a failed status after start of the driver</p>
<p>THX</p>
<p> </p>
<p>used environment:</p>
</div>
<div>
<ul>
<li>
<p>OS: 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux</p>
</li>
<li>
<p>NUT version 2.7.4</p>
</li>
<li>
<p>NUT installation method: apt-get install nut</p>
</li>
<li>
<p>UPS: PowerWalker VI 650 SB</p>
</li>
<li>
<p>problem description, with any relevant traces, like system log excerpts, and driver debug output</p>
</li>
<li>
<p>lsusb<br>
Bus 001 Device 003: ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS</p>
</li>
<li>
<div>cat /etc/nut/ups.conf<br>
# Set maxretry to 3 by default, this should mitigate race with slow devices:<br>
maxretry = 3<br>
[PowerWalker650]<br>
driver = usbhid-ups<br>
port = auto<br>
desc = "server"<br>
</div>
</li>
<li>
<div>upsdrvctl start<br>
Network UPS Tools - UPS driver controller 2.7.4<br>
Network UPS Tools - Generic HID driver 0.41 (2.7.4)<br>
USB communication driver 0.33<br>
No matching HID UPS found<br>
Driver failed to start (exit status=1)<br>
Network UPS Tools - Generic HID driver 0.41 (2.7.4)<br>
USB communication driver 0.33<br>
No matching HID UPS found<br>
Driver failed to start (exit status=1)<br>
Network UPS Tools - Generic HID driver 0.41 (2.7.4)<br>
USB communication driver 0.33<br>
No matching HID UPS found<br>
Driver failed to start (exit status=1)</div>
</li>
<li>
<p>You can obtain the latter using the following command, as root and after having stopped NUT:</p>
<div>
<div>
<pre><code>/path/to/driver -DD -a <upsname></code></pre>
<div><code>/lib/nut/usbhid-ups -DD -a PowerWalker650<br>
Network UPS Tools - Generic HID driver 0.41 (2.7.4)<br>
USB communication driver 0.33<br>
0.000000 debug level is '2'<br>
0.003634 upsdrv_initups...<br>
0.026290 Checking device (1D6B/0003) (002/001)<br>
0.043513 - VendorID: 1d6b<br>
0.044473 - ProductID: 0003<br>
0.044928 - Manufacturer: unknown<br>
0.045433 - Product: unknown<br>
0.045847 - Serial Number: unknown<br>
0.046276 - Bus: 002<br>
0.046843 - Device release number: 0419<br>
0.047250 Trying to match device<br>
0.047684 Device does not match - skipping<br>
0.050203 Checking device (0764/0601) (001/003)<br>
0.053610 - VendorID: 0764<br>
0.054105 - ProductID: 0601<br>
0.054620 - Manufacturer: 1<br>
0.055013 - Product: 650<br>
0.055434 - Serial Number:<br>
0.055845 - Bus: 001<br>
0.056418 - Device release number: 0200<br>
0.056845 Trying to match device<br>
0.057251 Device matches<br>
0.057334 failed to claim USB device: could not claim interface 0: No such file or directory<br>
0.057475 failed to detach kernel driver from USB device: could not detach kernel driver from interface 0: No route to host<br>
0.057554 failed to claim USB device: could not claim interface 0: No such file or directory<br>
0.057600 failed to detach kernel driver from USB device: could not detach kernel driver from interface 0: No route to host<br>
0.057768 failed to claim USB device: could not claim interface 0: No such file or directory<br>
0.057825 failed to detach kernel driver from USB device: could not detach kernel driver from interface 0: No route to host<br>
0.057870 failed to claim USB device: could not claim interface 0: No such file or directory<br>
0.058006 failed to detach kernel driver from USB device: could not detach kernel driver from interface 0: No route to host<br>
0.058050 Can't claim USB device [0764:0601]: could not detach kernel driver from interface 0: No route to host</code><br>
</div>
</div>
</div>
</li>
</ul>
</div></div></div>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>