similar to: APC Smart-UPS 1000RM issues with newhidups

Well, after our first real extended power outage, I found out that even though the UPS 1000 RM is recognized okay, it does not work properly. It never seems to see any change in UPS status. It looks very similar to the other issue I reported with the APC CyberFort 350. I never was able to get to the bottom of the CyberFort issue, but I'll bet it's the same issue as we have with the

Does anyone on this list have a CyberFort 350? It's a European model, and should be equivalent to the US BackUPS ES 350 model. What I'm seeing is upsd reporting stale data. While the battery is running down, upsc doesn't see the battery % changing, so I'm assuming the driver isn't collecting data at that point. Unfortunately, the system/UPS is not here (I'm in the

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

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

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

Hi. I had a problem recently with %subj, and I've solved it. Sent a letter with solution to maintainers, but it seems like I've lost it somewhere. May be just simply forgot to write it.. But anyway. I've noticed that I'm not the only one who had it. So I post the workaround. The problem is similar to the one mentioned in letter with alike subject at Oct. 5. When the UPS

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

Greetings, I'm new to the list, and didn't find an archive, so please bear with me: I have a new APC Back-UPS XS 1200 model BX1200. The USB cable attaches with an RJ-45 on the UPS side. I'm using the hidups driver, and the default log format gives me lines like this: 20060317 041353 100 NA 0 [OL] NA NA 20060317 041454 100 NA 0 [OL] NA NA Can I do better than that with (a

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

Hi there, I'm trying to track down a problem with said combination. Broadcast message from nut (Thu Jan 26 13:22:06 2006): Communications with UPS UPS@localhost lost Broadcast message from nut (Thu Jan 26 13:22:11 2006): UPS UPS@localhost is unavailable "newhidups -DDD hiddev0" seems happy enough, as does "upsd -DDD -f" - at least until I start upsmon. Then I

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

Hi Scott, Scott Alfter wrote: > I had a UPS go bad recently (shuts off all by itself for no good reason, >AFAICT), so I bought a CyberPower 685AVR this afternoon. The two CyberPower >drivers in NUT 2.0.2 don't know how to talk to it, but the hidups driver >appears to work properly. This means you have to use USB instead of RS-232 (it >supports both), but at least it works. >

I'd like to submit a patch to the 'hidups' driver. I'm a bit new to open-source development model, so I hope I'm not committing a faux paus by just posting it here. I did verify that the problem still exists (by source code inspection) in the latest dev snapshot, which is nut-2.0.3-pre2. I'm using nut-2.0.2 myself. The problem is when I'm connecting to my APC

Paolo, Try sudo /lib/nut/newhidups -DDD -u root -a SmartUps1500 newhidups would only run on my computer if I ran it using sudo and as root user. I know this indicates a problem with the USB permissions, but I could not, for the life of me, get the permissions to change when I plugged the UPS in. I know this isn't a true fix, but it worked for me. -- ~Brian Foster

I am forwarding the below message. Does anybody on this list know anything about this problem? Petr - perhaps you should switch from the "hidups" to the "newhidups" driver. I believe it supported the APC Back UPS even in NUT 2.0.2, and it certainly does so in the Development version that you can get from CVS (see the NUT download page). Also, could you post the output of

Whenever I try to use the newhidups driver with my new UPS I get the following message: #/lib/nut/newhidups -DDD -a SmartUps1500 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) debug level is '3' [...skip unrelevant device...] Checking device (051D/0002) (001/005) - VendorID: 051d - ProductID: 0002 - Manufacturer: American Power Conversion - Product: Smart-UPS 1500 FW:601.3.I USB

I'm using an APC Back-UPS XS with nut 2.0.3. I've recompiled/reinstalled the source, and switched over to the newhidups driver (instead of the old hidups driver). I modified by ups.conf to use newhidups. The hotplug files were not automatically installed, I had to copy those from the scripts directory to my hotplug/usb directory. The newhidups driver loads find and then works for a

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