Nut upsuser - Oct 2020 - Can't get CyberPower UPS to work with Raspberry Pi 4

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 at 10% charge or 300 seconds
left, whichever comes first), it's just a matter of testing the shutdown
command, and any power sequencing (including any auto power-on settings on the
motherboard) issues on the way back up.

If not, there are ways to either adjust the UPS low power thresholds, or ignore
them completely. Roger Price has a good enumeration of alternate shutdown
strategies in his Configuration Examples document linked here:
http://rogerprice.org/NUT/

As I just mentioned in my reply to Gene, it would be handy to have the output of
"upsrw" and "upscmd -l" for your UPS. Those commands show
the read/write variables and instant commands that the NUT driver detects,
respectively.

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

[battery.runtime.low]
Remaining battery runtime when UPS switches to LB (seconds)
Type: STRING
Maximum length: 10
Value: 300

[ups.delay.shutdown]
Interval to wait after shutdown with delay command (seconds)
Type: STRING
Maximum length: 10
Value: 20

[ups.delay.start]
Interval to wait before (re)starting the load (seconds)
Type: STRING
Maximum length: 10
Value: 30

$ upscmd -l pbx

Instant commands supported on UPS [pbx]:

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

On Wed, Oct 28, 2020 at 9:40 PM Charles Lepple <clepple at gmail.com>
wrote:
> 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 at 10% charge or 300
> seconds left, whichever comes first), it's just a matter of testing the
> shutdown command, and any power sequencing (including any auto power-on
> settings on the motherboard) issues on the way back up.
>
> If not, there are ways to either adjust the UPS low power thresholds, or
> ignore them completely. Roger Price has a good enumeration of alternate
> shutdown strategies in his Configuration Examples document linked here:
> http://rogerprice.org/NUT/
>
> As I just mentioned in my reply to Gene, it would be handy to have the
> output of "upsrw" and "upscmd -l" for your UPS. Those
commands show the
> read/write variables and instant commands that the NUT driver detects,
> respectively.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20201029/c693dc4b/attachment.html>

On Oct 29, 2020, at 2:44 PM, Robert Stocker <kneadtoknow at gmail.com>
wrote:
> 
> 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.
> 
Yes, ups.conf, plus the other locations that refer to it (upsmon.conf, and any
scripts). You'll want to restart the systemd services, too.

Thanks for posting the variables and commands.