<div dir="ltr"><div>Hello,</div><div><br></div><div>>
The three <i>Cannot load</i> errors...</div><div><br></div><div>These should not be a problem. The nut-scanner takes a truly dynamic approach to optionally loading dynamic libraries, so it does not have run-time (and packaging) dependencies on capabilities a particular NUT deployment does not need. In your case it did not complain about a missing libusb implementation, and did find a usb device, so far so good.</div><div><br></div><div>> My UPS is... usbhid-ups</div><div><br></div><div>I am not sure if you meant the older UPS (in config backup), or the one you replaced it with? Anyhow, <font face="monospace">vendorid = "0665" productid = "5161"</font> in NUT sources is only associated with nutdrv_qx (or the older blazer_usb) drivers for a dialect of Megatec Q<x> protocol family. So I would be very surprised if that device does actually work with USB HID protocol (also? instead?)</div><div><br></div><div>>
<font face="monospace">Network UPS Tools - UPS driver controller 2.8.1</font>
</div><div><br></div><div>This is somewhat aged now, the latest NUT release is 2.8.4. But sadly seems normal for a stable distro who set a base line and do not change it for half a decade. At least they do not offer 2.7.4 as the latest anymore ;)</div><div><br></div><div>>
When I execute
<b>upsdrvctl start</b> I get...</div><div><br></div><div>This older way of directly starting the drivers may collide with systemd units automatically generated to wrap each driver instance independently, fo more details please see <a href="https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE)">https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE)</a></div><div><br></div><div>TLDR: Either use `systemctl start/stop/restart nut-driver@upsname` (or the new `upsdrvsvcctl` tool), or temporarily stop/mask the NDE service and the nut-driver@ service instance, while you experiment with the driver configuration. In that case you may want to first run the driver program directly and list all the options you would later copy into `ups.conf`, e.g. </div><div><br></div><div>:; /lib/nut/usbhid-ups -s test -x port=....</div><div><br></div><div>and at this point you may want to bump the driver's debug verbosity to see more precisely what it complains about - see <a href="https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity">https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity</a></div><div><br></div><div>Hope this helps,</div><div>Jim Klimov</div><div><br></div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Oct 23, 2025 at 9:18 AM Alan Bonnici 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><img width="1" height="1"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">Hi,<div><br></div><div>I had a stable NUT environment for quite a while until I had to change UPS and reinstalled my Proxmox environment.</div><div><br></div><div>I had a backup of my /etc/nut directory and have only used it as reference. </div><div><br></div><div>My UPS is a Powerwalker VI 2200 IEC/UK and that corresponded to <b>usbhid-ups</b>.</div><div><br></div><div><b>nut-scanner -U</b> returns the following<br><font face="monospace">Cannot load SNMP library (libnetsnmp.so.40) : file not found. SNMP search disabled.<br>Cannot load XML library (libneon.so.27) : file not found. XML search disabled.<br>Cannot load IPMI library (libfreeipmi.so.17) : file not found. IPMI search disabled.<br>Scanning USB bus.<br>[nutdev1]<br> driver = "nutdrv_qx"<br> port = "auto"<br> vendorid = "0665"<br> productid = "5161"<br> product = "USB to Serial"<br> serial = "20100826"<br> vendor = "INNO TECH"<br> bus = "001"<br> device = "003"<br> busport = "003"<br> ###NOTMATCHED-YET###bcdDevice = "0002"</font></div><div><br></div><div>The three <i>Cannot load</i> errors are not present in my notes and I suspect they could be the root cause of successive errors.</div><div><br></div><div>My <b>/etc/nut/ups.conf</b> is as follows:</div><div><br></div><div># Wait 10 seconds for the driver to finish starting.<br>maxstartdelay = 10<br><br># Try 3 times to start the driver, before giving up.<br>maxretry = 3<br><br># Wait 5 seconds between attempts to start the driver.<br>retrydelay = 5<br><br># Poll the ups every 5 seconds<br>pollinterval = 5<br><br></div><div>[pve1]<br> # PowerWalker<br> driver = usbhid-ups<br> port = auto<br> desc = "Cypress Semiconductor USB to Serial"<br> vendorid = 0665<br> productid = 5161<br> # if the charge is less than 75 percent trigger a LB status<br> override.battery.charge.low = 75<br> # Some drivers reset battery.charge.low. lowbatt addresses this<br> lowbatt = 75<br> # if the remaining charge is less than 1200s (20 minutes) trigger a low battery status<br> override.battery.runtime.low = 1200<br> # Wait 10 minutes before attempting to restart the ups load after a power cut<br> ondelay = 600<br> # wait 5 minutes for ups to power off<br> override.ups.delay.shutdown = 300<br> # Could offdelay act as an override for override.ups.delay.shutdown?<br> offdelay = 300<br> serial = 20100826</div><div><br></div><div><br></div><div>When I execute
<b>upsdrvctl start</b> I get the following repeated 3 times</div><div><font face="monospace">Network UPS Tools - UPS driver controller 2.8.1<br>Network UPS Tools - Generic HID driver 0.52 (2.8.1)<br>USB communication driver (libusb 1.0) 0.46<br>libusb1: Could not open any HID devices: insufficient permissions on everything<br>No matching HID UPS found<br>upsnotify: notify about state 4 with libsystemd: was requested, but not running as a service unit now, will not spam more about it<br>upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it<br>Driver failed to start (exit status=1)</font></div><div><br></div><div>Thanks,</div><div>Alan</div></div>
</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>