Re: [Nut-upsuser] Low Battery Problems

[Gene Heskett]

On Monday 22 June 2020 20:36:13 Gene Heskett wrote:

> On Monday 22 June 2020 18:50:25 Gene Heskett wrote:
> > On Monday 22 June 2020 18:03:16 Charles Lepple wrote:
> > > On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote:
> > > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote:
> > > >> So I just edited /etc/nut/upsd.users to add both the commands
> > > >> it claims to have but get this response to either:
> > > >
> > > > In your original example, you had multiple “instcmd =“ lines for
> > > > one user- I think the allowed commands all need to be listed on
> > > > one instcmd line.
> > >
> > > Ignore this, I misremembered (and didn't read far enough down the
> > > URL I sent). Multiple allowed commands are specified with one
> > > command per instcmd.
> >
> > Or as instcmds = ALL, which also doesn't work, ACCESS-DENIED.
> >
> > Aha!  Found it, very old version of upsmon.conf had gene as
> > operayor, not pi, but that didn't fix it until it had all been
> > restarted, so a quick battery test is underway.  And it was quick,
> > 15 secs OB.
> >
> > So a .deep its running now.
> > Broadcast message from n...@rpi4.coyote.den (somewhere) (Mon Jun 22
> > 18:35:49 202
> >
> > UPS myups@localhost on battery
> >
> > upsc myups says zero load, battery.runtime: 4080
> > The pi don't draw a lot when its not busy.
> >
> > I assume it will use about 90 % & switch back to line ending the a
> > deep test?
> >
> > In which case this might take hours,
>
> Quicker than I thought, 20:22 when it ran out of battery but instead
> of reverting to charge, it did a full shutdown. Is something
> miss-configured yet?
>
And apparently turned itself back on as its rebooted 3 minutes later and 
has put a bit of charge back in the battery already. Without any 
intervention from me.

> > Cheers, Gene Heskett
>
> Cheers, Gene Heskett


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Gene Heskett]

On Monday 22 June 2020 18:50:25 Gene Heskett wrote:

> On Monday 22 June 2020 18:03:16 Charles Lepple wrote:
> > On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote:
> > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote:
> > >> So I just edited /etc/nut/upsd.users to add both the commands it
> > >> claims to have but get this response to either:
> > >
> > > In your original example, you had multiple “instcmd =“ lines for
> > > one user- I think the allowed commands all need to be listed on
> > > one instcmd line.
> >
> > Ignore this, I misremembered (and didn't read far enough down the
> > URL I sent). Multiple allowed commands are specified with one
> > command per instcmd.
>
> Or as instcmds = ALL, which also doesn't work, ACCESS-DENIED.
>
> Aha!  Found it, very old version of upsmon.conf had gene as operayor,
> not pi, but that didn't fix it until it had all been restarted, so a
> quick battery test is underway.  And it was quick, 15 secs OB.
>
> So a .deep its running now.
> Broadcast message from n...@rpi4.coyote.den (somewhere) (Mon Jun 22
> 18:35:49 202
>
> UPS myups@localhost on battery
>
> upsc myups says zero load, battery.runtime: 4080
> The pi don't draw a lot when its not busy.
>
> I assume it will use about 90 % & switch back to line ending the a
> deep test?
>
> In which case this might take hours,
>
Quicker than I thought, 20:22 when it ran out of battery but instead of 
reverting to charge, it did a full shutdown. Is something 
miss-configured yet?

> Cheers, Gene Heskett


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Mike Dillinger]

*From:* Charles Lepple [mailto:clep...@gmail.com]
*To:* Mike Dillinger 
*Cc:* nut-upsuser@alioth-lists.debian.net
*Date:* Monday, June 22, 2020, 5:19 AM PDT
*Subject:* [Nut-upsuser] Low Battery Problems

I’d recommend a battery test. Starting the test via the front panel should be 
sufficient, or you might be able to do it with upscmd.

This should let the UPS firmware discharge the battery a bit, and see how long 
it should last.

Conceptually, “OL LB” is not inconsistent- it means the UPS has AC power, but 
the battery state of charge is reading low (as might happen after the UPS 
restarts after an extended power failure) . You might have a CPS unit where the 
battery voltage returned to NUT is hard-coded to 24.0 V, which is annoying, but 
should not affect internal decisions about shutdown. Example: 
https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html and 
https://github.com/networkupstools/nut/issues/459#issuecomment-325163688



