Network UPS Tools (NUT Server) Ultimate Guide

21 thoughts on “Network UPS Tools (NUT Server) Ultimate Guide”

• I couldn't think of any good NUT jokes during the video, so post them here. Cashew later!

• Tim, a couple ways to either clear text files, or delete them and create a new blank file w/o having to open the file to clear contents.

  Clear the file: echo > nut.conf
  Delete the file: rm nut.conf
  Recreate a deleted blank file: touch nut.conf

  This has saved me hours of deleting file contents!
  Great Vid, well thought out and produced!

• Another thing I've been meaning to do! Thanks for the tutorial!

• Awesome tutorial as always @technotim! Its great to get the real life happiness of a successful configuration. Makes me wanna tinker 😁

• What a super detailed video! I got everything working the first time!
  But the reason im doing this is so that i can control my Synology NAS, and i found a site where that says i have to create the user with the name "ups" cause thats what Synology NAS is looking for, so went through the vvideo again and changed its name in every step. But now the monitoring website can not connect, but the NAS has gone from "No ups found/connected" to "Can't connect to the network Ups server".. So i guess it see something but it does not work properly.. You should make another awsome video explaining how to connect Synology NAS to this NUT server, that would be so awsome! 🫡😊👌

• Loved the Video and got my two UPS up and running and working like a bomb, but i added another UPS the other day and fro the life of me i cannot get it work. The problem is that the 3rd UP is identical to the 2nd UPS Vendor ID etc all identical. there is no way to tell them apart when i run nutscanner, i see all 3 UPS, and yet i dont se serial numbers, I found a thread that said that the serial numbers were generated by nutscanner, but I don't see that.
  Please if anyone can help i think i have watched this video 40 times, and read just about every page in the official site, but nothing is helping.
  Is there a way to distinguish the 2 UPS apart from each other, because in the UPS.config file it everything is the same because i cannot give it a different vendor, product, serial number, for it to know they are separate UPS's.

  Dont know where else to ask for help. (yes i have the latest 2.7.4-13 of nut server and nut-client running on a Pi 3B+)

• Just wanted to say thank you. This was an excellent tutorial and saved me a ton of time. Love your channel, keep up the good work!

• any app x64 ? WinNut Setup is 32 bits

• Thanks for a great and thorough video Tim. I was trying to do this for my home network because I have more devices than UPS units. Like some others have commented here, I too wanted to protect a pfsense firewall and some Synology NASes. I'm happy to report this worked like a champ! For the benefit of others I thought I would add a couple of things that worked for me to get those two things working.

  1. PFSense: install the NUT application. Then under Services/UPS/Settings, select 'Remote NUT Server' from the dropdown and enter your IP address, user name and PW that you defined on the NUT server in Tim's video.

  2. Synology: I read elswhere that Synology expects the UPS to be named 'ups' so that's what I did in the conf files that Tim walks us through in the video. Don't name it anything else and I kept it lowercase. Then on the Synology, go to Control Panel/Hardware & Power/UPS and select 'enable UPS Support' , choose 'Synology UPS Server' and enter the IP in the field that asks for it. No user name or PW is required here.

  Hope this helps others!

• Could you do the absolute bare minimums of this video, to get NUT installed and functioning? It seems this software is not the easiest one to get it working in the first place – at least not before you master it, but there just is not always enough available free time to study everything. Can you squeeze the essentials to 5-10 minutes?

• Hi Tim, can you (or anyone else) give a hint on how to format the shutdown command on a Ubuntu server please. Usually the shutdown command requires a sudo and then requests a password.

• Too bad this does not work with (crash and burn) Unifi!

• THAAANK YOUUU! This was so much harder than you made it look for my slightly more complicated setup, but I came back and used the website cgi-stats setup in this video and was just so happy that it just worked easily!

  I really wish you would've given a tiny bit more of a rundown of what each .conf file is used for and what each service does as I had to do a lot of reading to troubleshoot little misunderstandings I had, but I am still so happy to have a guru's quick walkthrough. "Quick" ha! If this video was over 50 minutes, I think it would have been a lot more intimidating to click on, though. I dunno.

• You could move the example conf file, then run nano with the original file name and path. Nano will create a new file if it doesn’t exist.

• this is an immaculate walk-through. Thanks for putting this video together and sharing. Much appreciated.

• Thanks!

• Struggled to find a way to get data from my salicru ups and thought "mmmmhhhhh lemme run to youtube and search nut techno tim" lol and fair enough, I found this vid lol

• The whole nut-server, nut-client, etc took me an entire day to fully grasp. This video helped me get the bigger picture and clarify things.

• Okay, so how do I set for instance a client to shut down when the ups battery reaches a battery percentage?

• Nut scanner probes to get information.
  Right 😂

• Really good video. Thank you! I am a bit confused how to set up and run both the server and the client on the linux (debian) server that is directly plugged into the UPS (via USB) and that I want to control the shutdown of. Do I edit the nut.conf file to stay as MODE=netserver and then edit the upsmon.conf as per your video? Cheers!

Comments are closed.