Thank you. For sure it was my running across an old article that set me on the wrong path. Once I followed the advice from you and others on this awesome list, the integration itself found the nut-servers on my network, and the associated UPS devices themselves. Thank you for helping me learn and
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
Posted https://github.com/networkupstools/nut/issues/1560 lest we forget :)
Jim
On Sun, Aug 14, 2022, 02:06 Jim Klimov wrote:
> Haven't poked INSTALL.nut for a while, PRs welcome. And there were many
> bite-size PR ideas in this thread ;)
>
> There was quite a bit of details poured into
Also search NUT github issues, there were a few threads about Home
Assistant in the past year or two. Something about "just one of something
at a time" rings a bell in this context, but I can't elaborate just OTOH
now :)
I think some posts also detailed (or referred to docs about) building your
"z.kevino--- via Nut-upsuser"
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
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
"z.kevino--- via Nut-upsuser"
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