Thanks for the information.  I did initiate a deep test and it finished 
successfully.

I spent a fair amount of time look at this issue this weekend and ended up lowering 
override.battery.charge.low from 60 to 40 and the problem went away.  I haven't had any 
of the "OL LB" warnings since changing that threshold which has not been the 
case for a while now.  I think I'll try bumping override.battery.charge.low back up to 60 
after running the test that you suggested and see how that works out.

Thanks again!
-MikeD

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] Issue with Eaton network-M2

[Karim.afifi]

Hello Guys,

After several days searching on the net and checking my set-up, I can't 
resolve an issue with Eaton network-M2 and "github nut".


I have two ups on the LAN :
- Eaton S3 Evolution with "old network card" => no problem.
- Eaton 5PX3000 with new "network-M2" card  => I can't load driver.

sudo /usr/local/ups/sbin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4.1
Network UPS Tools - Generic SNMP UPS driver 1.12 (2.7.4.1)
Detected Evolution on host 192.168.200.252 (mib: mge 0.52)
Network UPS Tools - Generic SNMP UPS driver 1.12 (2.7.4.1)

>> Create theses files in var/state/ups
"snmp-ups-MGE"
"snmp-ups-MGE.pid"
"snmp-ups-MGE2.pid"
>> and system stucky here.

>> After a while, it's continue :
Startup timer elapsed, continuing...
Network UPS Tools - Generic SNMP UPS driver 1.12 (2.7.4.1)
Duplicate driver instance detected (PID file 
/var/state/ups/snmp-ups-MGE2.pid exists)! Terminating other driver!
Duplicate driver instance detected (PID file 
/var/state/ups/snmp-ups-MGE2.pid exists)! Terminating other driver!
Duplicate driver instance detected (PID file 
/var/state/ups/snmp-ups-MGE2.pid exists)! Terminating other driver!

Startup timer elapsed, continuing...
Network UPS Tools - Generic SNMP UPS driver 1.12 (2.7.4.1)
Duplicate driver instance detected (PID file 
/var/state/ups/snmp-ups-MGE2.pid exists)! Terminating other driver!
Duplicate driver instance detected (PID file 
/var/state/ups/snmp-ups-MGE2.pid exists)! Terminating other driver!
Duplicate driver instance detected (PID file 
/var/state/ups/snmp-ups-MGE2.pid exists)! Terminating other driver!


>> An finally displays that :
Startup timer elapsed, continuing...
No supported device detected

In /var/state/ups :
"snmp-ups-MGE2.pid" is deleted
"snmp-ups-MGE.pid" remains (the ups with the old network card is running 
fine).


/usr/local/ups/bin/upsc -l
MGE (old ups is up)

Configuration seems to be OK.
ups.conf
[MGE]
driver = snmp-ups
port = 192.168.200.252
desc = "Eaton Evolution S3000"
community = public

[MGE2]
driver = snmp-ups
port = 192.168.200.244
desc = "Eaton 5PX3000"
community = public

uspd.users
[admin]
    password = ***
    allowfrom = localhost
    upsmon master
    actions = SET
    instcmds = ALL

cd /home/test/nut-master/server/
sudo ./upsd
Network UPS Tools upsd 2.7.4.1
fopen /var/state/ups/upsd.pid: No such file or directory
/usr/local/ups/etc/upsd.conf is world readable
not listening on 127.0.0.1 port 3493
no listening interface available

Github nut version should be compatible since 2 months :
"eaton-ats16-mib.c  - snmp-ups: cleanup Eaton ATS16 with new Network-M2"

Did I missed something ?
Could you please help me to fix this problem ?

Thanks a lot.



___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Gene Heskett]

On Monday 22 June 2020 18:05:56 Charles Lepple wrote:

> On Jun 22, 2020, at 3:42 PM, Gene Heskett wrote:
> > pi@rpi4:~ $ sudo nano /etc/nut/upsd.users
> > pi@rpi4:~ $ upscmd myups test.battery.start.deep
>
> You'll need a "sudo upsd -c reload" in between editing the users file
> and trying a new command.
>
> https://networkupstools.org/docs/man/upsd.html
> 

I didn't know that, so I reached into /etc/init.d and restarted it all, 
one at a time,  and a deep test that I expect will take half a day, is 
running now.

