-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libusb1: Could not open any HID devices: insufficient permissions on everything #398
Comments
I'm having the same problem |
Me too |
me too : libusb1: Could not open any HID devices: insufficient permissions on everything |
This issue is about the same problem that occurred last year with many people.: #322 |
Same issue here. |
I'm having the same problem |
I seem to get it to work after disconneting and connecting the USB cable and restart NUT plug in. Anyone knows the code for mount / unmount using Home Assistant? |
Same here:
|
Ok after an extended power outage where everything was shutdown including
the UPS, the NUT add-on is working.
Cheers
Steve
…On Wed, 8 Jan 2025, 22:59 JanPolnicky, ***@***.***> wrote:
Same here:
> Add-on: Network UPS Tools
> Manage battery backup (UPS) devices
> -----------------------------------------------------------
> Add-on version: 0.14.0
> You are running the latest version of this add-on.
> System: Home Assistant OS 14.1 (aarch64 / green)
> Home Assistant Core: 2025.1.1
> Home Assistant Supervisor: 2024.12.3
>
> 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.
—
Reply to this email directly, view it on GitHub
<#398 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXEVJZ3KVPH356O7QXLDTU32JU4M7AVCNFSM6AAAAABTNU4RZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZXHA4DCOJWHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
I can confirm it's still not working with 2025.2.1 (HAOS 14.2), at least not for me with an APC EPS700 UPS.. |
Did some more testing. If HAOS is started without the addon (not even installed), the USB port is available in /dev as hidraw0 and /dev/usb/hiddev0. 2025-02-10 21:03:01.269 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/nut/aarch64 with version 0.14.0 |
Agreed still not working with Tripp Lite UPS. Core 2025.2.3 |
Tried everything when this happened once in the past and still no joy! Been down since Feb release I believe. Getting the same permissions error as everyone else. Core 2025.2.4 deleted add-on and integration, full reboot of Host machine (not just HA restart) with no change. Removed usb into UPS and plugged back in. Eaton UPS that was running fine without issue prior. Thanks for the help! |
Same specs here with a CyberPower. |
Problem/Motivation
I'm having and USB Powercom BNT-xxxAP (product id: 0004) fully supported by usbhid-ups driver
i have tried everything to get it started. Find some answers that everything should work after shutdown, but no luck
UPS is detected by HAOS, but not able to be connected by plugin or driver due to permissions

my yml config:
libusb1 should be able connect to my USB connected UPS
Actual behavior
Logs from addon:
Steps to reproduce
Proposed changes
The text was updated successfully, but these errors were encountered: