similar to: KDE battery icon says "no battery available" after installing NUT

Hi, This might be a simple thing to fix, but I can?t figure it out. We replaced the battery for the first time in our Eaton 5PX a couple of weeks ago, but we haven?t been able to clear the ?ups.alarm: replace battery!? status. Details of our installation are: OS: Debian 6 NUT version: 2.7.4 Installation method: from source tarball UPS device: Eaton 5PX2000IRT, 240V, 1800W, 2000VA, bought in

On 10/01/2015 00:45, Charles Lepple wrote: > On Jan 8, 2015, at 11:43 PM, Graham Menhennitt > <graham at menhennitt.com.au <mailto:graham at menhennitt.com.au>> wrote: > >> Hello Nutters, >> >> I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) >> with an APC Back-UPS CS 350 connected via USB. I get persistent >> (every few

Thanks for the reply. However these two FAQ are unfortunately not describing the situation. - The first issue is that NUT switches off the UPS upon reboot on low battery (not that it dies because of low battery) - The second issue is that the UPS does not recognise being online again (not that the PC does not restart) Sent from my iPhone > On 11 Jun 2019, at 02:03, Charles Lepple <clepple

Jim Klimov <jimklimov+nut at gmail.com> writes: >> "battery voltage is unreasonably high" is a reasonable concept. <...> I >> would not call it HB, though because that makes it sound parallel to LB, >> which is about believed remaining capacity, not detection of overcharging >> failure. > > Well, given that a "battery.charge.high" is

Kicking the old tyre a bit once more: In my recent reading I saw "float charge", "float mode", "float voltage" etc. Maybe that is what I meant in the earlier discussion - similar concept, similar word. In case of PbAc per https://chargetek.com/basic-information.html : "Float mode is where the voltage on the battery is maintained at approximately 2.25 volts

What is the sign of battery.current value? I wonder if the negative number means charging or discharging. Gabor

My UPS is connected to a Raspberry Pi by USB. After a few hours of working, the service fails. Looking at kernel messages I noticed that the device is repeatedly disconnecting and reconnecting. I have tried using a different USB port and using a brand new USB cable. I have not had success by changing config parameters like pollfreq/pollinterval/etc. What is causing the UPS to keep disconnecting?

On Jun 10, 2019, at 2:32 PM, Marc Finns wrote: > > Hello, I read all FAQ and other sources but I could not find this situation, so I thought of asking the experts. > I successfully configured a Raspberry NUT server to control my UPS that powers several devices (NUC with ESXI VMs, Synology NAS etc). > All works well in principle, but I have the following behaviours that I could not

Thanks for the insights, especially these: > If this is about having variables with thresholds that control devices or cause synthetic setting of some variable (like turning on LB if charge% is < battery.charge.low), then it makes sense. > "battery voltage is unreasonably high" is a reasonable concept. <...> I would not call it HB, though because that makes it sound

Citeren "David C. Rankin" <drankinatty at suddenlinkmail.com>: > Discharged battery.voltage: > > 17.4 Volts - (indicated on shutdown, discharging battery.charge 77%) > 16.9 Volts - (indicated on shutdown, discharging battery.charge 51%%) > 16.6 Volts - (indicated on shutdown, discharging battery.charge 33%) > > -- Shutdown Occurred at < 3% -- Battery

2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: > Hi, Hi Thomas, > I want the driver report the battery status from ABM charging controllers > -patch attached- : thanks for your patch. since it introduces a new variable (battery.status.abm), I prefer to step back and think to something useful more widely. thus, I'm thinking about a generic

Hello, I have been using NUT for a short period of time and have some questions regarding the UPS reboot signal that I can't figure out. Have tried some googling and reading the DOCs but I am struggling to understand how some variables / things are supposed to work, so would appreciate any help with any of the following questions. I am running NUT on standalone mode on a linux machine

data/Makefile.am | 8 ++--- player/swfdec-player.ui | 22 +++++++------- player/swfdec-window.c | 2 - po/POTFILES.in | 1 po/POTFILES.skip | 1 po/fr.po | 72 ++++++++++++++++++++++++++++++++---------------- thumbnailer/Makefile.am | 20 +++++-------- 7 files changed, 74 insertions(+), 52 deletions(-) New commits: commit

Hello Nutters, I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason described in the FAQ (but I'm not 100% sure). In the trace output I can see that

Thanks again for your patience. I'm still learning how to deal with systemctl myself (and starting from, I'm sure, a much lower level of understanding), so if I've neglected to restart or start something, please let me know. I made the change to /etc/nut/upsd.conf. I restarted upsdrvctl, which reported back: Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic

This is new install on Ubuntu 16.04, using packages from Synaptic, *Network UPS Tools upsd 2.7.2 I am getting these messages in the terminal: Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): UPS CyberUPS1 at localhost is unavailable I am still unclear on where to set when nut shutdowns system. I see nut-client and nut server are automatically starting from SystemD.

Charles, It starts out good, then goes into a Connection timed out loop. If I can provide any information to fix a driver I'll do my best. Here's the output: # /usr/local/ups/bin/usbhid-ups -DD -a eaton Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 0.000000 debug level is '2' 0.002550 upsdrv_initups... 0.288229 Checking device

Gentlemen, Please note that what follows pre-dates the latest changes from Arnaud (just thought someone might want to look at these before I can test the latest!). When running newhidups with -D -D -D I saw messages that looked like errors, and it took me a while to understand that they were not really errors. I therefore added two new entries in apc-hid.h, and I modified a couple of diagnistic

Hi UPS List members, I have purchased a number of Emerson Power / Liebert GXT4 UPS units. I have these working correctly under nut, but limited detsils are being reported. I am happy to supply information on the USB communications to improve the reported details I can use WireShark to capture the comms between the supplied Windows GUI tool and the UPS Please advise the best way I can

Hello, I am hoping someone can point me in the right direction. I am setting up a new UPS, most things seem to be working except the UPS turns off immediately during a test shutdown using///"//upsmon -c fsd".//No delay before the UPS turns itself off leaving no time for the server to shutdown properly. I have attempted to set the delay higher using "upsrw -s