similar to: OMNIVSX1000D Compatibility

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

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

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

>>>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, 2935AVHOM87BB00152 is Protocol 2012 That said, 2010 and 2012 should be similar. Off the top of my head,

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

Borrowing from our friends at Ask Ubuntu ( https://askubuntu.com/a/276637 ) there is. I've modified it for use with a Tripp Lite UPS and 3024 protocol below. Try disconnect/reconnect after and see what happens. :/etc/nut$ cat /etc/udev/rules.d/90-nut-ups.rules # /etc/udev/rules.d/90-nut-ups.rules ACTION=="add", \ SUBSYSTEM=="usb", \ ATTR{idVendor}=="09ae",

Wow - you're doing all the work for me! Thanks for the rule set.  I can't easily reboot that box just now, so I'm working on reloading the rules. When I try  udevadm control --reload-rules && udevadm trigger May 20 15:19:01 elmer systemd-udevd[3413]: Process '/sbin/crda' failed with exit code 234. May 20 15:19:01 elmer systemd-udevd[3413]: Using default

Glad to hear it's working, thanks Tom. Network UPS Tools team: is fixing this as simple as me telling you what new UPS protocols are HID-PDC compliant? Thank you, David Zomaya Tripp Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 2:42 PM To: David Zomaya Cc: nut-upsuser Subject: Re:

My thoughts for a test: * Just have MODE=standalone in nut.conf * Put [tripplite] driver = usbhid-ups port = auto productid=3024 desc = "Tripp Lite Internet600U" In ups.conf * Put LISTEN 127.0.0.1 3493 LISTEN ::1 3493 [tripplite] driver = usbhid-ups port = auto in upsd.conf That may be suboptimal but will probably work for a test. Side

Tested a Ubuntu 18.04 LTS virtual machine with NUT 2.7.4 and a 3024 protocol Tripp Lite UPS (mine is a INTERNET550U, but same protocol) :/etc/nut$ lsusb | grep Tripp Bus 002 Device 004: ID 09ae:3024 Tripp Lite I it got generally working (outputting reasonable responses to upsc, although there are some issues with variables like frequency) by adding productid=3024 to my ups.conf. Like this:

No, it's not. I'd defer to the list for tips on that one. First thing I'd try if no one else has ideas is checking lsusb and restarting the service. Thank you, David Zomaya Tripp Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 7:00 PM To: David Zomaya Cc: nut-upsuser

"Can't claim USB device [09ae:3024]: could not detach kernel driver from interface 0: Operation not permitted" Is probably an issue with NUT grabbing the UPS... can you disconnect and reconnect the USB cable and try again? If that fails, maybe a udev rule will help. Thank you, David Zomaya Tripp Lite <http://www.tripplite.com/> ________________________________ From:

That would be great.  If there is something I can do to collect data or troubleshoot, please let me know. ---- On Wed, 20 May 2020 08:51:14 -0400 David Zomaya <David_Zomaya at tripplite.com> wrote ---- I'm still working remotely, but I should be able to get something set up soon. I'll reply all here once I have something to report. Thank you, David Zomaya Tripp

If I installed and tested against Ubuntu, how useful would that be in general and in this specific case? I think we've seen a few reports of issues with the newer 3024 protocols and I'd like to help get them sorted out. Thank you, David Zomaya Tripp Lite ________________________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at

I'm running Raspbian Buster, but given that the error seems to be "higher order" than a hardware issue - one of parsing the protocol?  I suspect that Ubuntu would be a decent "lookalike" to model the issue.  ---- On Tue, 19 May 2020 22:31:56 -0400 David Zomaya <David_Zomaya at tripplite.com> wrote ---- If I installed and tested against Ubuntu, how useful would

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

Did it stay stable this time? It looks like the restart of the service restored communication. If it reoccurs: >>> Bus 001 Device 011: ID 09ae:3024 Tripp Lite I wonder if this is the same device number after? Something to keep an eye on Thank you, David Zomaya ________________________________ This message is for the addressee's use only. It may contain confidential information. If

Hello! I am currently having issues monitoring a Tripp-Lite AVR900U. First, here are a few system details: > Manjaro Linux - kernel 5.4.30-1 > network-ups-tools 2.7.4-5 (built from Arch User Repository) > (lsusb output) Bus 003 Device 003: ID 09ae:3024 Tripp Lite AVR900U Contents of /etc/ups/ups.conf: > [tripplite] > driver =  usbhid-ups > port = auto Contents of

After a quick glance, it looks like that older version of the INTERNET750U supports only a few controls Shutdown of the inverter, cancelling that shutdown, setting the delay for the shutdown timer, and enabling/disabling a USB watchdog function. My *guess* is that Network UPS Tools is just exposing the shutdown command as one command. Does that help? Note to users with the same model but