search for: cooperfamili

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

Will do. Ball in my court for now. Thank you, David Zomaya Tripp Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 8:47:28 AM To: David Zomaya Cc: nut-upsuser Subject: Re: [EXTERNAL] Re: [Nut-upsuser] Help with Tripp Lite Internet600U That would be great. If there is something I can do to

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",

Sorry, neglected to mention: You'll need to either reload the udev rules or reboot to make the new rule "active". Thank you, David Zomaya Tripp Lite ________________________________ From: David Zomaya Sent: Wednesday, May 20, 2020 2:11:24 PM To: Tom Cooper Cc: nut-upsuser Subject: Re: [POSSIBLE FRAUD] Re: [Nut-upsuser] [EXTERNAL] Re: Help with Tripp Lite Internet600U

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:

"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:

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

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 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 Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 7:48:32 AM To: David Zomaya Cc: nut-upsuser Subject: Re: [EXTERNAL] Re:

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

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

David, Thanks again for your help today.  You're amazing. If the folks on the list could chime in - thoughts about what I could try next? May 20 19:57:28 elmer upsmon[3828]: Poll UPS [tripplite at localhost] failed - Data stale pi at elmer:/home/macbackup $ lsusb Bus 002 Device 006: ID 0bc2:3343 Seagate RSS LLC Bus 002 Device 005: ID 0bc2:3343 Seagate RSS LLC Bus 002 Device

Funny - I thought of that  and had tried it.  Didn't work I also moved it from the USB2 ports to the USB3 ports. Same result. I have not heard of udev, but after quick googling and glancing at an example, /etc/udev/rules.d/99-com.rules I am not convinced that I coule come up with a formula to make a working rule. Is there a simple sample I can copy to help figure out elevated

I'm not seeing this in the log.  I'm guessing that's not great. May 20 19:57:28 elmer upsmon[3828]: Poll UPS [tripplite at localhost] failed - Data stale May 20 19:57:33 elmer upsmon[3828]: Poll UPS [tripplite at localhost] failed - Data stale May 20 19:57:38 elmer upsmon[3828]: Poll UPS [tripplite at localhost] failed - Data stale May 20 19:57:43 elmer upsmon[3828]: Poll UPS

The fix: Was following a howto here: https://raymondjdouglas.com/blog/2018/ups-monitoring/ Much thanks to David Zomaya for coming up with the recipe! Nut.conf: Just have  MODE=standalone UPS.conf [tripplite]      driver = usbhid-ups      port = auto      productid=3024      desc = "Tripp Lite Internet600U" upsd.conf  LISTEN 127.0.0.1 3493  LISTEN ::1 3493

David, I appreciate the quick feedback! If I didn't fat finger any of the parameters you sent me, it's still not working. Here's the output from the attempt to start.  (BTW - nothing appears in the daemon.log when I use the upsdrvctl command.) pi at elmer:/home/macbackup $ sudo vi /etc/nut/nut.conf pi at elmer:/home/macbackup $ sudo vi /etc/nut/ups.conf pi at

I have a brand new Tripp Lite Internet 600U UPS connected to my Raspberry Pi 4 running the latest Raspbian. I installed nut and tried to configure based on your HCL (which I did not check before buying...) Doesn't "just work" - help? this page says that my model is NOT on the HCL, but the drop downs on the search seemed to say otherwise? (see attachment)

David, That's exciting - but I am not seeing similar results.  I *must* be doing something dumb - but I can't see it. I've got nut-2.7.4-8 installed on my pi Hope you can help. Tom pi at elmer:/home/macbackup $ lsusb | grep ipp Bus 001 Device 004: ID 09ae:3024 Tripp Lite pi at elmer:/home/macbackup $ sudo cat /etc/nut/nut.conf # Network UPS Tools: example nut.conf #