similar to: Looking for a low cost USB UPS that supports shutdown.return

Hello everybody, I got tree UPS devices connected to a Debian server, and i am searching for a way to configure them. The server power-cord is only connected to one of the ups devices, and should monitor the other ups systems to sent email status. I got a HP R3000XR UPS with has a RS232 communication port that I have working perfectly. Then I have two APC SmartUPS 750V devices that are

Hello! I have installed the nut package from the OpenBSD 4.4 packages tree, nut-2.2.1p0 I have a new APC Smart-UPS 750 which I plan to connect via USB. When I try to start the usbhid-ups i get debug level is '2' upsdrv_initups... No appropriate HID device found No matching HID UPS found for almost anything i try. OpenBSD detects my UPS and assigns it to a device and it can be seen

Hi all, I am trying to get a APC Back-UPS CS 500 running on my QNAP 419P Nas. Since on all my work I figure out the following: from Network UPS Tools upscmd 2.4.1 [~] # upscmd -l qnapups Instant commands supported on UPS [qnapups]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper beeper.off - Obsolete (use

?I've been using nut on an APC Back-UPS 750 for several years with no problem, seeing the walled "UPS on battery power" messages during short 1-2 minute outages. This is connected with the original USB cable that came with the unit. After replacing the battery recently, nut always triggers a shutdown when AC power is cut off, even if only for 1 minute. I see that the data fields

Arnaud, I was finally able to get back to this issue and would recommend adding these items to the FAQ #37 about recalibrating the UPS: 1a. It's important that the UPS be at 100% charge before starting the procedure; starting at lower will not work at all, not just produce inaccurate numbers. ? ? ? [I started the procedure when the UPS was at 91% charge. After that it would never report

Hi, I have data room with single master nut instance which calling scripts to shutdown environment. I have two Delta UPS reachable from network. Everything works fine but I need to configure nut to shutdown environment when both UPS on battery or low battery. Can you advise me how to do that (is it possible?). THX for any help. -------------- next part -------------- A non-text attachment was

I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2274 bytes Desc: Kryptograficzna sygnatura S/MIME URL:

On Jan 21, 2014, at 8:05 AM, Rafa? Oleszek wrote: > MONITOR UPS_251 at localhost 2 monmaster password master > MONITOR UPS_252 at localhost 2 monmaster password master I think the "2"s here should be "1". "powervalue is an integer representing the number of power supplies that the UPS feeds *on this system*." So if UPS_251 is connected to one power supply on

On Jan 21, 2014, at 8:05 AM, Rafa? Oleszek wrote: > It does not matter what value I'll put in MONITOR and MINSUPPLIES line. NUT not waiting for both UPS to start timer. Correct. You can think of upssched as operating on raw UPS status, rather than the calculated powervalue that upsmon uses to decide when to shut down. -- Charles Lepple clepple at gmail

I tried all options: 1,2 and in MINSUPPLIES: 1,2,3,4 still didn't work. UPS_251 and UPS_252 feeds all environment and it's not feed directly one server, but many of them. > On Jan 21, 2014, at 8:05 AM, Rafa? Oleszek wrote: > >> MONITOR UPS_251 at localhost 2 monmaster password master >> MONITOR UPS_252 at localhost 2 monmaster password master > > I think the

So it's impossible to configure upssched to start timer only if all ups are in status: OB or LB ? > On Jan 21, 2014, at 8:05 AM, Rafa? Oleszek wrote: > >> It does not matter what value I'll put in MONITOR and MINSUPPLIES line. >> NUT not waiting for both UPS to start timer. > > Correct. You can think of upssched as operating on raw UPS status, rather > than the

On Jan 21, 2014, at 9:27 AM, Rafal Oleszek wrote: > So it's impossible to configure upssched to start timer only if all ups > are in status: OB or LB ? Not impossible, just not possible inside a single configuration file. You can always put that logic into an external script called by upssched. -- Charles Lepple clepple at gmail

> On Jan 21, 2014, at 9:27 AM, Rafal Oleszek wrote: > >> So it's impossible to configure upssched to start timer only if all ups >> are in status: OB or LB ? > Not impossible, just not possible inside a single configuration file. You can always put that logic into an external script called by upssched. > Thank for your help Charles. I checked it and it works like you

On Tue, 16 May 2017, Dinow Hsieh wrote: > BB. Could you show us the output of command "upsc pcmups"? > > ==> Yes. Below 2 mode were the outputs of command "upsc pcmups" > > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 30 > battery.date: 2010/12/20 ... > ups.date: 2010/12/20 > ups.load: 4 ... > ups.status: OB

On May 17, 2017, at 4:53 AM, Dinow Hsieh <dinow at upspowercom.com.tw> wrote: > > ==> I tried below set-command but it react fail > > dinow-All-Series:~# upsrw -s "ups.delay.shutdown"="30" -u pcmups pcmups at localhost > Password: > Unexpected response from upsd: ERR ACCESS-DENIED > This error is not from the driver. Be sure to specify a NUT

> What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines when to shut down. > > Also, if you don't want to wait for both UPSes to drain to the low battery state, you can set up a pair of dummy-ups drivers. I'm

> On Jan 21, 2014, at 9:24 AM, Rafal Oleszek wrote: > >> I tried all options: >> 1,2 >> and in MINSUPPLIES: 1,2,3,4 >> still didn't work. > > My mistake - I gave you the wrong advice before. For MINSUPPLIES, I'm used > to either a 1:1 UPS-to-server ratio, or 2:1 where the server can run with > either power supply unpowered. > > I just tried

Hi all, just installed the nut package from apt on Ubuntu. Here's what I got. Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 This APC device (051d:0003) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the

Hi there... nut 2.4.3 kicks an error at me when I try to talk to my UPS. machine is linux 2.4.21-32.ELsmp with libusb-0.1.8-3 package update. # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver: APC HID 0.95 libusb_get_interrupt: error submitting URB: Invalid

On Jan 21, 2014, at 3:16 AM, Rafa? Oleszek wrote: > I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines