search for: apcshutdownafterdelay

...For reference, here's the thread related to adding that mapping: https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-January/006550.html > 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 -- Karol Olszewski ipflow.pl

...ed. > I borrowed PowerWalker (driver blazer_usb), and all function + offdelay, > ondelay works perfectly. unfortunately, it looks like there are several different places where the offdelay value could be applied: 1.478906 Report[get]: (3 bytes) => 26 00 00 1.478968 Path: UPS.Output.APCShutdownAfterDelay, Type: Feature, ReportID: 0x26, Offset: 0, Size: 16, Value: 0 1.489559 Report[get]: (3 bytes) => 27 ff ff 1.489622 Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID: 0x27, Offset: 0, Size: 16, Value: -1 [...] 1.539002 Report[get]: (3 bytes) => 41 ff ff 1.539068 Path: U...

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 users, Two APC Back-UPS CS 650 1) Firmware 817.v4.I 2) Firmware 817.v3.I File apc-hid.c line 431  { "shutdown.return", 0, 0, "UPS....

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

W dniu 23.08.2018 o 02:16, Charles Lepple pisze: > > For some reason, this is being hardcoded to 1: > > drivers/apc-hid.c- /* used by APC BackUPS CS */ > drivers/apc-hid.c: { "shutdown.return", 0, 0, "UPS.Output.APCDelayBeforeReboot", NULL, "1", HU_TYPE_CMD, NULL }, > > Can you rebuild the NUT drivers as described here?

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

...208.000000 > > Path: UPS.Output.LowVoltageTransfer, Type: Feature, Value: > > 208.000000 > > Path: UPS.Output.APCDelayBeforeStartup, Type: Input, Value: 0.000000 > > Path: UPS.Output.APCDelayBeforeStartup, Type: Feature, Value: > > 0.000000 > > Path: UPS.Output.APCShutdownAfterDelay, Type: Input, Value: > > 90.000000 > > Path: UPS.Output.APCShutdownAfterDelay, Type: Feature, Value: > > 90.000000 > > Path: UPS.Output.DelayBeforeShutdown, Type: Feature, Value: > > -1.000000 > > Path: UPS.Output.DelayBeforeStartup, Type: Feature, Value: -1.00...

Hello I recently switched from apcupsd to NUT2.2.2 without any troubles. I tried to figure out how I can configure the self-test intervall. The command upsrw lists only the variables battery.charge.low battery.runtime.low ups.delay.shutdown ups.delay.start The command usbhid-ups -D and the listing under http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart at localhost&treemode

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

Peter Selinger wrote: > Hm. I need more information, as NUT seems to garble the values even > before I can see them. I am not so worried about the date and > temperatures (although, strangely, the battery replacement date > appears to be Sept 25, 2001, which makes no sense). But the voltage is > definitely important. > > [...] > Thanks Peter - I'll send the new