similar to: CyberPower CST150UC: Question re: battery.runtime.low configuration settings

> 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 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, 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

On Wednesday 28 October 2020 21:32:02 Charles Lepple wrote: > On Oct 26, 2020, at 9:38 AM, Gene Heskett <gheskett at shentel.net> wrote: > >>> battery.voltage: 24.0 > >>> battery.voltage.nominal: 24 > >> > >> I don't have the citation handy, but I think another user reported > >> that the battery.voltage returned by the UPS is a

CyberPower Value 1500ELCD-RU root at ubuntu:/home/oper# upsc myups at localhost battery.charge: 87 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 5220 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 16.5 battery.voltage.nominal: 24 device.mfr: CPS device.model: Value1500E device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq:

On Oct 26, 2020, at 9:38 AM, Gene Heskett <gheskett at shentel.net> wrote: > >>> battery.voltage: 24.0 >>> battery.voltage.nominal: 24 >> >> I don't have the citation handy, but I think another user reported >> that the battery.voltage returned by the UPS is a constant 24.0 V, >> regardless of the actual battery voltage. [...] > I think

[shutdown sequence] I have tested and verified the shutdown sequence works. [manufacturor] https://www.cyberpowersystems.com/product/ups/ec350g/ mbeisser at nas:~$ upsc ups Init SSL without certificate database battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1575 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 9.3

*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

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

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:

On Nov 10, 2017, at 5:31 PM, Christoph Lampl <chris at weeone.de> wrote: > > Dear Charles, > > thanks for your quick answer and your information! I didn't know there is a difference in the PR-series between old and new. So thanks for this valuable information! Just a lucky guess :-) We tend not to know about changes like this until someone reports an issue. > >

I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id: 0764:0501, UPS.PowerSummary.Voltage reports 26.6 for the 24V batteries so when the 0.667 battery scale is applied that goes down to 17.7V. upsc output: battery.charge: 100

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 >

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 Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: > I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id: 0764:0501, UPS.PowerSummary.Voltage reports 26.6 for the 24V batteries so when the 0.667

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> wrote: > >> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: >> >>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage

On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: > >> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id:

On Oct 27, 2020, at 2:45 PM, Robert Stocker <kneadtoknow at gmail.com> wrote: > > Thanks so much for all the help! It looks like at present I've at least got a working configuration that I need to test and fine-tune, am I interpreting this correctly? Yes. If you're good with the default NUT behavior of shutting down when the UPS signals LB (low battery; per upsc, seems to be

I have a device that seems almost, but not quite supported, I'd like very much to help get it working, though I am no programmer. Feel free to ask me to test :) This could probably go in https://networkupstools.org/ddl/ : -------file: Salicru__SPS_2000_ADV_T__usbhid-ups__2.8.1-94-gd59c05349__01.dev , or maybe 1__2000__usbhid-ups__2.8.1-94-gd59c05349__01.dev # DEVICE:URL:VENDOR:

[please use reply-all to include the list. thanks!] > On Nov 9, 2017, at 9:19 PM, Christoph Lampl <chris at weeone.de> wrote: > > Hey guys, :) > > recently, I installed Cyberpower PR2200ELCDRT2U, however, I have not managed to get this UPS working with FreeNAS 11, yet. > > According to compatibility list, PR2200 should work fine, when using powerpanel driver: >