I am assuming it will log the back on line time and start charging a 
nearly dead leadacid battery when it hits a 10% remaining voltage. 
Sometime in the night maybe. pi's don't draw much, not enough to 
register in a upsc report.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Gene Heskett]

On Monday 22 June 2020 18:03:16 Charles Lepple wrote:

> On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote:
> > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote:
> >> So I just edited /etc/nut/upsd.users to add both the commands it
> >> claims to have but get this response to either:
> >
> > In your original example, you had multiple “instcmd =“ lines for one
> > user- I think the allowed commands all need to be listed on one
> > instcmd line.
>
> Ignore this, I misremembered (and didn't read far enough down the URL
> I sent). Multiple allowed commands are specified with one command per
> instcmd.

Or as instcmds = ALL, which also doesn't work, ACCESS-DENIED.

Aha!  Found it, very old version of upsmon.conf had gene as operayor, not 
pi, but that didn't fix it until it had all been restarted, so a quick 
battery test is underway.  And it was quick, 15 secs OB.

So a .deep its running now.
Broadcast message from n...@rpi4.coyote.den (somewhere) (Mon Jun 22 
18:35:49 202

UPS myups@localhost on battery

upsc myups says zero load, battery.runtime: 4080
The pi don't draw a lot when its not busy.

I assume it will use about 90 % & switch back to line ending the a deep 
test?

In which case this might take hours,

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] USBHID-UPS not detecting USB UPS even though options match

[Stephen Walker-Weinshenker]

Hello:

It turned out that it didn't like the Vendor line. Bus, Serial and Product
all worked in ups.conf.

Thanks for all the help. It is working now.

On Mon, Jun 22, 2020 at 6:02 AM Charles Lepple  wrote:

> > On Jun 21, 2020, at 5:34 PM, Stephen Walker-Weinshenker wrote:
> >
> > product = "OL1500RTXL2U"
> >   serial = ""
> >   vendor = "CyberPower Systems"
> >   bus = "001"
>
> Generally we only recommend including these extra parameters if there are
> multiple UPSes on one host, and you need to distinguish between them. Is it
> possible that there are extra spaces around some of the strings (that
> aren’t shown by nut-scanner)?
>
> Quick fix would be to remove all of the options I quoted, but I would be
> curious as to which one is causing the problem.
>
> If it does turn out to be some weird characters, and you need to add
> another UPS later, it should be possible to use regular expressions to
> match the well-formed parts of the strings.
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Charles Lepple]

On Jun 22, 2020, at 3:42 PM, Gene Heskett wrote:
> 
> pi@rpi4:~ $ sudo nano /etc/nut/upsd.users
> pi@rpi4:~ $ upscmd myups test.battery.start.deep

You'll need a "sudo upsd -c reload" in between editing the users file and 
trying a new command.

https://networkupstools.org/docs/man/upsd.html 


___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Charles Lepple]

On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote:
> 
> On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote:
>> 
>> So I just edited /etc/nut/upsd.users to add both the commands it claims 
>> to have but get this response to either:
> 
> In your original example, you had multiple “instcmd =“ lines for one user- I 
> think the allowed commands all need to be listed on one instcmd line.

Ignore this, I misremembered (and didn't read far enough down the URL I sent). 
Multiple allowed commands are specified with one command per instcmd.





___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Gene Heskett]

On Monday 22 June 2020 16:30:40 Larry Fahnoe wrote:

> On Mon, Jun 22, 2020 at 2:45 PM Gene Heskett  
wrote:
> > On Monday 22 June 2020 15:36:21 Charles Lepple wrote:
> > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote:
> > > > So I just edited /etc/nut/upsd.users to add both the commands it
> > > > claims to have but get this response to either:
> > >
> > > In your original example, you had multiple “instcmd =“ lines for
> > > one user- I think the allowed commands all need to be listed on
> > > one instcmd line.
> >
> > They are now # commented, and instcmds  = ALL added in a new line. 
> > Made zero diff.
>
> If instcmds = ALL is not working, makes me wonder if the problem is
> more with the declaration of the pi user in upsd.users. Is there any
> chance you're supplying the linux password for pi rather than the one
> defined in upsd.users?
>
> --Larry
No, hey are visibly identical.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Larry Fahnoe]

On Mon, Jun 22, 2020 at 2:45 PM Gene Heskett  wrote:

