Nut addon issues, not the edge version!

@mattlward wrote:

First off, running latest HA with Hassio on an Ubuntu system running 18.04 with docker running the HA instance and addons.

I have 5 ups’s that I would like to get working, 1 directly attached and 4 remote nut clients supported via Raspberry Pi’s. I was running the edge version of Nut and all was working well, but I decide to convert to the more supported non-edge version and it is driving me nuts. Each time that I reload HA, I am getting a new integration request for Nut, even though the old one is there and working.

image1103×549 89.1 KB

Please note the existing nut config, the first is the directly connected unit and the second is the remote UPS.

Data gathered from both installed UPS units.

image1003×418 25.2 KB

I am getting the following in my logs:

2020-06-03 09:21:53 ERROR (MainThread) [homeassistant.components.nut] NUT Sensor has no data, unable to set up
2020-06-03 09:21:53 WARNING (MainThread) [homeassistant.config_entries] Config entry for nut not ready yet. Retrying in 80 seconds.
2020-06-03 09:23:19 ERROR (MainThread) [homeassistant.components.nut] Error fetching NUT resource status data: Error fetching UPS state
2020-06-03 09:23:19 ERROR (MainThread) [homeassistant.components.nut] NUT Sensor has no data, unable to set up
2020-06-03 09:23:19 WARNING (MainThread) [homeassistant.config_entries] Config entry for nut not ready yet. Retrying in 80 seconds.

The server appears to think, to me, that I have a UPS that it is not managing or that Nut is not installed in the first place.

This is my nut config within the addon, this is the directly connected unit.
nut config:

users:
  - username: xxx
    password: 'yyy'
    instcmds:
      - all
    actions: []
  - username: xxx
    password: 'yyy'
    instcmds:
      - all
    actions: []
devices:
  - name: DR_UPS
    alias: dr_ups
    driver: usbhid-ups
    port: auto
    config:
      - vendorid = 0764*
mode: netserver
shutdown_host: 'false'
shutdown_hassio: 'false'

This is my config in sensors.yaml:

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

Within the addon config, it seems that I only need the directly connected UPS defined? Maybe that is the mistake, but I am not sure how to set the addon config for a netclient and net server, if that is the case.

Posts: 1

Participants: 1

Read full topic