You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NUT add-on stopped recognising my UPS that is connected via USB. Won't start.
I'm creating a separate issue as I'm not sure what caused this behaviour – I recently updated HA Core, Supervisor and HassOS and noticed that issue after a couple of days.
I tried different "paths" for device instead of 'auto', but it did not help at all. I am running out of ideas.
Expected behaviour
NUT starts up properly as it was before.
Actual behavior
Add-on log below. Please note that device is visible on hardware list in Supervisor -> System panel.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] nut: applying...
[fix-attrs.d] nut: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: Network UPS Tools
Manage battery backup (UPS) devices
-----------------------------------------------------------
Add-on version: 0.4.0
You are running the latest version of this add-on.
System: Home Assistant OS 5.11 (amd64 / qemux86-64)
Home Assistant Core: 2021.2.1
Home Assistant Supervisor: 2021.02.5
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nut.sh: executing...
[09:49:26] INFO: Setting mode to netserver...
[09:49:26] INFO: Generating /etc/nut/upsd.users...
[09:49:27] INFO: Configuring user: upsmon_local
[09:49:27] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[09:49:27] INFO: Configuring Device named UPS...
[09:49:27] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4)
No supported devices found. Please check your device availability with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these options
(man 8 blazer_usb).
Driver failed to start (exit status=1)
[cont-init.d] nut.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
-----------------------------------------------------------
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when
starting or running this add-on.
Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
Obviously, I also found this in Supervisor logs:
21-02-08 08:46:43 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'auto_uart' is deprecated, use 'uart'. Please report this to the maintainer of Network UPS Tools
21-02-08 08:46:43 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'devices' use a deprecated format, the new format uses a list of paths only. Please report this to the maintainer of Network UPS Tools
Problem/Motivation
NUT add-on stopped recognising my UPS that is connected via USB. Won't start.
I'm creating a separate issue as I'm not sure what caused this behaviour – I recently updated HA Core, Supervisor and HassOS and noticed that issue after a couple of days.
I tried different "paths" for device instead of 'auto', but it did not help at all. I am running out of ideas.
Expected behaviour
NUT starts up properly as it was before.
Actual behavior
Add-on log below. Please note that device is visible on hardware list in Supervisor -> System panel.
Obviously, I also found this in Supervisor logs:
Steps to reproduce
My add-on config:
Entries on hardware list:
Environment details
HA Core: 2021.2.1
Supervisor: 2021.02.5
HassOS: 5.11 (OVA)
Host: Intel NUC with Proxmox
USB: Passed-through directly to the VM
Thanks!
The text was updated successfully, but these errors were encountered: