Closed kloodhu closed 3 years ago
Hi, the same happened to me this morning, after the update to 0.4 - mine was also running fine for months. I already tried to physically reboot both UPS and the RPi and to jack out/in the cable connecting them (but doesn't help). My system:
Please roll back to a snap and post the addon startup log, listing the USB devices. In what was posted I don't see the device.
Rolled back with snapshot and all working again. The log says:
[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... [15:28:19] INFO: Setting mode to netserver... [15:28:20] INFO: Connected USB devices: Bus 001 Device 009: ID 1cf1:0030 Dresden Elektronik Bus 002 Device 003: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 007: ID 10c4:8a2a Silicon Labs Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 010: ID 0463:ffff MGE UPS Systems UPS Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [15:28:20] INFO: Generating /etc/nut/upsd.users... [15:28:20] INFO: Configuring user: klood [15:28:22] INFO: Configuring Device named eaton... [15:28:22] INFO: Starting the UPS drivers... Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) Using subdriver: MGE HID 1.39 USB communication driver 0.33 [15:28:27] WARNING: UPS Shutdown will shutdown the host [cont-init.d] nut.sh: exited 0. [cont-init.d] nutclient.sh: executing... [cont-init.d] nutclient.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [15:28:28] INFO: Starting the UPS information server... Network UPS Tools upsd 2.7.4 0.000000 fopen /var/run/nut/upsd.pid: No such file or directory 0.000512 listening on 0.0.0.0 port 3493 0.001659 Connected to UPS [eaton]: usbhid-ups-eaton 0.003501 /etc/nut/upsd.users is world readable [15:28:28] INFO: Starting the UPS monitor and shutdown controller... Network UPS Tools upsmon 2.7.4 0.000000 fopen /var/run/upsmon.pid: No such file or directory 0.000752 Using power down flag file /etc/killpower 0.001047 UPS: eaton@localhost (master) (power value 1) 0.001156 debug level is '1' 0.001172 Warning: running as one big root process by request (upsmon -p) 0.001683 Trying to connect to UPS [eaton@localhost] 0.020107 User upsmonmaster@127.0.0.1 logged into UPS [eaton] 0.002602 Logged into UPS eaton@localhost
If you see the difference the device is now listed, the main change is the container runs updated Alpine.
You may want to look at how the device is connected (i.e. is it direct or through a hub). Not having the hardware it will be very difficult for anyone to assist with this.
Same happened here with Eaton 3S UPS . After updating to 0.4.0 the add-on couldn't find my UPS anymore --> "No matching HID UPS found". Rolled back to version 0.3.1 and it's working again.
Same issue here: Eaton 3S UPS was working until 0.3.1 and it's not working with 0.4.0.
Hi, same problem for me, Eaton Ellipse ECO 1200VA, version 0.4.0 could't find UPS, version 0.3.1 works
[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... [08:57:22] INFO: Setting mode to netserver... [08:57:22] INFO: Generating /etc/nut/upsd.users... [08:57:22] INFO: Configuring user: Maste_nut [08:57:22] INFO: Password is NOT in the Have I Been Pwned database! Nice! [08:57:23] INFO: Configuring Device named myups... [08:57:23] INFO: Starting the UPS drivers... Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) Using subdriver: MGE HID 1.39 USB communication driver 0.33 [cont-init.d] nut.sh: exited 0. [cont-init.d] nutclient.sh: executing... [cont-init.d] nutclient.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [08:57:36] INFO: Starting the UPS information server... Network UPS Tools upsd 2.7.4 0.000000 fopen /var/run/nut/upsd.pid: No such file or directory 0.001975 listening on 0.0.0.0 port 3493 0.002938 Connected to UPS [myups]: usbhid-ups-myups 0.005105 /etc/nut/upsd.users is world readable [08:57:36] INFO: Starting the UPS monitor and shutdown controller... Network UPS Tools upsmon 2.7.4 0.000000 fopen /var/run/upsmon.pid: No such file or directory 0.000226 Using power down flag file /etc/killpower 0.000437 UPS: myups@localhost (master) (power value 1) 0.001694 debug level is '1' 0.001837 Warning: running as one big root process by request (upsmon -p) 0.002011 Trying to connect to UPS [myups@localhost] 0.020264 User upsmonmaster@127.0.0.1 logged into UPS [myups] 0.002429 Logged into UPS myups@localhost
I am running supervised in a supported and healty environment. I have 2 ups units that I monitor, 1 remote connect to an RPi and 1 directly connected to the server via USB. The directly connected unit is not reporting data. I have the following logging info and usbc output from a console in the container.
I have restored my nut integration from a snapshot that was working and loads version 0.3.1. This install had been working for nearly 2 years and through an upgrade to a supported and healty install.
usbc output from container... it is connected and gathering data: root@a0d7b954-nut:/etc/nut$ upsc dr_ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1860 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 24.0 battery.voltage.nominal: 24 device.mfr: CPS device.model: CP1500PFCLCD device.serial: 000000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.parameter.vendorid: 0764* driver.version: 2.7.4 driver.version.data: CyberPower HID 0.4 driver.version.internal: 0.41 input.transfer.high: 139 input.transfer.low: 88 input.voltage: 124.0 input.voltage.nominal: 120 output.voltage: 140.0 ups.beeper.status: disabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 24 ups.mfr: CPS ups.model: CP1500PFCLCD ups.productid: 0501 ups.realpower.nominal: 900 ups.serial: 000000000000 ups.status: OL ups.test.result: No test initiated ups.timer.shutdown: -60 ups.timer.start: -60 ups.vendorid: 0764 root@a0d7b954-nut:/etc/nut$
Log output from integration shows connected as well.
[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... [cont-init.d] 00-banner.sh: exited 0. [cont-init.d] 01-log-level.sh: executing... Log level is set to DEBUG [cont-init.d] 01-log-level.sh: exited 0. [cont-init.d] nut.sh: executing... [16:37:28] INFO: Setting mode to netserver... [16:37:28] INFO: Generating /etc/nut/upsd.users... [16:37:28] INFO: Configuring user: admin [16:37:28] DEBUG: Password SHA1: 9701D8B48A84B7C45FBBA4B993EFBB47184111B0 [16:37:28] DEBUG: Requested API resource: https://api.pwnedpasswords.com/range/9701D [16:37:28] DEBUG: API HTTP Response code: 200 [16:37:28] INFO: Password is NOT in the Have I Been Pwned database! Nice! [16:37:28] INFO: Configuring Device named DR_UPS... [16:37:29] INFO: Starting the UPS drivers... Network UPS Tools - UPS driver controller 2.7.4 0.000000 Starting UPS: DR_UPS Network UPS Tools - Generic HID driver 0.41 (2.7.4) Using subdriver: CyberPower HID 0.4 USB communication driver 0.33 [cont-init.d] nut.sh: exited 0. [cont-init.d] nutclient.sh: executing... [cont-init.d] nutclient.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [16:37:29] INFO: Starting the UPS information server... 0.000000 fopen /var/run/nut/upsd.pid: No such file or directory 0.000176 listening on 0.0.0.0 port 3493 0.000350 Connected to UPS [DR_UPS]: usbhid-ups-DR_UPS Network UPS Tools upsd 2.7.4 0.001504 /etc/nut/upsd.users is world readable [16:37:29] INFO: Starting the UPS monitor and shutdown controller... Network UPS Tools upsmon 2.7.4 0.000000 fopen /var/run/upsmon.pid: No such file or directory 0.000109 Using power down flag file /etc/killpower 0.000227 UPS: DR_UPS@localhost (master) (power value 1) 0.000271 debug level is '1' 0.000281 Warning: running as one big root process by request (upsmon -p) 0.000375 Trying to connect to UPS [DR_UPS@localhost] 0.007539 User upsmonmaster@127.0.0.1 logged into UPS [DR_UPS] 0.000700 Logged into UPS DR_UPS@localhost
Sensor configs: `
Add-on version: 0.3.1 There is an update available for this add-on! Latest add-on version: 0.4.0 Please consider upgrading as soon as possible. System: Debian GNU/Linux 10 (buster) (amd64 / qemux86-64) Home Assistant Core: 2021.1.5 Home Assistant Supervisor: 2021.01.7
@mattlward I don't see this being the same issue, as the previous issues logged were to do with the addon not being able to pick up specific Eaton UPS devices. Your issue seems to be relating to the integration.
Hi same problem here about the .4.0 release but... Downgrade the addon to reverse the issue with a snapshot but still the same error in log
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when starting or running this add-on.
[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.`
Home assistant Log (just the snapshot restore)
21-01-26 07:38:53 INFO (MainThread) [supervisor.snapshots] Found 2 snapshot files 21-01-26 07:39:23 INFO (MainThread) [supervisor.snapshots] Partial-Restore 08c87e1c start 21-01-26 07:39:25 INFO (MainThread) [supervisor.snapshots] Restoring 08c87e1c Docker Config 21-01-26 07:39:25 INFO (MainThread) [supervisor.snapshots] Restoring 08c87e1c folders 21-01-26 07:39:25 INFO (SyncWorker_7) [supervisor.snapshots.snapshot] Restore folder addons/local 21-01-26 07:39:25 INFO (SyncWorker_7) [supervisor.snapshots.snapshot] Restore folder addons/local done 21-01-26 07:39:25 INFO (MainThread) [supervisor.snapshots] Restoring 08c87e1c Repositories 21-01-26 07:39:25 INFO (MainThread) [supervisor.store] Loading add-ons from store: 79 all - 0 new - 0 remove 21-01-26 07:39:25 INFO (MainThread) [supervisor.snapshots] Restoring 08c87e1c old add-ons 21-01-26 07:39:25 INFO (MainThread) [supervisor.addons.addon] Restore config for addon a0d7b954_nut 21-01-26 07:39:25 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_a0d7b954_nut application 21-01-26 07:39:25 INFO (MainThread) [supervisor.addons.addon] Restoring data for addon a0d7b954_nut 21-01-26 07:39:27 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on hassioaddons/nut-armv7 with version 0.3.1 21-01-26 07:39:27 INFO (MainThread) [supervisor.snapshots] Partial-Restore 08c87e1c done 21-01-26 07:39:29 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_nut 21-01-26 07:39:36 INFO (SyncWorker_3) [supervisor.docker.interface] Restarting homeassistant/tinker-homeassistant 21-01-26 07:39:44 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready 21-01-26 07:40:08 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
@sinclairpaul where should I be asking? The data source is connected and providing data but the sensors do not see the data provided by nut.
Just a +1, however I just got this UPS today, so there’s no way to roll back :(
just for information, i connect my ups ton another device with usb and retrieved the data with apcupsd
In home assistant (Tinker Board) he's not listed with lsusb anymore, maybe the usb driver ?
Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 No matching HID UPS found
On my server (Linux debian 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) ) I validate the state of the ups, it's not the problem.
Bus 003 Device 004: ID 0463:ffff MGE UPS Systems UPS
Package: apcupsd Version: 3.14.14-2 Priority: optional Section: admin Maintainer: Thorsten Alteholz <debian@alteholz.de> Installed-Size: 904 kB Provides: ups-monitor Depends: libc6 (>= 2.27), libgcc1 (>= 1:4.2), libusb-0.1-4 (>= 2:0.1.12), libwrap0 (>= 7.6-4~), lsb-base Recommends: apcupsd-doc, s-nail | mailx Suggests: apcupsd-cgi, udev Conflicts: ups-monitor Homepage: http://www.apcupsd.org/ Tag: admin::power-management, hardware::power, hardware::power:ups, interface::daemon, interface::graphical, interface::text-mode, interface::x11, network::server, role::program, scope::utility, uitoolkit::gtk, uitoolkit::ncurses, use::monitor, x11::application Download-Size: 264 kB APT-Manual-Installed: yes APT-Sources: http://ftp.fr.debian.org/debian stable/main amd64 Packages
I also have a Eaton USB-HID UPS device which worked for months and failed after upgrading to 0.4.0. I figured it just needed a reload so I've just powered down all of my equipment and pulled the plug on the Eaton for while. Just restarted everything but the UPS is still not recognised in the USB hardware list.
We are hours away from shipping a completely new hardware management layer with the Supervisor. That should take care of all the issues listed here (does require an add-on update).
At this point, hold tight 😄
Thanks @frenck , will keep an eye out for updates :)
Would it be possible for someone to test the version that was just pushed to the edge repo https://github.com/hassio-addons/repository-edge/blob/master/README.md
You will need to ensure the supervisor that is running is the latest release.
Hi, on my system i've same problem using version from the edge repo many thanks!
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when starting or running this add-on.
[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.
Same problem with addon 0.5.0, Home Assistant OS 5.11 and supervisor-2021.02.5 😕
My addon stopped working with Eaton 3s UPS also. Used to work before 0.4.0 and 0.5.0 (0.3.1 ) I have three HA setups with Eaton 3S UPS. RPI3B+ continues working with new versions. Two Intel NUC (HA NUC image) stopped working.
Add-on version: 0.5.0
You are running the latest version of this add-on.
System: Home Assistant OS 5.11 (amd64 / intel-nuc)
Home Assistant Core: 2021.2.1
Home Assistant Supervisor: 2021.02.5
No matching HID UPS found
USB communication driver 0.33
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.
My addon stopped working with Eaton 3s UPS also. Used to work before 0.4.0 and 0.5.0 (0.3.1 ) I have three HA setups with Eaton 3S UPS. RPI3B+ continues working with new versions. Two Intel NUC (HA NUC image) stopped working.
I'm also running on NUC with the official image and as mentioned it stopped working for me with 0.4.0 as well.
ALso, I just downgraded the addon to v0.3.1, and it does not work anymore with the latest supervisor.
Can you please post the device info from the supervisor hardware tab?
Sure:
Same
Add-on version: 0.5.0
You are running the latest version of this add-on.
System: HassOS 4.20 (armv7 / raspberrypi4)
Home Assistant Core: 2021.2.2
Home Assistant Supervisor: 2021.02.6
USB communication driver 0.33
No matching HID UPS found
Driver failed to start (exit status=1)
- name: 1-1.4
sysfs: >-
/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4
dev_path: /dev/bus/usb/001/004
subsystem: usb
by_id: null
attributes:
BUSNUM: '001'
DEVNAME: /dev/bus/usb/001/004
DEVNUM: '004'
DEVPATH: >-
/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4
DEVTYPE: usb_device
DRIVER: usb
ID_BUS: usb
ID_MODEL: Eaton_3S
ID_MODEL_ENC: Eaton\x203S
ID_MODEL_ID: ffff
ID_REVISION: '0100'
ID_SERIAL: EATON_Eaton_3S_000000000
ID_SERIAL_SHORT: '000000000'
ID_USB_INTERFACES: ':030000:'
ID_VENDOR: EATON
ID_VENDOR_ENC: EATON
ID_VENDOR_ID: '0463'
MAJOR: '189'
MINOR: '3'
PRODUCT: 463/ffff/100
SUBSYSTEM: usb
TYPE: 0/0/0
USEC_INITIALIZED: '1131217354145'
My hardware info:
Add-on version: 0.5.0
You are running the latest version of this add-on.
System: Home Assistant OS 5.11 (amd64 / intel-nuc)
Home Assistant Core: 2021.2.2
Home Assistant Supervisor: 2021.02.6
sysfs: '/sys/devices/pci0000:00/0000:00:15.0/usb1/1-4'
dev_path: /dev/bus/usb/001/006
subsystem: usb
by_id: null
attributes:
BUSNUM: '001'
DEVNAME: /dev/bus/usb/001/006
DEVNUM: '006'
DEVPATH: '/devices/pci0000:00/0000:00:15.0/usb1/1-4'
DEVTYPE: usb_device
DRIVER: usb
ID_BUS: usb
ID_FOR_SEAT: usb-pci-0000_00_15_0-usb-0_4
ID_MODEL: Eaton_3S
ID_MODEL_ENC: Eaton\x203S
ID_MODEL_ID: ffff
ID_PATH: 'pci-0000:00:15.0-usb-0:4'
ID_PATH_TAG: pci-0000_00_15_0-usb-0_4
ID_REVISION: '0100'
ID_SERIAL: EATON_Eaton_3S_000000000
ID_SERIAL_SHORT: '000000000'
ID_USB_INTERFACES: ':030000:'
ID_VENDOR: EATON
ID_VENDOR_ENC: EATON
ID_VENDOR_ID: '0463'
MAJOR: '189'
MINOR: '5'
PRODUCT: 463/ffff/100
SUBSYSTEM: usb
TAGS: ':seat:'
TYPE: 0/0/0
USEC_INITIALIZED: '17339317'
In order to test a possible fix, we need some volunteers who are happy to run the beta channel of the Supervisor, this can be done by visiting the Supervisor, System page and Selecting Join Beta Channel.
You can opt out after testing.
hello I joined the beta channel and install supervisor supervisor-2021.02.7 but still same error
[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... [20:12:48] INFO: Setting mode to netserver... [20:12:48] INFO: Connected USB devices: Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] Bus 001 Device 007: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC) Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20:12:48] INFO: Generating /etc/nut/upsd.users... [20:12:49] INFO: Configuring user: admin [20:12:50] INFO: Password is NOT in the Have I Been Pwned database! Nice! [20:12:52] INFO: Configuring Device named myups... [20:12:52] INFO: Starting the UPS drivers... Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 No matching HID UPS found Driver failed to start (exit status=1)
I joined the beta channel and updated HA, but I'm getting the same error.
[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.5.0
You are running the latest version of this add-on.
System: Home Assistant OS 5.11 (armv7 / raspberrypi3)
Home Assistant Core: 2021.2.2
Home Assistant Supervisor: 2021.02.7
-----------------------------------------------------------
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...
[20:03:54] INFO: Setting mode to netserver...
[20:03:54] INFO: Connected USB devices:
Bus 001 Device 005: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC)
Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[20:03:55] INFO: Generating /etc/nut/upsd.users...
[20:03:55] INFO: Configuring user: nutuser
[20:03:56] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[20:03:58] INFO: Configuring Device named eaton...
[20:03:58] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
No matching HID UPS found
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.
I need the full ha hardware info
output
@pvizeli I've updated to the 2021.02.8 version, but it doesn't work either.
Can you please test the latest version just pushed to the edge repo (cd890fc)?
Same problem here with the same UPS seen with the hardware info. ID_MODEL: Eaton_3S ID_VENDOR_ID: '0463'
Raspberry Pi 3 Network UPS tools 5.0 core-2021.2.2 Home Assistant OS 5.11 supervisor-2021.02.6
...
[07:00:39] INFO: Connected USB devices:
Bus 001 Device 005: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC)
Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[07:00:40] INFO: Generating /etc/nut/upsd.users...
[07:00:40] INFO: Configuring user: monuser
[07:00:42] INFO: Configuring Device named ups...
[07:00:43] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
No matching HID UPS found
Driver failed to start (exit status=1)
...
@sinclairpaul here are the output messages from the cd890fc version.
@pvizeli I tried Supervisor: 2021.02.8. It did not help. I hate to say it but I do not know how to test: edge repo (cd890fc)?
Add-on version: 0.5.0 You are running the latest version of this add-on. System: Home Assistant OS 5.11 (amd64 / intel-nuc) Home Assistant Core: 2021.2.2 Home Assistant Supervisor: 2021.02.8
We have somethings to test:
ha su options --channel dev
ha su reload
ha su update
@pvizeli done, but same results as before
I'll add to this as I run both a NUC and Rpi3B+. The NUC add-on is working as expected. The RPi is not. Log from the RPi:
[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.3.1
You are running the latest version of this add-on.
System: Home Assistant OS 5.11 (aarch64 / raspberrypi3-64)
Home Assistant Core: 2021.2.2
Home Assistant Supervisor: 2021.02.6
-----------------------------------------------------------
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...
[08:57:35] INFO: Setting mode to netserver...
[08:57:36] INFO: Generating /etc/nut/upsd.users...
[08:57:38] INFO: Configuring user: garyk
[08:57:40] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[08:57:44] INFO: Configuring Device named CP1500...
[08:57:45] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
No matching HID UPS found
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.
My stats:
System Health
version: core-2021.2.2
installation_type: Home Assistant OS
dev: false
hassio: true
docker: true
virtualenv: false
python_version: 3.8.7
os_name: Linux
os_version: 5.4.83-v8
arch: aarch64
timezone: America/Denver
host_os: Home Assistant OS 5.11
update_channel: stable
supervisor_version: supervisor-2021.02.6
docker_version: 19.03.13
disk_total: 28.6 GB
disk_used: 4.2 GB
healthy: true
supported: true
board: rpi3-64
supervisor_api: ok
version_api: ok
installed_addons: Check Home Assistant configuration (3.6.0), Samba share (9.3.0), FTP (3.5.0), SSH & Web Terminal (7.8.0), Network UPS Tools (0.3.1), MariaDB (2.2.1), phpMyAdmin (0.1.4), Duck DNS (1.12.4), NGINX Home Assistant SSL proxy (3.0.1), Portainer (1.3.0)
dashboards: 1
resources: 9
views: 5
mode: storage
@garyak I believe this is a different issue, v0.3.1 is not the latest version of the addon.
@mrtmsgh Could you possibly try 164df22 on the edge repo?
Just did - still the same issue
@sinclairpaul sorry, I don't see any difference with previous versions
After updating to the most recent supervisor, ha-core, and Nut 0.5.0 I had this problem again. So I reverted to 0.3.1 (as I did previously). This time it does not fix the problem and I get exactly the same issue:
No matching HID UPS found
On another addon (frigate), I had a similar problem accessing the USB port and I fixed turning off "protection mode" until they updated the addon to solve the need for that. I hope this feedback can help.
I just pushed another edge release (cda5f79), if someone could validate.
good news! seems working
[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... [22:20:21] INFO: Setting mode to netserver... [22:20:21] INFO: Generating /etc/nut/upsd.users... [22:20:22] INFO: Configuring user: Maste_nut [22:20:22] INFO: Password is NOT in the Have I Been Pwned database! Nice! [22:20:22] INFO: Configuring Device named myups... [22:20:22] INFO: Starting the UPS drivers... Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) Using subdriver: MGE HID 1.39 USB communication driver 0.33 [cont-init.d] nut.sh: exited 0. [cont-init.d] nutclient.sh: executing... [cont-init.d] nutclient.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [22:20:35] INFO: Starting the UPS information server... Network UPS Tools upsd 2.7.4 0.000000 fopen /var/run/nut/upsd.pid: No such file or directory 0.000190 listening on 0.0.0.0 port 3493 0.000422 Connected to UPS [myups]: usbhid-ups-myups 0.001013 /etc/nut/upsd.users is world readable [22:20:35] INFO: Starting the UPS monitor and shutdown controller... Network UPS Tools upsmon 2.7.4 0.000000 fopen /var/run/upsmon.pid: No such file or directory 0.000205 Using power down flag file /etc/killpower 0.000390 UPS: myups@localhost (master) (power value 1) 0.000539 debug level is '1' 0.000659 Warning: running as one big root process by request (upsmon -p) 0.000847 Trying to connect to UPS [myups@localhost] 0.008876 User upsmonmaster@127.0.0.1 logged into UPS [myups] 0.001255 Logged into UPS myups@localhost`
working here too ! gj !!
[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: cda5f79
You are running the latest version of this add-on.
System: Home Assistant OS 5.11 (armv7 / raspberrypi3)
Home Assistant Core: 2021.2.2
Home Assistant Supervisor: 2021.02.8
-----------------------------------------------------------
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...
[22:35:41] INFO: Setting mode to netserver...
[22:35:42] INFO: Connected USB devices:
Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik
Bus 001 Device 007: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC)
Bus 001 Device 005: ID 0463:ffff MGE UPS Systems UPS
Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[22:35:42] INFO: Generating /etc/nut/upsd.users...
[22:35:43] INFO: Configuring user: admin
[22:35:44] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[22:35:46] INFO: Configuring Device named myups...
[22:35:48] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
Using subdriver: MGE HID 1.39
USB communication driver 0.33
[cont-init.d] nut.sh: exited 0.
[cont-init.d] nutclient.sh: executing...
[cont-init.d] nutclient.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[22:35:54] INFO: Starting the UPS information server...
Network UPS Tools upsd 2.7.4
0.000000 fopen /var/run/nut/upsd.pid: No such file or directory
0.001601 listening on 0.0.0.0 port 3493
0.002319 Connected to UPS [myups]: usbhid-ups-myups
0.015063 /etc/nut/upsd.users is world readable
[22:35:54] INFO: Starting the UPS monitor and shutdown controller...
Network UPS Tools upsmon 2.7.4
0.000000 fopen /var/run/upsmon.pid: No such file or directory
0.001981 Using power down flag file /etc/killpower
0.003682 UPS: myups@localhost (master) (power value 1)
0.003965 debug level is '1'
0.003994 Warning: running as one big root process by request (upsmon -p)
0.004821 Trying to connect to UPS [myups@localhost]
0.072579 User upsmonmaster@127.0.0.1 logged into UPS [myups]
0.006966 Logged into UPS myups@localhost
🥂 Finally......
Will look for a long term solution
Can confirm too! Thanks @sinclairpaul and everyone involved for your reactivity, that's nice to see. 😉
Problem/Motivation
What changed? What should i do?
Thank yőu!
Expected behavior
Actual behavior
[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: Raspbian GNU/Linux 10 (buster) (armv7 / raspberrypi4) Home Assistant Core: 2021.1.4 Home Assistant Supervisor: 2021.01.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... Log level is set to DEBUG [cont-init.d] 01-log-level.sh: exited 0. [cont-init.d] nut.sh: executing... [09:06:39] INFO: Setting mode to netserver... [09:06:39] INFO: Connected USB devices: Bus 001 Device 009: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] Bus 002 Device 003: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 007: ID 10c4:8a2a Silicon Labs HubZ Smart Home Controller Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub [09:06:39] INFO: Generating /etc/nut/upsd.users... [09:06:39] INFO: Configuring user: klood [09:06:41] INFO: Configuring Device named eaton... [09:06:41] INFO: Starting the UPS drivers... Network UPS Tools - UPS driver controller 2.7.4 0.000000 Starting UPS: eaton Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 No matching HID UPS found 0.024455 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...
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.
Steps to reproduce
Proposed changes