Nut upsuser - Aug 2022 - NUT add on for Home Assistant

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>

"z.kevino--- via Nut-upsuser" <nut-upsuser at
alioth-lists.debian.net>
writes:
> 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 don't understand why you are running a "NUT add on".  The
integration
doesn't need that, if what you are trying to do is monitor some existing
nut instance.

If you are trying to have a local nut with no attached UPS, so that the
local machine shut down, that's fine.  But you would still configure the
remote nut server in the integration, because that connects to servers.

If you have the local nut instance being a client and also exposing a
copy of the remote server as if it is local, then I don't see why HA
wouldn't connect -- but I also don't understand why you would do that.

But I've never dealt with "add ons" in HA, as I run Core (which is
just
"run the home assistant python process without delegating OS management
to the HA world", in other words the normal unix approach).
> 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
That is certainly up to date.  I just wondered from the yaml as there
has been a huge yaml->UI-config gradual transition over the last year.


If it still won't do two, I would look at the source code for the
integration.
-------------- 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/75ab94ce/attachment.sig>