similar to: Question about "HB" flag and a "battery.charge.high" name

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > During discussion at > https://github.com/networkupstools/nut/pull/2430#discussion_r1592317940 I > found that while `nut-names.txt` documents the `battery.charge.low` as the > "Remaining battery level when UPS switches to LB (percent)", there is no > counterpart as `battery.charge.high`.

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

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

Hello, I'm willing to implement call barring for incoming and outgoing calls and I would like to discuss it with the list first, since I think It can't be implemented in a 'natural way' and I will need to use agi scripting - database. Process would be: 1. incoming calls priority 1, call incoming.agi, select all the blocked cli's for the called user, if caller is on

I'm sorry about a wrong place to address, because my problem most likely is in a hardware, not the NUT software. I had tried to contact the MGE support team, but got no answer. I have purchased the MGE Ellipse 650 UPS, and after testing it with the Linux/NUT package (v. 2.0, mge-shut driver) found out that the battery.charge indicator and related things (battery.lifetime, low battery signal)

Hi, Right now my UPS has "battery.charge.low" set to 30. I think thats pretty silly, I'd like it to be alot lower. Its a read only variable so I can't modify it. I can't find a setting in a conf file to override it. Did I miss it? Thanks, Tuc

Hello! I have Megaline 5000 UPS, which I need to monitor via RS232 interface. I'm using "metasys" driver, and everything is Ok, but I can't see battery charge. From command line and cgi-interface I can see battery voltage, input and output voltage and load of UPS in %. But there is nothing about battery charge and remaining time (when on-battery). Is there any chance to see

Hi all! I have a nut 2.4.1 on FreeBSD 7.1 i386. UPS model is IPPON smart smart power pro 2000. When i try to see battery charge, in output it have not such variable, and i can't control other servers (Win2k3 + WinNUT) because they not knows about current battery charge. How i can solve that problem? Thanks! upsc IPPON at localhost:54672 --------------------------- battery.voltage: 27.50

Hi; Charels get me e hint about comment out root user and add $ sudo adduser nut dialout. This was work, Kind regards, Janez 2014-12-29 16:03 GMT+01:00 ??????? ??????? <freemgm at gmail.com>: > Any news? > > Send dubug with explore one more time > in attach > > > 19.12.2014 15:39, Charles Lepple ?????: > >> On Dec 19, 2014, at 5:16 AM, ??????? ???????

Hi, While writing a new driver for Siemens UPSes, I encountered the following problem: The UPS is not able to indicate the current battery charge level as a numeric value, but only as a Boolean value: below or above 85%. (Apart from that, it can also signal a Boolean 'critical' level, which is used to activate the 'LB' status in NUT. This works fine.) There is currently no

On Mon, 4 Mar 2024, Alan C. Bonnici via Nut-upsuser wrote: > Platform: Proxmox VE 8.1.4 > NUT 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: STRING >

Thanks Charles for the clarification. If NUT cannot control it then removing it would, IMO add value. On Sun, 10 Mar 2024 at 00:14, Charles Lepple < clepple_at_gmail.com_chribonn at duck.com> wrote: > On Mar 9, 2024, at 5:16?PM, chribonn at duck.com wrote: > > > > The posting at > https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 > references

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

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 >

Privet Yaroslav, all my apologies for the eternity taken to answer. 2014-12-30 18:22 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Dec 29, 2014, at 10:03 AM, ??????? ??????? <freemgm at gmail.com> wrote: > > Any news? > > Send dubug with explore one more time > in attach > > > Unless I am mistaken, there is no new information in the latest debug

Dear NUT user, You are right concerning the autonomy calculation on Ellipse 650 UPS ("Low End" small Off Line UPS) => the estimation is not really accurate (and also a little bit pessimistic) => this is a known limitation that was documented on the previous NUT mailing list (before Alioth.org) MGE will stop soon the production of these models and will sell Protection Center and

On Mar 9, 2024, at 5:16?PM, chribonn at duck.com wrote: > > The posting at https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 references ups.delay.start and suggests setting it to -1. > > upsrw -l pve1 at localhost listed this as modifiable but any attempt at modifying the value failed. I used the override.ups.delay.start = -1 in nut.conf and this is now being

On Dec 19, 2014, at 5:16 AM, ??????? ??????? <freemgm at gmail.com> wrote: > # /usr/local/libexec/nut/usbhid-ups -DD -a eaton9sx -u root -x explore -x vendorid=0x0463 2>&1 | tee /tmp/eaton9sx-explore.log Ah, I forgot about the vendorid. The string is a regex which must match what is printed by the debug output (case-insensitive) rather than a numerical match, so it should be

*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