I am able to get the NUT add-on for Home Assistant to act as a client for one of
the UPS units attached to my NUT-server running on another Raspberry Pi. What I
am unable to do is to get it to attach to a second. I can attach to the second,
or the first, but just not the second and first if that makes sense. Does anyone
run this add on ?
My YAML:
devices:
- config:
- nada
driver: usbhid-ups
name: myups
port: auto
mode: netclient
shutdown_host: false
users:
- actions: []
instcmds:
- all
password: XYZ
username: ABC
remote_ups_name: apc600
remote_ups_host: 192.168.1.232
remote_ups_user: XYZ
remote_ups_password: ABC
upsd_maxage: 10
log_level: debug
-----
The problem with the world is that the intelligent people are full of doubts,
while the stupid ones are full of confidence.
"z.kevino--- via Nut-upsuser" <nut-upsuser at alioth-lists.debian.net> writes:> I am able to get the NUT add-on for Home Assistant to act as a client > for one of the UPS units attached to my NUT-server running on another > Raspberry Pi. What I am unable to do is to get it to attach to a > second. I can attach to the second, or the first, but just not the > second and first if that makes sense. Does anyone run this add on ?I think it's very likely that this is an HA issue not a NUT issue. I have run it, but only with 1 UPS. It is IMHO a clue that the entities have display names that don't include the device name (even if the nerd-name does). For example, I have a UPS named "foo" (not its real name :-) and I get sensor.foo_ups_input_voltage V_in Instead the display name defaulting to "Foo V_in". It looks like your YAML was munged. But the documentation https://www.home-assistant.io/integrations/nut says to set up the integration via the UI. I have an entry for my UPS in .homeassistant/.storage/core.config_entries In theory, a second instance should work fine, and if not it's a bug. But you'll have to be on 2022.8 and use the UI before they want to hear about it, probably.> My YAML: > > devices: > - config: > - nada > driver: usbhid-upsI'm surprised to see driver; that's configured in NUT and HA shouldn't care.> name: myups > port: auto > mode: netclient > shutdown_host: falseagain these two are surprising.> users: > - actions: [] > instcmds: > - all > password: XYZ > username: ABC > remote_ups_name: apc600 > remote_ups_host: 192.168.1.232 > remote_ups_user: XYZ > remote_ups_password: ABC > upsd_maxage: 10 > log_level: debug-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 194 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220814/05e7e2fc/attachment.sig>
Thanks for the reply. I was only showing the yaml to make it easier to send to this email list as I didn?t think a screenshot of the UI would make it through. The thing to note here is that these UPS are not connected to the home assistant raspberry pi, but are on another raspberry pi device which runs as the server. So the NUT add on is running as a client. I?ll start the process over and see if I can get it to work. Appreciate your kindness. As an aside, I am running on the latest Home Assistant 2022.8.4 Supervisor 2022.08.3 Operating System 8.4 Frontend 20220802.0 - latest ----- The problem with the world is that the intelligent people are full of doubts, while the stupid ones are full of confidence.> On Aug 13, 2022, at 23:56, z.kevino at gmail.com wrote: > > ?I am able to get the NUT add-on for Home Assistant to act as a client for one of the UPS units attached to my NUT-server running on another Raspberry Pi. What I am unable to do is to get it to attach to a second. I can attach to the second, or the first, but just not the second and first if that makes sense. Does anyone run this add on ? > My YAML: > > devices: > - config: > - nada > driver: usbhid-ups > name: myups > port: auto > mode: netclient > shutdown_host: false > users: > - actions: [] > instcmds: > - all > password: XYZ > username: ABC > remote_ups_name: apc600 > remote_ups_host: 192.168.1.232 > remote_ups_user: XYZ > remote_ups_password: ABC > upsd_maxage: 10 > log_level: debug > > > > ----- > > The problem with the world is that the intelligent people are full of doubts, while the stupid ones are full of confidence.-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220814/a3b93822/attachment.htm>
I did a quick experiment.
Machine A runs NetBSD 9, ups-nut 2.8.0, and Home Assistant Core
2022.8.4. It has a ups foo. Note there is no "nut addon" involved,
or
any "addon" at all. ("addon" is a Home Assistant concept
for the Home
Assistant OS or Supervisor running progams not from Home Assistant.)
Machine A runs NetBSD 9, ups-nut 2.8.0. It has a ups bar.
Since a long time, a year or two, the nut integration has been
configured on A to talk to foo, over the usual 127.0.0.1:3493.
I just set up an ssh tunnel to forward 3494 on A to 127.0.0.1:3493 on B.
I then added 127.0.0.1:3494 using the UI, and it appeared. The entities
are better named, "Foo Voltage", so it appears a bunch of rough edges
are gone (which is typical in HA; just wait 6 months and things are
smoother). I should delete and re-add my first UPS to get better names.
I then graphed some of the things together and it all seems fine.
So that's proof the integration can support two upsd servers, but you
have to be able to contact them, and there is the convention that they
listen on localhost only unless you change that.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220814/bc4576bf/attachment.sig>