similar to: UPS not Shutting Down

My bad. I'll check it out. On Sun, 2 Jun 2024 at 08:14, Roger Price < roger_at_rogerprice.org_chribonn at duck.com> wrote: > On Sat, 1 Jun 2024, Alan via Nut-upsuser wrote: > > > root at proxmox-01:~# cat nano /etc/nut/ups.conf > > If you send us hundreds of lines of comments it makes your post difficult > to > understand. Could you trim out the comments with

I'm not sure I understand your question. The UPS was running for more than 15 minutes before it went below the battery.charge.low: of 70. Below is my /etc/nut/nut.conf. My goal is that when the UPS report a battery.charge.low of < 70 (or, if possible has been running for 5 minutes) it starts the shutdown process. The shutdown process should take 15 minutes so that proxmox can shutdown

On Sun, 2 Jun 2024, chribonn at duck.com wrote: > ? # if the charge is less than 75 percent trigger a LB status > ? override.battery.charge.low = 75 > ? # if the remaining charge is less than 1200s (20 minutes) trigger a low battery status > ? override.battery.runtime.low = 1200 > ? # wait 5 minutes for ups to power off > ? override.ups.delay.shutdown = 300 > ? # Could

Hello nuters, FreeBSD, Ellipse USBS 800, serial line, nut 2.02 everything works fine. But I'm only able to get an automatic shutdown when reaching the built-in 30% level. I the "lowbatt parameter" is set to anything, it's simply ignored. This is a problem as I want to shutdown around 90% to avoid the battery to drain out when multiple shutdowns occur. Any idea ?

Wow :-) I'll have a read through it. On Sun, 10 Mar 2024 at 15:54, Roger Price < roger_at_rogerprice.org_chribonn at duck.com> wrote: > On Sun, 10 Mar 2024, Alan via Nut-upsuser wrote: > > > Very good point. I hope to write a beginners guide -- more like > adopting my > > notes --on NUT. > > I did the same thing, 131 pages, at >

Hi! I have a MGE Pulsar ES 8+ UPS. Here is the response of some commands: - Si --> 3000 44 0 - Si 1 --> Pulsar ES8+ 0 - Ai --> 5 0 It's not recognized very well by the current (from CVS) mge-utalk driver: [root@srv01 ~]# /home/rog/src/nut/drivers/mge-utalk -i 20 -DDD -u root /dev/ttyS0 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.86 (2.1.0) debug level is '3'

Does the github link not come through (https://github.com/networkupstools/nut/issues/799)? All the documentation that Tripp-Lite sent me on the 2012 protocol and my configuration files are on that issue. I doubt this mailing list will allow me to attach any files. It's the NUT github page. At any rate ups.conf just has this in it. No offdelay or ondelay entries: [ups] driver =

Set with upsrw: ups.delay.shutdown=60 is the same as offdelay = 30. This time was done correctly by UPS. Set with upsrw: ups.delay.start=90 is the same as ondelay = 40. The UPS shut down and reset and forget about the settings. If I use the program in Win 10 settings in the program from Eaton are stable!? Jan. > -----Original Message----- > From: Nut-upsuser

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

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

On Tue, 3 Jul 2018, rakoi at mail.telekom.sk wrote: > UPS is Eaton 5SC 500i. > Please do not know how to write some parameters permanently to UPS? Read man ups.conf and man usbhid-ups and try setting the required values in ups.conf. For example [Eaton] driver = usbhid-ups port = auto desc = "Eaton 5sc 500i" offdelay = 30 ondelay =

Here is a Compatibility Report for the Eaton Ellipse ECO 1600 UPS. Roger battery.charge: 100 battery.charge.low: 20 battery.runtime: 1575 battery.type: PbAc device.mfr: EATON device.model: Ellipse ECO 1600 device.serial: 000000000 device.type: ups driver.name: usbhid-ups driver.parameter.lowbatt: 37 driver.parameter.offdelay: 30 driver.parameter.ondelay: 40 driver.parameter.pollfreq: 30

Dear list, Can't make upssched notify me on event occured. OS: Debian, 2.6.26-1-amd64 Nut: 2.4.3-1.1squeeze1 UPS: Ippon Smart Winner 3000 connected via COM On event ( plug out the cord from UPS ) upsmon detect's status change to OB and gives WALL and syslog notify, but no script starting. In syslog no errors and no upssched process occured, just upsmon. There're no PIPE and LOCK

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

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

Hello there. Have been experimenting with an APC Smart-UPS 1500 RM and would like to share the results of my research. I hope this could be of help to people having this kind of units. I would also like to give something back to the NUT community. :) Here are the details of the unit in question (a 1500 VA rack mountable one): Model: Smart-UPS 1500 RM Firmware revision: 617.3.I USB firmware

On Mon, 17 Feb 2020, Stefan Schulze wrote: > So currently the sequence is: > 1. Main power goes off > 2. UPS and nut goes "OB DISCHRG" > 3. I enter `upsmon -c fsd` Does upsmon.conf specify a shutdown on LB? What happens if you let the battery power the system until LB is reached? You could set LB to say 85% for more rapid testing with upsrw -s battery.charge.low=85

On 2/18/20 9:34 AM, Stefan Schulze wrote: > Hi Roger, Hi all, > >> Does upsmon.conf specify a shutdown on LB? > I think so. You mean SHUTDOWNCMD? > The relevant parts of my upsmon.conf (notifications removed): > > MONITOR ups at localhost 1 upsmaster secret master > MINSUPPLIES 1 > SHUTDOWNCMD "/sbin/shutdown -h +0" > POLLFREQ 5 > POLLFREQALERT 2

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

I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath. Is there something I am missing? Please see attached. Dan -------------- next part -------------- An HTML attachment was