similar to: A proper way to modify battery.charge.low persistently

Hi there, my HP R1500 G3 UPS doesn't apply my battery.charge.low value i set via upsrw. Is this a common problem with this model in nut 2.6.4? Any ideas how to force the UPS to accept this value? Regards Jan % upsc hp1500 battery.charge: 100 battery.charge.low: 20 battery.charge.warning: 20 battery.runtime: 23917 battery.temperature: 49.0 battery.type: PbAc battery.voltage: 39.0

*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

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

I would like to solicit some feedback re: the battery.runtime.lowconfiguration settings through NUT. I was able to set the value using the 'upsrw' command but when I did a 'upsc' the configuration seems incorrect. Please see below for details. Thank you OS name and version: ?? ?Description:??? Debian GNU/Linux 12 (bookworm) ?? ?Release:??????? 12 ?? ?Codename:?????? bookworm

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

Hello all, I have a CyberPower Systems CP850PFCLCD that I'm hooking up to NUT 2.4.3 from apt running under Ubuntu 10.04. Using the usbhid-ups driver, things *seem* to work at first glance, but there are some odd issues. The most notable issue is that the battery.charge indicator reads 120 when at full charge. I came across this post here:

Hi Charles, 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 reported. Two observations are that once a variable setting

Windows 7 Pro x64, NUT 2.6.5-4 (interim release) Product: Back-UPS RS 1200 FW:8.g3 .D USB FW:g3 Setting UPS values can be confusing. For example, battery.charge.low and battery.runtime.low. Using upsrw, the values will be retained after restarting the OS, but not if the UPS is turned off/restarted. In the driver log (below), it looks like the values are obtained from the UPS, but if I set

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

> 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

On Jun 2, 2014, at 12:25 PM, Andreas Lausch / TBT wrote: > > Hi, > > thanks for the reply. > > On 2014-05-29 05:21, Charles Lepple wrote: >>> Now my questions: >>> 1. should the blazer_ser's high voltage be the voltage during charging >>> or right after I've unplugged it from the mains? >> sounds like during charging (or more

On 12/03/2016 11:46 AM, Charles Lepple wrote: > > If you don't mind sending the full output of "upsc" and "upsrw", we can update the DDL page (it only has "upsc" output for an older version of NUT). This UPS provides some sort of serial number (doesn't match the label) in the device.model (and mirrored at ups.model) variables, so if you want to mask off

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

> On 9 Jun 2019, at 21:19, Roger Price <roger at rogerprice.org> wrote: > Using upssched and a upssched-cmd script to shut down the system is an alternative to using the builtin upsmon SHUTDOWNCMD on status [OB LB]. A upssched-cmd script can provide a managed shutdown well before [OB LB] is reached, but should the UPS reach that status upsmon's SHUTDOWNCMD will take over and

Sorry for the delay. Here are my outputs, but first a quick question: am I right in thinking I can change the name of my ups simply by editing ups.conf? That script I ran from the Pi forum used that name, and I don't care for it. Thanks again for your help. $ upsrw pbx [battery.charge.low] Remaining battery level when UPS switches to LB (percent) Type: STRING Maximum length: 10 Value: 10

Hi! I am not really experienced with UPS devices or UPS control software like NUT but i am enthusiastic and trying to use Eaton-9130 (it has one extra EBM too) as rationally as possible with NUT. I believe in general things are under control and behave, although i have some glitches and i would like to ask for help. I am using Debian v. 7 amd64 and from its packages nut-server and nut-client, v.

01.12.2014, 14:50, "Charles Lepple" <clepple at gmail.com>: > On Dec 1, 2014, at 4:11 AM, Victor Porton <porton at narod.ru> wrote: >> ?battery.voltage: 13.70 >> ?battery.voltage.high: 13.00 >> ?battery.voltage.low: 10.40 > > These are the voltage thresholds for the UPS, so theoretically the UPS will send the LB signal when the battery voltage goes

Hi Charles, Thanks for your response. > For the 1000, do the values match this page? > > > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/APC/Smart-UPS_1000.html > > Yes it does (except that mine is a 120 V model, so input/output voltage is about 125) It doesn't look like we have an entry for a C1500 yet. Would you care to > submit the output of

Hmm, looking at status_commit(), if the UPS actually reported just ?OB", but the ?ignorelb? logic kicked in, wouldn?t status_commit() change it to ?OB LB?? And would clients interpret that correctly? And, assuming status_commit() is called, is the status so saved what?s returned on a future client query? I?m really unsure how all of this works. I don?t suppose there?s some kind of ?general