> On Monday 22 June 2020 15:36:21 Charles Lepple wrote:
>
> > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote:
> > > So I just edited /etc/nut/upsd.users to add both the commands it
> > > claims to have but get this response to either:
> >
> > In your original example, you had multiple “instcmd =“ lines for one
> > user- I think the allowed commands all need to be listed on one
> > instcmd line.
>
> They are now # commented, and instcmds  = ALL added in a new line.  Made
> zero diff.
>

If instcmds = ALL is not working, makes me wonder if the problem is more
with the declaration of the pi user in upsd.users. Is there any chance
you're supplying the linux password for pi rather than the one defined in
upsd.users?

--Larry

-- 
Larry Fahnoe, Fahnoe Technology Consulting, fah...@fahnoetech.com
   Minneapolis, Minnesota   www.FahnoeTech.com
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Gene Heskett]

On Monday 22 June 2020 15:36:21 Charles Lepple wrote:

> On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote:
> > So I just edited /etc/nut/upsd.users to add both the commands it
> > claims to have but get this response to either:
>
> In your original example, you had multiple “instcmd =“ lines for one
> user- I think the allowed commands all need to be listed on one
> instcmd line.

They are now # commented, and instcmds  = ALL added in a new line.  Made 
zero diff.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Gene Heskett]

On Monday 22 June 2020 15:26:23 Larry Fahnoe wrote:

> On Mon, Jun 22, 2020 at 12:26 PM Gene Heskett  
wrote:
> > So I just edited /etc/nut/upsd.users to add both the commands it
> > claims to have but get this response to either:
> >
> > pi@rpi4:~ $ upscmd myups test.battery.start.quick
> > Username (pi): pi
> > Password:
> > Unexpected response from upsd: ERR ACCESS-DENIED
> > pi@rpi4:~ $ upscmd myups test.battery.start.deep
> > Username (pi): pi
> > Password:
> > Unexpected response from upsd: ERR ACCESS-DENIED
>
> What about "instcmds = ALL" as a test, perhaps to rule out a parsing
> error?

Same result:
pi@rpi4:~ $ sudo nano /etc/nut/upsd.users
pi@rpi4:~ $ upscmd myups test.battery.start.deep
Username (pi): pi
Password:
Unexpected response from upsd: ERR ACCESS-DENIED

Interesting maybe, user 'nut' and group 'nut' own that whole diretory and 
contents.

OTOH, pi is a member of group 'nut'

???

Thanks Larry.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Charles Lepple]

On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote:
> 
> So I just edited /etc/nut/upsd.users to add both the commands it claims 
> to have but get this response to either:

In your original example, you had multiple “instcmd =“ lines for one user- I 
think the allowed commands all need to be listed on one instcmd line. 
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Larry Fahnoe]

On Mon, Jun 22, 2020 at 12:26 PM Gene Heskett  wrote:

> So I just edited /etc/nut/upsd.users to add both the commands it claims
> to have but get this response to either:
>
> pi@rpi4:~ $ upscmd myups test.battery.start.quick
> Username (pi): pi
> Password:
> Unexpected response from upsd: ERR ACCESS-DENIED
> pi@rpi4:~ $ upscmd myups test.battery.start.deep
> Username (pi): pi
> Password:
> Unexpected response from upsd: ERR ACCESS-DENIED
>

What about "instcmds = ALL" as a test, perhaps to rule out a parsing error?

-- 
Larry Fahnoe, Fahnoe Technology Consulting, fah...@fahnoetech.com
   Minneapolis, Minnesota   www.FahnoeTech.com
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Gene Heskett]

On Monday 22 June 2020 09:50:50 Larry Fahnoe wrote:

> On Mon, Jun 22, 2020 at 8:27 AM Gene Heskett  
wrote:
> > > On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote:
> > > > pi@rpi4:~ $ upscmd myups *test.battery.start.quick*
> > > > Username (pi):
> > > > Password:
> > > > Unexpected response from upsd: ERR ACCESS-DENIED
> >
> > [pi]
> > password  = x
> > instcmds  = *test.battery.start*
> > instcmds  = test.battery.stop
> > calibrate.start
> > calibrate.stop
>
> Hi Gene,
>
> Looks like it might be that you're allowing test.battery.start but
> executing test.battery.start.quick. You'd think one would imply the
> other, but maybe not.

