(Bit by the goofy, only on this forum, reply-to add'r nonsense . . . sorry!)
Add an appropriate udev rule to give "nutty" access, or grant "nutty" the group
which has it already.
USB devices are *NOT* public by design.
- Tim
On February 28, 2024 12:13:33 PM EST, Jim Klimov via Nut-upsuser
<nut-upsuser@alioth-lists.debian.net> wrote:
>To me, this line is suspect:
>
>libusb1: Could not open any HID devices: insufficient permissions on everything
>
>
>it seems like USB permissions on the host do not allow the NUT run-time
>user (nutty?) to own the device filesystem node.
>Check the upower/udev/... settings relevant there.
>
>According to Git, this ID should be known in NUT v2.8.0 or newer (so the
>rest is about OS integration for this bit):
>
>$ git blame v2.8.0 scripts/upower/95-upower-hid.hwdb | grep usb:v0764p0601
>8b72ac9fc2 (Benjamin Berg 2022-03-28 17:19:41 +0200 103) usb:v0764p0601*
>
>Hope this helps,
>Jim Klimov
>
>
>
>On Wed, Feb 28, 2024 at 1:23 PM Giacomo Tognetti via Nut-upsuser <
>nut-upsuser@alioth-lists.debian.net> wrote:
>
>> Hi guys
>> I just struggling to configure my EPYC Neon UPS (it appears like Cyber
>> Power System, Inc. PR1500LCDRT2U UPS) using NUT on my Home Assistant server.
>> I installed official NUT from HACS add-ons and I placed a very easy config:
>>
>> users:
>> - username: nutty
>> password: xxxxxxxxxxxx
>> instcmds:
>> - all
>> actions: []
>> devices:
>> - name: neon
>> driver: usbhid-ups
>> port: auto
>> config: []
>> mode: netserver
>> shutdown_host: false
>> list_usb_devices: true
>>
>> But it doesn’t work, even if UPS is actually listed, as you can see from
>> the complete log.
>>
>> s6-rc: info: service s6rc-oneshot-runner: starting
>> s6-rc: info: service s6rc-oneshot-runner successfully started
>> s6-rc: info: service base-addon-banner: starting
>> ----------------------------------------------------------- Add-on: Network
>> UPS Tools Manage battery backup (UPS)
>> devices----------------------------------------------------------- Add-on
>> version: 0.13.0 You are running the latest version of this add-on. System:
>> Home Assistant OS 11.5 (amd64 / qemux86-64) Home Assistant Core: 2024.2.3
>> Home Assistant Supervisor:
>> 2024.02.0----------------------------------------------------------- Please,
>> share the above information when looking for help or support in, e.g.,
>> GitHub, forums or the Discord
>> chat.-----------------------------------------------------------
>> s6-rc: info: service base-addon-banner successfully started
>> s6-rc: info: service fix-attrs: starting
>> s6-rc: info: service base-addon-timezone: starting
>> s6-rc: info: service base-addon-log-level: starting
>> s6-rc: info: service fix-attrs successfully started
>> [15:30:13] INFO: Configuring timezone (Europe/Rome)...
>> s6-rc: info: service base-addon-log-level successfully started
>> s6-rc: info: service base-addon-timezone successfully started
>> s6-rc: info: service legacy-cont-init: starting
>> cont-init: info: running /etc/cont-init.d/nut.sh
>> [15:30:16] INFO: Setting mode to netserver...
>> [15:30:16] INFO: Connected USB devices:
>> Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 002 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
>> Bus 002 Device 002: ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS
>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
>> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> [15:30:17] INFO: Generating /etc/nut/upsd.users...
>> [15:30:17] INFO: Configuring user: nutty
>> [15:30:17] INFO: Password is NOT in the Have I Been Pwned database! Nice!
>> [15:30:18] INFO: Configuring Device named neon...
>> [15:30:18] INFO: Starting the UPS drivers...
>> Network UPS Tools - Generic HID driver 0.47 (2.8.0)
>> USB communication driver (libusb 1.0) 0.43
>> libusb1: Could not open any HID devices: insufficient permissions on
>> everything
>> No matching HID UPS found
>> Driver failed to start (exit status=1)
>> Network UPS Tools - UPS driver controller 2.8.0
>> cont-init: info: /etc/cont-init.d/nut.sh exited 1
>> cont-init: info: running /etc/cont-init.d/nutclient.sh
>> cont-init: info: /etc/cont-init.d/nutclient.sh exited 0
>> cont-init: warning: some scripts exited nonzero
>> s6-rc: warning: unable to start service legacy-cont-init: command exited 1
>> /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all
>> the services up! Check your logs (in /run/uncaught-logs/current if you have
>> in-container logging) for more information.
>> /run/s6/basedir/scripts/rc.init: fatal: stopping the container.
>> s6-rc: info: service fix-attrs: stopping
>> s6-rc: info: service base-addon-timezone: stopping
>> s6-rc: info: service base-addon-log-level: stopping
>> s6-rc: info: service fix-attrs successfully stopped
>> s6-rc: info: service base-addon-timezone successfully stopped
>> s6-rc: info: service base-addon-log-level successfully stopped
>> s6-rc: info: service base-addon-banner: stopping
>> s6-rc: info: service base-addon-banner successfully stopped
>> s6-rc: info: service s6rc-oneshot-runner: stopping
>> s6-rc: info: service s6rc-oneshot-runner successfully stopped
>>
>>
>>
>> I tried to add vendorid (764) and producid (601, in my case) but results
>> are the same.
>>
>> I really need your help, also because I’ve struggling around forums and
>> GitHub and I see many people in my situation with no answers at all.
>>
>> Please let me know.
>>
>> Giacomo
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Nut-upsuser mailing list
>> Nut-upsuser@alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
