similar to: Patch - NUT-monitor: parse battery.runtime as a float instead of as int

Hi all, I've attached a patch that changes the parsing of battery.runtime in NUT-monitor from int to float. This already happens for ups.temperature, charge and load. Without this patch, I get a flood of "Invalid literal for int with base 10: '28500.00" errors. Kind regards, Sven -------------- next part -------------- A non-text attachment was scrubbed... Name:

Thanks for the help, with the apcsmart-old driver it works again! Didn't notice my UPS is now so "old" ;-) Here is the output of upsc with apcsmart-old driver: battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 00 battery.date: 11/22/06 battery.packs: 001 battery.packs.bad: 000 battery.runtime: 540 battery.runtime.low: 120 battery.voltage: 53.73

On Mar 8, 2016, at 12:54 PM, Mike Lee <curby+forums at cur.by> wrote: > > On Mon, Mar 7, 2016 at 9:00 PM, Charles Lepple <clepple at gmail.com> wrote: >> If you stop and start the driver, it should refresh. > > Hi Charles, thanks for the reply! Pardon the dead horse beating, but > I just want to clarify/confirm two things: > > 1) I did my full power down

On Mar 6, 2016, at 1:40 AM, Mike Lee <curby+forums at cur.by> wrote: > > As part of the desired second configuration, I reset the UPS to report > low battery when it had 10 minutes (600s) of estimated battery left. > However, battery.runtime.low as reported to NUT is still the default > of 120. "There are 2 hard problems in computer science: cache invalidation, naming

That's an idea Charlie. The APC UPS I am using has an AP9630 card in it and pfSense is grabbing the snmp. I could try to use the USB cable on the FreeNAS so both could be masters. ----- Original Message ----- From: "Charles Lepple" <clepple at gmail.com> To: "Danny Siminiuk" <daniel at siminiuk.com> Cc: "nut-upsuser" <nut-upsuser at

> 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

Hi Charles, I don't think "ignorelb" will work in my case because that is set on the master. I am using the nut package in pfSense as the master and I want pfSense to shutdown on LOWBATT as designed. I tried using upssched.conf with timers on the netclients but that's not appropriate because ONBATT by itself doesn't tell you how much capacity remains in the UPS. You still

On Jun 13, 2013, at 7:14 AM, ML mail wrote: > I just upgraded to Network UPS Tools upsstats 2.6.4 on Debian wheezy and noticed that it does not show the battery runtime anymore, the field is simply empty. It used to work before with NUT 2.4.1. Does anyone know what could be wrong? > > I am using the apcsmart UPS driver. The apcsmart driver was overhauled, and in 2.6.x, the previous

On Mon, Mar 7, 2016 at 9:00 PM, Charles Lepple <clepple at gmail.com> wrote: > If you stop and start the driver, it should refresh. Hi Charles, thanks for the reply! Pardon the dead horse beating, but I just want to clarify/confirm two things: 1) I did my full power down test (including powering down UPS and NAS, and restarting them) after the change to 600s on the UPS. Shouldn't

David, do you have any screenshots of PyNUT that fit this format? Please see Richard's link below. Begin forwarded message: > From: Richard Hughes > Subject: [nut] Please create an AppData file for NUT Monitor (#127) > Date: May 28, 2014 5:37:04 AM EDT > > Please consider writing and installing an AppData file with the application description and some screenshots, else NUT

Hi David, it seems that your below mail went unmoderated :-/ anyway, any news on the appData side? as usual, I can provide help if needed... have you also been able to take a look at the pyNut3 thread / pull requests? cheers, Arno From: David Goncalves <david at lestat.st> To: Charles Lepple <clepple at gmail.com> Cc: <nut-upsdev at lists.alioth.debian.org> Date: Fri, 30 May

On Mar 8, 2024, at 8:22?AM, Dan Grostick via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian 12) with success. > > When I take that same configuration to a PI 3B running bookworm 32 bit, compile from source, use the same files from /etc/nut, I get a 'nut-monitor ups at

> If you have any more questions regarding this, please use the nut-upsuser > mailinglist instead. Redirected to the appropriate list, sorry. > > Is there a place in the upsmon.conf (or elsewhere) > > file where one may enter something like: > > > > OVERRIDE_BATTERY_CHARGE_LOW 20 > > OVERRIDE_BATTERY.LOW 240 > > > See 'man 8 upsrw'.

Hi Charles, Thanks for the response! I don't believe the battery.charge is actually 30%. I watched the "battery.charge" go down from "100" to "3", so I can only assume this field to be "%". Here is what it currently looks like after charging over the weekend: ==================================================== [root at localhost ~]# upsc myups at

Hi Charles, I made the change, and it still won't incite a poweroff: ========================================================================== [root at localhost ~]# upsc myups at localhost battery.charge: 76 battery.charge.low: 90 battery.charge.warning: 30 battery.runtime: 1811 battery.temperature: 31.9 battery.type: PbAC battery.voltage: 49.2 battery.voltage.nominal: 48.0 device.mfr:

On Nov 10, 2014, at 9:10 AM, ??????? ?????????? <v.linch at icloud.com> wrote: > My windows version is 2.6.5-3, latest on NUT site. > "upsc ups" shows many ups parameters such as ups.load, battery.charge etc. but there is no battery.voltage, which I need (ups - is the name of my device in config). > If I load driver usbhid-ups in debug mode (-DD), I see something like

Very good point. I hope to write a beginners guide -- more like adopting my notes --on NUT. I could summarise your point that technically one should only override settings that NUT can act upon (like those settings that control Low Battery or, as stated in the documentation if the reported value is known to be incorrect. Overriding a variable that is out of scope for NUT (as with

Attached is the first 32 seconds of the driver output after applying the patch which fixes the battery scaling problem for this UPS. Matthew Stapleton Email: matthew4196 at gmail.com On 10/08/14 01:27, Charles Lepple wrote: > On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com>

On 11/04/17 03.36, Charles Lepple wrote: [cuuuuuut] good points. > Not sure if this got answered already, but is the "No battery installed" alarm > accurate, or is it just an old battery? If old, does the battery.runtime value > get adjusted downwards after a battery test? Either way, we would need to > establish which reading should take priority, and I don't think

> Unfortunately, the SUCCESS response is just saying that upsrw was able to send that request to upsd (i.e. the username/password were correct). As you saw, the real proof is in what you read back from upsc. Ah, gotcha. > Have you tried any other values? 3600 is hex 0xe10, and 16 is 0x10, so it is quite possible the UPS is using an 8-bit field to store battery.runtime.low. I'm guessing