similar to: Setting offdelay and ondelay in Smart-UPS 1500 RM units

Are there plans to change the default offdelay/ondelay for the Windows versions of NUT since it can't be invoked at the end of shutdown? E.g. I have a Win2k3 server that takes just over 4min to shut down, so I set my offdelay to 600 (ondelay is +15 that) to be extra safe. Maybe a 2 min by default would be good? Most (all?) APC non-smart UPS's are hard-coded at an annoying 1min delay,

Thanks On Sat, 16 Mar 2024 at 18:57, Charles Lepple <clepple_at_gmail.com_chribonn at duck.com> wrote: > > On Mar 14, 2024, at 11:41?AM, Alan via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > > Hi, > > > > My Cyber Power reports these two values. Each pair has the same value. > > > > Would they normally be the same thing? >

On Nov 12, 2014, at 3:53 AM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Hi Charles, > >> Sigh, I wish the vendors wouldn't change operation without changing identifiers. >> >> Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? > > No-no, there is no an old 0x0004 or new 0x0004

Welcome, Acctualy, I'm try to poweroff my ESXi (6.7). Virtual machine with Ubuntu and redirected USB port with APC Back UPS CS 650, have nut-server and send info to ESXi. When battery is low, ESXi poweroff gracefully all VM and same ESX go down. This work fine and don't have any problem. But important to me, is set to more offdelay on UPS than the default 60 sec. (cut off power socket

Hi Charles, > Sigh, I wish the vendors wouldn't change operation without changing identifiers. > > Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? No-no, there is no an old 0x0004 or new 0x0004 device, I guess that we have to handle general case for all 0d9f:0x0004 devices. From PCM_USB_LIST_device2014.pdf attached

Dear All, I am running Slackware64-14.1(Linux marto 3.10.17 #1 SMP Fri Feb 14 16:39:21 CST 2014 x86_64 Intel(R) Pentium(R) CPU G3250 @ 3.20GHz GenuineIntel GNU/Linux) with kernel 3.10.17 and nut package nut-2.6.5-x86_64-1_SBo, buit from source using the build script http://slackbuilds.org/repository/14.1/system/nut/ In the README.Slackware it is suggested that the commands for killing the

Hi, My Cyber Power reports these two values. Each pair has the same value. Would they normally be the same thing? Thanks Alan

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

On Fri, 2 Feb 2018, nut.user.u830 at neverbox.com wrote: > I have an older box set up this way for continuous integration, and it needs to see more than a few seconds of power loss for the "always turn > on" BIOS setting to work. I forget how many different intervals I tried, but 30 seconds of off time is reliable for that particular box. > > Thanks. This

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.

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

Angel Tsankov wrote, On 12/6/2013 12:31 PM: > Hello, Ren?. > >> You can change the parameter >> ups.delay.start into your UPS to set the "Interval to wait before >> (re)starting the load (seconds)" >> >> use upsset to change the value. > > So far, the ups.delay.start parameter in my MGE Protection Center 675 > has always been equal to the

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

Hi, I have the Eaton 5E850iUSBDIN UPS connected via USB to a Raspberry Pi 3B+. It seems that everything but the ondelay parameter works so far. when I test the setup with this command: upsmon -c fsd The NUT server makes the NUT clients shut down properly and the Raspberry Pi running the NUT server shuts down correctly too. The problem is that after UPS shuts down, it immediatelly brings the

On Aug 21, 2018, at 1:37 PM, Karol Olszewski <karol.olszewski at ipflow.pl> wrote: > > I'm send debug file /lib/nut/usbhid-ups -a apc -DDD in attachement. > I tested two different ones APC BackUPS CS 650 and on both problem occurred. > I borrowed PowerWalker (driver blazer_usb), and all function + offdelay, > ondelay works perfectly. unfortunately, it looks like there

W dniu 24.08.2018 o 23:13, Karol Olszewski pisze: > Hi > I'm bit closer :) > Acctually change "UPS.Output.APCDelayBeforeReboot" to > >   { "shutdown.return", 0, 0, "UPS.Output.APCShutdownAfterDelay", NULL, > "90", HU_TYPE_CMD, NULL }, > > Now, UPS turn off load after 90 sec, but not power ON when power is back > Dear nut

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

I got sick & tired of constant power outages with no warning, so when I saw various UPSes at the store, I decided to get one, and the one I got was a model 200897 from Newpoint (a.k.a. Power Sentry). A couple of days later the power went out and I decided to use the opportunity to hook up the UPS. I added up the wattages of the equipment I would be connecting, and found that the only way I