similar to: Smart1500lcdt will not connect with usbhid-ups

Barry, I have had success with NUT on Debian and an EATON 5E2000IUSB-AU 5E 2000VA/1200W UPS With 3 x OUTLETS which I believe is good value. I would believe the the EATON ?5E 1500VA/900W UPS With 3 x OUTLETS would work just as well. The 1500VA also uses the same batteries as the 2000VA so I would believe it would run its raited load longer than 2000VA. My eight drive RAID driver uses less that

I talked to Tripp Lite Technical support. Their policy is that they only support Fedora and SUSE. There is no one there that could help with Ubuntu or NUT issues. The only answer they could give me was to port the rpm files to Ubuntu and use them. This is way beyond my experience level. I will go to the local electronics store and buy a cheap USB 2 hub to see if that works. I will post the

On Aug 29, 2014, at 2:02 PM, Barry Skrypnyk <barry at skrypnyks.com> wrote: > See comments below. > >> -----Original Message----- >> From: Charles Lepple [mailto:clepple at gmail.com] >> Sent: Friday, August 29, 2014 5:35 AM >> To: barry at skrypnyks.com >> Cc: nut-upsuser at lists.alioth.debian.org >> Subject: Re: [Nut-upsuser] Smart1500lcdt will

See comments below. > -----Original Message----- > From: Charles Lepple [mailto:clepple at gmail.com] > Sent: Friday, August 29, 2014 5:35 AM > To: barry at skrypnyks.com > Cc: nut-upsuser at lists.alioth.debian.org > Subject: Re: [Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups > > On Aug 28, 2014, at 6:49 PM, Barry Skrypnyk <barry at skrypnyks.com>

On Aug 28, 2014, at 6:49 PM, Barry Skrypnyk <barry at skrypnyks.com> wrote: > I have searched the archives and googled this problem with usbhid-ups. I would really appreciate any help anyone could offer to solve the problem. > > System: Ubuntu 14.04.1 Trusty Tahr Which kernel version are you using? > Installed nut from Ubuntu repositories ? nut 2.7.1 > > Ups.conf file

I have searched the archives and googled this problem with usbhid-ups. I would really appreciate any help anyone could offer to solve the problem. System: Ubuntu 14.04.1 Trusty Tahr Installed nut from Ubuntu repositories - nut 2.7.1 Ups.conf file maxretry = 3 # user = nut [TrippLite] driver = usbhid-ups port = auto productid = 3016 desc = "Tripp Lite UPS,

[please use reply-all to include the list - the NUT lists do not add a reply-to header.] On Oct 23, 2015, at 2:03 AM, Null <null at wuffleton.com> wrote: > > Hi List, > > I recently picked up a Tripp Lite SMART1500LCDT while they were on sale to pair with my home server, and have tried getting it set up with NUT, since it seems to be supported. I can get the whole NUT stack up

I bought this UPS to use with NUT. I've used Belkin, APC, CyberPower, Best, Powerware upses with NUT on dozens of servers beginning with RHEL3. http://www.amazon.com/Tripp-Lite-Display-Protection-SMART1500LCDT/dp/B009TZTGWK Since this was advertised as USB HID, I didn't expect any problems. Bad idea (should have gotten the Cyberware with somewhat less runtime). Initially, it seems to

Hi List, I recently picked up a Tripp Lite SMART1500LCDT while they were on sale to pair with my home server, and have tried getting it set up with NUT, since it seems to be supported. I can get the whole NUT stack up and running, but the driver seems to only stay up for a couple minutes before crashing out. I've uploaded the level 6 debug output of the driver (with my serial number

Charles, > What is the new behavior? The CentOS minimal install had different print statements and a broadcast message whenever the UPS was disconnected. The broadcast isn't really important. Below are the differences I pasted though I'm not sure if they are important, I just noticed they were different. Particularly the bolded parts which I think you alluded to in your email about

Some of my messages never went through since I hit a message size limit. I'm resending them in the hopes they are under the limit. Charles, The lsusb command did not trigger a disconnect. The output of that command is below. I ran "usbhid-ups -a upsunit -DDD &> output.log" and I have attached the /var/log/messages and output.log to this email. Before running this test

On 2015-10-23 5:42, Charles Lepple wrote: > So the interesting part is that I was testing the master branch yesterday (same commit) on an older Debian box (3.16 kernel). The driver had trouble starting, but once it got going, it has been running continuously. > > I'm not really sold on this approach (due to the testing needed on other hardware), but this pull request reworks the USB

On May 22, 2016, at 10:18 AM, Stuart Gathman wrote: > > I have a ticket open with TrippLite, but at this point it seems to be a > software, rather than hardware problem, since with the newer kernel and > usbhid-ups, the ups stays on the bus, and I could kludge around the > problem by making systemd keep restarting nut-driver. They seem to be > interested in actually resolving

Hi Stuart, I am using OpenMedaVault and purchased the Tripp-Lite SMART1300LCDT. I can't get it to work with OMV. Any ideas for me? I posted a request on the OMV community but no answers. Any direction would be appreciated. Thanks, Roman -------------- next part -------------- An HTML attachment was scrubbed... URL:

Thanks again for your help, Charles. I was able to install the Tripp Lite software on my Ubuntu machine, and it sort of works. It does something which continually changes the USB device ID of the UPS, and prints voluminous error messages in the log. However, one of the things that it can do is to schedule a UPS shutdown, which Nut does not know how to do. So I monitored the USB port with

On 08/03/2016 05:25 AM, Stuart Gathman wrote: > I've made some progress getting this Tripplite to work: > http://gathman.org/2016/07/30/Standard_Schmandard/ > > Basically, plug it into a USB hub that actually implements USB2.0, then > power cycle the port when it hangs. It does seem to be a hardware > problem with the USB controller. Finally an idea;-) I had the same problem

Thanks Marco, I may try this if I can't get David's udev rules to work. On Mon, Dec 9, 2019 at 12:58 AM Marco Walther <marco at sonic.net> wrote: > On 12/8/19 8:18 PM, David Zomaya wrote: > > I haven't tried it on RaspberryPi, but if there's some specific Tripp Lite > information I can help with, let me know. > > We had that discussion about the

I've made some progress getting this Tripplite to work: http://gathman.org/2016/07/30/Standard_Schmandard/ Basically, plug it into a USB hub that actually implements USB2.0, then power cycle the port when it hangs. It does seem to be a hardware problem with the USB controller. On 05/24/2016 09:06 AM, Charles Lepple wrote: > On May 22, 2016, at 10:18 AM, Stuart Gathman wrote: >> I

On 5/13/2017 10:20 AM, Charles Lepple wrote: > On May 12, 2017, at 10:06 AM, Mike <the.lists at mgm51.com> wrote: >> >> >> OpenBSD 6.1/amd64 >> nut-2.7.4p0 (from OpenBSD package) >> UPS: Tripp-Lite OMNI1500LCDT >> >> I cannot get the driver for the UPS to load without error. >> >> Here are the commands, with the output, and the config

On May 12, 2017, at 10:06 AM, Mike <the.lists at mgm51.com> wrote: > > > OpenBSD 6.1/amd64 > nut-2.7.4p0 (from OpenBSD package) > UPS: Tripp-Lite OMNI1500LCDT > > I cannot get the driver for the UPS to load without error. > > Here are the commands, with the output, and the config files: > > ======================================================= > #