similar to: 2.0.3-pre2: Spurious UPS UPS@localhost battery is

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:

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

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

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

> 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 Jun 10, 2019, at 2:32 PM, Marc Finns wrote: > > Hello, I read all FAQ and other sources but I could not find this situation, so I thought of asking the experts. > I successfully configured a Raspberry NUT server to control my UPS that powers several devices (NUC with ESXI VMs, Synology NAS etc). > All works well in principle, but I have the following behaviours that I could not

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

Thanks Kjell for the help with the build problem. Thanks for your input, too, Charles. Now I have a new problem that I think has already been solved. I have Tripp Lite Smart1000LCD UPS (usb), but I can't get the newhidups driver to communicate correctly. I found a thread on the development list from last December where Jonathan Freedman described had a problem with this UPS in a thread

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 Guys Having trouble getting my LiebertPSP UPS to work. $ upsc upsname battery.charge.low: 38 battery.charge.warning: 38 battery.type: PbAc device.mfr: Emerson Network Power device.model: LiebertPSP device.serial: device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.vendorid: 10af driver.version:

Hello! First time posting to this list. I recently purchased a Tripp-Lite OMNIPLUS1000LCD from Costco (USA). I have it attached via USB to a Dell computer with Ubuntu 8.04 server (all updates on it). I've gone through a lot of research on google and this list and can't figure out why my UPS will not connect using nut/usbhid-ups. My setup in ups.conf is: ------- [OMNI1000LCD]

Gentlemen, I have now had a chance to run some initial tests of my changes to apc-hid.c of the current development tree. Running newhipups and inspecting the -DDDD output seems to indicate that with the fix below everything seems to work as expected. However, I have not yet shut my system in order to take the UPS out of action so that I can do my various tests with a lightbulb load. I still hope

On Mar 17, 2015, at 11:46 AM, Philip Taylor <philip at kelsotowers.co.uk> wrote: > Charles, > > Did you get chance to look at the data I sent you, please? > > I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant

OS name and version: FreeBSD 9.0-RELEASE amd64 exact NUT version: 2.6.1 NUT installation method: >From ports collection (cd /usr/ports/sysutils/nut; make install) Exact device name and related information: American Power Conversion/Back-UPS ES 525 FW:851.t2.I USB FW:t2 Complete problem description: /usr/local/etc/rc.d/nut start Network UPS Tools - UPS driver controller 2.6.1 Network UPS

This took a long time because I had problems with my system. After I reloaded my operating system several times I found I had a bad memory module. Here is the output from newhidups for my Geek Squad GS1285U. It just kept repeating until I hit ctl-z. I think that this means nut will work for this ups. My computer is not powered by the ups yet. I did not want it to be powered down by accident.

I'm trying to set up nut-2.6 with a SMX1000 ups unit from APC on a CentOS 4.8 server. It's connected via USB, and Linux has detected it as a HID device. Nut was built from source code. T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 21 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=051d ProdID=0003 Rev= 1.06 S: Manufacturer=American Power

On 10/01/2015 00:45, Charles Lepple wrote: > On Jan 8, 2015, at 11:43 PM, Graham Menhennitt > <graham at menhennitt.com.au <mailto: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