hassio-addons / addon-nut Goto Github PK

View Code? Open in Web Editor NEW

155.0 6.0 31.0 851 KB

Network UPS Tools - Home Assistant Community Add-ons

Home Page: https://addons.community

License: MIT License

Dockerfile 14.28% Shell 55.39% Jinja 30.33%

nut network-ups-tools ups battery-backup home-assistant homeassistant addon addons

addon-nut's Introduction

Home Assistant Community Add-on: Network UPS Tools

A Network UPS Tools daemon to allow you to easily manage battery backup (UPS) devices connected to your Home Assistant machine.

About

The primary goal of the Network UPS Tools (NUT) project is to provide support for Power Devices, such as Uninterruptible Power Supplies, Power Distribution Units, Automatic Transfer Switch, Power Supply Units and Solar Controllers.

NUT provides many control and monitoring features, with a uniform control and management interface.

More than 140 different manufacturers, and several thousands models are compatible.

The Network UPS Tools (NUT) project is the combined effort of many individuals and companies.

Be sure to add the NUT integration after starting the add-on.

Note: The host a0d7b954-nut can be used to allow Home Assistant to communicate directly with the addon

For more information on how to configure the NUT integration in Home Assistant see the NUT integration documentation.

📚 Read the full add-on documentation

Support

Got questions?

You have several options to get them answered:

The Home Assistant Community Add-ons Discord chat server for add-on support and feature requests.
The Home Assistant Discord chat server for general Home Assistant discussions and questions.
The Home Assistant Community Forum.
Join the Reddit subreddit in /r/homeassistant

You could also open an issue here GitHub.

Contributing

This is an active open-source project. We are always open to people who want to use the code or contribute to it.

We have set up a separate document containing our contribution guidelines.

Thank you for being involved! 😍

Authors & contributors

The original setup of this repository is by Dale Higgs.

For a full list of all authors and contributors, check the contributor's page.

We have got some Home Assistant add-ons for you

Want some more functionality to your Home Assistant instance?

We have created multiple add-ons for Home Assistant. For a full list, check out our GitHub Repository.

License

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

addon-nut's People

Contributors

Stargazers

Watchers

addon-nut's Issues

Strange issue with missing sensors.

Problem/Motivation

I am getting a couple of odd errors in my logs...

2020-05-14 09:53:22 WARNING (MainThread) [homeassistant.components.nut.sensor] Sensor type: output.current does not appear in the NUT status output, cannot add
2020-05-14 09:53:22 WARNING (MainThread) [homeassistant.components.nut.sensor] Sensor type: ups.temperature does not appear in the NUT status output, cannot add

(Why the issue was filed)
Not asking for those values in my config and a grep of my complete config folder only finds the entries in the home-assistant.log file.

Expected behavior

(What you expected to happen)
Did not expect to see the entries.

Actual behavior

(What actually happened)

Steps to reproduce

Not sure how to reproduce, but here are my nut configs...

- platform: nut
  alias: drups
  name: "DR UPS"
  username: 
  password: 
  host: 40817795-nut
  resources:
    - ups.load
    - battery.charge
    - input.voltage
    - battery.runtime
    - ups.status
    - ups.status.display
    
- platform: nut
  alias: lrups
  name: "LR UPS"
  username: 
  password:
  host: 192.168.1.203
  port: 3494
  resources:
    - ups.load
    - battery.charge
    - input.voltage
    - battery.runtime
    - ups.status
    - ups.status.display

I am running the latest version of HA with Hassio on Ubuntu in a docker install. I have NUT version eafc871. 1 UPS is connected to the system via USB the other is a RPi acting as a remote NUT server connected to the UPS via USB.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Scan interval still not work

Problem/Motivation

Scan interval does not work.

Expected behavior

sensor:

platform: nut
scan_interval: 5
name: "CyberPower PR1500ELCD"
host: a0d7b954-nut #EDGE
username: user
password: !secret nut
resources:

this should update the readings every 5 seconds

NUT Discovered every times.

Why home assistant notify me that new device is discovered (NUT) if nut is configured and running fine.

Thanks.

Feature request: choose between stable (2.7.4 version) and development version (github master branch)

Problem/Motivation

New UPS models and features have been incorporated in recent pull requests to NUT's github master branch.
Network UPS Tools has a very slow release rate (the current 2.7.4 version was released in 2016).

Expected behavior

Giving the option to choose between the stable and the github version would maintain the current features but giving advanced users the chance to have new supported devices/sensors.

Actual behavior

Actually the source code is downloaded from http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz then uncompressed, compiled and installed.

Steps to reproduce

n/a

Proposed changes

Downloading the source from github ( git clone git://github.com/networkupstools/nut.git ) requires an additional step (running autogen.sh).
The remaining steps would be the same.

How is it possible to use this addon in Home Assistant?

I tried to add the repository:

https://github.com/hassio-addons/repository
like it is written in the readme, but Home Assitant don't let me add this!

What can be the problem? How can I use this addon in my Home Assitant installation?

GitHub
hassio-addons/repository
Community Hass.io Add-ons for Home Assistant. Contribute to hassio-addons/repository development by creating an account on GitHub.

Poll UPS [user@localhost] failed - Data stale

Problem/Motivation

After upgrading today to the latest version ( Add-on version: 4213c06), Eaton UPS USB started to get "Data stale" errors. Previous version was working perfectly.

Running hassio on Raspberry pi 4 with 4GBs of RAM (All details on the module log below).

Expected behavior

Work as usual

Actual behavior

Poll UPS [user@localhost] failed - Data stale

Steps to reproduce

Eaton 5E connected through USB.

Configuration:

{
  "users": [
    {
      "username": "admin",
      "password": "passwd_hidden",
      "instcmds": [
        "all"
      ],
      "actions": []
    }
  ],
  "devices": [
    {
      "name": "eaton5e",
      "driver": "usbhid-ups",
      "port": "auto",
      "config": [
        "pollfreq = 5"
      ]
    }
  ],
  "mode": "netserver",
  "shutdown_hassio": "false",
  "i_like_to_be_pwned": "true",
  "list_usb_devices": "false"
}

If you change list_usb_devices, it shows properly.
hassio log:

[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... 
-----------------------------------------------------------
 Hass.io Add-on: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 Add-on version: 4213c06
 You are running the latest version of this add-on.
 System: HassOS 3.7  (aarch64 / raspberrypi4-64)
 Home Assistant version: 0.103.5
 Supervisor version: 193
-----------------------------------------------------------
 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:24:44] INFO: Setting mode to netserver...
[22:24:44] INFO: Connected USB devices:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0463:ffff MGE UPS Systems UPS
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[22:24:44] INFO: Generating /etc/nut/upsd.users...
[22:24:44] INFO: Configuring user: admin
[22:24:46] INFO: Configuring Device named eaton5e...
[22:24:46] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 3.8.0-3259-g81f05ada5a
Network UPS Tools - Generic HID driver 0.41 (3.8.0-3259-g81f05ada5a)
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:24:52] INFO: Starting the UPS information server...
Network UPS Tools upsd 3.8.0-3259-g81f05ada5a
   0.000000	fopen /var/run/nut/upsd.pid: No such file or directory
   0.000696	listening on 0.0.0.0 port 3493
   0.001871	Connected to UPS [eaton5e]: usbhid-ups-eaton5e
[22:24:52] INFO: Starting the UPS monitor and shutdown controller...
Network UPS Tools upsmon 3.8.0-3259-g81f05ada5a
   0.000000	fopen /var/run/upsmon.pid: No such file or directory
   0.001396	Using power down flag file /etc/killpower
   0.002645	UPS: eaton5e@localhost (master) (power value 1)
   0.003780	debug level is '1'
   0.025697	Trying to connect to UPS [eaton5e@localhost]
   0.437283	User [email protected] logged into UPS [eaton5e]
   0.044911	Logged into UPS eaton5e@localhost
 212.656081	Data for UPS [eaton5e] is stale - check driver
 215.075504	Poll UPS [eaton5e@localhost] failed - Data stale
 220.076508	Poll UPS [eaton5e@localhost] failed - Data stale
 225.077193	Poll UPS [eaton5e@localhost] failed - Data stale
 230.077656	Poll UPS [eaton5e@localhost] failed - Data stale
 235.078529	Poll UPS [eaton5e@localhost] failed - Data stale
 240.079161	Poll UPS [eaton5e@localhost] failed - Data stale
 245.079796	Poll UPS [eaton5e@localhost] failed - Data stale
 250.080840	Poll UPS [eaton5e@localhost] failed - Data stale
 255.081822	Poll UPS [eaton5e@localhost] failed - Data stale
 260.082700	Poll UPS [eaton5e@localhost] failed - Data stale
 265.083785	Poll UPS [eaton5e@localhost] failed - Data stale
 270.084475	Poll UPS [eaton5e@localhost] failed - Data stale
 275.085014	Poll UPS [eaton5e@localhost] failed - Data stale
 280.085596	Poll UPS [eaton5e@localhost] failed - Data stale
 285.086211	Poll UPS [eaton5e@localhost] failed - Data stale

System log showing all OK with the module startup:

20-01-06 22:24:07 INFO (MainThread) [hassio.addons] Found 10 installed add-ons
20-01-06 22:24:07 INFO (SyncWorker_8) [hassio.docker.interface] Attach to hassioaddons/nut-aarch64 with version 4213c06
20-01-06 22:24:07 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-01-06 22:24:07 INFO (MainThread) [hassio.snapshots] Found 3 snapshot files
20-01-06 22:24:07 INFO (MainThread) [hassio.discovery] Load 0 messages
20-01-06 22:24:07 INFO (MainThread) [hassio.ingress] Load 12 ingress session
20-01-06 22:24:07 INFO (MainThread) [hassio.secrets] Load Home Assistant secrets: 19
20-01-06 22:24:07 INFO (MainThread) [__main__] Run Hass.io
20-01-06 22:24:07 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
20-01-06 22:24:07 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
20-01-06 22:24:07 INFO (MainThread) [hassio.addons] Phase 'system' start 1 add-ons
20-01-06 22:24:07 INFO (SyncWorker_11) [hassio.docker.interface] Clean addon_40817795_nut application
20-01-06 22:24:09 INFO (SyncWorker_11) [hassio.docker.addon] Start Docker add-on hassioaddons/nut-aarch64 with version 4213c06
20-01-06 22:24:42 INFO (MainThread) [hassio.api.security] /host/info access from 40817795_nut

upsserver is working but no data can be seen in hassio?

This is my configuration for addon-nut (I have an EATON 3S 550 attached via USB to the Pi):

 {
   "users": [
     {
       "username": "admin",
       "password": "12345",
       "instcmds": [
         "all"
       ],
       "actions": []
     }
   ],
   "devices": [
     {
       "name": "qnapups",
       "driver": "usbhid-ups",
       "port": "auto",
       "config": []
     }
   ],
   "mode": "netserver",
   "shutdown_hassio": "false",
   "i_like_to_be_pwned": "true",
   "list_usb_devices": "true"
 }

This is the log from addon-nut:

