@hspindel Excellent. Thank you for helping test.

@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/)

@viragomann SNMP will be what I'm going to do. Thanks for all your help with this! Mucho appreciated.

@digitalgimpus said in NUT unable to connect to apcupsd: I'd suggest learning to Google your thoughts before commenting. Or just RTFM. Wow.

Thank you very much for your reply, I hadn't understood this so logical thing, my apologies for my stupid question. I thought I had a problem on my new pfsense. I'm relieved :-)

@sgnoc You’re welcome

@dennypage Thanks and good to know. Infortunately My issue is om a SG-2100 ARM based device