Apparently not:

pi@rpi4:~ $ upscmd myups test.battery.start
Username (pi): pi
Password:
Unexpected response from upsd: ERR CMD-NOT-SUPPORTED

It's working, but me goes away scratching what little hair I have left.

So I just edited /etc/nut/upsd.users to add both the commands it claims 
to have but get this response to either:

pi@rpi4:~ $ upscmd myups test.battery.start.quick
Username (pi): pi
Password:
Unexpected response from upsd: ERR ACCESS-DENIED
pi@rpi4:~ $ upscmd myups test.battery.start.deep
Username (pi): pi
Password:
Unexpected response from upsd: ERR ACCESS-DENIED

Back to scratching head. That gets boring too.

Thanks, Larry.
> --Larry


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] Runtime testing

[Phil Stracchino]

So, a while back I got around to ordering replacement batteries for my
CyberPower PR3000LCDRTXL2U.  When they arrived, I went to swap them in.
 I was horrified at the flimsiness of CyberPower's battery "trays".
I've seen heavier gauge plastic on "blister" packages in the store.


I ALSO discovered that the expansion unit had been shipped to me with
one of its two battery trays not even connected.

Well, that could sure account for unexpectedly short runtime, huh?

Anyway, I reconnected it.  Can anyone point me at where the procedures
for runtime calibration using NUT are documented?  Can anyone tell me
whether Cyberpower's behavior on runtime calibration is to drain the
battery to low-power threshold, then keep power on while it recharges,
or to drain to low-power threshold and then kill the power?  I've been
unpleasantly surprised that way before.



-- 
  Phil Stracchino
  Babylon Communications
  ph...@caerllewys.net
  p...@co.ordinate.org
  Landline: +1.603.293.8485
  Mobile:   +1.603.998.6958

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Larry Fahnoe]

On Mon, Jun 22, 2020 at 8:27 AM Gene Heskett  wrote:

>
> > On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote:
> > > pi@rpi4:~ $ upscmd myups *test.battery.start.quick*
> > > Username (pi):
> > > Password:
> > > Unexpected response from upsd: ERR ACCESS-DENIED
>
> [pi]
> password  = x
> instcmds  = *test.battery.start*
> instcmds  = test.battery.stop
> calibrate.start
> calibrate.stop
>


Hi Gene,

Looks like it might be that you're allowing test.battery.start but
executing test.battery.start.quick. You'd think one would imply the other,
but maybe not.

--Larry

-- 
Larry Fahnoe, Fahnoe Technology Consulting, fah...@fahnoetech.com
   Minneapolis, Minnesota   www.FahnoeTech.com
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Gene Heskett]

On Monday 22 June 2020 09:18:29 Charles Lepple wrote:

> On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote:
> > pi@rpi4:~ $ upscmd myups test.battery.start.quick
> > Username (pi):
> > Password:
> > Unexpected response from upsd: ERR ACCESS-DENIED
> >
> > Looking at /etc/nut/uspd.users, I (me, pi) should be able to do
> > that. ???
>
> Hi Gene,
>
> You have a [pi] section in upsd.users, then? If it's one of the
> example users from the man page or comments, you'll need to use that
> name with upscmd, or change upsd.users.
>
> Plus, you'll need "instcmds = all" (or the specific test command) in
> the section for that NUT user.
>
> Ref: https://networkupstools.org/docs/man/upsd.users.html
> 

I think its all there. Heresa snip, edited
[pi]
password  = x
instcmds  = test.battery.start
instcmds  = test.battery.stop
calibrate.start
calibrate.stop

#
# --- Configuring for upsmon
#
# To add a user for your upsmon, use this example:
#
[upsmon]
password  = x
upsmon master


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Charles Lepple]

On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote:
> 
> pi@rpi4:~ $ upscmd myups test.battery.start.quick
> Username (pi):
> Password:
> Unexpected response from upsd: ERR ACCESS-DENIED
> 
> Looking at /etc/nut/uspd.users, I (me, pi) should be able to do that. ???
> 
Hi Gene,

You have a [pi] section in upsd.users, then? If it's one of the example users 
from the man page or comments, you'll need to use that name with upscmd, or 
change upsd.users.

Plus, you'll need "instcmds = all" (or the specific test command) in the 
section for that NUT user.

Ref: https://networkupstools.org/docs/man/upsd.users.html 


