search for: scolbi

Did you see what objecttothis posted on GitHub already? In any event, your issue with NUT and the 3024 AVR750U is that the UPS reboots output instead of shutting off when the shutdown command is sent, correct? Good suggestion on the driver authors, thanks. Thank you, David Zomaya From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on

No, I had not! I'll take a look at the protocol docs. My problem is the opposite: all the permutations that NUT can send of "turn off but turn back on later" either do nothing or turn the UPS off in such a way that it requires me pressing the physical power button to bring it back on. (I guess I haven't tested trying commands to turn it back on, but that's not so helpful if

I wouldn't be surprised if they both use the same driver. I think they are essentially the same model, but with one having a slightly larger battery. My issue is primarily with the UPS turning back on after having shut off like it should. @Scott Colby if you take a look at the config files I posted in the github issue I created, perhaps that will give you some hints on your issue. Maybe

David, Thank you. I created a Github issue (https://github.com/networkupstools/nut/issues/808). I don't know who monitors those tickets, but no one has responded to my previous issue on that project repository about the AVRX550U, so it's unclear if the right person is going to see this one. Can you tell me what other models use the 3024 protocol? Listing those may help provide

Thanks for chiming in @David Zomaya. Tripp Lite replaced my AVRX550U once thinking that the powering back on was a defective unit, but the replacement does the same thing. The SN on the first one is 2935AVHOM87BB00152. NUT has my model listed as protocol 2010, so that needs to be corrected to 2012, but I'm not sure if anyone is doing active development on it right now. I also have a

Hi, I can confirm that with my AVR750U connected to my Windows machine using the TrippLite Power Alert software, I can configure it to do the behavior I want: turn off at a low power level and turn back on when the power is reconnected, so I guess it's now a question of if NUT can be adapted to the 3024 protocol. I am not the most experienced C programmer out there, but given there are

On Sat, Jun 27, 2020, at 23:11, Manuel Wolfshant wrote: > On 6/28/20 5:54 AM, Scott Colby wrote: >> >> I'm not convinced this is the problem; I think that pfSense has an alternative way of running the NUT components: # ps aux | grep ups root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon uucp 45751 0.0 0.1 6796 772 - S 02:22

Thanks for the quick response! On Sat, Jun 27, 2020, at 22:17, Manuel Wolfshant wrote: > On 6/28/20 4:25 AM, Scott Colby wrote: > > Hello, > > > > I am having difficulty using NUT to shut down my Netgate SG-1100 > > (a pfSense router) when the power level of the UPS gets critically > > low. > > > > Here is some relevant information: > > - OS:

Hello, I am having difficulty using NUT to shut down my Netgate SG-1100 (a pfSense router) when the power level of the UPS gets critically low. Here is some relevant information: - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) - NUT version: 2.7.4 - Installed from: pfSense package 2.7.4_7 - UPS: AVR750U (Device release number 2) - I have included my config files, output from `upsc`, and