similar to: newhidups with APC Smart-UPS 1500

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

Peter Selinger wrote: > Hm. I need more information, as NUT seems to garble the values even > before I can see them. I am not so worried about the date and > temperatures (although, strangely, the battery replacement date > appears to be Sept 25, 2001, which makes no sense). But the voltage is > definitely important. > > [...] > Thanks Peter - I'll send the new

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:

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

> 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

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

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 am having an issue running NUT and using an TrippLite OMNI900LCD. When I run ./upsdrvctl start I get : [player@V0002-S002 bin]$./upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) Detected a UPS: Tripp Lite /TRIPP LITE UPS Using subdriver: TrippLite HID 0.1 (experimental) dstate_setflags: base variable

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 everybody, If we let the feature running, it appears that the driver gets unbound after a while ( variable from quarter of hour to 6 hours ) and cannot reconnect. This behavior appear with both MGE Ellipse ASR and non-ASR models with connection to an UHCI and OHCI controllers. The USB core is from 2.4.28 kernel. We use nut-2.0.3. Start, powerfail and recovery detections, UPS shutdown work

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

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

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

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

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

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:

On Jan 2, 2008 3:34 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Wed Jan 2 20:34:26 2008 > New Revision: 1210 > > Log: > Parsing continues if the HID path for a report ends in 0x00000000 (these will not be made available). Commonly used as placeholders. > > It looks like (but correct me if I'm wrong) that reports

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

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