similar to: Is usbhid-ups compatible with APC Back-UPS ES 550VA and 700VA devices?

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

On May 2, 2019, at 4:08 PM, Mathias Passow wrote: > > 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"

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, 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

I have an older system which has a simple APC Back-UPS ES 500 connected via USB. I built nut 2.0.2 from source and am attempting to get it to work. I had to manually create the device links and I think it's ok because hidups is recognizing the UPS but any attempts to read data from it fail: [root@server bin]# ./hidups -D -D -D /dev/usb/hid/hiddev0 Network UPS Tools: HID UPS driver 0.13

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 =

?With Arnaud Quette's help, I have tried to fix the regression concerning the APC Back UPS ES unit. This regression is related to an issue in this UPS firmware. It cannot be reverted to previous version because the current code fixes communication issue with others UPS (which behave correctly, but are not very permissive). So we (Arnaud and I) have decided to add a tweak (call it a hack if you

On 12/27/18 8:09 AM, Charles Lepple wrote: > If you leave off the "-d 051d:" part, do you see anything in the > listing that looks like it could be the UPS? (The 051d vendor ID is > for the vast majority of APC UPS models, but we have seen a few other > IDs here and there - mostly from acquisitions.) > > For instance, this is what one of my development boxes shows

Hi, I cant get it working. Here is my terminal output: root at debian-jessie-final:~# lsusb -d 051d:0002 Bus 001 Device 010: ID 051d:0002 American Power Conversion Uninterruptible Power Supply root at debian-jessie-final:~# ls -l /dev/bus/usb/001/010 crw-rw-r-- 1 root nut 189, 9 Mai 6 15:35 /dev/bus/usb/001/010 root at debian-jessie-final:~# sudo upsdrvctl start Network UPS Tools - UPS driver

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

hi list, im running debian/testing(act. squeeze) with 2.6.26-2-amd64 kernel. first tried apcupsd what flawlessly worked but because i run nagios (needs nut running for 'check_ups'), im trying to run nut. dmesg and syslog show the device: Jul 27 00:08:06 kate kernel: [16001.477941] hiddev96hidraw0: USB HID v1.10 Device [APC Back-UPS ES 700 FW:829.D3 .I USB FW:D3 ] on usb-0000:00:1d.1-1

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

All, I recently connected my UPS to my NAS. The NAS detected the UPS, and I checked the "Enable network UPS server" option and added relevant IPs to the "Permitted DiskStation devices" option. The NAS is running DSM 5.2-5592 Update 4, with a NUT version of SDS5-2-2015Q1branch-5579-15061. I then attempted to connect my desktop via SNMP. My desktop is running Arch Linux, with a

Hi Chad, Thanks for your report. Everything seems fine, apart from the battery.date (2052/00/36), which vaguely recall me something... I've added this info to the Testing and trunk driver.list Arnaud -- Please note my new email address: arnaudquette at eaton.com -- Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader -

Hi Folks, I just bought two APC UPSes, an EX 1300 and an ES 550 for two different sites and installed NUT for the first time on two machines (one Centos 4.1, the other Ubuntu 7.04). So far I'm well impressed -- excellent work by the dev team! The EX 1300 is working beautifully with NUT on the Centos box, but I'm having a bit of a problem with the ES 550: even while loaded, the ups.load

On 12/28/18 12:24 AM, David Melik wrote: > > On 12/27/18 8:17 AM, Charles Lepple wrote: >>> >>>> Maybe it's not a standard ethernet-to-UPS cable? >>> >>> That's Ben's point - either it is actual Ethernet (usually found on an add-on UPS SNMP monitoring card, where the jack typically has two status LEDs, one on either side of the notch for the

I'm using FreeNAS 9.1, and I've just got an APC Back-UPS CS 500. In theory it's supported by NUT, but the latest released version (2.6.5) doesn't have support for it (the driver reports an error, which is apparently due to an overflow). According to a thread on the mailing list, Back-UPS ES series requires a fix that's in source control, and CS series requires an additional

On Dec 26, 2018, at 8:59 PM, David Melik wrote: > > root at 0.darwinheim <mailto:root at 0.darwinheim>:~# lsusb -d 051d: > root at 0.darwinheim <mailto:root at 0.darwinheim>:~# If you leave off the "-d 051d:" part, do you see anything in the listing that looks like it could be the UPS? (The 051d vendor ID is for the vast majority of APC UPS models, but we have seen

Lately I got (used) an APC Back UPS Pro 1000 and Back UPS NS 1080. I got an ethernet-to-USB cable from another UPS, but the Pro isn't detected (with usbhid-ups.) I haven't tried the NS yet but it seems to not be on the list though looks just like the Pro. Some months ago I was discussing setup of a Ferrups 700VA.  I got it to work only with a command in rc.local, but not automatically

Hi there, I'm one of the maintainers of the SME Server distro (www.contribs.org) and we've been chasing this one for some time: http://www.contribs.org/bugzilla/show_bug.cgi?id=352 http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-January/000543.html Many thanks to Peter Selinger and everyone else who helped with the debugging and patches. Thanks, Gordon