Hello, it seems like the use-case for dummy-ups driver in relay mode. The driver instance on server X would act as a client to a particular device from NUT server on the NAS, and republish the data points as its own.
It is also a useful setup for networked UPSes, which often can handle only a few client connections at once. Hope this helps, Jim Klimov On Tue, Nov 16, 2021, 19:18 K.C. Tessarek via Nut-upsuser < [email protected]> wrote: > I've searched for quite some time and read the FAQ, but to no avail. > > I have a UPS connected to a NAS. Unfortunately I have to specify every > single > client IP (ups slave), because the stupid NAS system (QNAP) does not allow > me > to set a /16 or /24. Changing the config files manually does not work > either, > because the service won't come up anymore. (One has to love QNAP at this > point.) > > Thus I wanted to setup a nut server + client on a separate machine X. > > On X the nut client should read the UPS info via network. It works when > accessing it on X with: upsc qnapups@qnap-ip > Using upsmon also works. > > Now I want to provide this info to other clients via the nut server on X. > > But I wasn't able to set it up so that X is basically a proxy for the UPS > on > the NAS. > > Is this even possible? I really could need some help here. And no, > unfortunaetly I currently cannot connect the UPS to X and use the NAS as > slave. > > Cheers, > K. C. > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
