NUT fails to start reporting insufficient permissions on libusb #322
Comments
|
23:04:57] INFO: Connected USB devices: |
|
I'm having the same problem |
|
I finally got it working. I needed to do a full power reset (shutting everything down & pull the power plug of HA, the UPS and the USB cable to the UPS & plugging everything back in). After everything has started again, the addon works without issues. |
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
github-actions
bot
added
the
stale
|
I have exactly the same issue. In my case, the full restart described above didn't help. Here are logs from my system: |
|
The same is now happening here. Before this I had no issues running this addon with my UPS. But then that UPS is now dead, so I went and bought a new UPS and now this addon doesn't work with the same above issue and logs. |
github-actions
bot
removed
the
stale
|
I am experiencing the same issue reported above, tried a full reboot that didn't help. |
|
Also here I am experiencing the same issue reported above, tried a full reboot that didn't help. |
|
Same problem here. Latest version, rechecked after full reboot too. Not sufficient permision for libusb1. |
|
I've managed to work around this error by specifying a vendorid and productid in the "config" directive using data from lsusb: Unplug UPS USB, run lsusb, plug UPS back in and find the new id: Add to config: Your mileage may vary, though. |
|
I also have the same problem and would be happy to see an solution. |
|
Is there any progress on this issue? This AddOn is basically useless since >2 months now. |
|
Same here. Addon will not start anymore due to: OS 11.1 - Core 2023.11.3 on a Raspberry pi 4 GB |
|
hey there, Could you please all report the output from the addon list_usb_devices config option. I'd like to be sure of my hypothesis :) As preliminary side notes:
|
|
Hi @aquette And that's the output of lsusb executed on HA: Note that my UPS still connects and survived all restarts after the power reset I did. |
|
@Xitee1 I have the exact same (I work at Eaton 😄) and config (2h ago) went like a charm. Just driver+port... It's true that I've not rebooted the RPI since deployed... Let me check |
|
I was trying to connect to my Serioux LD600LI UPS which shows up on lsusb as: I was getting the same error: My guess is that because this is a cheap UPS, it doesn't feature a proper USB HID implementation and so the
|
|
@voltlog thanks for your feedback, |
|
@aquette I'm just running the latest addon version in HomeAssistant, I don't know how I could run the PR that you proposed and I can't run "nut-scanner -U" inside the container shell that HomeAssistant provides. |
|
@voltlog the only possibility is to wait for the PR to be merged and addon updated. |
I also just have driver + port in my config: driver: usbhid-ups
port: auto |
|
thanks for the confirmation @Xitee1 :) to all, if possible, I would encourage you to test the new SmartNUT Add-on that I'm writing ;) I'm interested in feedback, especially with the kind of device like @voltlog |
|
@aquette I installed the SmartNUT add-on, everything worked first go with auto detect and default settings, UPS was detected, info started flowing into MQTT. However for the time being I have switched back to using the classic NUT addon because it is more convenient to use in automations with the sensor entities that it creates in HA. SmartNUT currently only pushes data to MQTT which is a little inconvenient for me because I have to manually create a config and define sensors based on the MQTT topics. Example output from SmartNUT below. |
|
Awesome @voltlog , you're my first tester. Thanks a lot! 😄 Also, SmartNUT is indeed not yet production ready, so stick with the current addon for now. |
|
For those of you struggling with the libusb permission error, have you tried replacing |
|
I was having this issue, "insufficient permissions on everything" error, running Home Assistant Yellow. A complete system reboot (not a restart of HASS) resolved it! |
github-actions
bot
added
the
stale
|
Well it does look like it is still a problem. This just started happening on mine too.... [16:26:14] INFO: Starting the UPS drivers... Going to try a full shutdown and reboot... |
github-actions
bot
removed
the
stale
|
Having the same issue... It works for some time after a full shutdown then the addon stops. |
|
Well, for me the problem continues, I think the possible error is in Proxmox, which for some reason that I don't know changes ports and the program does not have enough privileges to access the new USB configuration. |
|
The exact same error continues for me also, even when trying different drivers. I'm using the Home Assistant OS for the Raspberry Pi 5. |
|
Same Issue here; Legrand KEOS was running pretty well on a raspberry4, then I switched to an Intel-64-based mini-PC (both running the "HA-OS") and I do not get the stuff running again. Any hint would be very appreciated |
Thanks for this hint. I was running into the same error message. By changing the driver to |
|
@pspot2
I still get the same error message, so I tried again with your 0001:0000 but I always get the same "libusb1: Could not open any HID devices: insufficient permissions on everything" I find it peculiar how the plugin works for some people, while other get permission errors. |
|
Problem still persist with version v0.13.1 |
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
github-actions
bot
added
the
stale
|
still no function :-( |
|
Well, NUT has continued to fail with the same lack of privilege symptom, I have just finished installing the latest Proxmox update. Let's see how it behaves in a few days. |
|
I'm definitely interested in the result of your test! |
github-actions
bot
removed
the
stale
|
Hi, I run Nut on plain Debian 12.6 and I have a Powerwalker UPS that the server is plugged into. I get these permission issues in logwatch output frequently. After reading this issue, I started digging a bit. 'lsusb' did not show the UPS. Unplugging the usb cable and re-plugging it and then running 'lsusb' shows the device and Nut picks up that data is no longer stale. It leads me to think that this may be relating to some kind of power-management, where something is determined to be idle and put to sleep, and then it does not recover from that. To test the theory: For me, it was set to '2'. To disable it: I have now added the 'echo -1' part to my /etc/rc.local and I will monitor this thing with UPS device disappearing. If in a week the UPS still have not disconnected, I will consider USB AutoSuspend the culprit. /Sirius |
|
What are the USB vendor and product id? |
|
root@debian:~# lsusb So far so good, still connected and no errors in the logs. |
|
Well, it wasn't that. USB device for the UPS has disappeared, though it took four days for it to happen. I will look at other USB kernel stack settings to see if there is something else I can tweak to resolve this. |
This worked for me ! |
|
Well after seeing a suggestion regarding autosuspend, and the information in the url: https://community.home-assistant.io/t/how-to-disable-usb-autosuspend/392320/14 Rule for a Salicru UPSACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="06da", ATTR{idProduct}=="ffff", MODE="0660", GROUP="nut", TEST==”power/control”, ATTR={power/control}=”on” |
|
I have also applied the information to have the autosupend value = -1, but after several days the error returns, for the moment the only solution is reboot proxmox. |
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
github-actions
bot
added
the
stale
|
same issue: |
|
Apologies for the delay, I am changing the structure of my installation and I cannot dedicate time to this situation. I have changed the old mini PC for a Chuwi with 12GB of RAM and 500GB of disk and although NUT has gone down it has taken a few days to give the error. I hope to be able to continue with the issue in a few days. |
github-actions
bot
removed
the
stale
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
github-actions
bot
added
the
stale
and others
Problem/Motivation
Expected behavior
Actual behavior
Steps to reproduce
The text was updated successfully, but these errors were encountered: