similar to: LiebertPSP

Apologies for resurrecting an old thread and likely poor formatting - I wasn't subscribed to the list at the time and have copied it out of the archives (http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-July/006104.html). I've been unable to locate any further progress on this UPS (Liebert 10af:0001) - a thread from 2009

Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Now I'm back to another issue, every 2 seconds I get in the logs: May 3 13:45:23 myhost upsd[2587]: Connected to UPS [eaton]: usbhid-ups-eaton It seems happy to do this forever. On Tue, May 3, 2016 at 8:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On

Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection. I need help resolving the connextion issue So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys: Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 ? ?0.000000 ? ? send_to_all: SETINFO

> On Thu, 8 Sep 2016, Jeff Bowman wrote: > > > (Note: running > > 'upsc ups at localhost' echoes only a blank line to the screen, as do > > both 'upsmon' and 'upsd.') > > Something is wrong here. Is the daemon upsd running? On a Unix/Linux > system, the command ps aux | grep ups gives the report > > upsd 3196 0.0 0.0 13228

On Apr 5, 2014, at 7:18 AM, Mick wrote: > $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost > Username (suzy): admin > Password: > OK This command is sending the value to the UPS (via the usbhid-ups driver). > $ upsc iDowell at localhost ups.delay.shutdown > 30 And this command ends up reading the value back from the UPS. > However, following

On Jan 8, 2015, at 11:43 PM, Graham Menhennitt <graham at menhennitt.com.au> wrote: > Hello Nutters, > > I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason

Hello Nutters, I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason described in the FAQ (but I'm not 100% sure). In the trace output I can see that

Hi All, I'm using an iDowell UPS with the usbhid-ups driver: $ upsc iDowell at localhost battery.charge: 100 battery.charge.low: 15 battery.runtime: 650 battery.type: Pb acc device.mfr: iDowell device.model: iBox device.serial: 00000001 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto

On 09/11/14 21:43, Charles Lepple wrote: > On Sep 11, 2014, at 9:48 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> I have an APC USB UPS that was working on OpenBSD 5.5 with NUT 2.7.1 When I installed the latest 5.6 snapshot with NUT 2.7.2 the UPS no longer sends status messages when it loses line power. I asked over on the OpenBSD ports list and so far haven't had

Hi, I just decided to fix some scaling issues for my UPS (TRIPP-LITE SMART1500LCDT). Apparently that issue existed for some time (and I knew about it as well:-() See http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 for a thread. My little patch is attached (against 2.7.3). It seems to be working better for me but I don't have any other TRIPP-LITE's to test that I did

Hi, I just decided to fix some scaling issues for my UPS (TRIPP-LITE SMART1500LCDT). Apparently that issue existed for some time (and I knew about it as well:-() See http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 for a thread. My little patch is attached (against 2.7.3). It seems to be working better for me but I don't have any other TRIPP-LITE's to test that I did

Charles, It starts out good, then goes into a Connection timed out loop. If I can provide any information to fix a driver I'll do my best. Here's the output: # /usr/local/ups/bin/usbhid-ups -DD -a eaton Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 0.000000 debug level is '2' 0.002550 upsdrv_initups... 0.288229 Checking device

On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: > I see a libusb_get_interrupt message in the log. Could that be the problem? Yes, it seems related. 1.126896 upsdrv_initinfo... 1.126906 upsdrv_updateinfo... 1.127023 libusb_get_interrupt: Function not implemented 1.127030 Got 0 HID objects... 1.127036 Quick update... Come to think of it, this

I'm working on a gentoo server with Nut 2.0.5-r1 and libusb-0.1.12. I originally tried the hidups driver which seemed to work, but produced a large amount of unhandled events. Then I tried the newhidups which told me my ups wasn't supported. When I try using tripplite_usb -u root -DDDD /proc/bus/usb/002/002 I get that there isn't a match. But when I try using tripplite_usb -DDDD

On Jun 8, 2015, at 8:23 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > Hi Charles. I patched, reconfigured, remake'd, remake install'd - but > no change. however, some more likely helpful information below for > you. Thank you Odd. Are you sure that the new version of usbhid-ups got installed to the same path you are running? Also, there is no protection against

Hello all, About a month ago Peter and Charles were kind enough to try to help me with getting a Tripp Lite USB UPS to work with NUT. I reported quite a bit of initial success, and then other things here fell apart. Between work, fence building and a week-long out of town business trip, I have had to drop this from my list of things to do lately. I am back at it, and I believe I will have

Hi, I have an MGE Ellipse UPS connected to a FreeBSD 7.0 system and it works OK to begin with but after an hour or so it dies, eg.. Starts out OK.. debug level is '2' upsdrv_initups... Checking device (0463/FFFF) (/dev/usb2//dev/ugen0) - VendorID: 0463 - ProductID: ffff - Manufacturer: MGE UPS SYSTEMS - Product: ELLIPSE - Serial Number: 000000000 - Bus: /dev/usb2 Trying to match device

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

Hello I recently switched from apcupsd to NUT2.2.2 without any troubles. I tried to figure out how I can configure the self-test intervall. The command upsrw lists only the variables battery.charge.low battery.runtime.low ups.delay.shutdown ups.delay.start The command usbhid-ups -D and the listing under http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart at localhost&treemode

Hi, I have two ups (Turbo-X 1000SD, Turbo-X 1500SD). The both report themselves as # lsusb Bus 008 Device 002: ID 0001:0000 Fry's Electronics The are produced by MEC and report MEC0002 as product (although the working one report it in dmesg but not in lsusb) The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) doesn't. I am attaching lsusb and blazer_urb output