Yet another user who is unable to configure NUT

[arrowd]

I moved my OPNsense from one UPS to another. When on the first UPS, OPNsense was a NUT slave to a TrueNAS Core NUT master. Things worked well.

I need to set OPNsense as a NUT master on this UPS. (I will eventually add a RaspberryPi and a Windows 11 PC as slaves.) I am having a lot of trouble and can't find a solution after following many web leads.

If I enter "upsc ups" at a terminal prompt, I see all of the correct data for this UPS. I have the NUT widget on my dashboard but it is showing data from the old master! I tried deleting the NUT plugin and reinstalling it, but that didn't change the widget display. I feel there is some config file with the old data still in it that's being used and should be manually deleted.)

Under Services - NUT - Configuration - UPS Type, I have only USBHID-Driver enabled; all others are disabled. And in the extra arguments field I have port, vendorid, productid, serial and desc filled in.

For Services - NUT - General Settings, I have 'Enabled'; 'Service Mode' = standalone (netclient didn't work either); 'Name' = ups; 'Listen Address' = 127.0.0.1 (OPNsense address doesn't work either)

For Services - NUT - Nut Account Settings, I have 'Admin Password' = Password; 'Monitor Password' = same as former password.

Thanks for any suggestions!

[arrowd]

I think I have the Nut service on OPNsense setup correctly now. In 'Services - Nut - Configuration - General Settings - General Nut Settings', I have 'Enabled'; 'Service Mode' = standalone, 'Name' = ups; 'Listen Address' = [localhost] & [192.168.15.1] (my OPNsense IP)'.

For 'Services - Nut - Configuration - General Settings - Nut Account Settings' and 'Services - Nut - Configuration - UPS Type', they're set as in my original post.

I now see the correct data in the Nut dashboard widget and can connect here from both my TrueNAS Core servers using 'upsc ups@192.168.15.1'. I can also use 'upsc' to see the info from those TN servers.

Next step is to set up my RPi and Win 11 PC as clients. And then do a shutdown test.