similar to: (no subject)

Hello, I have encountered problems trying to set up nut to work with APC BackUps Pro CS connected over USB to an AMD64 machine running Debian. While apcupsd works fine with that device, whenever I start upsd I get the following messages in syslog: hidups[23159]: Startup successful upsd[23160]: Connected to UPS [apc1]: hidups-hiddev0 upsd[23161]: Startup successful hidups[23159]: Unhandled event:

Hi, I'm new to nut, just installed it. I configured it using the hidups driver to work with my APC BackUPS: # upsc apc350@localhost battery.charge: 100 battery.runtime: 885 battery.voltage: 13.5 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.delay.shutdown: -1 ups.delay.start: 0 ups.load: 660 ups.mfr: American Power Conversion ups.model: Back-UPS CS 350

Hi! I've got a Mandrake 2006.0 machine and a APC Back-UPS Pro 500/1000/1500 (from lsusb). The Mandrake package version of nut is 2.0.1 and hidups actually detects the UPS, however I get loads of these: Sep 12 18:26:11 vader hidups[7658]: Ignoring x86 page event 0xff860080 (0) Sep 12 18:26:11 vader hidups[7658]: Unhandled event: 0x840058 (6) Sep 12 18:26:11 vader hidups[7658]: Unhandled

Another update! It works. The systems shuts down properly when power is lost. Almost. "upsdrvctl shutdown" disconnects my UPS from the mains. From everything I've read in the documentation this should turn off the output of the UPS, not the input. Am I right here? I'm still having the following problem. Any help is appreciated. >> Also - I get the following every 4

An update - I ran a test by unplugging my UPS and letting it run down. The system shut down as it should. However, the /etc/killpower file was not created, and the UPS did not shut off power as it should from the shutdown scripts. This may be because the command to kill the output of the UPS isn't available, or that by not being able to log in as master prevents this. The permissions on the

Using the "hidups" driver produces better results, however, I'm not sure if these "unhandled events" errors are good or bad.. I would suspect bad... Any direction would be appreciated.. Thanks, Richard. root@excalibur:/usr/src/nut-2.0.5-pre2# ./drivers/hidups -u root -DDDD -a apc /dev/usb/hiddev0 Network UPS Tools: HID UPS driver 0.13 (2.0.5-pre2) Warning: This is an

I am having problems building usb on mac os x. First, mac os x doesn't seem to have asm/types.h, just sys/types.h. I can't find hiddev.h on mac os x either. Also, it doesn't have usb.h but instead IOKIT/usb/USB.h. I am using mac os x (10.4), and the latest cvs of nut. Is the new usb support going to work on mac os x? Is anyone working on it? It seems that libusb is available

Greetings, When starting upsdrvctl with the hipups driver, I get the following "addtional" output Unhandled Event 0x840073 (0) Ignoring x86 page event 0xff86002 (0) Ignoring x86 page event 0xff860029 (34) It does not appear to be affecting anything in my tests so far.. (not finished with the entire install process yet) but was hoping someone might have an idea..

Nut shut down a machine last night when there was no power outage. When I came in this morning, the UPS was turned off, but it turned on cleanly and passed its self-test. The battery was at 62% when I first checked it, and it's up to 63% now, about 20 minutes later. The UPS is a Tripp-Lite AVR550U. I'm running nut version 2.0.3. I expect to be told to update to a newer version and to

I Seem to have made some progress in getting nut-2.0.5 installed, but hidups still has a version number of 0.13. First is hidups 0.13 the correct version? if not how do I find the correct version. Second if my Geek Squad GS1285U UPS is not supported how do I proceed. I have been a programmer for 35 years(mostly high level computer aided design), written code in 20 some languages, am retired

2006/1/13, Paul Mogren <fkamogee@yahoo.com>: > > This thread is FYI. I don't need any help here. > no, but some details for those who will read it, maybe ;-) I have SUSE 10.0 and an MGE Ellipse. I installed the NUT package from MGE. > > 1) The generated ups.conf pointed to a bad location: > /dev//dev/input/event0 > who generated that ? it seems like an old hiddev

Good afternoon, I am trying to communicate with a new Tripp-Lite UPS via usb and having little luck. After more than a week on this I've decided to ask for help. I am very inexperienced at posting information to message boards, so hopefully I'm doing this right. I assume this is the correct place to post this message. I will start with the equipment I have. I am using Debian Sarge

is there a way to override the productid (like -x productid=1234) when using newhidups? just thought i'd try it with the F6C1500-TW-RK over usb. i was able to get hidups to work using the below settings, but it provides limited information. my ups.conf entry: [belkin] driver = hidups port = /dev/usb/hiddev0 and the output of upsc: gateway:/etc/nut# upsc

I downloaded nut-2.0.5 and followed the install instructions down to step 6. Since I will be using a USB port to connect to the Geek Squad GS 1285U did not go any farther yet. I tried to run "/lib/nut/hidups -DD -u root auto" to see if it found my UPS. But it is still the old hidups 0.13 from nut-2.0.3. Do I need to do something additional to get the new hidups?

I just installed NUT and my UPS is an APC Back-UPS ES 500. I looked in the list of drivers and found APC Back-UPS ES 350 listed in "drivers.txt" -- that list said I should use either the newhidups or hidups driver. I looked in the installation and I found headers and c files to create these drivers (I think), but in /usr/local/ups/bin there is no driver named, "newhidups or

Hello Linas, > Just wanted to inform You (for the compatibility list), that HP R/T2200 works perfectly with the hidups driver. Thank You very much for NUT! :) > > # upsc hp at localhost > battery.charge: 100 > battery.chemistry: PbAC > battery.voltage: 22.7 > driver.name: hidups > driver.parameter.port: /dev/usb/hiddev0 > driver.version: 2.0.5 > ups.delay.shutdown:

Greetings, I imagine this question must have been answered previously on the list, but I can't search for the answer because the archives are gone. Executive summary: I am trying to install and configure nut 2.0.1 on Fedora Core. I have a SmartUPS Pro plugged into a USB port. Upsmon is logging "UPS myups@localhost is unavailable" to syslog and via wall when it starts up and

Hi, All! I've recently bought an UPS. It is Krauler UP-M500VA, it has USB port and is a HID device. But as I discovered the only HID application it supports is 0x860004, so it isn't claimed by both hidups and newhidups drivers, because it uses a vendor-specific values. I tried to discover values in that x86 page, but I failed. How can I do it? And after I get values how to understand

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried