[Nut-upsuser] Eaton USB no connection?

Aaron Turner synfinatic at gmail.com
Mon May 4 00:48:16 BST 2026


Thanks Jim... That at least fills in one of the blanks- wasn't clear
to me if the driver was built into nutd or a separate process.  As you
guessed, OpnSense is based on FreeBSD.   I was able to track down the
ups driver and try to start it and it is erroring out:

$ upsdrvctl start ups
Network UPS Tools upsdrvctl - UPS driver controller 2.8.3 release
Network UPS Tools 2.8.3 release - Generic HID driver 0.62
USB communication driver (libusb 1.0) 0.50
libusb1: Could not open any HID devices: no USB buses (or devices) found
No matching HID UPS found
Driver failed to start (exit status=1)

Confused by this since I'm running the above command as root and
nut-scanner -U works fine?
--
Aaron Turner
https://synfin.net/
My father once told me that respect for the truth comes close to being
the basis for all morality.  "Something cannot emerge from nothing,"
he said.  This is profound thinking if you understand how unstable
"the truth" can be.  -- Frank Herbert, Dune

On Sun, May 3, 2026 at 4:16 PM Jim Klimov <jimklimov+nut at gmail.com> wrote:
>
> You did not show logs from the actual usbhid-ups driver, did you(r system) start one? Note that on Linux with systemd and NUT 2.8.x (and a nut-driver-enumerator service/daemon), it may be wrapped into a nut-service at upsname.service instance, similarly on Solaris/illumos with SMF. You seem to be running a variant of BSD thiugh, so maybe lack some init script for NUT drivers? Also note that typically such scripts call `upsdrvctl` and let it handle your population of the devices.
>
> Jim
>
> On Sun, May 3, 2026, 23:56 Aaron Turner via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote:
>>
>> Running opnsense nut plugin package and unable to connect to the UPS
>> (Eaton 5S1500LCD).
>>
>> -- ups.conf
>> [ups]
>> driver=usbhid-ups
>> port=auto
>>
>> -- Running upsd -D as root:
>>
>> $ upsd -D
>> Network UPS Tools upsd 2.8.3 release
>>    0.000000 fopen /var/db/nut/upsd.pid: No such file or directory
>>    0.000020 [D1] Just failed to send signal, no daemon was running
>>    0.000280 WARNING: /usr/local/etc/nut/upsd.conf is world readable
>> (hope you don't have passwords there)
>>    0.000482 [D1] debug level is '1'
>>    0.000545 listening on 127.0.0.1 port 3493
>>    0.000571 listening on ::1 port 3493
>>    0.000587 listening on 172.16.1.1 port 3493
>>    0.000597 [D1] server_load: tried to set up 3 listening sockets,
>> succeeded with 3
>>    0.000677 [D1] Succeeded to become_user(nut): now UID=316 GID=316
>>    0.000693 [D1] chdired into statepath /var/db/nut for driver sockets
>>    0.000703 WARNING: /var/db/nut is world readable (hope you don't
>> have passwords there)
>>    0.000773 Can't connect to UPS [ups] (/var/db/nut/usbhid-ups-ups):
>> No such file or directory
>>    0.000850 Found 1 UPS defined in ups.conf
>>    0.002465 WARNING: /usr/local/etc/nut/upsd.users is world readable
>> (hope you don't have passwords there)
>>    0.002485 Running as foreground process, not saving a PID file
>>    0.002490 upsnotify: failed to notify about state
>> NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not
>> spam more about it
>>    0.002496 [D1] On systems without service units, consider `export
>> NUT_QUIET_INIT_UPSNOTIFY=true`
>>    0.002501 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    0.002510 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>>    2.012544 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    2.012630 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>>    2.325366 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    2.325431 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>>    2.325496 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    2.325524 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>>    2.325579 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    2.325605 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>>    2.325633 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    2.325652 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>>    2.325674 User monuser at 127.0.0.1 logged into UPS [ups]
>>    2.325695 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    2.325713 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>>    2.325740 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    2.325758 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>>    2.325815 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    2.325839 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>>    2.325878 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    2.325901 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>>    2.325928 [D1] mainloop: UPS [ups] is not currently connected,
>> trying to reconnect
>>    2.325946 [D1] mainloop: UPS [ups] is still not connected (FD -1)
>> ^C   2.478568 mainloop: Interrupted system call
>>    2.478600 Signal 2: exiting
>>    2.478632 [D1] upsd_cleanup: starting the end-game
>>    2.478723 [D1] driver_free: forgetting UPS [ups] (FD -1)
>>    2.478771 [D1] upsd_cleanup: finished
>>
>> ---
>> $ ls -la /var/db/nut/
>> total 10
>> drwxrwxr-x   2 nut  nut    4 May  3 12:02 .
>> drwxr-xr-x  24 root wheel 33 May  3 13:45 ..
>> -rw-r--r--   1 nut  nut    6 May  3 11:02 upslog.pid
>> -rw-r--r--   1 nut  nut    6 May  3 12:02 upsmon.pid
>>
>> -- output of `dmesg` when disconnecting/reconnecting USB:
>> [15200] ugen1.2: <EATON Ellipse PRO> at usbus1 (disconnected)
>> [15205] ugen1.2: <EATON Ellipse PRO> at usbus1
>>
>> --
>> $ nut-scanner -U
>> Scanning USB bus.
>> [nutdev-usb1]
>> driver = "usbhid-ups"
>> port = "auto"
>> vendorid = "0463"
>> productid = "FFFF"
>> product = "Ellipse PRO"
>> serial = "P344T41PHY"
>> vendor = "EATON"
>> # bus = "001"
>> # device = "002"
>> # busport = "001"
>>
>> Am I supposed to manually create the unix socket FD or???   Not sure
>> if this is a nut or opnsense package issue?
>>
>> --
>> Aaron Turner
>> https://synfin.net/
>> My father once told me that respect for the truth comes close to being
>> the basis for all morality.  "Something cannot emerge from nothing,"
>> he said.  This is profound thinking if you understand how unstable
>> "the truth" can be.  -- Frank Herbert, Dune
>>
>> _______________________________________________
>> Nut-upsuser mailing list
>> Nut-upsuser at alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser



More information about the Nut-upsuser mailing list