This post is probably of interest only to me, and I'm posting it just because I'm getting tired of remembering where I stored this tidbit on my Mac.
Our home router is a Protectli box running pfSense firewall/router software; the Protectli box is connected to a CyberPower UPS. Within pfSense, you can install the Network UPS Tools package (called NUT in pfSense) to monitor and report on the UPS; here's how it looks in the overview screen:
After recently updating to a newer Protectli box, however, all I saw was a message that read "Cannot communicate with UPS" (or something close to that). I knew I had a fix for this issue somewhere, but I couldn't remember where. Today I found it, so also today, it goes on my blog so I'll always know where it is…
If there happens to be more than one person out there with my setup, and your CyberPower UPS isn't talking to the NUT plug-in in pfSense, here's the fix:
- Login via Terminal to the pfSense box, then use item (8) to exit to the shell.
- Run these two commands:
$ /usr/local/sbin/upsdrvctl -u root start $ service devd restart
- Exit the connection to your pfSense box.
Once I did the above, communications were restored and the status box returned.
Thanks for this, recently upgraded my install of pfSense and it broke my connection to my CyberPower UPS. This resolved it.
I entered the commands from the Diagnostics->Command Prompt option as it wasn't easy to get access and easier from my desk. :-)
Just thought I'd let you know it was worth posting this.
Thanks for commenting; always nice to know someone else found the info useful!
-rob.
Totally found this helpful! Thanks! Solved my problem.
That makes two more people than I thought would find this! :)
-rob.
Rob, do you know why this happens? I've just had to perform this again to get UPS status back.
No idea why—mine usually stays connected after I do the above. I'll see if it breaks again when I install the 2.7 update this weekend.
-rob.
And yes, it did break after the update, and I had to run the fix again.
-rob.
Thank you! It's rare that the first article that pops up in a search actually fixes my problem.
Awesome! Thanks, exactly fixed my issue. Now to research to understand what those commands actually do. :)
Yup, those were also the 2 commands missing for me! Everything works now thanks :)
Thanks for sharing this. An old APC UPS was replaced with a new CyberPower UPS and after uninstalling the APC package and installing the NUT package it wouldn't start. The commands that you mentioned fixed the problem and were entered from the GUI Diagnostics->Command Prompt option.
Thanks for the post.
Do you get e-mail notifications from pfSense when the UPS is on batter? There is a setting for that but somehow it doesn't work for me.
We haven't had a power outage just yet, and I don't recall what happened the last time we did. With winter approaching, though, I expect it'll be tested again soon ... I'll try to remember to post when it does. (Yes, I could just pull the plug, but it's more complicated than that as I have things in the UPS that aren't on the battery that I don't really want to shut down just for a test.)
-rob.
Thanks for the quick reply.
Maybe you don't even know about short outages because you didn't get a notification?
I managed to get notifications working with the help of the first response here: https://forum.netgate.com/topic/101604/nut-package-how-to-email-notifications-on-pfsense-2-3/2
Needed some modifications though.
I just reinstalled pfSense with my old config to switch to zfs and was confused about why my UPS wasn't showing up. Yours was the first search result and solved it! Thanks so much for posting!