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.kev...@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.
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
