"z.kevino--- via Nut-upsuser" <nut-upsuser@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.
signature.asc
Description: PGP signature
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
