I have an Eaton 5E2000i UPS connected to HA on HP EliteDesk 800 G4 via a USB cable. HA can shutdown gracefully (set to turn off after 1 min of being on battery) but I would also like my other computer, also the same model, which hosts Jellyfin running Windows 11 Home with two external HDDs to shutdown gracefully.
Secondly, I would like to change the UPS shutdown delay from 20 seconds to 60 or 120 seconds before the UPS cuts power to the devices. Followed this post - Network UPS Tools "$ upsc [email protected]". But I get the following.
Not sure how I can change it. I have a Windows 10 laptop which I can use to contol the beeping but not much else.
Just to make sure I understand your setup correctly, you have two HP EliteDesk 800 G4 computers (one running HA, other running Jellyfin/W11) connected to the same UPS?
If correct, I’m thinking that the server has to be setup with two users, one for HA client (NUT Integration), one for Jellyfin/W11 client, and in addition, the HA user is also configured as “master” (since it has the UPS USB plugged into it) and the Jellyfin/W11 user as “slave”. The AddOn Server Document seems to support this.
As for the W11 NUT Client you referenced, I think you would download WinNUT-Setup.msi and double-click on it to execute it (but I haven’t tried this myself).
As for the upsc command, I don’t know as I don’t actually use the AddOn, but it may be a docker permission/protection issue. Maybe try upsc myups@addon_a0d7b954_nut or upsc myups@localhost.
On the Win11 VM, installed Win-NUT client and added the details, does not pick up the NUT Server in HA. Tried with the IP address as the NUT host and also the name, no luck. Am I doing this correctly?
Work pick it up with the IP address either. I’ve tried on a Windows 10 laptop which the UPS was connected to via USB to confirm connection, the NUT Client doesn’t pick up the UPS on that either. Most likely the NUT Client configuration is incorrect but not sure.
[Id 5: 4/09/2024 9:42:00 am] Connection to Nut Host 192.168.1.5:3493 Failed: No connection could be made because the target machine actively refused it 192.168.1.5:3493