similar to: compatibility

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

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 am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. The attached UPS is an APC xs1500 (model bx1500g). The connection is an RJ45 to USB cable. Here is my ups.conf: [xs1500] driver = usbhid-ups port = auto desc = "APC Back-UPS xs1500" The problem I am encountering is upsd crashing with an 'Out of memory' error. I can

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%

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

On Nov 8, 2014, at 6:12 PM, Selva Nair <selva.nair at gmail.com> wrote: > Everything works rather well, except that the cgi-interface does not report input/output voltages and load for the C 1500 unit. > upsc also reports these values only for model 1000, not for 1500. Battery charge is and runtime are reported. For the 1000, do the values match this page?

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

Thank you, looks like the regex idiosyncracy might have been the issue. My current file: [sl] driver = usbhid-ups port = auto desc = "CyberPower UPS SL" product = "SL.*" productid = 0501 vendorid = 0764 #model = "SL Series" [ab] driver = usbhid-ups port = auto desc =

Hi all, I just got myself 2 APC Back-UPS CS 350 I downloaded the stable nut tar.gz installed it. This is not the first time i install and configure nut so i used the same configuration as on my other server as i always did. Then i made the 2 required modification. I changed these 2 thing: driver = apcsmart port = /dev/hiddev0 # ls -al /dev/hiddev0 crw------- 1 nut nut 180, 96

Thanks! FWIW if you do get to test new code, https://github.com/networkupstools/nut/pull/1811 adds warnings for situations like yours. Would be great to check if it works actually, with many "same-serial" devices :) Jim On Sat, Jan 14, 2023, 23:39 Bruce Pleat <bpleat at gmail.com> wrote: > Thank you, looks like the regex idiosyncracy might have been the issue. > > My

Hello! I have tested APC Back UPS ES 700 and NUT 2.6.5-3 a few days ago and I have got some news. This device is detected by nut-scanner as: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 700 FW:829.D2 .I USB FW:D2 " serial =

Part of what made my life harder is nut-scanner isn't in the package. Once I get a chance, I'll update to 2.8, but that'll be a little while off. (Any clue how to get 2.8 included in the package provider for my Raspberry Pi is presumably beyond the scope of this list, but if someone knows and wants to let me know, I wouldn't complain...) On Sat, Jan 14, 2023 at 3:12 PM Jim

Hi, I have setup NUT in netserver mode on debian wheezy with two APC UPS units connected to it by usb. lsusb identifies the units as Smart-UPS 1000 and Smart-UPS C1500. It appears these do not use the smart protocol and usbhid-ups is the correct driver to use. System: Debian wheezy with stock version of nut (Version: 2.6.4-2.3+deb7u1) Everything works rather well, except that the

Just a note: recent PRs are naturally not in 2.8.0 release (April 2022), but would be in eventual 2.8.1 Jim On Sun, Jan 15, 2023, 00:51 Bruce Pleat <bpleat at gmail.com> wrote: > Part of what made my life harder is nut-scanner isn't in the package. > > Once I get a chance, I'll update to 2.8, but that'll be a little while off. > (Any clue how to get 2.8 included in

On Jan 1, 2019, at 7:06 PM, Stuart D. Gathman wrote: > > On Tue, 1 Jan 2019, Stuart D. Gathman wrote: > >> Our server has 2 UPS on 2 PSUs. At 8am, someone unplugged one UPS. At >> 8:10, they plugged it back in, but turned off the load - presumably to stop >> the beeping. >> So the system is still up on 1 PSU, and can talk to both UPS. Can't I turn

On Jan 24, 2015, at 12:45 AM, Ryan Sizemore <ryan.sizemore at gmail.com> wrote: > Hello, > > I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. I am not sure why they are not listed on the main download page, but there are actually three Windows MSI releases after that: http://www.networkupstools.org/package/windows/ I

Hi all, I'm currently trying to install a APC Back-UPS ES 700 on FreeBSD. This UPS has a usb connection to the PC and is recognized as: ugen0: APC Back-UPS ES 700 FW:829.D2 .I USB FWD2 rev 1.10/1.06, addr 2 my ups.conf looks like: [back-ups] driver = usbhid-ups port = auto desc = "server" When I now run /usr/local/libexec/nut/upsdrvctl start the output is: Network UPS Tools

Hi, I've got a question about managing two UPSes under NUT. I have two similar model APC usb-connected UPSes to work with, but don't know how to manage them simultaneously from under Windows. Long story short, my ups.conf looks like this: --- ups.conf --- [ups1] driver= usbhid-ups port= auto serial=AS1054340323 [ups2] driver= usbhid-ups port= auto serial=AS1026662626 ---

I was testing out newhidups with an APC UPS, and I noticed that I needed '-x vendor=American.Power.*' instead of '-x vendor=APC.*' as indicated in the man page. Do other APC USB UPSes use 'APC' in the vendor string? Should we sidestep any such problems and just go with the hex vendor ID for APC examples? This was tested with a snapshot from the development branch, but the