___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Gene Heskett]

On Monday 22 June 2020 08:19:15 Charles Lepple wrote:

> > On Jun 18, 2020, at 12:39 PM, Mike Dillinger wrote:
> >
> > ups.test.result: No test initiated
>
> I’d recommend a battery test. Starting the test via the front panel
> should be sufficient, or you might be able to do it with upscmd.
from man pi@rpi4:~ $ upscmd -l myups
Instant commands supported on UPS [myups]:

beeper.disable - Disable the UPS beeper
beeper.enable - Enable the UPS beeper
beeper.mute - Temporarily mute the UPS beeper
beeper.off - Obsolete (use beeper.disable or beeper.mute)
beeper.on - Obsolete (use beeper.enable)
load.off - Turn off the load immediately
load.off.delay - Turn off the load with a delay (seconds)
load.on - Turn on the load immediately
load.on.delay - Turn on the load with a delay (seconds)
shutdown.return - Turn off the load and return when power is back
shutdown.stayoff - Turn off the load and remain off
shutdown.stop - Stop a shutdown in progress
test.battery.start.deep - Start a deep battery test
test.battery.start.quick - Start a quick battery test
test.battery.stop - Stop the battery test

pi@rpi4:~ $ upscmd myups test.battery.start.quick
Username (pi):
Password:
Unexpected response from upsd: ERR ACCESS-DENIED

Looking at /etc/nut/uspd.users, I (me, pi) should be able to do that. ???

Some help plz.

> This should let the UPS firmware discharge the battery a bit, and see
> how long it should last.
>
> Conceptually, “OL LB” is not inconsistent- it means the UPS has AC
> power, but the battery state of charge is reading low (as might happen
> after the UPS restarts after an extended power failure) . You might
> have a CPS unit where the battery voltage returned to NUT is
> hard-coded to 24.0 V, which is annoying, but should not affect
> internal decisions about shutdown. Example:
> https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html
> and
> https://github.com/networkupstools/nut/issues/459#issuecomment-3251636
>88


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Low Battery Problems

[Charles Lepple]

> On Jun 18, 2020, at 12:39 PM, Mike Dillinger wrote:
> 
> ups.test.result: No test initiated

I’d recommend a battery test. Starting the test via the front panel should be 
sufficient, or you might be able to do it with upscmd.

This should let the UPS firmware discharge the battery a bit, and see how long 
it should last.

Conceptually, “OL LB” is not inconsistent- it means the UPS has AC power, but 
the battery state of charge is reading low (as might happen after the UPS 
restarts after an extended power failure) . You might have a CPS unit where the 
battery voltage returned to NUT is hard-coded to 24.0 V, which is annoying, but 
should not affect internal decisions about shutdown. Example: 
https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html and 
https://github.com/networkupstools/nut/issues/459#issuecomment-325163688___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] reboot of nut managment node resets Tripplite SMX1000LCD

[Roger Price]

On Mon, 22 Jun 2020, Yogesh Bhanu wrote:


I'm not sure if it is a bug or a feature.

I'm running Ubuntu 20.04 on my RPi4 which connects to the UPS over USB.
I have noticed whenever  I reboot my RPi4. It resets the UPS ( I can
hear the relay)  -- Powerloss.
Any pointers to disable this annoying bug / feature.


It looks as if the shutdown part of the reboot is issuing a "delayed UPS 
shutdown".   You should be able to see this in the log.   The UPS will then turn 
off it's power outlets say 20 seconds later when the RPi4 has already restarted.


Ways to avoid this:

1. Remove wall power and wait to hear the "clunk" of the relay.  Then restore 
wall power.


2. Stop nut.server before rebooting the RPi4.  This could happen in a script.

Roger


___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] reboot of nut managment node resets Tripplite SMX1000LCD

[Yogesh Bhanu]

Hi,

I'm not sure if it is a bug or a feature.

I'm running Ubuntu 20.04 on my RPi4 which connects to the UPS over USB.
I have noticed whenever  I reboot my RPi4. It resets the UPS ( I can
hear the relay)  -- Powerloss.
Any pointers to disable this annoying bug / feature.

ups.conf:
--8<
[tripp]
driver = usbhid-ups
port = auto
vendorid = 09ae
productid = 2009
bus = 001
desc = "Tripp Lite SMX1000LCD"
-->8

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser