@hspindel See the pfSense NUT support thread.

@RyanM said in Downgrade NUT package vs. remote upgrade of pfSense CE:

Just wasn't sure if there was an easy way to "downgrade" NUT.

You could go into the old NUT support thread and grab one of the testing builds that was done earlier in the year. If you do, make sure you get the right arch... the amd64 version was in the February timeframe, and the arm version was a couple of months later.

@dennypage

Good morning,
I updated to pfsense 2.7.1 with Nut ver 2.8.2

The quirk is always inserted in the boot loader.
hw.usb.quirk.0="0x04b4 0x5500 0x0000 0xffff UQ_HID_IGNORE"

I confirm that the Riello VST1100 UPS is working well without disconnection of the USB port

Soon I will also let you know for the "Riello Sentinel Pro 2200" and "Riello Sentinel Dual SDU 6Kw" models

Yesterday (Wednesday 29th November 2023) I upgraded my pfSense router
from v2.7.0-RELEASE and 'nut' version 2.8.0_2
to v2.7.1-RELEASE with 'nut' version 2.8.2

Now after 24 hours of normal usage, and having done a couple of test mains power breaks,
all the issues I was previously having with the intermittent USB monitoring of my Eaton-3S-550 UPS, and associated missing notification emails, appear to have been resolved.

@JHanko

Great,

Now that I had some more time, was going to create a redmine for this issue

and of course discovered there is one that has a similar proposed fixed. So I'm not going to create an account on redmine for the sole purpose of updating it.

https://redmine.pfsense.org/issues/14398

perhaps we could kindly ask @stephenw10 to update the redmine for you (us) so that at some point down the road it ends up in the system.
The redmine indicates affected version is 23.01 (and certainly it is) it is still there for 23.09 and 2.7.1 CE

Thanks

@hspindel Excellent. Thank you for helping test.

Beginning with 2.8.1, I am transitioning NUT support to a new thread, which can be found here.

Please continue to post issues related to 2.8.0_2 and below to this thread.

Also, I am actively seeking people to test the new 2.8.1 pfSense NUT package prior to general release. I would appreciate any help you can offer. Thanks!

@dennypage said in NUT frequently disconnects netgate 2100:

The short version is that the new pfSense NUT package, which fixes the USB and SNMP issues, should start with 23.09. Soon.

Ok thx always

@hspindel said in NUT UPS shutdown configuration:

Would like to configure shutdown settings. Searched this forum and found:
default is Batt Alert at 20%, pfShutdown and UPS -> off.

Where are these values configured? Where is a list of what can be configured?

FWIW, there is no battery alert level in the pfSense NUT package so I don't know where that 20% came from.

I strongly recommend that you leave NUT in the default configuration unless you are trying to address a specific problem.

@niloc1234 NUT, including the master/slave relationship, is designed around LB (Low Battery) management. You would either need your custom Synology stuff to wait for LB before taking action, or you would have to send a FSD (Forced ShutDown) to manage your own shut down of the slaves.

NUT is probably one of the most over and/or incorrectly configured systems in existence. Unless someone really understands what they are doing with NUT, I generally recommend that they leave it alone to do its job as designed.

@stevencavanagh
You’re welcome. You’re lucky I have the same gear.🙂

@dennypage Reboot and after some time connected!!!! Thanks

@jrey Thank you so much, your information fixed both issues.

@dennypage said in NUT losing connection w/ UPS when WAN disconnects:

This is normal. pfSense restarts packages when any interface changes link state

I know I this is a better safe then sorry solution, and not NUT's fault.
The system logs clearly shows "everything" get restarts.

Still, NUT listening to 127.0.0.1 and LAN (192.168.1.1) is being restart because something happened "WAN", knowing that NUT has nothing to do with WAN, or any other interface, ... its somewhat bothering me, to say the least.

@dennypage : Again : not your issue.
Maybe I'm somewhat spoiled by other OS's like Debian who use 'smarter' /usr/local/erc/rc.d/ process start/stop files where dependencies are used.

@Thondwe Confirm that Worked!

@alekslyse Search for "For those of you affected by the APC issue" either in the forum or in Google.

This should be fixed in the next kernel upgrade.

@dennypage
That's great news! Appreciate the feedback on a really old post!

@Austin-0 Ok, The solution works. I mixed the advance section and the additional driver option field.
@ purleigh, in my case, the issue was happening after 1h or so.

@Herrmann_wst

I know this is an older post but I will respond in case it helps someone with the same error. I agree it appears to be related to how the widget handles the date format pulled from the APC UPS EEPROM.

I ran into the same error after replacing a battery and updating the "battery change date" in the EEPROM. After this change the widget threw the same error as you have posted.

In troubleshooting I referenced the APCUPSD user manual and noticed it shows two different date formats: BATTDATE [ mm/dd/yy | dd/mm/yy ] ... Last battery replacement date. Maximum of 8 characters.

When I saw this I remembered that when I changed the date using APCTEST it had prompted for the "DD/MM/YY" format.

This made me also think it might be related to the date format so I updated the battery date again using "MM/DD/YY" just to test, and this resolved the widget issue in my case.

Summary:

stop APCUPSD service ssh/ open shell run apctest select option #5 to program EEPROM select option #2 to change battery date update as MM/DD/YY to make widget happy :) save, quit and exit shell restart service and enable daemon /NIS enable widget and check dashboard

Hope this helps.

@Stef_R said in APCUPSD with network connection from Smart-UPS 1000 RM to pfSense 6100:

Thanks for the help, but unfortunately that doesn't help either.

Probably not the same situation - maybe you can find a hint in the apcupsd documentation? (http://www.apcupsd.org/manual/)