similar to: APC Back UPS ES 700

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

Hello, I have an openups2 ups. It works very well with nut, except two things: 1) It keeps sending a 'libusb_get_string: invalid argument' message to the log; 2) It does not report any command. Following http://nut-upsdev.alioth.debian.narkive.com/bmJyFFkO/libusb-get-string-invalid-argument, I was able to fix the error message using the attached patch. I do not know how ot fix the

?Hello, There is a new intermediate Windows binaries release available at : http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-2.msi This fixes three regressions: - upssched was not working - Event logging was not working (unless for NUT service binary itself) - usbhid-ups was not working with Back-UPS ES ups. Feedback is highly appreciated. Regards, Fred -- Eaton

Hi all, I have problem with UPS from PowerWalker model VFI 2000 RT LCD over USB (didn't try serial yet). UPS should work via HID driver but ups.status is not rendered properly. Specification of UPS says USB HID compatible. HID driver is the only one which talks with UPS as i try a few from /lib/nut. I use driver usbhid-ups (which communicate with ups), but subdriver resolving is

?Hello, There is a new intermediate Windows binaries release available at : http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-3.msi This fixes a regression about stopping the NUT service. Feedback is highly appreciated. Regards, Fred -- Eaton Opensource Team - http://opensource.eaton.com ----------------------------- -----------------------------

look : winbind depends on samba (= 2:4.1.18+dfsg-3~inverse1); however: >2:4.1.18+dfsg-3~inverse1 so mixed setup of ubuntu with inverse packages of samba. You need to use the inverse packages of samba to keep openchange working. I suggest you set your package pinning. OR ! remove the inverse : winbind version and install the ubuntu version. Greetz, Louis >-----Oorspronkelijk

> I suspect you will want the newer version for production (there was some > issue regarding the popups when certain events happen), but let's get this > version working first before changing another variable. Appreciate that. Agreed. > For reference, I think the source code to NUT.exe is here: > https://github.com/networkupstools/nut/blob/Windows-v2.6.5- >

On Sep 14, 2016, at 9:29 AM, Jeff Bowman <jeff.bowman at intexx.com> wrote: > C:\Users\Admin>upsc ups at localhost > battery.charge: 100 ... > ups.status: OL If ups.status follows the state of line power, the driver is working (and upsc talks to upsd, so that connection is working as well). > So this all represents significant progress. But we're not out of the woods

?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

Hello all, There is a new Windows package of NUT. It now contains nut-scanner binary. Note that there is a known issue with libupsclient.dll with nut-scanner. The scan of NUT servers using nut-scanner will not work for now. You can find it at : http://www.networkupstools.org/source/2.6/NUT-Installer-2.6.3-1.msi Please send feedback to the list. Regards, Fred -- Team Open Source Eaton -

Network UPS Tools version 2.6.5 has been released: http://www.networkupstools.org/ Among the many improvements and bugfixes, this release fixes the upssched regression, that rendered it unusable. Update to 2.6.5 is thus highly recommended. As noted in the news, website hosting is under migration. While I don't expect any service disruption, please report any issue you may face. Direct

I was wondering what you guys do about UPS shutdown on Windows systems? Apcupsd has the same issue, so I'm assuming it is the same with NUT. Windows just makes it hard/impossible to do. Do you find draining the batteries down so much cause issues for longevity? Regarding my Eaton 5110, I found that automatic driver setup works just fine on Windows XP but not at all on Windows 7 x64 (I

My network at home/home office is primarily a Windows environment. However, I have 3 ReadyNAS Ultra machines which use NUT for UPS monitoring. The ReadyNAS devices are running a slightly modified Debian (2.6.37.6.RNx86_64.2.4) with NUT 2.0.5. What I would like to do is add some sort of web-based UPS monitoring on my intranet web server (IIS 7.5 on 2008 R2), however nut-cgi appears to be

Hi, the terminating part of nut-scanner can crash in pthread code, because some threads won't exist. For example snmp part: ============================== if( allow_snmp && nutscan_avail_snmp ) { if( start_ip == NULL ) { printq(quiet,"No start IP, skipping SNMP\n"); } else { printq(quiet,"Scanning SNMP bus.\n"); #ifdef HAVE_PTHREAD if(

> On Sep 11, 2016, at 3:37 PM, Jeff Bowman <jeff.bowman at intexx.com> wrote: > > > > Using subdriver: APC HID 0.95 > > > > ...and then hangs for 45 seconds before returning to a command prompt. No > UPS hardware information is printed. > > It can take about that long to read the descriptors. The non-Windows NUT > drivers will print that message,

I was doing some testing with the 2.6.0-1 beta Windows installer and a Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the usbhid-ups driver if the UPS is lost on the UPS bus. This is on a Windows XP SP3 system. USB device access is via libusb 1.2.4.0 (driver mode, not filter) in case that matters. Everything seems to work just fine so far while the UPS is connected (so kudos,

Hi all ! I have a little problem using NUT from FreeNAS. Operating system FreeBSD 8.3-RELEASE-p4 (FreeNAS 8.3.0 BETA 2) UPS American Power Conversion/Back-UPS CS 650 FW:817.v7 .I USB FW:v7 NUT Driver Network UPS Tools - Generic HID driver 0.37 (2.6.5) USB communication driver 0.31 Trying to configure the UPS from FreeNAS failed so I try to investigate which is the problem. Running

Hello, I am currently working on the nut scanner. For detecting available upsd on the network, I rely on upscli_connect. The problem with this function is that it calls a blocking "connect" function. So the nut-scanner is blocked while waiting for the TCP timeout when trying to connect to an IP without upsd available . Since this timeout may be rather long (3 minutes on my host), I

Windows 7 Pro x64 Eaton 3S550 (brand new, battery mfg 8/15/2012) NUT 2.6.5-3 ups.status: OL CHRG CHRG was present even though it has been plugged in a few days turned on and battery.charge was 100%. Log includes me running upsc and removing power long enough to see that battery.charge will decrease. This UPS doesn't have controlled outlets despite what the upsc output says. ---

Charles Lepple a ?crit : > Thanks for the patch. For reference, what does the rest of the "upsc" > output look like for this device? Here it is: $ upsc openups2 Init SSL without certificate database battery.capacity: 100 battery.charge: 100 battery.charge.low: 5 battery.charge.warning: 20 battery.current: 0.000 battery.mfr.date: battery.runtime: 3932100 battery.temperature: