similar to: Battery runtime not displaying

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

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

Hello, I am using Nut 2.8.0 (2.8.0-7 packages) Debian 'Bookworm' in it's Devuan form 'Daedalus'. When I look at my Eaton (ex-MGE Powerware) E5115 UPS boxes in NUT 'upsstats" I am confused by the battery readings. Under the 'System' column I can click on the link and obtain a GUI with a few meters. The NUT 'upsstats' battery voltage meter for these

Hello Jeff, `upsstats` by itself only relays and renders the information provided by a NUT data server (upsd) and the NUT driver for the device. So you can revise the specific reported values with e.g. `upsc` command-line client to be sure. What I think happens here is that the driver uses a `battery.voltage.low/nominal/high` group of readings which does not match the hardware circumstances

Michal, I ran across this Debian bug today: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707223 It's a bit of a corner case, and it's for NUT 2.6.4 (apcsmart driver v3.04), but I was wondering if it was still applicable for the latest code? "nut reports 100% battery charge after unplugging the battery on a Smart-UPS 2200 RM (SUA2200RMI2U) using apcsmart. Powerchute correctly

The (2.2.1) upshid-ups driver reports battery.temperature rather than ups.temperature. Here's a quick patch to have it show up in the status page... --- clients/upsstats.c.DIST 2008-03-04 09:15:40.000000000 +0000 +++ clients/upsstats.c 2008-03-04 09:16:20.000000000 +0000 @@ -787,6 +787,11 @@ return 1; } + if (!strcmp(cmd, "BATTTEMP")) { +

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

Citeren Michal Soltys <msoltyspl-guest at alioth.debian.org>: > Log: > apcsmart: allow tearing down/setting up serial connection during > normal activity; If this is needed at all (why?), I don't think this should be handled at driver level, but this would need to be in the serial.c library. Opening/closing a serial port is independent from the protocol used (no data

Hello, is there a way to query from the cmdline if the UPS data is stale? "upsc" outputs a lot of information, but not if the data is stale. Example output from a "stale" UPS on the server: (nut version: nut-2.7.2-3.el7) # upsc apcsmart battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.mfr.date: 2014/09/01 battery.runtime: 1320

Hello. Trouble to communicate with APC SmartUPS via serial port. UPS connected to the com1 port on windows host. Communication witch hyperterm works well. There is a log: YSM ^ASmart-UPS SC1000 n5S0713T63247 m03/29/07 L240.0 B27.10 apcupsd also can communicate with the UPS and works well. running apcsmart -a ups gives the following: com1: device reports different attributes than what were set

On 2014-01-14 10:12, dstrr wrote: > Hello. > Trouble to communicate with APC SmartUPS via serial port. > UPS connected to the com1 port on windows host. > Communication witch hyperterm works well. > There is a log: > > YSM > ^ASmart-UPS SC1000 > n5S0713T63247 > m03/29/07 > L240.0 > B27.10 > > apcupsd also can communicate with the UPS and works well. >

*Platform: Proxmox VE 8.1.4NUT version: Network UPS Tools upsstats 2.8.0* I configured Proxmox and I can pull up the UPS stats. Typing in `*upsrw -l cyberpower at localhost*` I get the following: *[battery.charge.low]Remaining battery level when UPS switches to LB (percent)Type: STRINGMaximum length: 10Value: 10[battery.runtime.low]Remaining battery runtime

Hi all, I use an APC Back-UPS RS 800, overall my experience with NUT is very good but there is one feature I am missing: the ability to ask the UPS for a battery test. upscmd -l shows the following commands available: $ upscmd -l rs800 Instant commands supported on UPS [rs800]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS

Hi, I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date (NUT) but BATTDATE shows the correct date of 2016/05/11. While NUT shows the battery.date as 2001/09/25 which doesn't make sense. Any ideas? Pfsense 2.4.3-RELEASE-p1 (amd64) NUT 2.7.4_6 NUT installed through

2017-04-04 14:18 GMT+02:00 Jon Bendtsen <jon.bendtsen at jonix.dk>: > On 04/04/17 14.10, Roger Price wrote: > >> On Tue, 4 Apr 2017, Arnaud Quette wrote: >> >> > [cuuuuut] > > Hi Arnaud, It seems to me that, looking out into the future, there are >> three >> things upsmon needs: >> >> 1. A fall-through <notify type> of

On Jul 31, 2013, at 3:36 AM, Pavel Potcheptsov (EKTOS) wrote: > Does it looks good? I think so - 40.8 volts with a nominal of 36 volts is 13.6 V/cell, which agrees with the 100% charge value. Hopefully the line voltages and frequency make sense for your region. > Another question what does riello experimental driver warning mean? We add that to all new drivers. This driver was written by

Thank you very much!! I have tried configure downloaded source with # ./configure --with-user=_ups --with-group=_ups --with-statepath=/var/db/nut/ and then build driver and copy again. but this doesn't help (driver pid still in the /var/state/ups). Maybe I must add more arguments to change driver's pid location, but I did next, I changed this argument in openbsd ports: # pkg_delete nut #

I'd like to have the UPS status web page automatically refreshed. I've found a reference to using @REFRESH@ in the upsstats.html page, but as far as I can tell in looking at the code, somewhere I need to provide a value to the refreshdelay variable, and I see no way to do that other than changing the source code. I'm using nut 2.2.

Hi, I'm using the CGI program upsstats.cgi to view the status of UPS's on a web browser. I'd want to do something like that: /var/www/nut-cgi-bin-group-A/upsstats.cgi /var/www/nut-cgi-bin-group-B/upsstats.cgi /var/www/nut-cgi-bin-group-C/upsstats.cgi In that way using .htaccess I allow only certains IPs access to UPS from group A. How could I do that? Thanks in advance" --

Dear Ladies and Gentlemen, I have several old, yet functioning APC Smart-UPS (Model 600LS, Part AP600I, Firmware 6JI, no EEPROM, from 1991). They are not supported by Powerchute any more. I run NUT 2.6.5-4 on Windows XP SP3. I use COM1 port with cable 940-0024C. The connection fails with APC Smart protocol driver 3.0 (2.6.3-3534:3540M), APC command table version 3.0 or higher - it works with APC