similar to: Problems with NUT on Raspberry Pi

I checked it with the Windows machine. There are nearly no parameters to set directly to the ups. The only thing to set is the low battery-state. All other settings seem to run on the windows machine only. Ups.delay.start was set to 30 after Windows-configuration. The rest seems to be unattended: Init SSL without certificate database battery.charge: 64 battery.charge.low: 10

Hi Roger, it was set by ups.conf. Should I use the upsr-command? Bjoern -----Ursprüngliche Nachricht----- Von: Nut-upsuser Im Auftrag von Roger Price Gesendet: Sonntag, 27. Oktober 2019 11:06 An: nut-upsuser at alioth-lists.debian.net Betreff: Re: [Nut-upsuser] Problems with NUT on Raspberry Pi On Sun, 27 Oct 2019, EP wrote: > OK, reporting back. Just tested the setting

Hhm. OK, but it doesn't work. The ups goes offline and starts back immediately. Even if ups.delay.start is set 0. I will try another test circuit after using the upsrw command. -----Ursprüngliche Nachricht----- Von: Nut-upsuser Im Auftrag von Roger Price Gesendet: Sonntag, 27. Oktober 2019 11:11 An: Nut-upsuser at alioth-lists.debian.net Betreff: Re: [Nut-upsuser] Problems with NUT on

On Monday 26 October 2020 09:01:31 Charles Lepple wrote: > On Oct 25, 2020, at 11:52 AM, Robert Stocker <kneadtoknow at gmail.com> wrote: > > Init SSL without certificate database > > battery.charge: 100 > > battery.charge.low: 10 > > battery.charge.warning: 20 > > battery.mfr.date: CPS > > battery.runtime: 15690 > > battery.runtime.low: 300

Hello, I installed NUT on raspberry pi as a NUT-Server. It works fine so far with a Cyberpower OR600ELCDRM1U (used driver: usbhid-ups). The Pi recognizes power loss and shuts down itself and the ups as it should. Problem: The UPS comes up immediately after shutting down. This is a big issue because there is no power, the server (NUT-Slave) begins powering up and the battery will drain

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

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

On Oct 25, 2020, at 11:52 AM, Robert Stocker <kneadtoknow at gmail.com> wrote: > > Init SSL without certificate database > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPS > battery.runtime: 15690 > battery.runtime.low: 300 > battery.type: PbAcid > battery.voltage: 24.0 > battery.voltage.nominal: 24 I

On Sun, 27 Oct 2019, EP wrote: > I can't imagine that's the way cyberpower wants their unit to work. With this > behavior the unit does exactly the opposite of what it is built for. It > doesn't protect your equipment. It will destroy it because the server which > was just shutted down cleanly will boot again on a battery-powererd ups. What > a crap. > > But I

I've searched the listserv archive, to no avail, so I hope I'm not duplicating a previous problem. I am anxious to get this working, so I'm open to uninstalling what I have and starting over. One note which may not be meaningful is that this UPS pre-dates the Raspberry Pi I've got connected to it, and I used to use it with the CyberPower software, which requires logging in with a

Everything runs fine for several hours, then communication is lost and nut doesn't reestablish communication on its own. Running sudo upsdrvctl stop then sudo upsdrvctl start reestablishes communication. OS Version: Linux piaware 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux Nut Version: 2.7.2-4 Nut Installation Method: apt Device: CyberPower PR1500LCD Uses ? ? Generic

This was very helpful for me, thank you! On Sat, Oct 24, 2020 at 9:06 AM Charles Lepple <clepple at gmail.com> wrote: > The easiest way to tell if upsd is working is to run "upsc -l" on the same > system, which will list the NUT UPS names, and then run e.g. "upsc mge" > (replacing "mge" with the name returned by "upsc -l") > Here was the

On Oct 26, 2020, at 9:01 AM, I wrote: > >> 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. Here's what I was thinking of:

Same behavior here. I tested it by executing the usrw-command (bash) as well. UPS turns off and on again. It even seems to ignore the ups.delay.shutdown (was set to 120 seconds but shutted down faster). Afterwards I set the ups.delay.start to -1. That makes the ups staying off. But - and that is the big mistake - it doesn't turn on when power returns with this setting. I can't imagine

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

Hi, thanks for your reply. >> The Unit is new, the battery drains because it went down to about 15 >> percent before NUT shuts it down. >> >> Yes, I can here a "clac". The problem is not the shutdown procedure, >> it works quite good. After the Unit reaches 20 percent the NUT-Server >> on the pi shuts down the system and the ups is turned off as

That's it. It works with ondelay=0 (ups shuts down and stays so until power returns). Thanks a lot for your help, I never would have figured this out on my own. Let me ask one more question even if it is not on topic. Is there any chance to tell NUT - server to shut down the system at a battery percentage of i. e. 50? By now it waits until the battery is about 10 %. That's really not

On Oct 26, 2019, at 9:45 AM, EP wrote: > [Roger wrote:] >> By the way, do you have offdelay and ondelay values in your ups.conf ? > > No, I haven’t. I just added. Should I add more lines here? > > maxretry = 3 > > [ups] > driver = usbhid-ups > port = auto > desc = "CPS" > pollinterval = 15 Yes, ondelay and offdelay

>> [Roger wrote:] >>> By the way, do you have offdelay and ondelay values in your ups.conf ? >> >> No, I haven’t. I just added. Should I add more lines here? >> >> maxretry = 3 >> >> [ups] >> driver = usbhid-ups >> port = auto >> desc = "CPS" >> pollinterval = 15 >Yes, ondelay

On Sun, 27 Oct 2019, EP wrote: > it was set by ups.conf. Should I use the upsr-command? Setting the value in ups.conf is correct, since that is the value which will be used the next time upsd starts. Roger