similar to: after power outage and proper shutdown, UPS turns on before power returns

On Tue, Oct 2, 2018 at 3:59 PM Charles Lepple <clepple at gmail.com> wrote: > > On Sep 27, 2018, at 6:59 PM, Gabriel <jarod125 at gmail.com> wrote: > > > > Hi, > > > > I'm struggling with a peculiar issue with my UPS. After a power > > outage, the devices powered by it properly shut down via nut. > > Eventually, the UPS also goes down.

On Sep 27, 2018, at 6:59 PM, Gabriel <jarod125 at gmail.com> wrote: > > Hi, > > I'm struggling with a peculiar issue with my UPS. After a power > outage, the devices powered by it properly shut down via nut. > Eventually, the UPS also goes down. Power is still out, however, > roughly 40 seconds after the UPS shut down, it turns back on and it > starts supplying

On Oct 3, 2018, at 8:13 PM, Gabriel <jarod125 at gmail.com> wrote: > > On Tue, Oct 2, 2018 at 3:59 PM Charles Lepple <clepple at gmail.com> wrote: >> >> On Sep 27, 2018, at 6:59 PM, Gabriel <jarod125 at gmail.com> wrote: >>> >>> Hi, >>> >>> I'm struggling with a peculiar issue with my UPS. After a power >>>

Hello, I am a new user of NUT and trying to wrap my ahead around a couple of things. I installed NUT 2.7.4-13 from package on RasPi 4, running Raspbian Linux 11 (bullseye). I have Cyberpower SL700U connected to it. For testing I set battery.charge.low to 90, so I wouldn't have to wait a long time. See all relevant config below. First of all, what seems to happen is that UPS gets to the low

Hi there, I just purchased a CyberPower BR850ELCD and while setting NUT up with the install instructions from the homepage was pretty straightforward, and the UPS was detected by the usbhid-ups driver, I'm having problems getting the UPS to work properly. First issue: whatever I set as the offdelay, seems to be ignored and the UPS just cuts the power about 2sec after receiving the

> > After sending the email, I revisited the usbhid-ups driver man page > > and found the part that specified that ondelay=-1 can be used in the > > scenario I am facing (for some reason, I haven't noticed this when > > initially reading the docs). And sure enough, this works, but the side > > effect is that the UPS won't come back when power returns. I've

Hi, thanks for your reply. >> The Unit is new, the battery drains because it went down to about 15 >> percent before NUT shuts it down. >> >> Yes, I can here a "clac". The problem is not the shutdown procedure, >> it works quite good. After the Unit reaches 20 percent the NUT-Server >> on the pi shuts down the system and the ups is turned off as

On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote: > Hi there, > > I just purchased a CyberPower BR850ELCD and while setting NUT up with the install instructions from the homepage was pretty straightforward, and the UPS was detected by the usbhid-ups driver, I'm having problems getting the UPS to work properly. > > First issue: whatever I

2018-02-28 21:11 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > Hello, > > I think that on this file nutdrv_qx_megatec.c the definition for > shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m > while on the megatec protocol description ( > http://networkupstools.org/protocols/megatec.html) the command is just > "S%s\r".

> On Apr 23, 2024, at 3:51?PM, tim.o via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > The value changed to battery.runtime.low: 16, instead of 3600. I don't understand why, because executing the command resulted in SUCCESS. Unfortunately, the SUCCESS response is just saying that upsrw was able to send that request to upsd (i.e. the username/password were

On 12/06/2013 10:57 PM, Kris Jordan wrote: > [...] > (*) Some UPS's do provide extra options to determine when they will > restore power to load. That would be a nice feature. Anyway, it is a strange thing that I can set the waiting time for power to be restored if main power comes back before offdelay has elapsed, but the UPS ignores this setting if main power comes back after

Angel Tsankov wrote, On 12/24/2013 1:22 AM: > On 12/06/2013 10:57 PM, Kris Jordan wrote: > > [...] >> (*) Some UPS's do provide extra options to determine when they will >> restore power to load. > > That would be a nice feature. > > Anyway, it is a strange thing that I can set the waiting time for > power to be restored if main power comes back before

Hi all. UPS is Eaton 5SC 500i. I tested three solutions: 1. swap "usbhid-ups -a qnapups" with "usbhid-ups -a qnapups -k" Result: server shutdown, but ups does not shut off! 2. run prog with params "upsmon -c fsd" Result: server shutdown, but ups does not shut off! 3. run prog "upscmd -u name -p passwd qnapups shutdown.return" and next

On Sun, 27 Oct 2019, EP wrote: > I can't imagine that's the way cyberpower wants their unit to work. With this > behavior the unit does exactly the opposite of what it is built for. It > doesn't protect your equipment. It will destroy it because the server which > was just shutted down cleanly will boot again on a battery-powererd ups. What > a crap. > > But I

An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200217/b486de30/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: usbhid.zip Type: application/zip Size: 4031 bytes Desc: not available URL:

Answers bellow. 2018-02-28 1:41 GMT-03:00 Daniele Pezzini <hyouko at gmail.com>: > 2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > > Hi, > > > > I had an issue where after returning the power from a shutdown.return the > > ups would do another shutdown.return during the boot, and kept this > forever. > > After some

>> [Roger wrote:] >>> By the way, do you have offdelay and ondelay values in your ups.conf ? >> >> No, I haven’t. I just added. Should I add more lines here? >> >> maxretry = 3 >> >> [ups] >> driver = usbhid-ups >> port = auto >> desc = "CPS" >> pollinterval = 15 >Yes, ondelay

Hello, I installed NUT on raspberry pi as a NUT-Server. It works fine so far with a Cyberpower OR600ELCDRM1U (used driver: usbhid-ups). The Pi recognizes power loss and shuts down itself and the ups as it should. Problem: The UPS comes up immediately after shutting down. This is a big issue because there is no power, the server (NUT-Slave) begins powering up and the battery will drain

Cyber Power Systems CP600LCD https://www.cyberpowersystems.com/product/ups/cp600lcd/ upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2220 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS CP600 device.type: ups driver.name: usbhid-ups

This was very helpful for me, thank you! On Sat, Oct 24, 2020 at 9:06 AM Charles Lepple <clepple at gmail.com> wrote: > The easiest way to tell if upsd is working is to run "upsc -l" on the same > system, which will list the NUT UPS names, and then run e.g. "upsc mge" > (replacing "mge" with the name returned by "upsc -l") > Here was the