similar to: Windows 2008 R2 USBHID-UPS VendorID & Serial

I'm having trouble with the usbhid-ups driver and Windows. NUT won't connect to an APC SmartUPS 3000 via USB. I've had good success with NUT and Raspbian as well as NUT and Windows using the tripplitesu driver. The current system is: Windows 7 Enterprise 64 bit NUT 2.6.5-6 installed from MSI installer downloaded from networkupstools.org libusb-win32-bin-1.2.6.0 installed and

Hi, Folks, I'm new to this admin game, and one of the hardest parts for me is figuring out where files/programs/data are stored in the file system. I think this is one of these situations. I've installed NUT on my Mac OS X 10.5 server, using the macports build. The machine is a dual processor G4 tower, connected to an APC UPS via USB. usbhid-ups seems to be working, see output

Hello, I was thinking about what could be going wrong here, and a few ideas pop up: 1) If you installed NUT from packaging, there should have been no need to add OS groups/users manually. There is a valid use-case for running different daemons under different accounts, as long as they talk over network and access same files or UNIX sockets at best by sharing a group for that, but it does need

Hi Jim, Thanks for your help. I'll respond in the same order as you did: 1. Unfortunately, I did "chown" stuff to these created users... Since the other three responses don't seem to be what you're looking for (but that's only my uninformed interpretation), I suppose the problem lies here? Is there a number of files/directories that I should

Hello world; been using nut atop Debian GNU/Linux (sid) for about two years by now, my configuration broke as I upgraded the machine this morning (headin' for kernel 2.6 to have full support for the new GBE NIC included). I read through the UPGRADE.gz instructions provided with the Debian packages and tried to fix things according to the instructions pointed out there, but things still just

hi NUT 2.4.3 on new server can not see serial number, but old nut on different hardware can? I have 2 USB-hid ups from APC, 1500 and 3000 RM, i use the serial number to identify them. However my new UPS monitor server can not see the serial number? It works on Linux dkserver 2.6.22.18-vs2.2.0.6 #1 SMP Sat Feb 16 20:54:32 CET 2008 i686 GNU/Linux debian package 2.2.2-6.5 it does not work on

Hi. I use NUT on embedded system, and after update distro to fresh one I've got a non-working usbhid APC monitoring. There's 2 troubles: 1) I/O error for root on usbhid device 2) Permissions error for nut user Root log: # /usr/bin/usbhid-ups -u root -DDDDDD -a infocom Network UPS Tools - Generic HID driver 0.37 (5.1.2-beta1-28-g04cd334) USB communication driver 0.31 0.000000

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

Hello, Upon upgrading to the Debian package of NUT 2.2.0 my APC Back-UPS Pro is no longer recognized. Here is the output if I try to run the driver manually: ----------- # /lib/nut/usbhid-ups -DDD -x vendorid=051d -x productid=0002 -a foxstarups Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-) debug level is '3' No appropriate HID device found No matching HID

Dear list, since some days I own an APC Back-UPS BX1400U. Now I try to connect my Raspberry Pi to it using NUT, but ... ;) The UPS is connected via an USB-cable, and "lsusb" shows an APC device. NUT is installed via "sudo apt-get install nut". My goal: a Synology DiskStation DS1515+ should "read" UPS-data provided from the Raspberry an shut-down itselt at 30%

Hello! I tried NUT 2.6.5-1 (Windows port) with my APC Back UPS ES. It seems I have configured NUT properly, nut-scanner found my UPS: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 525 FW:851.t3.I USB FW:t3" serial = "8B0745R23575

Hi, Can't get newhidups (2.0.5) or usbhid-ups (SVN trunk) to work 2.0.5 hidups seems to work, but I was hoping for more information... like temperature, etc. Tried newhidups and usbhid-ups, but they don't seem to detect my UPS... should I switch back to serial? Will I get more information? (trying not to move back to apcupsd, since i have a mixed environment) Here is some debug

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

Hi. I use NUT on embedded system, and after update distro to fresh one I've got a non-working usbhid APC monitoring. There's 2 troubles: 1) I/O error for root on usbhid device 2) Permissions error for nut user Root log: # /usr/bin/usbhid-ups -u root -DDDDDD -a infocom Network UPS Tools - Generic HID driver 0.38 (5.1.2-beta1-28-g04cd334) USB communication driver 0.32 0.000000

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

Howdy nut-users :) Got a problem with nut detecting my UPS. Here's my scenario. Base platform is a HP ML350 G6. UPS is an APC Smart-UPS 1000. Base OS is VMware ESXi 5.0 with all current patches. I've created a virtual machine using the VMWare supplied VMA. USB passthrough is configured to pass the UPS through to the VMA. So I essentially have a SLES 11 (x86_64) server with a USB

2007/3/14, R.J. Baart <R.J.Baart@prompt.nl>: > Hello, I know you are the nut guru: you helped me before with a > udev problem. That's why I write you again. > > I use the debian package of nut. With some googling I found out > that I am not the only one with this problem. However, does the > latest release of nut solves my problem? I try to figure out, but it > was

Hi list, I seem to need another pair of eyes. Here's my ups.conf: [myups] driver = usbhid-ups port = auto vendor = 051d product = 0002 serial = 4B1717P25055 And here's the output of `/lib/nut/usbhid-ups -a myups -DDD`: 0.017467 Trying to match device 0.017479 Device does not match - skipping 0.017499 Checking device (051D/0002) (001/003) 0.094770 -

Hi all, Yesterday, I bought a UPS for the first time in my life, and was eager to dive into NUT. But not all is working as expected... I saw a similar thread started on 18 October, but it didn't help me. (I also spent a handful of hours searching the web for solutions, and of course read the manual and FAQ - "queequeg".) I tried shutting my UPS (APC "Back-UPS BX750MI

Hi, the following UPS isnt supported by the driver "usbhid-ups". Manufacturer: APC Model: Back-UPS 950 (https://www.apc.com/shop/de/de/products/APC-BACK-UPS-950VA-230V-AVR-Schuko- Sockets/P-BX950U-GR) Config: [USV] driver = usbhid-ups port = auto desc = "USV" . MODE=standalone Terminal: root at debian-jessie-final:~# sudo upsd -u root