[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... 
-----------------------------------------------------------
 Hass.io Add-on: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 Add-on version: 4213c06
 You are running the latest version of this add-on.
 System: HassOS 3.7  (armv7 / raspberrypi4)
 Home Assistant version: 0.103.6
 Supervisor version: 193
-----------------------------------------------------------
 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... 
[16:48:55] INFO: Setting mode to netserver...
[16:48:55] INFO: Connected USB devices:
Bus 001 Device 003: ID 0463:ffff MGE UPS Systems UPS
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root 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
[16:48:55] INFO: Generating /etc/nut/upsd.users...
[16:48:56] INFO: Configuring user: admin
[16:48:57] INFO: Configuring Device named qnapups...
[16:48:57] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 3.8.0-3396-gcdc7c4b5b1
Network UPS Tools - Generic HID driver 0.41 (3.8.0-3396-gcdc7c4b5b1)
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.
[16:49:03] INFO: Starting the UPS information server...
Network UPS Tools upsd 3.8.0-3396-gcdc7c4b5b1
   0.000000	fopen /var/run/nut/upsd.pid: No such file or directory
   0.000606	listening on 0.0.0.0 port 3493
   0.001670	Connected to UPS [qnapups]: usbhid-ups-qnapups
[16:49:03] INFO: Starting the UPS monitor and shutdown controller...
Network UPS Tools upsmon 3.8.0-3396-gcdc7c4b5b1
   0.000000	fopen /var/run/upsmon.pid: No such file or directory
   0.001328	Using power down flag file /etc/killpower
   0.001969	UPS: qnapups@localhost (master) (power value 1)
   0.002466	debug level is '1'
   0.008893	Trying to connect to UPS [qnapups@localhost]
   0.026224	User [email protected] logged into UPS [qnapups]
   0.009874	Logged into UPS qnapups@localhost

This is my configuration in hassio inside the configuration.yaml:

 sensor:
   - platform: nut
     name: "qnapups"
     host: "192.168.178.108" (I used also localhost)
     username: admin
     password: 12345
     resources:
       - battery.charge
       - battery.runtime
       - ups.load
       - ups.status
       - ups.status.display

This is what I get in the hassio-log:

2020-01-08 16:47:57 ERROR (SyncWorker_18) [homeassistant.components.nut.sensor] Failure getting NUT ups alias, Socket error.
2020-01-08 16:47:57 ERROR (SyncWorker_18) [homeassistant.components.nut.sensor] NUT Sensor has no data, unable to set up
2020-01-08 16:47:58 WARNING (MainThread) [homeassistant.components.sensor] Platform nut not ready yet. Retrying in 30 seconds.
2020-01-08 16:48:29 ERROR (SyncWorker_14) [homeassistant.components.nut.sensor] Failure getting NUT ups alias, Socket error.
2020-01-08 16:48:29 ERROR (SyncWorker_14) [homeassistant.components.nut.sensor] NUT Sensor has no data, unable to set up
2020-01-08 16:48:29 WARNING (MainThread) [homeassistant.components.sensor] Platform nut not ready yet. Retrying in 60 seconds.
2020-01-08 16:49:30 ERROR (SyncWorker_19) [homeassistant.components.nut.sensor] Failure getting NUT ups alias, Socket error.
2020-01-08 16:49:30 ERROR (SyncWorker_19) [homeassistant.components.nut.sensor] NUT Sensor has no data, unable to set up
2020-01-08 16:49:30 WARNING (MainThread) [homeassistant.components.sensor] Platform nut not ready yet. Retrying in 90 seconds.
2020-01-08 16:51:01 ERROR (SyncWorker_3) [homeassistant.components.nut.sensor] Failure getting NUT ups alias, Socket error.
2020-01-08 16:51:01 ERROR (SyncWorker_3) [homeassistant.components.nut.sensor] NUT Sensor has no data, unable to set up
2020-01-08 16:51:01 WARNING (MainThread) [homeassistant.components.sensor] Platform nut not ready yet. Retrying in 120 seconds.

Is there anything I did wrong? Is this normal?

Cyberpower 1500 reconnects USB on status change and Hassio gets Data stale

Hello @etatus

i have the exact same problem, when the UPS go in battery mode, the USB disconnected on my RPI4 and the info are unavailable to Hassio...

Have you find a solution for RPI4?

(dont want to go back to RPI3 to solve this lol).

Thanks

Permissions errors when using Serial

Problem/Motivation

same as here - #33

current config:
devices:

name: myups
driver: apcsmart
port: /dev/ttyUSB0
config: []
mode: netserver
shutdown_host: 'false'

(Devices are seen when listed)

Expected behavior

Connect to ups. (Tested in raspbian with nut and works)

Actual behavior

[17:52:10] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 3.8.0-3396-gcdc7c4b5b1
Network UPS Tools - APC Smart protocol driver 3.1 (3.8.0-3396-gcdc7c4b5b1)
Fatal error: unusable configuration
APC command table version 3.1

Unable to open /dev/ttyUSB0: Permission denied

Current user id: nut (100)
Serial port owner: root (0)
Serial port group: dialout (20)
Mode of port: 0660

Steps to reproduce

Setup Hass.io addon Nut
Setup APC Smart ups (which uses serial)
Connect Server to UPS using: USB to Serial (if no serial available), 940-0024C Cable.
Run Nut server in Addon.
Get permissions errors.

Proposed changes

home-assistant/supervisor#1614

"It's docker, you should run the software as root not as nut."

Is there a way to run it as root?

USB APC UPS NUT won't start

Problem/Motivation

I was trying to migrate nut addon from initial versions where there were no UI settings, and It was doing great. However now after searching few other issues here, I found config which I think should work, I can see my USB on host, but when I added list_usb_devices: true , I've got error unable to initialize libusb: -99 .. whole logs bellow.

Expected behavior

Start the addon and show connected USB devices

Actual behavior

Addon stops with error code. unable to initialize libusb: -99

Steps to reproduce

[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: c022f38
 You are running the latest version of this add-on.
 System: Debian GNU/Linux bullseye/sid  (amd64 / qemux86-64)
 Home Assistant Core: 0.114.4
 Home Assistant Supervisor: 235
-----------------------------------------------------------
 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... 
[18:39:03] INFO: Setting mode to netserver...
[18:39:03] INFO: Connected USB devices:
unable to initialize libusb: -99
[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.

users:
  - username: usr
    password: pass
    instcmds:
      - all
    actions: []
devices:
  - name: apcups
    driver: usbhid-ups
    port: auto
    config:
      - vendorid = 051d*
mode: netserver
shutdown_host: 'false'
list_usb_devices: true

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

I also tried edge version as well as community versions.

No matching HID UPS found

Problem/Motivation

when I'm trying to start add-on I've got an error(in log):

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.

the same issue: #21

Expected behavior

I'm expecting it will run

Actual behavior

add-on stops

Steps to reproduce

Install NUT add-on, configure it and run.
my config:

`users:

username: nut
password: mypassword
instcmds:
- all
  actions: []
  devices:
name: apc_ups
driver: usbhid-ups
port: auto
config:
- ignorelb
  mode: netserver
  shutdown_host: 'false'
  vendorid: 051d`

Proposed changes

possible cause: add-on worked perfectly till I've reconfigure UPS to remove Green Power mode because it cut power after 15 minutes. Now it power my HA RPI 4 for more then 2 hours (tested) but can't be monitored...
any ideas?

Have I been Pwned Bypass

Problem/Motivation

Required to support "weak" secrets for systems that cannot be changed (synology) example: https://roll.urown.net/NAS/nas-ups.html

Expected behavior

Be able to set a variable to bypass the HIBP Database check as required

Actual behavior

Service was prevented from starting for using the phrase "secret" as the password

Steps to reproduce

Set Secret as password

Proposed changes

Support ability to bypass HIBP check where required

Won't work with Cyber Power UPSes

Problem/Motivation

Cyber Power UPSes have an annoying quirk where if a connection is not established for 20 seconds, it resets the USB interface which causes its /dev/bus/usb path to change. Because of that, the addon is unable to connect to them. The /dev/bus/usb path gets mapped in as a device, but Docker doesn't support hot plugging USB devices, so even though the device is visible via lsusb it is not accessible with the usbhid-ups driver.

Expected behavior

I expected the UPS to work

Actual behavior

The UPS doesn't work because the USB path is frequently reset until a successful connection is made.

Steps to reproduce

Have a Cyber Power UPS
Try using this addon
See that startup will never properly complete

Proposed changes

It's possible this can be fixed by setting full_access / privileged to True and mapping in /dev/bus/usb as a volume in addition to the existing device. I've tried adding udev rules on the host to map the UPS to /dev/ups0 to give Docker a stable device path but it seems as soon as the UPS resets that symlink is lost until it reconnects and Docker will never re-attach properly

NUT 0.1.2 - under HassOS 3.13 Error adding custom device "/dev/bus/usb": no such file or directory

Problem/Motivation

Trying to monitor APC snmp device, which doesn't use USB.

20-04-27 17:49:23 INFO (SyncWorker_4) [supervisor.docker.interface] Clean addon_a0d7b954_nut application
20-04-27 17:49:23 ERROR (SyncWorker_4) [supervisor.docker] Can't start addon_a0d7b954_nut: 500 Server Error: Internal Server Error ("error gathering device information while adding custom device "/dev/bus/usb": no such file or directory")
20-04-27 17:49:23 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<Addon.start() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:472> exception=AddonsError()>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/addons/addon.py", line 493, in start
    raise AddonsError() from None
supervisor.exceptions.AddonsError

Expected behavior

Have a option to turn off searching for USB devices?

Actual behavior

Error above

Steps to reproduce

HA -> Add Network UPS Tools plugin from store, config it to:

users:
  - username: user
    password: 'pass'
    instcmds:
      - all
    actions: []
devices:
  - name: myups
    driver: dummy-ups
    port: dummy.dev
    config: []
  - name: apcups
    driver: snmp-ups
    port: 192.168.1.242
    config:
      - snmp_version = v1
      - community = public
      - pollfreq = 30
      - desc = APC UPS
mode: netclient
shutdown_host: 'false'
log_level: trace
fake_usb_devices: true

Proposed changes

Perhaps a skip_usb_devices: true

Cannot Connect to NUT Server

Forgive me as I am new to Home Assistant and to this add-on. I installed the NUT add-on and added the necessary info the configuration.yaml. I go to Configuration>Integrations to add the Network UPS Tools (NUT) and not matter what I do, I get a "Failed to connect, please try again" error. I should add that I am running this on Hassio on a Raspberry Pi 4.

Here is my configuration.yaml entry:
sensor:

platform: nut
name: "Basement UPS"
host: localhost
username: lcbingman
password: Hellfire50!
resources:
- ups.status

Here is what is in the NUT config section:
users:

username: username
password: password
instcmds:
- all
  actions:
- set
- fsd
  devices:
name: mainups
driver: usbhid-ups
port: auto
config: []
mode: netserver
shutdown_host: 'false'
list_usb_devices: 'true'

And here is the log file for the NUT:
[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.1.2
You are running the latest version of this add-on.
System: HassOS 3.12 (armv7 / raspberrypi4)
Home Assistant Core: 0.108.3
Home Assistant Supervisor: 217

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...
[11:44:15] INFO: Setting mode to netserver...
[11:44:15] INFO: Connected USB devices:
Bus 001 Device 003: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[11:44:15] INFO: Generating /etc/nut/upsd.users...
[11:44:16] INFO: Configuring user: username
[11:44:16] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[11:44:18] INFO: Configuring Device named mainups...
[11:44:18] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 3.8.0-3396-gcdc7c4b5b1
Network UPS Tools - Generic HID driver 0.41 (3.8.0-3396-gcdc7c4b5b1)
Using subdriver: APC HID 0.96
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.
[11:44:18] INFO: Starting the UPS information server...
Network UPS Tools upsd 3.8.0-3396-gcdc7c4b5b1
0.000000 fopen /var/run/nut/upsd.pid: No such file or directory
0.000399 listening on 0.0.0.0 port 3493
0.000957 Connected to UPS [mainups]: usbhid-ups-mainups
[11:44:18] INFO: Starting the UPS monitor and shutdown controller...
Network UPS Tools upsmon 3.8.0-3396-gcdc7c4b5b1
0.000000 fopen /var/run/upsmon.pid: No such file or directory
0.000464 Using power down flag file /etc/killpower
0.000832 UPS: mainups@localhost (master) (power value 1)
0.000937 debug level is '1'
0.009951 Trying to connect to UPS [mainups@localhost]
0.028922 User [email protected] logged into UPS [mainups]
0.011223 Logged into UPS mainups@localhost

Cannot access community forum

Problem/Motivation

On the support section of the README.md, it is mentioned the Home Assistant Community Forum of this add-on.

However, this link it is not accessible, this message is shown:

Sorry, you don't have access to that topic!

Expected behavior

I expected to have access to the topic, as in many other add-on.

Actual behavior

The topic is not accesible.

Steps to reproduce

Go to the link https://community.home-assistant.io/t/community-hass-io-add-on-network-ups-tools/68516

Proposed changes

Give access to this topic.

Home Assistant Community
Open source home automation that puts local control and privacy first.

Lost connection after recent update

After applying the update 5 days ago I haven't been able to get connected to my UPS.
I thought maybe it was an issue with the usb being disconnect from my vm machine but that is not the case.

Log
[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... 
-----------------------------------------------------------
 Hass.io Add-on: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 Add-on version: 79fe9c6
 You are running the latest version of this add-on.
 System: HassOS 2.12  (amd64 / qemux86-64)
 Home Assistant version: 0.103.0
 Supervisor version: 192
-----------------------------------------------------------
 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... 
[19:50:21] INFO: Setting mode to netserver...
[19:50:21] INFO: Generating /etc/nut/upsd.users...
[19:50:21] INFO: Configuring user: nut
[19:50:21] DEBUG: Password SHA1: 24118455D6BA570A87BEC4A9EBDADBE70D8ADBB3
[19:50:21] DEBUG: Requested API resource: https://api.pwnedpasswords.com/range/24118
[19:50:21] DEBUG: API HTTP Response code: 200
[19:50:21] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[19:50:22] INFO: Configuring Device named myups...
[19:50:22] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 3.8.0-3220-g866b921892
   0.000000	Starting UPS: myups
Network UPS Tools - Generic HID driver 0.41 (3.8.0-3220-g866b921892)
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.
[19:50:23] INFO: Starting the UPS information server...
Network UPS Tools upsd 3.8.0-3220-g866b921892
   0.000000	fopen /var/run/nut/upsd.pid: No such file or directory
   0.000297	listening on 0.0.0.0 port 3493
   0.000747	Connected to UPS [myups]: usbhid-ups-myups
[19:50:23] INFO: Starting the UPS Monitor...
Network UPS Tools upsmon 3.8.0-3220-g866b921892
   0.000000	fopen /var/run/upsmon.pid: No such file or directory
   0.000252	Using power down flag file /etc/killpower
   0.000439	UPS: myups@localhost (master) (power value 1)
   0.000527	debug level is '1'
   0.005219	Trying to connect to UPS [myups@localhost]
   0.015902	User [email protected] logged into UPS [myups]
   0.006455	Logged into UPS myups@localhost

2019-12-11 19:55:22 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.nut
2019-12-11 19:55:22 ERROR (SyncWorker_2) [homeassistant.components.nut.sensor] Failure getting NUT ups alias, Socket error.
2019-12-11 19:55:22 ERROR (SyncWorker_2) [homeassistant.components.nut.sensor] NUT Sensor has no data, unable to set up
2019-12-11 19:55:22 WARNING (MainThread) [homeassistant.components.sensor] Platform nut not ready yet. Retrying in 90 seconds.

v0.3.0 - Driver failed to start

Problem/Motivation

Upgraded to v0.3.0 of nut addon and driver fails to start

Expected behavior

Backward compatibility with prior version of plugin

Actual behavior

Startup failed with the following log output:

-----------------------------------------------------------
 Add-on: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 Add-on version: 0.3.0
 You are running the latest version of this add-on.
 System: HassOS 4.12  (amd64 / qemux86-64)
 Home Assistant Core: 0.114.4
 Home Assistant Supervisor: 235
-----------------------------------------------------------
 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... 
[22:29:23] INFO: Setting mode to netserver...
[22:29:23] INFO: Generating /etc/nut/upsd.users...
[22:29:23] INFO: Configuring user: nutuser
[22:29:24] DEBUG: Password SHA1: xxxxxxx
[22:29:24] DEBUG: Requested API resource: https://api.pwnedpasswords.com/range/52817
[22:29:24] DEBUG: API HTTP Response code: 200
[22:29:24] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[22:29:24] INFO: Configuring Device named apcups...
[22:29:24] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 2.7.4
   0.000000	Starting UPS: apcups
Error loading shared library libnetsnmp.so.35: No such file or directory (needed by /usr/lib/nut/snmp-ups)
Error relocating /usr/lib/nut/snmp-ups: snmp_open: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_api_errstring: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snprint_objid: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_clone_pdu: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_add_var: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_sess_init: symbol not found
Error relocating /usr/lib/nut/snmp-ups: netsnmp_oid_equals: symbol not found
Error relocating /usr/lib/nut/snmp-ups: init_snmp: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_parse_oid: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_free_pdu: symbol not found
Error relocating /usr/lib/nut/snmp-ups: generate_Ku: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_error: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_close: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_errstring: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_out_toggle_options: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_pdu_create: symbol not found
Error relocating /usr/lib/nut/snmp-ups: read_objid: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_sess_error: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snprint_hexstring: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_synch_response: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_add_null_var: symbol not found
Error relocating /usr/lib/nut/snmp-ups: snmp_errno: symbol not found
Error relocating /usr/lib/nut/snmp-ups: usmAES128PrivProtocol: symbol not found
Error relocating /usr/lib/nut/snmp-ups: usmDESPrivProtocol: symbol not found
Error relocating /usr/lib/nut/snmp-ups: usmHMACMD5AuthProtocol: symbol not found
Error relocating /usr/lib/nut/snmp-ups: usmHMACSHA1AuthProtocol: symbol not found
   0.004556	Driver failed to start (exit status=127)
[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.

Steps to reproduce

Using the following configuration:

users:
  - username: '!secret ups_tools_username'
    password: '!secret ups_tools_password'
    instcmds:
      - all
    actions: []
devices:
  - name: apcups
    driver: snmp-ups
    port: apc01.mydomain.com
    config:
      - snmp_version = v3
      - secLevel = authPriv
      - secName = snmpprofile1
      - authPassword = xxxxx
      - authProtocol = MD5
      - privPassword = xxxxx
      - privProtocol = DES
      - desc = APC UPS
mode: netserver
shutdown_host: 'false'
log_level: debug

Data stale

Using richcomm_usb driver with my TRUST OXXTROON UPS result in continuosly data stale problem:

Poll UPS [myups@localhost] failed - Data stale
82.534048 UPS [myups] data is no longer stale

I can read that a possible solution is to update upsd.conf with a new MAXAGE value (ex. 25).

[https://www.ixsystems.com/community/threads/data-for-ups-is-stale.20898/](Data for UPS is stale)

Poll UPS [myups@localhost] failed - Data stale

Problem/Motivation

NUT server Addon on supported Debian / Docker setup, USB to Belkin UPS

about 10 min the error is - Poll UPS [myups@localhost] failed - Data stale

rebooting the HA Server the addon comes back online and works fine, but then stops.

have seen some post about adding maxage: 25 to the upsd.conf , but don't have access to that conf as its an addon.

any advice or help.
thanks

Powerwalker VI 650 SHL LCD Not found

Problem/Motivation

Powerwalker VI 650 SHL LCD Plugged in to RPI3 Hass io (32.bit)

devices:
  - name: powerwalker
    driver: usbhid-ups
    port: auto
    config:
      - vendorid = 06DA

Expected behavior

finds UPS

Actual behavior

[14:18:06] INFO: Setting mode to netserver...
[14:18:07] INFO: Connected USB devices:
Bus 001 Device 005: ID 1781:0c30 Multiple Vendors Telldus TellStick
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 007: ID 1cf1:0030 Dresden Elektronik
Bus 001 Device 108: ID 06da:ffff Phoenixtec Power Co., Ltd
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[14:18:07] INFO: Generating /etc/nut/upsd.users...
[14:18:08] INFO: Configuring user: nut
[14:18:09] DEBUG: Password SHA1:
[14:18:09] DEBUG: Requested API resource: https://api.pwnedpasswords.com/range/1CC9E
[14:18:09] DEBUG: API HTTP Response code: 200
[14:18:09] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[14:18:12] INFO: Configuring Device named powerwalker...
[14:18:12] INFO: Faking USB devices for Cyber Power fix...
mknod: /dev/bus/usb/001/001: File exists
mknod: /dev/bus/usb/001/002: File exists
mknod: /dev/bus/usb/001/003: File exists
mknod: /dev/bus/usb/001/005: File exists
mknod: /dev/bus/usb/001/007: File exists
[14:18:15] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 2.7.4
0.000000 Starting UPS: powerwalker
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
No matching HID UPS found
USB communication driver 0.33
0.043471 Driver failed to start (exit status=1)
[cont-init.d] nut.sh: exited 1.

Other Info

nut-scanner on ubuntu

[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "06DA"
productid = "FFFF"
bus = "003"

NUT addon not able to communicate with IMD 3000A UPS

Problem/Motivation

NUT seems unable to communicate with Powercom IMD 3000A.

Expected behavior

Powercom IMD3000A works with the usbhid-ups driver

Actual behavior

I tested the UPS connected to a different Raspberry PI, running Hassbian. I then configured a nut server (NOT in a container)
NUT connected successfully to the UPS with the usbhid-ups driver
The ups.conf file:
[myups] driver = usbhid-ups port = auto

I then used the above variables in the NUT addon config in the following format:

users:
  - username: xxx
    password: xxx
    instcmds:
      - all
    actions: []
devices:
  - name: myups
    driver: usbhid-ups
    port: auto
    config:
      - vendorid = 0d9f`

I would have expected the config to work, as I confirmed that the ups.conf file within the container was correct. Via docker exec -it /bin/bash I checked the conf was populated correctly.
I do however receive the following error:

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: HassOS 4.12  (armv7 / raspberrypi3)
Home Assistant Core: 0.114.4
Home Assistant Supervisor: 242
-----------------------------------------------------------
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... 
[21:25:21] INFO: Setting mode to netserver...
[21:25:22] INFO: Generating /etc/nut/upsd.users...
[21:25:23] INFO: Configuring user: upsadmin
[21:25:24] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[21:25:26] INFO: Configuring Device named myups...
[21:25:27] 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)
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.

Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done

Steps to reproduce

I think this can only be reproduced on certain hardware

Proposed changes

I have done to following troubleshooting:

root@a0d7b954-nut:/$ lsusb
Bus 001 Device 096: ID 0d9f:0004 Powercom Co., Ltd
Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[ 6385.527594] hid-generic 0003:0D9F:0004.03C0: hiddev96,hidraw0: USB HID v1.00 Device [POWERCOM Co.,LTD HID UPS Battery] on usb-3f980000.usb-1.2/input0
[ 6389.187063] usb 1-1.2: USB disconnect, device number 103
[ 6391.787003] usb 1-1.2: new low-speed USB device number 104 using dwc_otg
[ 6391.953416] usb 1-1.2: New USB device found, idVendor=0d9f, idProduct=0004, bcdDevice= 0.02
[ 6391.960669] usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 6391.964350] usb 1-1.2: Product: HID UPS Battery
[ 6391.967975] usb 1-1.2: Manufacturer: POWERCOM Co.,LTD
[ 6391.971542] usb 1-1.2: SerialNumber: 004-0D9F-000

So the container can definately detect the UPS.
I did however find that the specific vendorid and productid was not in 62-nut-usbups.rules

cat /lib/udev/rules.d/62-nut-usbups.rules
# PowerCOM
#  PowerCOM Vanguard and BNT-xxxAP  - usbhid-ups
ATTR{idVendor}=="0d9f", ATTR{idProduct}=="0001", MODE="664", GROUP="root"
#  PowerCOM Vanguard and BNT-xxxAP  - usbhid-ups
ATTR{idVendor}=="0d9f", ATTR{idProduct}=="0004", MODE="664", GROUP="root"
#  PowerCOM IMP - IMPERIAL Series  - usbhid-ups
ATTR{idVendor}=="0d9f", ATTR{idProduct}=="00a2", MODE="664", GROUP="root"
#  PowerCOM SKP - Smart KING Pro (all Smart series)  - usbhid-ups
ATTR{idVendor}=="0d9f", ATTR{idProduct}=="00a3", MODE="664", GROUP="root"
#  PowerCOM WOW  - usbhid-ups
ATTR{idVendor}=="0d9f", ATTR{idProduct}=="00a4", MODE="664", GROUP="root"
#  PowerCOM VGD - Vanguard  - usbhid-ups
ATTR{idVendor}=="0d9f", ATTR{idProduct}=="00a5", MODE="664", GROUP="root"
#  PowerCOM BNT - Black Knight Pro  - usbhid-ups
ATTR{idVendor}=="0d9f", ATTR{idProduct}=="00a6", MODE="664", GROUP="root"
#  Unitek Alpha 1200Sx  - blazer_usb
ATTR{idVendor}=="0f03", ATTR{idProduct}=="0001", MODE="664", GROUP="root"

From https://wiki.archlinux.org/index.php/Network_UPS_Tools#Driver_configuration

USB communication driver 0.33
No matching HID UPS found
Driver failed to start (exit status=1)

It's most likely a problem with permissions for accessing the device. You can fix that by specifying an udev rule that sets the correct group

Can I suggest that the following be added to udev rules:

# Powercom IMP series
ATTR{idVendor}=="0d9f", ATTR{idProduct}=="0004", MODE="664", GROUP="root"

No matching HID UPS found

Problem/Motivation

No matching HID UPS found
USB Driver failed to start

Expected behavior

My UPS worked properly with NUT server on another RP without Home assistant
I wpould like to have NUT running as addon on hassio.

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...

Hass.io Add-on: Network UPS Tools
Manage battery backup (UPS) devices

Add-on version: 4213c06
You are running the latest version of this add-on.
System: HassOS 3.9 (armv7 / raspberrypi3)
Home Assistant version: 0.105.2
Supervisor version: 199

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...
[19:28:25] INFO: Setting mode to netserver...
[19:28:26] INFO: Connected USB devices:
Bus 001 Device 040: ID 0d9f:0004 Powercom Co., Ltd
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 103: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[19:28:26] INFO: Generating /etc/nut/upsd.users...
[19:28:27] INFO: Configuring user: upsmon
[19:28:30] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[19:28:34] INFO: Configuring Device named myups...
[19:28:34] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 3.8.0-3396-gcdc7c4b5b1
Network UPS Tools - Generic HID driver 0.41 (3.8.0-3396-gcdc7c4b5b1)
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.

Steps to reproduce

UPS - Powercom WOW500
Raspberry Pi 3

My config:
users:

username: upsmon
password: ****
instcmds:
- all
  actions: []
  devices:
name: myups
driver: usbhid-ups
port: auto
config: []
mode: netserver
shutdown_hassio: 'false'
list_usb_devices: 'true'

Sensor:

platform: nut
name: UPS Powercom
host: 40817795-nut
port: 3493
alias: NUT_Server
username: upsmon
password: ha_upsmon
resources:
- ups.load
- ups.status
- output.voltage
- battery.runtime
- battery.charge
- ups.timer.shutdown

Proposed changes

I have no idea how to get it working
My UPS is listed as USB device in the log

SNMP configuration

How do you configure for SNMP?

I have tried the following (I got config params from https://networkupstools.org/docs/man/snmp-ups.html)

users:
  - username: myusername
    password: mypassword
    instcmds:
      - all
    actions: []
devices:
  - name: apcups
    driver: snmp-ups
    port: 172.20.0.55
    config:
      snmp_version: v3
      secLevel: authPriv
      secName: snmpprofile1
      authPassword: myauthenticationpassphrase
      privPassword: myprivatepassphrase
mode: netserver
shutdown_host: 'false'

This results in:

[cont-init.d] nut.sh: executing... 
[19:45:41] INFO: Setting mode to netserver...
[19:45:41] INFO: Generating /etc/nut/upsd.users...
[19:45:41] INFO: Configuring user: myusername
[19:45:42] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[19:45:42] INFO: Configuring Device named apcups...
[19:45:42] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 3.8.0-3220-g866b921892
Network UPS Tools - Generic SNMP UPS driver 0.97 (3.8.0-3220-g866b921892)
Driver exited abnormally
[cont-init.d] nut.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...

snmp-ups(8)

Polling interval too slow.

Problem/Motivation

Polling interval is too slow and there is no configuration for it

Expected behavior

Have some sort of configuration to configure the polling interval

Using Cyberpower SmartUPS PR1500ELCD

Can't claim USB device [051d:0002]: Result not representable with an UPS APC XS 700U

I'm getting this error with this addon and an UPS APC XS 700U

My HA installation is on an Intel NUC i3 with Proxmox and Hassio in a VM

My addon config is

users:
  - username: xxxxxx
    password: xxxxxx
    instcmds:
      - all
    actions: []
devices:
  - name: myupsAPC
    driver: usbhid-ups
    port: auto
    config:
      - vendorid = 051d
mode: netserver
shutdown_host: 'false'
list_usb_devices: 'true'

my log is

[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: HassOS 4.13  (amd64 / qemux86-64)
 Home Assistant Core: 0.115.5
 Home Assistant Supervisor: 245
-----------------------------------------------------------
 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... 
[21:10:10] INFO: Setting mode to netserver...
[21:10:11] INFO: Connected USB devices:
Bus 003 Device 002: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[21:10:11] INFO: Generating /etc/nut/upsd.users...
[21:10:11] INFO: Configuring user: antonio
[21:10:11] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[21:10:11] INFO: Configuring Device named myupsAPC...
[21:10:11] 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)
Can't claim USB device [051d:0002]: Result not representable
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.
 
 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.

This is what I see in the Host Log

[    2.372365] usb 3-2: new low-speed USB device number 3 using uhci_hcd
[    2.564576] usb 3-2: New USB device found, idVendor=051d, idProduct=0002, bcdDevice= 1.06
[    2.565629] usb 3-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    2.566529] usb 3-2: Product: Back-UPS XS 700U   FW:924.Z5 .I USB FW:Z5 
[    2.567408] usb 3-2: Manufacturer: American Power Conversion
[    2.568270] usb 3-2: SerialNumber: 3B2025X61060  
[    2.570943] usb 3-2: can't set config #1, error -32

Is there anything I can check to let it work?

Thanks

PS: Some other times, if I disconnect and reconnect the USB, I get a different error:

No matching HID UPS found
Driver failed to start (exit status=1)

No changes to the configuration.

this is the host log

[ 3435.724142] usb 3-2: USB disconnect, device number 3
[ 3446.645735] usb 3-2: new low-speed USB device number 4 using uhci_hcd
[ 3446.836670] usb 3-2: New USB device found, idVendor=051d, idProduct=0002, bcdDevice= 1.06
[ 3446.837945] usb 3-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 3446.839085] usb 3-2: Product: Back-UPS XS 700U   FW:924.Z5 .I USB FW:Z5 
[ 3446.840250] usb 3-2: Manufacturer: American Power Conversion
[ 3446.841254] usb 3-2: SerialNumber: 3B2025X61060  
[ 3447.025476] hid-generic 0003:051D:0002.0002: hiddev96,hidraw1: USB HID v1.10 Device [American Power Conversion Back-UPS XS 700U   FW:924.Z5 .I USB FW:Z5 ] on usb-0000:00:1d.0-2/input0

This is the addon log

[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: HassOS 4.13  (amd64 / qemux86-64)
 Home Assistant Core: 0.115.5
 Home Assistant Supervisor: 245
-----------------------------------------------------------
 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... 
[21:43:03] INFO: Setting mode to netserver...
[21:43:03] INFO: Connected USB devices:
Bus 003 Device 002: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[21:43:03] INFO: Generating /etc/nut/upsd.users...
[21:43:03] INFO: Configuring user: antonio
[21:43:03] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[21:43:04] INFO: Configuring Device named myupsAPC...
[21:43:04] 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.

Have I Been Pwned abort the addon

Problem/Motivation

Addon aborted due to password in the Pwned list.

Expected behavior

Could you set the Have I Been Pwned as an option that can manual turn off if I don't need it?

Actual behavior

I am trying to setup the NUT server on my HASSIO to support my Synology NAS in LAN, but the username & password is in the Have I been Pwned list( well, it is a simple word, I not surprised they are in the list), and the whole add-on is aborted once detected password compromised.

Steps to reproduce

The problem is Synology NAS is using a fixed username & password that don't allow to edit, the purpose they are doing so is because their embedded UPS server is designed to link their own NAS which all have the same username & password, so synology NAS user does not need to setup anything, but with the NUT setup we need to key in the same username & password to login and it is stopped by Have I Been Pwned Check.

Synology Setting
UPS device name : ups
slave user name : monuser
slave password : secret

Input those in NUT Addon you can replicate the error.

[18:33:39] INFO: Setting mode to netserver...
[18:33:40] INFO: Generating /etc/nut/upsd.users...
[18:33:40] INFO: Configuring user: monuser
[18:33:40] WARNING: Password is in the Have I Been Pwned database!
[18:33:40] WARNING: Password appeared 243782 times!
[18:33:40] FATAL:
[18:33:40] FATAL: We are trying to help you to protect your system the
[18:33:40] FATAL: best we can. Therefore, this add-on checks your
[18:33:40] FATAL: configured password again the HaveIBeenPwned database.
[18:33:40] FATAL:
[18:33:40] FATAL: Unfortunately, your configured password is considered
[18:33:40] FATAL: unsafe. We highly recommend you to pick a different one.
[18:33:40] FATAL:
[18:33:40] FATAL: Please change the password in the 'users[0].password' option.
[18:33:40] FATAL:
[18:33:40] FATAL: Check the add-on manual for more information.
[18:33:40] FATAL:
[cont-init.d] nut.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...

Proposed changes

Could you make Have I Been Pwned to an option that allow user to turn it off?

Thank you.

Cyberpower 1500 reconnects USB on status change and Hassio gets Data stale

Problem/Motivation

I've configured the addon and everything works fine (I can see all the information), but when the UPS enters on battery mode usb disconnects and connects again (I can see with dmesg) so hassio lost connection with the ups and nut server seems to be down because the message Date stale shows up. If I restart the addon, everything works fine again.

Expected behavior

The driver should support short usb disconnections.

Actual behavior

The connection with the ups is lost and nut server is down (Data stale).

Steps to reproduce

Just force to enter on battery mode on Cyberpower CP1500EPFCLCD

Proposed changes

Is there a way to keep the nut server running after a short usb disconnection? Otherwise, is it possible to restart the nut server through hassio.addon_stdin service?

Can’t Save Configuration

Hello, I have a TecnoWare UPS Era + 1100.
I want to use this addon but I can’t save the configuration, every time I add something the config won’t save.
I think the correct driver is blazer_usb.
Also if o copy the config in the guide without modify I can’t save...

0.4.0+ fails to detect EATON devices

Problem/Motivation

I use the addon for months without any bigger issue with my Eaton UPS.
Now i upgraded, the addon stopped working.

What changed? What should i do?

Thank yőu!

Expected behavior

(What you expected to happen)

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...

            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.

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Is there a possibility to set the NUT-server name?

Hello!

I want to use the Pi with an attached UPS as a NUT-server (netserver mode).
One of the netclients will be my QNAP NAS. But QNAP is expecting that the name of the netserver (not the hostname!) is "qnapups". But I see no possibility to set the name of the netserver when using this addon.
When running in netclient mode I can set remote_ups_name but I can not set "local_ups_name" in netserver mode.

Or am I don't seeing the correct configuration option.

add on not listed in the repository

Problem/Motivation

the add on in listed in https://github.com/hassio-addons/repository. thus can't be found

Expected behavior

the add on is listed in https://github.com/hassio-addons/repository

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

GitHub
hassio-addons/repository
Community Hass.io Add-ons for Home Assistant. Contribute to hassio-addons/repository development by creating an account on GitHub.

USB not working after host reboot

Hi all,
I opened a similar issue on the operating system sysmtem since I think that it's more related to the OS but I open an issue here just to know if someone knows how to workaround the problem here.

I am going to close the issue in some days if no one answer.

Hardware Environment

Raspberry Pi 4 (4GB)

Home Assistant OS release:

Fresh installation of Home Assistant OS 5.9, supervisor 2020.12.7

~ $ ha info
arch: aarch64
channel: stable
docker: 19.03.13
features:
- reboot
- shutdown
- services
- network
- hostname
- hassos
hassos: "5.9"
homeassistant: 2020.12.2
hostname: homeassistant
logging: info
machine: raspberrypi4-64
operating_system: Home Assistant OS 5.9
supervisor: 2020.12.7
supported: true
supported_arch:
- aarch64
- armv7
- armhf
timezone: Europe/Rome
~ $

Supervisor logs:

21-01-03 17:48:20 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_a0d7b954_nut application
21-01-03 17:48:21 INFO (SyncWorker_7) [supervisor.docker.addon] Starting Docker add-on hassioaddons/nut-aarch64 with version 0.3.1
21-01-03 17:48:23 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_nut
21-01-03 17:48:51 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with a0d7b954_nut!

Kernel logs:

~ $ dmesg
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]
[    0.000000] Linux version 5.4.79-v8 (builder@32116dd22ffe) (gcc version 9.3.0 (Buildroot -g45d6d28)) #1 SMP PREEMPT Fri Dec 18 21:50:34 UTC 2020
[    0.000000] Machine model: Raspberry Pi 4 Model B Rev 1.1
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x000000002ac00000, size 64 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] On node 0 totalpages: 1012480
[    0.000000]   DMA zone: 3788 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 242432 pages, LIFO batch:63
[    0.000000]   DMA32 zone: 12032 pages used for memmap
[    0.000000]   DMA32 zone: 770048 pages, LIFO batch:63
[    0.000000] percpu: Embedded 31 pages/cpu s89432 r8192 d29352 u126976
[    0.000000] pcpu-alloc: s89432 r8192 d29352 u126976 alloc=31*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Detected PIPT I-cache on CPU0
[    0.000000] CPU features: detected: EL2 vector hardening
[    0.000000] ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 996660
[    0.000000] Kernel command line: zram.enabled=1 zram.num_devices=3 apparmor=1 security=apparmor rootwait systemd.machine_id=b58433c4fe834c2890f43902459357d9 cgroup_enable=memory fsck.repair=yes coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:0F:0D:A1 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000  dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=8d3d53e3-6d49-4c38-8349-aff6859e82fd rootfstype=squashfs ro rauc.slot=A
[    0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] software IO TLB: mapped [mem 0x37300000-0x3b300000] (64MB)
[    0.000000] Memory: 3819704K/4049920K available (11068K kernel code, 1176K rwdata, 3744K rodata, 1088K init, 1232K bss, 164680K reserved, 65536K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 36302 entries in 142 pages
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000] 	Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] random: get_random_bytes called from start_kernel+0x320/0x4b0 with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 54.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns
[    0.000005] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
[    0.000223] Console: colour dummy device 80x25
[    0.000646] printk: console [tty1] enabled
[    0.000703] Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 BogoMIPS (lpj=216000)
[    0.000737] pid_max: default: 32768 minimum: 301
[    0.000876] LSM: Security Framework initializing
[    0.001003] AppArmor: AppArmor initialized
[    0.001209] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.001279] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.003588] ASID allocator initialised with 32768 entries
[    0.003804] rcu: Hierarchical SRCU implementation.
[    0.004528] EFI services will not be available.
[    0.004996] smp: Bringing up secondary CPUs ...
[    0.005882] Detected PIPT I-cache on CPU1
[    0.005943] CPU1: Booted secondary processor 0x0000000001 [0x410fd083]
[    0.006956] Detected PIPT I-cache on CPU2
[    0.006995] CPU2: Booted secondary processor 0x0000000002 [0x410fd083]
[    0.007995] Detected PIPT I-cache on CPU3
[    0.008035] CPU3: Booted secondary processor 0x0000000003 [0x410fd083]
[    0.008168] smp: Brought up 1 node, 4 CPUs
[    0.008254] SMP: Total of 4 processors activated.
[    0.008276] CPU features: detected: 32-bit EL0 Support
[    0.008298] CPU features: detected: CRC32 instructions
[    0.034423] CPU: All CPU(s) started at EL2
[    0.034493] alternatives: patching kernel code
[    0.036081] devtmpfs: initialized
[    0.046189] Enabled cp15_barrier support
[    0.046243] Enabled setend support
[    0.046674] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.046719] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.048803] pinctrl core: initialized pinctrl subsystem
[    0.049480] DMI not present or invalid.
[    0.049842] NET: Registered protocol family 16
[    0.052745] DMA: preallocated 1024 KiB pool for atomic allocations
[    0.052779] audit: initializing netlink subsys (disabled)
[    0.053091] audit: type=2000 audit(0.052:1): state=initialized audit_enabled=0 res=1
[    0.053801] cpuidle: using governor menu
[    0.054302] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.054539] Serial: AMBA PL011 UART driver
[    0.057635] bcm2835-mbox fe00b880.mailbox: mailbox enabled
[    0.068220] raspberrypi-firmware soc:firmware: Attached to firmware from 2020-10-22 13:59, variant start
[    0.072202] raspberrypi-firmware soc:firmware: Firmware hash is 74e754ff8947c58d2773253f77f6f68a303188f8
[    0.113698] bcm2835-dma fe007000.dma: DMA legacy API manager, dmachans=0x1
[    0.117073] vgaarb: loaded
[    0.117513] SCSI subsystem initialized
[    0.117727] usbcore: registered new interface driver usbfs
[    0.117791] usbcore: registered new interface driver hub
[    0.117921] usbcore: registered new device driver usb
[    0.118202] usb_phy_generic phy: phy supply vcc not found, using dummy regulator
[    0.118492] mc: Linux media interface: v0.10
[    0.118550] videodev: Linux video capture interface: v2.00
[    0.120093] clocksource: Switched to clocksource arch_sys_counter
[    0.863295] VFS: Disk quotas dquot_6.6.0
[    0.863415] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.863599] FS-Cache: Loaded
[    0.863829] CacheFiles: Loaded
[    0.864597] AppArmor: AppArmor Filesystem Enabled
[    0.874430] thermal_sys: Registered thermal governor 'step_wise'
[    0.874786] NET: Registered protocol family 2
[    0.875594] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[    0.875669] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.875885] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear)
[    0.876390] TCP: Hash tables configured (established 32768 bind 32768)
[    0.876637] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    0.876721] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    0.877033] NET: Registered protocol family 1
[    0.877892] RPC: Registered named UNIX socket transport module.
[    0.877919] RPC: Registered udp transport module.
[    0.877938] RPC: Registered tcp transport module.
[    0.877957] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.877987] PCI: CLS 0 bytes, default 64
[    0.880028] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available
[    0.880317] kvm: Limiting the IPA size due to kernel Virtual Address limit
[    0.880341] kvm [1]: IPA Size Limit: 43bits
[    0.881165] kvm [1]: vgic interrupt IRQ1
[    0.881407] kvm [1]: Hyp mode initialized successfully
[    0.883385] Initialise system trusted keyrings
[    0.883656] workingset: timestamp_bits=46 max_order=20 bucket_order=0
[    0.892648] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.892945] FS-Cache: Netfs 'nfs' registered for caching
[    0.893653] NFS: Registering the id_resolver key type
[    0.893718] Key type id_resolver registered
[    0.893739] Key type id_legacy registered
[    0.893769] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.895070] Key type asymmetric registered
[    0.895095] Asymmetric key parser 'x509' registered
[    0.895152] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[    0.895416] io scheduler mq-deadline registered
[    0.895440] io scheduler kyber registered
[    0.898907] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
[    0.898948] brcm-pcie fd500000.pcie:   No bus range found for /scb/pcie@7d500000, using [bus 00-ff]
[    0.899024] brcm-pcie fd500000.pcie:      MEM 0x0600000000..0x0603ffffff -> 0x00f8000000
[    0.899099] brcm-pcie fd500000.pcie:   IB MEM 0x0000000000..0x00bfffffff -> 0x0000000000
[    0.946189] brcm-pcie fd500000.pcie: link up, 5 GT/s x1 (SSC)
[    0.946514] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
[    0.946545] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.946573] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff])
[    0.946646] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
[    0.946880] pci 0000:00:00.0: PME# supported from D0 D3hot
[    0.950756] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330
[    0.950908] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.951315] pci 0000:01:00.0: PME# supported from D0 D3cold
[    0.954911] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
[    0.954947] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]
[    0.955037] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.955067] pci 0000:00:00.0:   bridge window [mem 0x600000000-0x6000fffff]
[    0.955181] pci 0000:00:00.0: enabling device (0000 -> 0002)
[    0.955247] pci 0000:01:00.0: enabling device (0000 -> 0002)
[    0.958845] bcm2708_fb soc:fb: Unable to determine number of FBs. Disabling driver.
[    0.958890] bcm2708_fb: probe of soc:fb failed with error -2
[    0.964325] iproc-rng200 fe104000.rng: hwrng registered
[    0.964684] vc-mem: phys_addr:0x00000000 mem_base=0x3eb00000 mem_size:0x3ff00000(1023 MiB)
[    0.965481] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000
[    0.965855] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    0.976124] brd: module loaded
[    0.988116] loop: module loaded
[    0.988693] zram: Added device: zram0
[    0.989236] zram: Added device: zram1
[    0.989751] zram: Added device: zram2
[    0.991037] Loading iSCSI transport class v2.0-870.
[    0.993558] libphy: Fixed MDIO Bus: probed
[    0.993612] tun: Universal TUN/TAP device driver, 1.6
[    0.994353] bcmgenet fd580000.ethernet: failed to get enet clock
[    0.994385] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
[    0.994416] bcmgenet fd580000.ethernet: failed to get enet-wol clock
[    0.994445] bcmgenet fd580000.ethernet: failed to get enet-eee clock
[    0.994480] bcmgenet: Skipping UMAC reset
[    1.004132] libphy: bcmgenet MII bus: probed
[    1.052180] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
[    1.053103] usbcore: registered new interface driver r8152
[    1.053180] usbcore: registered new interface driver lan78xx
[    1.053721] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    1.053773] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[    1.054758] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000003000000890
[    1.056033] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    1.056066] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.056143] usb usb1: Product: xHCI Host Controller
[    1.056165] usb usb1: Manufacturer: Linux 5.4.79-v8 xhci-hcd
[    1.056188] usb usb1: SerialNumber: 0000:01:00.0
[    1.056793] hub 1-0:1.0: USB hub found
[    1.056904] hub 1-0:1.0: 1 port detected
[    1.057455] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    1.057489] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    1.057525] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[    1.057926] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[    1.057956] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.057981] usb usb2: Product: xHCI Host Controller
[    1.058003] usb usb2: Manufacturer: Linux 5.4.79-v8 xhci-hcd
[    1.058024] usb usb2: SerialNumber: 0000:01:00.0
[    1.058571] hub 2-0:1.0: USB hub found
[    1.058668] hub 2-0:1.0: 4 ports detected
[    1.060008] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    1.060295] dwc_otg: FIQ enabled
[    1.060304] dwc_otg: NAK holdoff enabled
[    1.060313] dwc_otg: FIQ split-transaction FSM enabled
[    1.060325] Module dwc_common_port init
[    1.060797] usbcore: registered new interface driver uas
[    1.060907] usbcore: registered new interface driver usb-storage
[    1.061035] usbcore: registered new interface driver usbserial_generic
[    1.061087] usbserial: USB Serial support registered for generic
[    1.061306] mousedev: PS/2 mouse device common for all mice
[    1.062943] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    1.066079] sdhci: Secure Digital Host Controller Interface driver
[    1.066110] sdhci: Copyright(c) Pierre Ossman
[    1.066651] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe
[    1.067091] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.073824] ledtrig-cpu: registered to indicate activity on CPUs
[    1.073957] hidraw: raw HID events driver (C) Jiri Kosina
[    1.074042] usbcore: registered new interface driver usbhid
[    1.074051] usbhid: USB HID core driver
[    1.074691] vchiq: vchiq_init_state: slot_zero = (____ptrval____)
[    1.076945] IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
[    1.076991] IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
[    1.077119] IPVS: ipvs loaded.
[    1.077129] IPVS: [rr] scheduler registered.
[    1.077576] NET: Registered protocol family 10
[    1.078249] Segment Routing with IPv6
[    1.078309] NET: Registered protocol family 17
[    1.078351] Bridge firewalling registered
[    1.078408] Key type dns_resolver registered
[    1.078798] registered taskstats version 1
[    1.078816] Loading compiled-in X.509 certificates
[    1.078931] Key type ._fscrypt registered
[    1.078939] Key type .fscrypt registered
[    1.078989] AppArmor: AppArmor sha1 policy hashing enabled
[    1.086102] uart-pl011 fe201000.serial: cts_event_workaround enabled
[    1.086184] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 14, base_baud = 0) is a PL011 rev2
[    1.092896] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    1.093347] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    1.093361] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated
[    1.142061] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.143686] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.145304] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.148181] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.149799] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.160037] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA
[    1.162362] printk: console [netcon0] enabled
[    1.162382] netconsole: network logging started
[    1.162436] of_cfs_init
[    1.162584] of_cfs_init: OK
[    1.164736] Waiting for root device PARTUUID=8d3d53e3-6d49-4c38-8349-aff6859e82fd...
[    1.185856] random: fast init done
[    1.215055] mmc1: new high speed SDIO card at address 0001
[    1.392119] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    1.542705] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[    1.542739] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.542764] usb 1-1: Product: USB2.0 Hub
[    1.544344] hub 1-1:1.0: USB hub found
[    1.544655] hub 1-1:1.0: 4 ports detected
[    1.668375] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[    1.689514] usb 2-2: New USB device found, idVendor=0781, idProduct=5580, bcdDevice= 0.10
[    1.689546] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.689571] usb 2-2: Product: Extreme
[    1.689591] usb 2-2: Manufacturer: SanDisk
[    1.689611] usb 2-2: SerialNumber: AA010731140240363648
[    1.692353] usb-storage 2-2:1.0: USB Mass Storage device detected
[    1.692953] scsi host0: usb-storage 2-2:1.0
[    1.840116] usb 1-1.4: new full-speed USB device number 3 using xhci_hcd
[    1.920348] usb 1-1.4: device descriptor read/64, error -32
[    2.108443] usb 1-1.4: device descriptor read/64, error -32
[    2.296141] usb 1-1.4: new full-speed USB device number 4 using xhci_hcd
[    2.376348] usb 1-1.4: device descriptor read/64, error -32
[    2.564347] usb 1-1.4: device descriptor read/64, error -32
[    2.672549] usb 1-1-port4: attempt power cycle
[    2.720798] scsi 0:0:0:0: Direct-Access     SanDisk  Extreme          0001 PQ: 0 ANSI: 6
[    2.721689] sd 0:0:0:0: [sda] 122544516 512-byte logical blocks: (62.7 GB/58.4 GiB)
[    2.722464] sd 0:0:0:0: [sda] Write Protect is off
[    2.722494] sd 0:0:0:0: [sda] Mode Sense: 33 00 00 08
[    2.723142] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    2.732770]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
[    2.736092] sd 0:0:0:0: [sda] Attached SCSI disk
[    2.755002] VFS: Mounted root (squashfs filesystem) readonly on device 8:3.
[    2.757019] devtmpfs: mounted
[    2.760816] Freeing unused kernel memory: 1088K
[    2.776162] Run /sbin/init as init process
[    2.928236] systemd[1]: System time before build time, advancing clock.
[    2.940803] systemd[1]: systemd 246 running in system mode. (+PAM -AUDIT -SELINUX -IMA +APPARMOR -SMACK -SYSVINIT -UTMP -LIBCRYPTSETUP +GCRYPT +GNUTLS -ACL -XZ -LZ4 -ZSTD -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN -PCRE2 default-hierarchy=hybrid)
[    2.941190] systemd[1]: Detected architecture arm64.
[    2.962856] systemd[1]: Set hostname to <homeassistant>.
[    2.963165] systemd[1]: Installed transient /etc/machine-id file.
[    3.107529] systemd[1]: /usr/lib/systemd/system/docker.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly.
[    3.185028] systemd[1]: Queued start job for default target Multi-User System.
[    3.185736] random: systemd: uninitialized urandom read (16 bytes read)
[    3.188277] systemd[1]: Created slice system-getty.slice.
[    3.188698] random: systemd: uninitialized urandom read (16 bytes read)
[    3.189793] systemd[1]: Created slice system-modprobe.slice.
[    3.190013] random: systemd: uninitialized urandom read (16 bytes read)
[    3.190994] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    3.192457] systemd[1]: Created slice User and Session Slice.
[    3.192869] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    3.193184] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    3.193533] systemd[1]: Reached target HassOS zram targets.
[    3.193760] systemd[1]: Reached target Paths.
[    3.193954] systemd[1]: Reached target Remote File Systems.
[    3.194138] systemd[1]: Reached target Slices.
[    3.196672] systemd[1]: Listening on Process Core Dump Socket.
[    3.197314] systemd[1]: Listening on Journal Audit Socket.
[    3.197792] systemd[1]: Listening on Journal Socket (/dev/log).
[    3.198276] systemd[1]: Listening on Journal Socket.
[    3.198821] systemd[1]: Listening on udev Control Socket.
[    3.199246] systemd[1]: Listening on udev Kernel Socket.
[    3.199711] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[    3.202466] systemd[1]: Mounting POSIX Message Queue File System...
[    3.206713] systemd[1]: Mounting Kernel Debug File System...
[    3.210973] systemd[1]: Mounting Kernel Trace File System...
[    3.215381] systemd[1]: Starting Create list of static device nodes for the current kernel...
[    3.218982] systemd[1]: Starting Load Kernel Module drm...
[    3.225832] systemd[1]: Starting Journal Service...
[    3.230225] systemd[1]: Starting Remount Root and Kernel File Systems...
[    3.235068] systemd[1]: Starting Coldplug All udev Devices...
[    3.240172] systemd[1]: Starting HassOS ZRAM swap...
[    3.245040] systemd[1]: Starting HassOS ZRAM tmp...
[    3.249646] systemd[1]: Starting HassOS ZRAM var...
[    3.256572] systemd[1]: Mounted POSIX Message Queue File System.
[    3.257443] systemd[1]: Mounted Kernel Debug File System.
[    3.258288] systemd[1]: Mounted Kernel Trace File System.
[    3.261343] systemd[1]: Finished Create list of static device nodes for the current kernel.
[    3.264694] systemd[1]: Finished Remount Root and Kernel File Systems.
[    3.269684] systemd[1]: Starting Create Static Device Nodes in /dev...
[    3.276232] usb 1-1.4: new full-speed USB device number 5 using xhci_hcd
[    3.276480] usb 1-1.4: Device not responding to setup address.
[    3.287990] zram1: detected capacity change from 0 to 33554432
[    3.291358] zram0: detected capacity change from 0 to 994902016
[    3.293581] systemd[1]: [email protected]: Succeeded.
[    3.295533] systemd[1]: Finished Load Kernel Module drm.
[    3.298000] zram2: detected capacity change from 0 to 16777216
[    3.325423] systemd[1]: Finished Create Static Device Nodes in /dev.
[    3.326210] systemd[1]: Reached target Local File Systems (Pre).
[    3.331316] systemd[1]: Starting Rule-based Manager for Device Events and Files...
[    3.334538] systemd[1]: Started Journal Service.
[    3.484307] usb 1-1.4: Device not responding to setup address.
[    3.497675] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x00010000
[    3.497901] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00001000
[    3.498077] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x00010000
[    3.498241] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x00010000
[    3.519190] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[    3.522609] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[    3.522634] [vc_sm_connected_init]: start
[    3.526240] [vc_sm_connected_init]: installed successfully
[    3.545137] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    3.551386] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[    3.552197] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[    3.564608] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[    3.573040] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[    3.573096] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[    3.577474] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    3.577940] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[    3.578067] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[    3.578107] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[    3.585181] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[    3.585511] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[    3.585598] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[    3.586971] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[    3.587470] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[    3.587514] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[    3.587529] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[    3.587542] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[    3.587554] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[    3.588745] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[    3.590551] bcm2835_audio bcm2835_audio: card created with 8 channels
[    3.692127] usb 1-1.4: device not accepting address 5, error -71
[    3.729608] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    3.772528] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    3.773340] usb 1-1.4: new full-speed USB device number 6 using xhci_hcd
[    3.774249] usb 1-1.4: Device not responding to setup address.
[    3.805961] brcmfmac: F1 signature read @0x18000000=0x15264345
[    3.814160] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    3.815376] usbcore: registered new interface driver brcmfmac
[    3.824359] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
[    3.984273] usb 1-1.4: Device not responding to setup address.
[    4.024058] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    4.027710] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[    4.027759] ext4 filesystem being mounted at /mnt/overlay supports timestamps until 2038 (0x7fffffff)
[    4.036161] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[    4.192132] usb 1-1.4: device not accepting address 6, error -71
[    4.192449] usb 1-1-port4: unable to enumerate USB device
[    4.220138] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
[    4.356345] Adding 971580k swap on /dev/zram0.  Priority:-2 extents:1 across:971580k SSFS
[    5.356836] EXT4-fs (zram2): mounted filesystem without journal. Opts: nobarrier
[    5.356863] ext4 filesystem being mounted at /tmp supports timestamps until 2038 (0x7fffffff)
[    5.359802] EXT4-fs (zram1): mounted filesystem without journal. Opts: nobarrier
[    5.359834] ext4 filesystem being mounted at /var supports timestamps until 2038 (0x7fffffff)
[    5.383720] random: crng init done
[    5.383728] random: 7 urandom warning(s) missed due to ratelimiting
[    5.940851] uart-pl011 fe201000.serial: no DMA platform data
[    6.183271] audit: type=1400 audit(1609695801.371:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor" pid=335 comm="apparmor_parser"
[    6.184049] audit: type=1400 audit(1609695801.371:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor///usr/bin/gdbus" pid=335 comm="apparmor_parser"
[    6.184112] audit: type=1400 audit(1609695801.371:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor///usr/bin/git" pid=335 comm="apparmor_parser"
[    6.184146] audit: type=1400 audit(1609695801.371:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor///usr/bin/socat" pid=335 comm="apparmor_parser"
[    6.551161] Bluetooth: Core ver 2.22
[    6.551213] NET: Registered protocol family 31
[    6.551217] Bluetooth: HCI device and connection manager initialized
[    6.551230] Bluetooth: HCI socket layer initialized
[    6.551238] Bluetooth: L2CAP socket layer initialized
[    6.551252] Bluetooth: SCO socket layer initialized
[    6.554194] bcmgenet: Skipping UMAC reset
[    6.559292] Bluetooth: HCI UART driver ver 2.3
[    6.559301] Bluetooth: HCI UART protocol H4 registered
[    6.559337] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    6.559471] Bluetooth: HCI UART protocol Broadcom registered
[    6.563728] bcmgenet fd580000.ethernet: configuring instance for external RGMII
[    6.563908] bcmgenet fd580000.ethernet eth0: Link is Down
[    6.604328] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[    6.677215] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.677223] Bluetooth: BNEP filters: protocol multicast
[    6.677236] Bluetooth: BNEP socket layer initialized
[    6.693272] NET: Registered protocol family 38
[    6.720159] cryptd: max_cpu_qlen set to 1000
[   11.680166] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   11.680193] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   17.769245] audit: type=1400 audit(1609695812.959:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=423 comm="apparmor_parser"
[   21.966596] audit: type=1325 audit(1609695817.155:4): table=nat family=2 entries=5
[   21.972535] audit: type=1325 audit(1609695817.163:5): table=filter family=2 entries=4
[   21.978458] audit: type=1325 audit(1609695817.167:6): table=filter family=2 entries=6
[   21.984451] audit: type=1325 audit(1609695817.175:7): table=filter family=2 entries=8
[   21.991359] audit: type=1325 audit(1609695817.179:8): table=filter family=2 entries=10
[   21.999230] audit: type=1325 audit(1609695817.187:9): table=filter family=2 entries=11
[   22.002576] audit: type=1325 audit(1609695817.191:10): table=filter family=2 entries=12
[   22.016653] Initializing XFRM netlink socket
[   22.046744] audit: type=1325 audit(1609695817.235:11): table=nat family=2 entries=7
[   22.053339] audit: type=1325 audit(1609695817.243:12): table=nat family=2 entries=8
[   22.778869] kauditd_printk_skb: 33 callbacks suppressed
[   22.778875] audit: type=1325 audit(1609695817.967:46): table=nat family=2 entries=11
[   22.785188] audit: type=1325 audit(1609695817.975:47): table=nat family=2 entries=12
[   22.794391] audit: type=1325 audit(1609695817.983:48): table=filter family=2 entries=19
[   22.801875] audit: type=1325 audit(1609695817.991:49): table=filter family=2 entries=20
[   22.821873] audit: type=1325 audit(1609695818.011:50): table=filter family=2 entries=21
[   22.829799] audit: type=1325 audit(1609695818.019:51): table=filter family=2 entries=22
[   22.835834] audit: type=1325 audit(1609695818.023:52): table=filter family=2 entries=23
[   22.839166] audit: type=1325 audit(1609695818.027:53): table=filter family=2 entries=22
[   22.845775] audit: type=1325 audit(1609695818.035:54): table=filter family=2 entries=23
[   22.859766] audit: type=1325 audit(1609695818.047:55): table=filter family=2 entries=24
[   22.904737] hassio: port 1(veth28b8f5c) entered blocking state
[   22.904746] hassio: port 1(veth28b8f5c) entered disabled state
[   22.904952] device veth28b8f5c entered promiscuous mode
[   22.906045] hassio: port 1(veth28b8f5c) entered blocking state
[   22.906054] hassio: port 1(veth28b8f5c) entered forwarding state
[   22.907093] hassio: port 1(veth28b8f5c) entered disabled state
[   23.248979] cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation
[   23.616067] eth0: renamed from veth79f0c48
[   23.645633] IPv6: ADDRCONF(NETDEV_CHANGE): veth28b8f5c: link becomes ready
[   23.645825] hassio: port 1(veth28b8f5c) entered blocking state
[   23.645837] hassio: port 1(veth28b8f5c) entered forwarding state
[   23.646091] IPv6: ADDRCONF(NETDEV_CHANGE): hassio: link becomes ready
[   24.945895] docker0: port 1(vethadceef2) entered blocking state
[   24.945907] docker0: port 1(vethadceef2) entered disabled state
[   24.946390] device vethadceef2 entered promiscuous mode
[   24.970504] hassio: port 2(veth4e21681) entered blocking state
[   24.970515] hassio: port 2(veth4e21681) entered disabled state
[   24.971024] device veth4e21681 entered promiscuous mode
[   24.974790] hassio: port 2(veth4e21681) entered blocking state
[   24.974799] hassio: port 2(veth4e21681) entered forwarding state
[   25.337339] eth0: renamed from veth3c290f1
[   25.357518] hassio: port 2(veth4e21681) entered disabled state
[   25.357711] IPv6: ADDRCONF(NETDEV_CHANGE): vethadceef2: link becomes ready
[   25.357864] docker0: port 1(vethadceef2) entered blocking state
[   25.357874] docker0: port 1(vethadceef2) entered forwarding state
[   25.358123] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
[   25.531194] eth1: renamed from vethd7c863e
[   25.553406] IPv6: ADDRCONF(NETDEV_CHANGE): veth4e21681: link becomes ready
[   25.553561] hassio: port 2(veth4e21681) entered blocking state
[   25.553571] hassio: port 2(veth4e21681) entered forwarding state
[   26.105393] udevd[205]: starting version 3.2.9
[   26.124532] udevd[206]: starting eudev-3.2.9
[   31.936382] kauditd_printk_skb: 29 callbacks suppressed
[   31.936388] audit: type=1400 audit(1609695827.123:85): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="hassio-supervisor" pid=1586 comm="apparmor_parser"
[   31.936406] audit: type=1400 audit(1609695827.123:85): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="hassio-supervisor///usr/bin/gdbus" pid=1586 comm="apparmor_parser"
[   31.936419] audit: type=1400 audit(1609695827.123:85): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="hassio-supervisor///usr/bin/git" pid=1586 comm="apparmor_parser"
[   31.936432] audit: type=1400 audit(1609695827.123:85): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="hassio-supervisor///usr/bin/socat" pid=1586 comm="apparmor_parser"
[   32.458767] hassio: port 3(vethbdf4b91) entered blocking state
[   32.458777] hassio: port 3(vethbdf4b91) entered disabled state
[   32.459000] device vethbdf4b91 entered promiscuous mode
[   32.459082] audit: type=1700 audit(1609695827.647:86): dev=vethbdf4b91 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[   32.835542] audit: type=1325 audit(1609695828.023:87): table=nat family=2 entries=0
[   32.842784] audit: type=1325 audit(1609695828.031:88): table=filter family=2 entries=0
[   32.850604] audit: type=1325 audit(1609695828.039:89): table=nat family=2 entries=5
[   32.853888] audit: type=1325 audit(1609695828.043:90): table=nat family=2 entries=7
[   32.859938] audit: type=1325 audit(1609695828.047:91): table=nat family=2 entries=8
[   32.909606] eth0: renamed from vethedafeb1
[   32.944913] IPv6: ADDRCONF(NETDEV_CHANGE): vethbdf4b91: link becomes ready
[   32.945101] hassio: port 3(vethbdf4b91) entered blocking state
[   32.945113] hassio: port 3(vethbdf4b91) entered forwarding state
[   33.394507] hassio: port 4(vethfa3584c) entered blocking state
[   33.394517] hassio: port 4(vethfa3584c) entered disabled state
[   33.395106] device vethfa3584c entered promiscuous mode
[   33.395912] hassio: port 4(vethfa3584c) entered blocking state
[   33.395920] hassio: port 4(vethfa3584c) entered forwarding state
[   33.460355] hassio: port 4(vethfa3584c) entered disabled state
[   33.949377] eth0: renamed from veth7f551f0
[   33.969188] IPv6: ADDRCONF(NETDEV_CHANGE): vethfa3584c: link becomes ready
[   33.969302] hassio: port 4(vethfa3584c) entered blocking state
[   33.969309] hassio: port 4(vethfa3584c) entered forwarding state
[   34.709504] hassio: port 5(vethd570b5b) entered blocking state
[   34.709513] hassio: port 5(vethd570b5b) entered disabled state
[   34.710198] device vethd570b5b entered promiscuous mode
[   35.241231] eth0: renamed from veth3dcc646
[   35.257833] IPv6: ADDRCONF(NETDEV_CHANGE): vethd570b5b: link becomes ready
[   35.258017] hassio: port 5(vethd570b5b) entered blocking state
[   35.258023] hassio: port 5(vethd570b5b) entered forwarding state
[   36.930880] udevd[494]: starting version 3.2.9
[   36.961169] udevd[495]: starting eudev-3.2.9
[   37.353230] Bluetooth: RFCOMM TTY layer initialized
[   37.353249] Bluetooth: RFCOMM socket layer initialized
[   37.353268] Bluetooth: RFCOMM ver 1.11
[   40.865941] hassio: port 6(vethae6b644) entered blocking state
[   40.865950] hassio: port 6(vethae6b644) entered disabled state
[   40.866175] device vethae6b644 entered promiscuous mode
[   40.866235] kauditd_printk_skb: 27 callbacks suppressed
[   40.866238] audit: type=1700 audit(1609695943.124:119): dev=vethae6b644 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[   40.897219] audit: type=1325 audit(1609695943.156:120): table=nat family=2 entries=15
[   40.904511] audit: type=1325 audit(1609695943.164:121): table=filter family=2 entries=30
[   40.911988] audit: type=1325 audit(1609695943.168:122): table=nat family=2 entries=16
[   40.926659] audit: type=1325 audit(1609695943.184:123): table=nat family=2 entries=17
[   40.934746] audit: type=1325 audit(1609695943.192:124): table=filter family=2 entries=31
[   40.942781] audit: type=1325 audit(1609695943.200:125): table=nat family=2 entries=18
[   40.957587] audit: type=1325 audit(1609695943.216:126): table=nat family=2 entries=19
[   40.965526] audit: type=1325 audit(1609695943.224:127): table=filter family=2 entries=32
[   40.973607] audit: type=1325 audit(1609695943.232:128): table=nat family=2 entries=20
[   41.475051] eth0: renamed from vethf89112a
[   41.489202] IPv6: ADDRCONF(NETDEV_CHANGE): vethae6b644: link becomes ready
[   41.489335] hassio: port 6(vethae6b644) entered blocking state
[   41.489344] hassio: port 6(vethae6b644) entered forwarding state
[   42.203335] hassio: port 7(vethd47f626) entered blocking state
[   42.203345] hassio: port 7(vethd47f626) entered disabled state
[   42.203637] device vethd47f626 entered promiscuous mode
[   42.757277] eth0: renamed from veth639b583
[   42.777598] IPv6: ADDRCONF(NETDEV_CHANGE): vethd47f626: link becomes ready
[   42.777714] hassio: port 7(vethd47f626) entered blocking state
[   42.777720] hassio: port 7(vethd47f626) entered forwarding state
[   48.563890] hassio: port 8(vethea1db53) entered blocking state
[   48.563904] hassio: port 8(vethea1db53) entered disabled state
[   48.564832] device vethea1db53 entered promiscuous mode
[   48.564903] kauditd_printk_skb: 24 callbacks suppressed
[   48.564906] audit: type=1700 audit(1609695950.820:153): dev=vethea1db53 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[   48.591594] audit: type=1325 audit(1609695950.848:154): table=nat family=2 entries=23
[   48.598875] audit: type=1325 audit(1609695950.856:155): table=filter family=2 entries=34
[   48.606718] audit: type=1325 audit(1609695950.864:156): table=nat family=2 entries=24
[   49.018163] audit: type=1325 audit(1609695951.276:157): table=nat family=2 entries=0
[   49.026752] audit: type=1325 audit(1609695951.284:158): table=filter family=2 entries=0
[   49.038526] audit: type=1325 audit(1609695951.296:159): table=nat family=2 entries=5
[   49.042867] audit: type=1325 audit(1609695951.300:160): table=nat family=2 entries=7
[   49.048632] audit: type=1325 audit(1609695951.308:161): table=nat family=2 entries=8
[   49.051901] audit: type=1325 audit(1609695951.308:162): table=nat family=2 entries=10
[   49.109115] eth0: renamed from vethdb0bdf0
[   49.125220] IPv6: ADDRCONF(NETDEV_CHANGE): vethea1db53: link becomes ready
[   49.125318] hassio: port 8(vethea1db53) entered blocking state
[   49.125323] hassio: port 8(vethea1db53) entered forwarding state
[   50.395558] hassio: port 9(veth058a7dc) entered blocking state
[   50.395567] hassio: port 9(veth058a7dc) entered disabled state
[   50.396063] device veth058a7dc entered promiscuous mode
[   51.195222] eth0: renamed from vetha953e1f
[   51.210346] IPv6: ADDRCONF(NETDEV_CHANGE): veth058a7dc: link becomes ready
[   51.210483] hassio: port 9(veth058a7dc) entered blocking state
[   51.210489] hassio: port 9(veth058a7dc) entered forwarding state
[   51.748131] usb 1-1.4: new full-speed USB device number 7 using xhci_hcd
[   51.828375] usb 1-1.4: device descriptor read/64, error -32
[   52.016389] usb 1-1.4: device descriptor read/64, error -32
[   52.208149] usb 1-1.4: new full-speed USB device number 8 using xhci_hcd
[   52.292393] usb 1-1.4: device descriptor read/64, error -32
[   52.338504] hassio: port 10(vethebdc4e4) entered blocking state
[   52.338515] hassio: port 10(vethebdc4e4) entered disabled state
[   52.338817] device vethebdc4e4 entered promiscuous mode
[   52.339360] hassio: port 10(vethebdc4e4) entered blocking state
[   52.339370] hassio: port 10(vethebdc4e4) entered forwarding state
[   52.340684] hassio: port 10(vethebdc4e4) entered disabled state
[   52.480332] usb 1-1.4: device descriptor read/64, error -32
[   52.588661] usb 1-1-port4: attempt power cycle
[   53.192142] usb 1-1.4: new full-speed USB device number 9 using xhci_hcd
[   53.192334] usb 1-1.4: Device not responding to setup address.
[   53.197428] eth0: renamed from veth4b16696
[   53.217679] IPv6: ADDRCONF(NETDEV_CHANGE): vethebdc4e4: link becomes ready
[   53.217832] hassio: port 10(vethebdc4e4) entered blocking state
[   53.217838] hassio: port 10(vethebdc4e4) entered forwarding state
[   53.400360] usb 1-1.4: Device not responding to setup address.
[   53.608136] usb 1-1.4: device not accepting address 9, error -71
[   53.688146] usb 1-1.4: new full-speed USB device number 10 using xhci_hcd
[   53.688342] usb 1-1.4: Device not responding to setup address.
[   53.896328] usb 1-1.4: Device not responding to setup address.
[   54.104139] usb 1-1.4: device not accepting address 10, error -71
[   54.104442] usb 1-1-port4: unable to enumerate USB device
[   54.609309] hassio: port 7(vethd47f626) entered disabled state
[   54.609994] veth639b583: renamed from eth0
[   54.672585] hassio: port 7(vethd47f626) entered disabled state
[   54.674062] device vethd47f626 left promiscuous mode
[   54.674116] kauditd_printk_skb: 26 callbacks suppressed
[   54.674119] audit: type=1700 audit(1609695956.908:189): dev=vethd47f626 prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295
[   54.674136] hassio: port 7(vethd47f626) entered disabled state
[   59.335221] udevd[192]: starting version 3.2.9
[   59.361532] udevd[193]: starting eudev-3.2.9
[  136.608219] hassio: port 7(vethe468e5f) entered blocking state
[  136.608231] hassio: port 7(vethe468e5f) entered disabled state
[  136.609492] device vethe468e5f entered promiscuous mode
[  136.609563] audit: type=1700 audit(1609696038.864:190): dev=vethe468e5f prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[  137.020823] audit: type=1325 audit(1609696039.280:191): table=nat family=2 entries=0
[  137.028641] audit: type=1325 audit(1609696039.284:192): table=filter family=2 entries=0
[  137.037958] audit: type=1325 audit(1609696039.296:193): table=nat family=2 entries=5
[  137.041699] audit: type=1325 audit(1609696039.300:194): table=nat family=2 entries=7
[  137.048393] audit: type=1325 audit(1609696039.304:195): table=nat family=2 entries=8
[  137.051803] audit: type=1325 audit(1609696039.308:196): table=nat family=2 entries=10
[  137.058110] audit: type=1325 audit(1609696039.316:197): table=nat family=2 entries=11
[  137.062467] audit: type=1325 audit(1609696039.320:198): table=nat family=2 entries=12
[  137.068275] audit: type=1325 audit(1609696039.324:199): table=nat family=2 entries=13
[  137.111474] eth0: renamed from veth33d4859
[  137.138100] IPv6: ADDRCONF(NETDEV_CHANGE): vethe468e5f: link becomes ready
[  137.138290] hassio: port 7(vethe468e5f) entered blocking state
[  137.138300] hassio: port 7(vethe468e5f) entered forwarding state
[  143.668883] usb 1-1.4: new full-speed USB device number 11 using xhci_hcd
[  143.749144] usb 1-1.4: device descriptor read/64, error -32
[  143.937109] usb 1-1.4: device descriptor read/64, error -32
[  144.124924] usb 1-1.4: new full-speed USB device number 12 using xhci_hcd
[  144.205134] usb 1-1.4: device descriptor read/64, error -32
[  144.393074] usb 1-1.4: device descriptor read/64, error -32
[  144.501330] usb 1-1-port4: attempt power cycle
[  145.104931] usb 1-1.4: new full-speed USB device number 13 using xhci_hcd
[  145.105150] usb 1-1.4: Device not responding to setup address.
[  145.313091] usb 1-1.4: Device not responding to setup address.
[  145.520910] usb 1-1.4: device not accepting address 13, error -71
[  145.600942] usb 1-1.4: new full-speed USB device number 14 using xhci_hcd
[  145.601141] usb 1-1.4: Device not responding to setup address.
[  145.809115] usb 1-1.4: Device not responding to setup address.
[  146.016957] usb 1-1.4: device not accepting address 14, error -71
[  146.017395] usb 1-1-port4: unable to enumerate USB device
[  146.526849] hassio: port 7(vethe468e5f) entered disabled state
[  146.527133] veth33d4859: renamed from eth0
[  146.610856] hassio: port 7(vethe468e5f) entered disabled state
[  146.612203] device vethe468e5f left promiscuous mode
[  146.612228] hassio: port 7(vethe468e5f) entered disabled state
[  146.616945] kauditd_printk_skb: 1 callbacks suppressed
[  146.616951] audit: type=1700 audit(1609696048.847:201): dev=vethe468e5f prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295
[  167.757029] hassio: port 7(veth3c0b3f6) entered blocking state
[  167.757043] hassio: port 7(veth3c0b3f6) entered disabled state
[  167.757699] device veth3c0b3f6 entered promiscuous mode
[  167.757781] audit: type=1700 audit(1609696070.011:202): dev=veth3c0b3f6 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[  168.170934] audit: type=1325 audit(1609696070.427:203): table=nat family=2 entries=0
[  168.177852] audit: type=1325 audit(1609696070.435:204): table=filter family=2 entries=0
[  168.186409] audit: type=1325 audit(1609696070.443:205): table=nat family=2 entries=5
[  168.189834] audit: type=1325 audit(1609696070.447:206): table=nat family=2 entries=7
[  168.195366] audit: type=1325 audit(1609696070.451:207): table=nat family=2 entries=8
[  168.200013] audit: type=1325 audit(1609696070.455:208): table=nat family=2 entries=10
[  168.204805] audit: type=1325 audit(1609696070.459:209): table=nat family=2 entries=11
[  168.209253] audit: type=1325 audit(1609696070.463:210): table=nat family=2 entries=12
[  168.213917] audit: type=1325 audit(1609696070.471:211): table=nat family=2 entries=13
[  168.258607] eth0: renamed from veth5a2d872
[  168.286507] IPv6: ADDRCONF(NETDEV_CHANGE): veth3c0b3f6: link becomes ready
[  168.286661] hassio: port 7(veth3c0b3f6) entered blocking state
[  168.286670] hassio: port 7(veth3c0b3f6) entered forwarding state
[  174.505487] usb 1-1.4: new full-speed USB device number 15 using xhci_hcd
[  174.585678] usb 1-1.4: device descriptor read/64, error -32
[  174.773701] usb 1-1.4: device descriptor read/64, error -32
[  174.961486] usb 1-1.4: new full-speed USB device number 16 using xhci_hcd
[  175.041676] usb 1-1.4: device descriptor read/64, error -32
[  175.229773] usb 1-1.4: device descriptor read/64, error -32
[  175.337884] usb 1-1-port4: attempt power cycle
[  175.941555] usb 1-1.4: new full-speed USB device number 17 using xhci_hcd
[  175.941874] usb 1-1.4: Device not responding to setup address.
[  176.149707] usb 1-1.4: Device not responding to setup address.
[  176.357508] usb 1-1.4: device not accepting address 17, error -71
[  176.437531] usb 1-1.4: new full-speed USB device number 18 using xhci_hcd
[  176.437738] usb 1-1.4: Device not responding to setup address.
[  176.645684] usb 1-1.4: Device not responding to setup address.
[  176.853509] usb 1-1.4: device not accepting address 18, error -71
[  176.853977] usb 1-1-port4: unable to enumerate USB device
[  177.345300] hassio: port 7(veth3c0b3f6) entered disabled state
[  177.345886] veth5a2d872: renamed from eth0
[  177.413478] hassio: port 7(veth3c0b3f6) entered disabled state
[  177.415742] device veth3c0b3f6 left promiscuous mode
[  177.415801] kauditd_printk_skb: 1 callbacks suppressed
[  177.415804] audit: type=1700 audit(1609696079.651:213): dev=veth3c0b3f6 prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295
[  177.415819] hassio: port 7(veth3c0b3f6) entered disabled state
[  199.007362] hassio: port 7(vethd1af506) entered blocking state
[  199.007371] hassio: port 7(vethd1af506) entered disabled state
[  199.008047] device vethd1af506 entered promiscuous mode
[  199.008108] audit: type=1700 audit(1609696101.263:214): dev=vethd1af506 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[  199.411677] audit: type=1325 audit(1609696101.667:215): table=nat family=2 entries=0
[  199.418146] audit: type=1325 audit(1609696101.675:216): table=filter family=2 entries=0
[  199.428265] audit: type=1325 audit(1609696101.683:217): table=nat family=2 entries=5
[  199.431873] audit: type=1325 audit(1609696101.687:218): table=nat family=2 entries=7
[  199.438571] audit: type=1325 audit(1609696101.695:219): table=nat family=2 entries=8
[  199.442050] audit: type=1325 audit(1609696101.695:220): table=nat family=2 entries=10
[  199.446866] audit: type=1325 audit(1609696101.703:221): table=nat family=2 entries=11
[  199.451346] audit: type=1325 audit(1609696101.707:222): table=nat family=2 entries=12
[  199.455882] audit: type=1325 audit(1609696101.711:223): table=nat family=2 entries=13
[  199.499607] eth0: renamed from veth0ab24dc
[  199.514750] IPv6: ADDRCONF(NETDEV_CHANGE): vethd1af506: link becomes ready
[  199.514909] hassio: port 7(vethd1af506) entered blocking state
[  199.514918] hassio: port 7(vethd1af506) entered forwarding state
[  205.917779] usb 1-1.4: new full-speed USB device number 19 using xhci_hcd
[  206.001966] usb 1-1.4: device descriptor read/64, error -32
[  206.189983] usb 1-1.4: device descriptor read/64, error -32
[  206.377762] usb 1-1.4: new full-speed USB device number 20 using xhci_hcd
[  206.457957] usb 1-1.4: device descriptor read/64, error -32
[  206.645987] usb 1-1.4: device descriptor read/64, error -32
[  206.754200] usb 1-1-port4: attempt power cycle
[  207.357781] usb 1-1.4: new full-speed USB device number 21 using xhci_hcd
[  207.357993] usb 1-1.4: Device not responding to setup address.
[  207.565971] usb 1-1.4: Device not responding to setup address.
[  207.773772] usb 1-1.4: device not accepting address 21, error -71
[  207.857781] usb 1-1.4: new full-speed USB device number 22 using xhci_hcd
[  207.857986] usb 1-1.4: Device not responding to setup address.
[  208.065962] usb 1-1.4: Device not responding to setup address.
[  208.273767] usb 1-1.4: device not accepting address 22, error -71
[  208.274246] usb 1-1-port4: unable to enumerate USB device
[  208.772199] hassio: port 7(vethd1af506) entered disabled state
[  208.774141] veth0ab24dc: renamed from eth0
[  208.854769] hassio: port 7(vethd1af506) entered disabled state
[  208.855858] device vethd1af506 left promiscuous mode
[  208.855880] hassio: port 7(vethd1af506) entered disabled state
[  208.855915] kauditd_printk_skb: 1 callbacks suppressed
[  208.855919] audit: type=1700 audit(1609696111.094:225): dev=vethd1af506 prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295
[  234.078600] hassio: port 7(veth803d5b6) entered blocking state
[  234.078608] hassio: port 7(veth803d5b6) entered disabled state
[  234.078829] device veth803d5b6 entered promiscuous mode
[  234.078894] audit: type=1700 audit(1609696136.334:226): dev=veth803d5b6 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[  234.488589] audit: type=1325 audit(1609696136.742:227): table=nat family=2 entries=0
[  234.495914] audit: type=1325 audit(1609696136.750:228): table=filter family=2 entries=0
[  234.505443] audit: type=1325 audit(1609696136.758:229): table=nat family=2 entries=5
[  234.508544] audit: type=1325 audit(1609696136.762:230): table=nat family=2 entries=7
[  234.514920] audit: type=1325 audit(1609696136.770:231): table=nat family=2 entries=8
[  234.517915] audit: type=1325 audit(1609696136.770:232): table=nat family=2 entries=10
[  234.522351] audit: type=1325 audit(1609696136.778:233): table=nat family=2 entries=11
[  234.526711] audit: type=1325 audit(1609696136.782:234): table=nat family=2 entries=12
[  234.530670] audit: type=1325 audit(1609696136.786:235): table=nat family=2 entries=13
[  234.571578] eth0: renamed from veth0b1b8d2
[  234.595480] IPv6: ADDRCONF(NETDEV_CHANGE): veth803d5b6: link becomes ready
[  234.595713] hassio: port 7(veth803d5b6) entered blocking state
[  234.595726] hassio: port 7(veth803d5b6) entered forwarding state
[  240.981974] usb 1-1.4: new full-speed USB device number 23 using xhci_hcd
[  241.062180] usb 1-1.4: device descriptor read/64, error -32
[  241.250175] usb 1-1.4: device descriptor read/64, error -32
[  241.437985] usb 1-1.4: new full-speed USB device number 24 using xhci_hcd
[  241.518223] usb 1-1.4: device descriptor read/64, error -32
[  241.706165] usb 1-1.4: device descriptor read/64, error -32
[  241.814427] usb 1-1-port4: attempt power cycle
[  242.418008] usb 1-1.4: new full-speed USB device number 25 using xhci_hcd
[  242.418229] usb 1-1.4: Device not responding to setup address.
[  242.626163] usb 1-1.4: Device not responding to setup address.
[  242.833982] usb 1-1.4: device not accepting address 25, error -71
[  242.913983] usb 1-1.4: new full-speed USB device number 26 using xhci_hcd
[  242.914183] usb 1-1.4: Device not responding to setup address.
[  243.122214] usb 1-1.4: Device not responding to setup address.
[  243.329977] usb 1-1.4: device not accepting address 26, error -71
[  243.330479] usb 1-1-port4: unable to enumerate USB device
[  243.839832] hassio: port 7(veth803d5b6) entered disabled state
[  243.840609] veth0b1b8d2: renamed from eth0
[  243.919029] hassio: port 7(veth803d5b6) entered disabled state
[  243.920178] device veth803d5b6 left promiscuous mode
[  243.920264] kauditd_printk_skb: 1 callbacks suppressed
[  243.920268] audit: type=1700 audit(1609696146.154:237): dev=veth803d5b6 prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295
[  243.920718] hassio: port 7(veth803d5b6) entered disabled state
[  265.242926] hassio: port 7(vethdc55a18) entered blocking state
[  265.242936] hassio: port 7(vethdc55a18) entered disabled state
[  265.243174] device vethdc55a18 entered promiscuous mode
[  265.243246] audit: type=1700 audit(1609696167.502:238): dev=vethdc55a18 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[  265.627376] audit: type=1325 audit(1609696167.886:239): table=nat family=2 entries=0
[  265.634271] audit: type=1325 audit(1609696167.890:240): table=filter family=2 entries=0
[  265.644298] audit: type=1325 audit(1609696167.902:241): table=nat family=2 entries=5
[  265.648444] audit: type=1325 audit(1609696167.906:242): table=nat family=2 entries=7
[  265.655856] audit: type=1325 audit(1609696167.914:243): table=nat family=2 entries=8
[  265.659615] audit: type=1325 audit(1609696167.918:244): table=nat family=2 entries=10
[  265.664023] audit: type=1325 audit(1609696167.922:245): table=nat family=2 entries=11
[  265.668488] audit: type=1325 audit(1609696167.926:246): table=nat family=2 entries=12
[  265.671972] audit: type=1325 audit(1609696167.930:247): table=nat family=2 entries=13
[  265.716449] eth0: renamed from veth18019c6
[  265.747437] IPv6: ADDRCONF(NETDEV_CHANGE): vethdc55a18: link becomes ready
[  265.747616] hassio: port 7(vethdc55a18) entered blocking state
[  265.747626] hassio: port 7(vethdc55a18) entered forwarding state
[  272.286346] usb 1-1.4: new full-speed USB device number 27 using xhci_hcd
[  272.366543] usb 1-1.4: device descriptor read/64, error -32
[  272.554525] usb 1-1.4: device descriptor read/64, error -32
[  272.742368] usb 1-1.4: new full-speed USB device number 28 using xhci_hcd
[  272.822566] usb 1-1.4: device descriptor read/64, error -32
[  273.010528] usb 1-1.4: device descriptor read/64, error -32
[  273.118746] usb 1-1-port4: attempt power cycle
[  273.722330] usb 1-1.4: new full-speed USB device number 29 using xhci_hcd
[  273.722550] usb 1-1.4: Device not responding to setup address.
[  273.930545] usb 1-1.4: Device not responding to setup address.
[  274.138359] usb 1-1.4: device not accepting address 29, error -71
[  274.218330] usb 1-1.4: new full-speed USB device number 30 using xhci_hcd
[  274.218531] usb 1-1.4: Device not responding to setup address.
[  274.426604] usb 1-1.4: Device not responding to setup address.
[  274.634429] usb 1-1.4: device not accepting address 30, error -71
[  274.634902] usb 1-1-port4: unable to enumerate USB device
[  275.138837] hassio: port 7(vethdc55a18) entered disabled state
[  275.139034] veth18019c6: renamed from eth0
[  275.224164] hassio: port 7(vethdc55a18) entered disabled state
[  275.226926] device vethdc55a18 left promiscuous mode
[  275.226949] hassio: port 7(vethdc55a18) entered disabled state
[  275.226977] kauditd_printk_skb: 1 callbacks suppressed
[  275.226980] audit: type=1700 audit(1609696177.466:249): dev=vethdc55a18 prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295
[  294.290690] usb 1-1.4: new full-speed USB device number 31 using xhci_hcd
[  294.397453] usb 1-1.4: New USB device found, idVendor=0764, idProduct=0601, bcdDevice= 2.00
[  294.397472] usb 1-1.4: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[  294.397485] usb 1-1.4: Product: PR1500ELCD
[  294.397497] usb 1-1.4: Manufacturer: CPS
[  294.397509] usb 1-1.4: SerialNumber: PRTGN2000005
[  294.412230] hid-generic 0003:0764:0601.0001: item 0 1 0 11 parsing failed
[  294.412309] hid-generic: probe of 0003:0764:0601.0001 failed with error -22
[  302.528745] hassio: port 7(veth47d38d2) entered blocking state
[  302.528755] hassio: port 7(veth47d38d2) entered disabled state
[  302.529299] device veth47d38d2 entered promiscuous mode
[  302.529361] audit: type=1700 audit(1609696204.785:250): dev=veth47d38d2 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[  302.924045] audit: type=1325 audit(1609696205.181:251): table=nat family=2 entries=0
[  302.931446] audit: type=1325 audit(1609696205.189:252): table=filter family=2 entries=0
[  302.942567] audit: type=1325 audit(1609696205.197:253): table=nat family=2 entries=5
[  302.946278] audit: type=1325 audit(1609696205.201:254): table=nat family=2 entries=7
[  302.953558] audit: type=1325 audit(1609696205.209:255): table=nat family=2 entries=8
[  302.957324] audit: type=1325 audit(1609696205.213:256): table=nat family=2 entries=10
[  302.962369] audit: type=1325 audit(1609696205.217:257): table=nat family=2 entries=11
[  302.967542] audit: type=1325 audit(1609696205.225:258): table=nat family=2 entries=12
[  302.972041] audit: type=1325 audit(1609696205.229:259): table=nat family=2 entries=13
[  303.013864] eth0: renamed from veth001b7c7
[  303.028111] IPv6: ADDRCONF(NETDEV_CHANGE): veth47d38d2: link becomes ready
[  303.028250] hassio: port 7(veth47d38d2) entered blocking state
[  303.028258] hassio: port 7(veth47d38d2) entered forwarding state
[  367.567100] udevd[192]: starting version 3.2.9
[  367.572016] udevd[193]: starting eudev-3.2.9
~ $

Description of problem:

I was using my Raspberry Pi4 4GB along with the Network UPS Tools to monitor my Cyberpower PR1500ELCD UPS.
UPS was connected to raspberry via USB and it worked flawlessly until I switched to a fresh install on HA OS 5.9 on an external USB SSD.

HA works very well on the SSD now but when the HA Host reboot, HA OS does not see the UPS.
I need to manually detach the UPS USB cable and reattach it to make it work.

I think that this is a common problem for connected USB devices when using a USB SSD instead of a microSD.

Thank you guys!!!

USB permissions problem

Problem/Motivation

I can see the configured USB port in Hardware info (Supervisor>System>Hardware) :
serial:
/dev/ttyUSB0
Despite that, when ran, addon-nut gives permissions error.

LOG


[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: ac56583
 You are running the latest version of this add-on.
 System: Raspbian GNU/Linux 10 (buster)  (armv7 / raspberrypi3)
 Home Assistant Core: 0.105.4
 Home Assistant Supervisor: 200
-----------------------------------------------------------
 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... 
[19:58:44] INFO: Setting mode to netserver...
[19:58:44] INFO: Generating /etc/nut/upsd.users...
[19:58:45] INFO: Configuring user: nutty
[19:58:46] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[19:58:48] INFO: Configuring Device named apcsmart-ups...
[19:58:48] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 3.8.0-3396-gcdc7c4b5b1
Network UPS Tools - APC Smart protocol driver 3.1 (3.8.0-3396-gcdc7c4b5b1)
Fatal error: unusable configuration
APC command table version 3.1

Unable to open /dev/ttyUSB0: No such file or directory

Things to try:

 - Check 'port=' in ups.conf

 - Check owner/permissions of all parts of path

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.

Poll UPS failed - Data stale

Problem/Motivation

NUT stops working after around 4 days.
When this happens, all related entities in Home Assistant become Unknown.

Expected behavior

Since the UPS is stable (it was not shutdown and has been working all the time), NUT should be working.

Actual behavior

Everytime I start NUT, after around 4 or 5 days, it hangs somehow and in the logs, it can be seen:
62165.284809 Poll UPS [myups@localhost] failed - Data stale
62170.285543 Poll UPS [myups@localhost] failed - Data stale
62175.286346 Poll UPS [myups@localhost] failed - Data stale
62180.287097 Poll UPS [myups@localhost] failed - Data stale
62185.287891 Poll UPS [myups@localhost] failed - Data stale
62190.288624 Poll UPS [myups@localhost] failed - Data stale
When this happens, all related entities in Home Assistant become Unknown.

Steps to reproduce

I have been using EDGE repo, NUT version 5715820, HA 0.106.5, HassOS 3.11, Supervisor 208.
The same happened in previous versions of HA/HassOS.
My addon configuration:
"
users:

username: myupsuser
password: myupsrandompassword
instcmds:
- all
  actions: []
  devices:
name: myups
driver: usbhid-ups
port: auto
config: [] #I was using before pollfreq = 5
mode: netserver
shutdown_host: 'false'
shutdown_hassio: 'false'
i_like_to_be_pwned: 'false'
list_usb_devices: 'true'
"

Proposed changes

If there no code issue is found, maybe a new parameter for restarting NUT can be created, to restart itself after a couple of days.

Proxmox HASSIO NUT will not install

Problem

NUT component will not install and did not transfer when upgrading from Raspberry Pi HASSIO to Proxmox. All other components transferred properly using the snapshot. Adding the repository does not add the component.

(Why the issue was filed)

I rely on the NUT to monitor power in my house to prevent floods from sump pump failure.

Expected behavior

It worked great before and now just will not install

(What you expected to happen)
Someone to help to get it functional again.

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Tecnoware ERA 1500

Problem/Motivation

addon not start

Actual behavior

i use this configuration:
users:

username: nutuser
password: edsdf3
instcmds:
- all
  actions: []
  devices:
name: myups
driver: blazer_usb
port: auto
config: []
mode: netserver
shutdown_host: 'false'

log is this:

[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.2.0
You are running the latest version of this add-on.
System: HassOS 4.9 (armv7 / raspberrypi4)
Home Assistant Core: 0.110.5
Home Assistant Supervisor: 227

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...
[00:56:43] INFO: Setting mode to netserver...
[00:56:43] INFO: Generating /etc/nut/upsd.users...
[00:56:43] INFO: Configuring user: nutuser
[00:56:44] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[00:56:45] INFO: Configuring Device named myups...
[00:56:45] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 3.8.0-3396-gcdc7c4b5b1
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (3.8.0-3396-gcdc7c4b5b1)
Supported UPS detected with megatec/old protocol
Rating information unavailable
Vendor information unavailable
No values provided for battery high/low voltages in ups.conf
Using 'guestimation' (low: -0.866667, high: -1.083333)!
Battery runtime will not be calculated (runtimecal not set)
Startup timer elapsed, continuing...
[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 try to set vendorid and productid but not change

I've tried everything, I don't understand why it doesn't work

Best regards
Giacomazzi Daniele

Eaton Ellipse ECO UPS not detected by the add-on

Problem/Motivation

HA system detects the USB device, but the add-on doesn't find it.

Expected behavior

It should work as the hardware is supported by NUT.

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: Home Assistant OS 5.10 (armv7 / raspberrypi3)
Home Assistant Core: 2021.1.5
Home Assistant Supervisor: 2021.01.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...
[18:08:48] INFO: Setting mode to netserver...
[18:08:48] 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
[18:08:49] INFO: Generating /etc/nut/upsd.users...
[18:08:49] INFO: Configuring user: nut4ha
[18:08:50] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[18:08:52] INFO: Configuring Device named eaton...
[18:08: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)
[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.

Steps to reproduce

Eaton Ellipse ECO 1200AV UPS.
Latest 32bit image available for a RaspberryPi 3.
Install the Terminal & SSH add-on.
Install the NUT add-on.
NUT add-on configuration:

users:
  - username: nutuser
    password: ********
    instcmds:
      - all
    actions: []
devices:
  - name: eaton
    driver: usbhid-ups
    port: auto
    config:
      - vendorid = 0463
mode: netserver
shutdown_host: 'false'
list_usb_devices: 'true'

When I connect to the HA system through SSH and run the following commands, I can see the data of the USB device in the output messages, but the add-on can't find the UPS. I also tried the EDGE version of the add-on, with no luck.

~ $ dmesg

...
[    5.999701] usb 1-1.2: New USB device found, idVendor=0463, idProduct=ffff, bcdDevice= 1.00
[    5.999710] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=4
[    5.999717] usb 1-1.2: Product: Ellipse ECO
[    5.999723] usb 1-1.2: Manufacturer: EATON
[    5.999729] usb 1-1.2: SerialNumber: 000000000
...
[    9.329771] hid-generic 0003:0463:FFFF.0001: hiddev96,hidraw0: USB HID v10.10 Device [EATON Ellipse ECO] on usb-3f980000.usb-1.2/input0
...

~ $ lsusb

Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:2514
Bus 001 Device 002: ID 0424:2514
Bus 001 Device 005: ID 0424:7800
Bus 001 Device 004: ID 0463:ffff

Permission denied /dev/ttyS0

Problem/Motivation

Using a device on /dev/ttyS0 gives permission denied.

Expected behavior

It should be able to access all serial ports.

Actual behavior

From addon log:

Unable to open /dev/ttyS0: Permission denied
  Current user id: nut (100)
Serial port owner: root (0)
Serial port group: audio (18)
     Mode of port: 0660

Steps to reproduce

users:
  - username: redacted
    password: redacted
    instcmds:
      - all
    actions: []
devices:
  - name: ups1
    driver: powerpanel
    port: /dev/ttyS0
    config: []
mode: netserver
shutdown_host: 'false'

Proposed changes

Please let me know if this is an issue with the supervisor and I should file this there instead (I suspect it might be).

Increase polling interval

Hi there,

I've hassio on a rpi 3. I have a Mecer UPS connected via USB.

Problem/Motivation

When the UPS state changes from OL to OB it sometimes takes over a minute before the sensor registers a change.

Is there any way to increase the polling frequency?

When I have a power failure I use the state change to turn some emergency/backup lights on.

My configuration for NUT is :

users:
  - username: xxxx
    password: xxxx
    instcmds:
      - all
    actions: []
devices:
  - name: mecer
    driver: nutdrv_qx
    port: auto
    config:
      - vendorid = 0665
      - productid = 5161
      - subdriver = cypress
      - protocol = mustek
mode: netserver
shutdown_hassio: 'false'
list_usb_devices: 'true'

Nut addon absent in community addons

Problem/Motivation

unable to install nut add-on

(Why the issue was filed)

Expected behavior

appearance of NUT add-on in add-on store

(What you expected to happen)

Actual behavior

addon does not populate in add-on store when the repository is added to the community addon-on

(What actually happened)
nothing

Steps to reproduce

add https://github.com/hassio-addons/repository to community add-on as indicated in the instructions

(How can someone else make/see it happen)
add https://github.com/hassio-addons/repository to community add-on as indicated in the instructions

Proposed changes

add NUT add-on to the community add-ons

(If you have a proposed change, workaround or fix,
describe the rationale behind it)
the instructions on the addon webpage, are not working

GitHub
hassio-addons/repository
Community Hass.io Add-ons for Home Assistant. Contribute to hassio-addons/repository development by creating an account on GitHub.

It fails to start after the latest update. Add-on version: 0.2.1

Problem/Motivation

It fails to start after the latest update.

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.2.1
 You are running the latest version of this add-on.
 System: HassOS 4.12  (armv7 / raspberrypi3)
 Home Assistant Core: 0.114.3
 Home Assistant Supervisor: 235
-----------------------------------------------------------
 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... 
[14:09:37] INFO: Setting mode to netserver...
[14:09:37] INFO: Generating /etc/nut/upsd.users...
[14:09:38] INFO: Configuring user: monuser
[14:09:40] INFO: Configuring Device named ups...
[14:09:41] INFO: Starting the UPS drivers...
Error relocating /usr/sbin/upsdrvctl: __select_time64: symbol not found
Error relocating /usr/sbin/upsdrvctl: __difftime64: symbol not found
Error relocating /usr/sbin/upsdrvctl: __gettimeofday_time64: symbol not found
Error relocating /usr/sbin/upsdrvctl: __stat_time64: symbol not found
[cont-init.d] nut.sh: exited 127.
[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.

Error when starting addon NUT

Problem/Motivation

Error when starting addon, log for NUT shows:

INFO: Starting the UPS information server
0.000000 fopen /var/run/nut/upsd.pid: No such file or directory

Expected behavior

Should be working

Actual behavior

Nothing actually happened, seems to be running but nothing shows up because rest of log shows:
Network UPS Tools upsd 3.8.0-3727-geade014bef
0.000991 listening on 0.0.0.0 port 3493
0.002534 Connected to UPS [myups]: usbhid-ups-myups

Steps to reproduce

I can only speak for my APC SUA1000 usb, but just by installing and running I get the same fault.

Proposed changes

Ok, I am far from an expert on the issue, but when searching the error I get from the log it seems there is something that is not getting the right permission.

New device (same as older)

Problem/Motivation

New device appeared in the integration but is the same device

Expected behavior

no new device

Actual behavior

older device is unavailable

Steps to reproduce

Don't know

Add-on stopped recognising UPS

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.

[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

Steps to reproduce

My add-on config:

users:
  - username: upsmon_local
    password: '!secret nut_password'
    instcmds:
      - all
    actions: []
devices:
  - name: UPS
    driver: blazer_usb
    port: auto
    config: []
mode: netserver
shutdown_host: 'true'

Entries on hardware list:

- name: 2-2
    sysfs: '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-2'
    dev_path: /dev/bus/usb/002/003
    subsystem: usb
    by_id: null
    attributes:
      BUSNUM: '002'
      DEVNAME: /dev/bus/usb/002/003
      DEVNUM: '003'
      DEVPATH: '/devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-2'
      DEVTYPE: usb_device
      DRIVER: usb
      ID_BUS: usb
      ID_MODEL: MEC0003
      ID_MODEL_ENC: MEC0003
      ID_MODEL_ID: '0000'
      ID_REVISION: '0100'
      ID_SERIAL: MEC_MEC0003
      ID_USB_INTERFACES: ':030000:'
      ID_VENDOR: MEC
      ID_VENDOR_ENC: MEC
      ID_VENDOR_ID: '0001'
      MAJOR: '189'
      MINOR: '130'
      PRODUCT: 1/0/100
      SUBSYSTEM: usb
      TYPE: 0/0/0
      USEC_INITIALIZED: '7399017'
  - name: hidraw0
    sysfs: >-
      /sys/devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-2/2-2:1.0/0003:0001:0000.0001/hidraw/hidraw0
    dev_path: /dev/hidraw0
    subsystem: hidraw
    by_id: null
    attributes:
      DEVNAME: /dev/hidraw0
      DEVPATH: >-
        /devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-2/2-2:1.0/0003:0001:0000.0001/hidraw/hidraw0
      MAJOR: '247'
      MINOR: '0'
      SUBSYSTEM: hidraw
  - name: hiddev0
    sysfs: >-
      /sys/devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-2/2-2:1.0/usbmisc/hiddev0
    dev_path: /dev/usb/hiddev0
    subsystem: usbmisc
    by_id: null
    attributes:
      DEVNAME: /dev/usb/hiddev0
      DEVPATH: >-
        /devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-2/2-2:1.0/usbmisc/hiddev0
      MAJOR: '180'
      MINOR: '96'
      SUBSYSTEM: usbmisc

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!

Not Available in hassio-addons/repository

Is there a reason this addon is not available in hassio-addons/repository?
I was using the version from https://github.com/colindunn/hassio-addons but now see this version is being updated but it's not in the repo.
I installed it locally and it's working.

GitHub
colindunn/hassio-addons
Hass.io Addons. Contribute to colindunn/hassio-addons development by creating an account on GitHub.

NUT from community EDGE works, NUT from community don't.

Problem/Motivation

Same config.
The NUT from community EDGE works, NUT from community don't.

Expected behavior

that it work, some sensors should be visible

Actual behavior

If I install the NUT addon from the community EDGE I can see all the sensors correctly working.
If I install the NUT addon from the comminity repo I see no sensors and I have some errors in the log.

Platform nut not ready yet. Retrying in 60 seconds.
23:44:34 – Sensore (WARNING) - il messaggio si è verificato per la prima volta alle 23:43:23 e compare 2 volte
NUT Sensor has no data, unable to set up
23:44:34 – nut (ERROR) - il messaggio si è verificato per la prima volta alle 23:42:42 e compare 3 volte
Setup of sensor platform nut is taking over 10 seconds.
23:44:34 – Sensore (WARNING) - il messaggio si è verificato per la prima volta alle 23:42:42 e compare 3 volte
Failure getting NUT ups alias, Socket error.
23:44:29 – nut (ERROR) - il messaggio si è verificato per la prima volta alle 23:42:37 e compare 3 volte

addon config:

users:

username: admin
password: XXX
instcmds:

all
actions: []
devices:

name: myups
driver: usbhid-ups
port: auto
config: []
mode: netserver
shutdown_host: 'false'
shutdown_hassio: 'false'

configuration.taml

sensor:
  - platform: nut
    scan_interval: 5
    name: "CyberPower PR1500ELCD"
    host: 40817795-nut
    username: user
    password: !secret nut
    resources:
      - ups.status.display
      - ups.timer.reboot
      - battery.voltage
      - ups.firmware.aux
      - ups.mfr
      - battery.runtime.low
      - ups.delay.shutdown
      - ups.load
      - ups.realpower.nominal
      - battery.charge.warning
      - battery.charge.low
      - ups.vendorid
      - ups.timer.shutdown
      - ups.test.result
      - ups.firmware
      - ups.productid
      - battery.runtime
      - battery.type
      - ups.model
      - ups.beeper.status
      - battery.charge
      - input.sensitivity
      - input.transfer.low
      - input.transfer.high
      - input.voltage
      - input.voltage.nominal
      - input.transfer.reason
      - output.current
      - output.frequency
      - output.voltage
      - output.voltage.nominal

Immediate shutdown

Problem/Motivation

First thanks for the addon. Even if it is not released yet it is already working really nice.
I notice that when the main power disappear he go in shutdown immediately (for the moment only the addon I'm still with shutdown_hassio set to false).

Expected behavior

Is this the expected behavior? I expect to see the shutdown not before the current battery.charge was lower that the battery.charge.low.
Am I correct?

Actual behavior

Immediate shutdown

Steps to reproduce

Unplug main UPS power.

Config and logs

{
  "users": [
    {
      "username": "!secret nut_username",
      "password": "!secret nut_password",
      "instcmds": [
        "all"
      ],
      "actions": []
    }
  ],
  "devices": [
    {
      "name": "myups",
      "driver": "usbhid-ups",
      "port": "auto",
      "config": []
    }
  ],
  "mode": "netserver",
  "shutdown_hassio": "false"
}

After boot:

[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... 
-----------------------------------------------------------
 Hass.io Add-on: Network UPS Tools
 Manage battery backup (UPS) devices
-----------------------------------------------------------
 Add-on version: 4213c06
 You are running the latest version of this add-on.
 System: HassOS 3.8  (amd64 / intel-nuc)
 Home Assistant version: 0.103.6
 Supervisor version: 195
-----------------------------------------------------------
 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... 
[11:52:54] INFO: Setting mode to netserver...
[11:52:55] INFO: Generating /etc/nut/upsd.users...
[11:52:57] INFO: Configuring user: adorem
[11:52:59] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[11:53:06] INFO: Configuring Device named myups...
[11:53:06] INFO: Starting the UPS drivers...
Network UPS Tools - UPS driver controller 3.8.0-3220-g866b921892
Network UPS Tools - Generic HID driver 0.41 (3.8.0-3220-g866b921892)
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.
[11:53:14] INFO: Starting the UPS information server...
Network UPS Tools upsd 3.8.0-3220-g866b921892
   0.000000	fopen /var/run/nut/upsd.pid: No such file or directory
   0.001387	listening on 0.0.0.0 port 3493
   0.004994	Connected to UPS [myups]: usbhid-ups-myups
[11:53:14] INFO: Starting the UPS monitor and shutdown controller...
Network UPS Tools upsmon 3.8.0-3220-g866b921892
   0.000000	fopen /var/run/upsmon.pid: No such file or directory
   0.001451	Using power down flag file /etc/killpower
   0.002919	UPS: myups@localhost (master) (power value 1)
   0.003834	debug level is '1'
   0.012264	Trying to connect to UPS [myups@localhost]
   0.039859	User [email protected] logged into UPS [myups]
   0.015698	Logged into UPS myups@localhost

After main power unplug:

  50.025322	Critical UPS: myups@localhost
  50.028619	Shutting down any UPSes in MASTER mode...
  50.054375	Client [email protected] set FSD on UPS [myups]
  50.029327	This system is a master... waiting for slave logout...
  50.031061	Executing automatic power-fail shutdown
{"message": "Event nut.ups_event fired."}{"message": "Event nut.ups_event fired."}{"message": "Event nut.ups_event fired."}

My UPS:

[email protected]:/$ upsc myups
battery.charge: 86
battery.charge.low: 20
battery.runtime: 554
battery.type: PbAc
device.mfr: EATON
device.model: Protection Station 800
device.serial: AN2E49008
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 5
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 3.8.0-3220-g866b921892
driver.version.data: MGE HID 1.39
driver.version.internal: 0.41
input.transfer.high: 264
input.transfer.low: 184
outlet.1.desc: PowerShare Outlet 1
outlet.1.id: 2
outlet.1.status: on
outlet.1.switchable: no
outlet.2.desc: PowerShare Outlet 2
outlet.2.id: 3
outlet.2.status: on
outlet.2.switchable: no
outlet.desc: Main Outlet
outlet.id: 1
outlet.power: 25
outlet.switchable: no
output.frequency.nominal: 50
output.voltage: 230.0
output.voltage.nominal: 230
ups.beeper.status: disabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.firmware: 1.13
ups.load: 22
ups.mfr: EATON
ups.model: Protection Station 800
ups.power.nominal: 800
ups.productid: ffff
ups.serial: AN2E49008
ups.status: OL
ups.timer.shutdown: 0
ups.timer.start: 0
ups.vendorid: 0463
[email protected]:/$

Password issue

using a password with special characters like @ or # mine was @1234567890# the add-on require the '' and hassio is not able to connect the integration when you try, the only feedback that it gives you back is that is not able to connect

Not powering down the UPS

Problem/Motivation

On Low Battery (LOWBATT), addon does not shut down UPS.

Expected behavior

When UPS battery get low, addon-nut should turn off UPS load (FSD) so that all devices that are attached to it are forcibly rebooted. The master should command the UPS into
the “forced shutdown” mode.

Actual behavior

On Low battery, I get LOWBATT notification.
It is followed by SHUTDOWN notification - Auto logout and shutdown proceeding.
The Home assistant gets shutdown but UPS continues and does not shutdown.

Steps to reproduce

Switch the mains Power to UPS (ONBATT)
Wait for Low battery condition (LOWBATT)
Below is the configuration file :
users:

username: '!secret nut_u'
password: '!secret nut_p'
upsmon: master
instcmds:
- all
  actions:
- set
- fsd
  devices:
name: cyberups
driver: usbhid-ups
port: auto
config:
- lowbatt=15
- offdelay=180
- ondelay=0
  mode: netserver
  shutdown_host: 'true'
  log_level: debug

Proposed changes

As part of the shutdown, the addon should shutdown UPS - to power off the load.
FSD "UPS %s: Forced shutdown in progress."

hassio-addons / addon-nut Goto Github PK

addon-nut's Introduction

Home Assistant Community Add-on: Network UPS Tools

About

Support

Contributing

Authors & contributors

We have got some Home Assistant add-ons for you

License

addon-nut's People

Contributors

Stargazers

Watchers

Forkers

addon-nut's Issues

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

Problem/Motivation

Expected behavior

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

Problem/Motivation

Be sure to check the log above, line by line, for hints.

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

Add-on: Network UPS Tools Manage battery backup (UPS) devices

Add-on version: 0.1.2 You are running the latest version of this add-on. System: HassOS 3.12 (armv7 / raspberrypi4) Home Assistant Core: 0.108.3 Home Assistant Supervisor: 217

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Problem/Motivation

Problem/Motivation

Expected behavior

Actual behavior

Other Info

Problem/Motivation

Add-on: Network UPS Tools
Manage battery backup (UPS) devices

Add-on version: 0.1.2
You are running the latest version of this add-on.
System: HassOS 3.12 (armv7 / raspberrypi4)
Home Assistant Core: 0.108.3
Home Assistant Supervisor: 217

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

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.