I ran into an issue today with Truenas CE (25.10.0.1) regarding the UPS service setup.
I was previously using an APC XS900 UPS on this TN system which was attached through the ‘usbhid’ driver and setup as a ‘Master’. I decided to remove it and setup the UPS service on this TN as a ‘Slave’ monitoring my rack master Truenas system which is monitoring the main UPS.
I stopped the UPS service on the system and removed the APC XS900 hardware. I then tried to edit the UPS configuration page in the WebUI to change the UPS mode over to ‘Slave’. Upon trying to save the new configuration I received the following error message from the WebUI:
ERROR: Validation errors: driver: Driver selected does not match local machine’s driver list
When editing the UPS configuration in the WebUI, with the ‘UPS mode → Slave’ selected, the hardware ‘driver’ field in the WebUI is replaced by a ‘remote host’ field, thus allowing the user to enter the remote host IP (master) address. However, the current TN WebUI seems to be ignoring UPS mode being setup as slave and complaining about the old hardware driver selection… which should be ignored when slave mode is selected.
Anyone else had this issue?
I have had so many issues with trying to use the NUT remote built into my TrueNAS that it drove me to distraction. As a master, the built-in TrueNAS NUT module seems to work well.
As a remote, I got things to work well until I started getting spammed with “NUT master not available” warnings, whose origin I could not trace since the Raspberry Pi running NUT in question was operating happily. And it wasn’t an intermittent problem either (think auto-update causing a system restart, for example).
I was ready to call a priest but instead got two UPS’ - one for the NSS, the other for my Pis. That allowed the TrueNAS NUT to do it’s thing via USB, which works.
Thanks to attempting to upgrade to a Ecoflow Delta 3+, I am having another go at it by running a NUT 2.8.4 master in a VM on the TrueNAS and then using the built in NUT 2.8.0 in TrueNAS to query that. Wish me luck… I’m not super convinced it will work but at least we can then rule out network issues since it’ll all happen in the same sanbox AND I’ll have PeaNUT app to prove that it’s TrueNAS and not my ham-fisted attempts to set up a NUT master / remote relationship.
Glad I’m not alone with UPS service issues here…
I checked the IP communications using upsc from the slave to my Master TN server and status of the main UPS all came back fine. So I know it’s not an issue with master/slave communications.
I also checked the config files in /etc/nut and /user/local/etc/nut and nothing is getting modified by the WebUI, so it seems like its a WebUI issue so far. I’m temped to go into the shell and modify the nut config files by hand.. but I have resisted the urge since the IX folks recommend against it. Besides I’d also like to track down the root cause of the issue.
More to come later…. 
1 Like
