similar to: APC SmartUPS 1500 not working for newhidups and usbhid-ups

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

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

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

I need direction. I don't know what to google for anymore. I am unable to get my SmartUPS 2200XL to be recognized. My suspicions are that it's UDEV or Kernel related. I've updated the kernel to the highest version I feel comfortable with due to other things that run on the server, and I've updated UDEV a bit too. When I plug in the USB cable from the UPS into the server, I

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 =

Hi all, I've tried installing NUT from both the Debian packages and the 2.0.4-pre1 source but I'm unable to sort out the USB permissions when using the newhidups driver and an APC XS series UPS. In each case, I'm able to run newhidups as user root but running it as user nut fails: --- as 'nut' # /lib/nut/newhidups -u nut -a apc1 Network UPS Tools: New USB/HID UPS driver 0.28

Hi all, I just downloaded, built and installed nut-2.0.4-pre2. I have an APC Smart ups 3000 connected via a usb cable. I have compiled and installed the usb drivers. I installed the libhidups and libhid.usermap per the README. I have the following ups.conf: [APC-3000-ups] driver = newhidups port = auto desc = "APC smart 3000" When I try to start the driver I get the

Gentlemen, Please note that what follows pre-dates the latest changes from Arnaud (just thought someone might want to look at these before I can test the latest!). When running newhidups with -D -D -D I saw messages that looked like errors, and it took me a while to understand that they were not really errors. I therefore added two new entries in apc-hid.h, and I modified a couple of diagnistic

I have a SmartUPS 750 (SUA750) which has the temperature and humidity SmartSlot card installed. When NUT 2.2 communicates with this UPS over /dev/ttyS0 using apcsmart, using the APC Smart cable connected to the SUA750 serial port, and this ups.conf: [su700] driver=apcsmart port = /dev/ttyS0 I can see the ambient temperature and humidity data with "upsc su700 at

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 have this strange problem with APC BackUPS RS 1500 ? older one model, white one under windows in powerchute is device OK, working everything ok selftest ok, just ordinary ups. under CentOS 7 minimal (CentOS-7-x86_64-Minimal-1708.iso) kernel version 3.10.0-693.el7.x68_64 driver version 2.7.2 i have this strange probem: nut driver didnt start automatically with error, after i enter in

Hello, i have this strange problem with APC BackUPS RS 1500 ? older one model, white one under windows in powerchute is device OK, working everything ok selftest ok, just ordinary ups. under CentOS 7 minimal (CentOS-7-x86_64-Minimal-1708.iso) kernel version 3.10.0-693.el7.x68_64 driver version 2.7.2 i have this strange probem: nut driver didnt start automatically with error, after i enter in

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

Folks, while I've got the above combination to compile and run under Solaris 10, it seems that there are still problems in the libusb/ugen driver stack from Sun and or the APC Smart UPS 1500, so things aren't actually working. It seems that the APC Smart UPS 1500RM doesn't return the HID descriptor length information in 0x21 as noted in a previous thread, but in my case, it also

Thought I would write some notes about how I got an APC BackUPS XS 1500 working with newhidups under Gentoo 2006.0. The specific issue here is the permissions on the device files used that libusb uses to access the USB hardware. I followed Peter Selinger's instructions at http://www.mscs.dal.ca/~selinger/ups/backups.html on getting newhidups going with an APC device. The sticking point for

I ran into the following issue today and would like some feedback from the group. Setup: I am using a MGE Pulsar Evolution 2200 UPS connected through a Belkin (F5U218-MOB) 4-Port USB Hub. Scenario: The newhidups subdriver_matcher function calls belkin_subdriver->belkin_claim. The belkin_claim function in belkin-hid.c matches the VendorID of the hub to Belkin's VendorID (0x050d), causing

On Mar 27, 2018, at 5:47 PM, <p1_p1_p1 at seznam.cz> wrote: > > if somebody has same problem with APC BackUPS (SmartUPS works correctly in same USB) > USE FASTEST USB that U have on board, (if you have USB 2.0 and USB 3.0 onboard use one 3.0 port for UPS), > sounds like nonsense, but it works, just OMG and halelujah for linux usb drivers. According to this, your UPS is using

Hi all, I have an APC/Smart-UPS 3000 RM that I am trying to connect to nut via the usb port. I have nut running just fine on several other machines using APC ups's via the serial ports but this usb thing is making me crazy. If I do a "/sbin/newhidups -u root -D -a PS1" it recgonizes the ups and dumps a bunch of information like below: (porky pts12) # /sbin/newhidups -u root -D -D

'lo, UPS model: APC Back-UPS BR 800 (supplied by Dell) My USB connection: Bus 001 Device 002: ID 051d:0002 American Power Conversion Back-UPS Pro 500/1000/1500 # upsc desk@localhost|grep load ups.load: 0.0 This UPS has 2 pc's and some minor other gear connected, yet the load stays at 0.0 when checking with nut. driver.version: 2.0.5 driver.version.data: APC/CyberPower HID 0.9

Hi. Is the subject UPS model supported? I believe so, but I don't have a unit to test with. Any comments on this model? I'm trying to advise a colleague. Thank you, as always. T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 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