Nut upsuser - Apr 2020 - Tripp-Lite SMART1500LCD: powers off with /etc/killpower...then powers back on...

Hi Everyone,

I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine,
connected via a USB cable. I installed Nut 2.7.4 from the Mint package
repository via sudo apt update && sudo apt install nut. Everything works
great: NUT issues low battery warning when it reaches the set low
battery point and then issues shutdown commands...computer shuts
down..then the UPS shuts down a few seconds after that (i hear a 'clunk'
noise from the outlets)...BUT...after the UPS has shut down, I hear
another clunk noise and the computer starts to power back on. Since the UPS
battery is about dead at this point, the computer starts to boot up only
till the UPS completely dies since its batteries are depleted.  This is
what is happening:

- Low Battery setpoint reached --> issue computer shutdown
- Shutdown commands sent --> computer starts shutting down
- At some point, /etc/killpower is sent before computer fully shuts down
- Computer shuts down
- A few seconds later, I hear a clunk in the UPS (UPS powers off... I used
a multimeter to verify no AC voltage on the UPS output outlets)
- Another few seconds later, I hear another clunk in the UPS --> computer
starts to power on --> AC voltage is present on the UPS output outlets
- A few seconds later the battery in the UPS depletes --> computer dies
while booting up

The computer BIOS is obviously set to turn back on when AC is restored.
What could be causing the UPS to turn back on after a few seconds of being
off ?? As testing, I grabbed my Linux laptop (a separate machine) and
installed Nut 2.7.4 via sudo apt install nut. I then manually issued the
command "sudo upsdrvctl shutdown". There is a big clunk noise and the
UPS
immediately turns off its outlets...and after a few seconds there is a
clunk and the ups outlets are back on. I don't understand why the UPS is
not staying off when issuing the command /etc/killpower or via sudo
upsdrvctl shutdown.

ups.conf:

[Tripp_Lite]
driver = usbhid-ups
port = auto
pollinterval = 10
desc = "Tripp-Lite SMART1500LCD"
vendorid = 09ae
ignorelb
override.battery.charge.low = 10
----------------------------------------------------------------------------

nut.conf

MODE=standalone
 ----------------------------------------------------------------------------

upsd.users

[upsmon]
password = xxxxx
actions = SET
instcmds = ALL
upsmon master
 ----------------------------------------------------------------------------

upsmon.conf

RUN_AS_USER root
MONITOR Tripp_Lite at localhost 1 upsmon xxxxxx master
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h +0"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 5
DEADTIME 15
POWERDOWNFLAG /etc/killpower
#
NOTIFYMSG ONLINE "UPS %s on line power"
NOTIFYMSG ONBATT "UPS %s on battery"
NOTIFYMSG LOWBATT "UPS %s battery is low"
NOTIFYMSG FSD "UPS %s: forced shutdown in progress"
NOTIFYMSG COMMOK "Communications with UPS %s established"
NOTIFYMSG COMMBAD "Communications with UPS %s lost"
NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding"
NOTIFYMSG REPLBATT "UPS %s battery needs to be replaced"
NOTIFYMSG NOCOMM "UPS %s is unavailable"
NOTIFYMSG NOPARENT "upsmon parent process died - shutdown impossible"
#
NOTIFYFLAG ONBATT SYSLOG+WALL
NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
NOTIFYFLAG COMMBAD SYSLOG+EXEC
NOTIFYFLAG COMMOK SYSLOG+EXEC
NOTIFYFLAG REPLBATT SYSLOG+WALL
NOTIFYFLAG FSD SYSLOG+WALL+EXEC
NOTIFYFLAG NOCOMM   SYSLOG+WALL
NOTIFYFLAG NOPARENT SYSLOG+WALL
#
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5
#
------------------------------------------------------------------------

Here is the output from "upsc Tripp_Lite"

Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
battery.runtime: 1692
battery.type: PbAC
battery.voltage: 26.3
battery.voltage.nominal: 24.0
device.mfr: Tripp Lite
device.model: Tripp Lite UPS
device.type: ups
driver.flag.ignorelb: enabled
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 10
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.parameter.vendorid: 09ae
driver.version: 2.7.4
driver.version.data: TrippLite HID 0.82
driver.version.internal: 0.41
input.frequency: 59.9
input.voltage: 119.0
input.voltage.nominal: 120
output.frequency.nominal: 60
output.voltage: 119.0
output.voltage.nominal: 120
ups.beeper.status: disabled
ups.delay.shutdown: 20
ups.load: 25
ups.mfr: Tripp Lite
ups.model: Tripp Lite UPS
ups.power: 0.0
ups.power.nominal: 1500
ups.productid: 2012
ups.status: OL
ups.timer.reboot: 65535
ups.timer.shutdown: 65535
ups.vendorid: 09ae
ups.watchdog.status: 0

-----------------------------------------------------
Thank you kindly,
Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200428/3f33a4ef/attachment.html>

Looking at the 2012 protocol, it seems like there is both a "shutdown"
and a "reboot" command. It sounds like the behavior is consistent with
a reboot.


I suppose we could look at exactly what command is being sent via software and
work backwards from there.


I'm still working remotely so testing this myself probably won't happen
in the near term.



Thank you,

David Zomaya

Tripp Lite<http://www.tripplite.com/>



________________________________
From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at
alioth-lists.debian.net> on behalf of Tom Velozo <tomvelozo3 at
gmail.com>
Sent: Tuesday, April 28, 2020 10:24:28 AM
To: nut-upsuser at alioth-lists.debian.net
Subject: [EXTERNAL] [Nut-upsuser] Tripp-Lite SMART1500LCD: powers off with
/etc/killpower...then powers back on...

This is an EXTERNAL email. Please take a moment and think before clicking any
links or opening any attachments from this email. If suspicious, please forward
to ishelpdesk at tripplite.com for review.
________________________________
Hi Everyone,

I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine,
connected via a USB cable. I installed Nut 2.7.4 from the Mint package
repository via sudo apt update && sudo apt install nut. Everything works
great: NUT issues low battery warning when it reaches the set low battery point
and then issues shutdown commands...computer shuts down..then the UPS shuts down
a few seconds after that (i hear a 'clunk' noise from the
outlets)...BUT...after the UPS has shut down, I hear another clunk noise and the
computer starts to power back on. Since the UPS battery is about dead at this
point, the computer starts to boot up only till the UPS completely dies since
its batteries are depleted.  This is what is happening:

- Low Battery setpoint reached --> issue computer shutdown
- Shutdown commands sent --> computer starts shutting down
- At some point, /etc/killpower is sent before computer fully shuts down
- Computer shuts down
- A few seconds later, I hear a clunk in the UPS (UPS powers off... I used a
multimeter to verify no AC voltage on the UPS output outlets)
- Another few seconds later, I hear another clunk in the UPS --> computer
starts to power on --> AC voltage is present on the UPS output outlets
- A few seconds later the battery in the UPS depletes --> computer dies while
booting up

The computer BIOS is obviously set to turn back on when AC is restored. What
could be causing the UPS to turn back on after a few seconds of being off ?? As
testing, I grabbed my Linux laptop (a separate machine) and installed Nut 2.7.4
via sudo apt install nut. I then manually issued the command "sudo
upsdrvctl shutdown". There is a big clunk noise and the UPS immediately
turns off its outlets...and after a few seconds there is a clunk and the ups
outlets are back on. I don't understand why the UPS is not staying off when
issuing the command /etc/killpower or via sudo upsdrvctl shutdown.

ups.conf:

[Tripp_Lite]
driver = usbhid-ups
port = auto
pollinterval = 10
desc = "Tripp-Lite SMART1500LCD"
vendorid = 09ae
ignorelb
override.battery.charge.low = 10
----------------------------------------------------------------------------

nut.conf

MODE=standalone
 ----------------------------------------------------------------------------

upsd.users

[upsmon]
password = xxxxx
actions = SET
instcmds = ALL
upsmon master
 ----------------------------------------------------------------------------
upsmon.conf

RUN_AS_USER root
MONITOR Tripp_Lite at localhost 1 upsmon xxxxxx master
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h +0"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 5
DEADTIME 15
POWERDOWNFLAG /etc/killpower
#
NOTIFYMSG ONLINE "UPS %s on line power"
NOTIFYMSG ONBATT "UPS %s on battery"
NOTIFYMSG LOWBATT "UPS %s battery is low"
NOTIFYMSG FSD "UPS %s: forced shutdown in progress"
NOTIFYMSG COMMOK "Communications with UPS %s established"
NOTIFYMSG COMMBAD "Communications with UPS %s lost"
NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding"
NOTIFYMSG REPLBATT "UPS %s battery needs to be replaced"
NOTIFYMSG NOCOMM "UPS %s is unavailable"
NOTIFYMSG NOPARENT "upsmon parent process died - shutdown impossible"
#
NOTIFYFLAG ONBATT SYSLOG+WALL
NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
NOTIFYFLAG COMMBAD SYSLOG+EXEC
NOTIFYFLAG COMMOK SYSLOG+EXEC
NOTIFYFLAG REPLBATT SYSLOG+WALL
NOTIFYFLAG FSD SYSLOG+WALL+EXEC
NOTIFYFLAG NOCOMM   SYSLOG+WALL
NOTIFYFLAG NOPARENT SYSLOG+WALL
#
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5
#
------------------------------------------------------------------------

Here is the output from "upsc Tripp_Lite"

Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
battery.runtime: 1692
battery.type: PbAC
battery.voltage: 26.3
battery.voltage.nominal: 24.0
device.mfr: Tripp Lite
device.model: Tripp Lite UPS
device.type: ups
driver.flag.ignorelb: enabled
driver.name<https://urldefense.proofpoint.com/v2/url?u=http-3A__driver.name&d=DwMFaQ&c=f9s1WCuF-N6cmD_YaZ7gBg&r=lhr3k4au5dVQgHY_iS-v_t9g8PHVkn8Px_wyaupZGfQ&m=-kILb5kcT8nDzE7jAgfNboB74UcVpE_QXoLwDFhLmqk&s=_GJmbN8Asvt5P3b39WZo3m8MXrPmnLGAd9UyK8-yFY4&e=>:
usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 10
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.parameter.vendorid: 09ae
driver.version: 2.7.4
driver.version.data: TrippLite HID 0.82
driver.version.internal: 0.41
input.frequency: 59.9
input.voltage: 119.0
input.voltage.nominal: 120
output.frequency.nominal: 60
output.voltage: 119.0
output.voltage.nominal: 120
ups.beeper.status: disabled
ups.delay.shutdown: 20
ups.load: 25
ups.mfr: Tripp Lite
ups.model: Tripp Lite UPS
ups.power: 0.0
ups.power.nominal: 1500
ups.productid: 2012
ups.status: OL
ups.timer.reboot: 65535
ups.timer.shutdown: 65535
ups.vendorid: 09ae
ups.watchdog.status: 0

-----------------------------------------------------
Thank you kindly,
Tom



________________________________
This message is for the addressee's use only. It may contain confidential
information. If you receive this message in error, please delete it and notify
the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no
responsibility for viruses which may infect an email sent to you from Tripp Lite
and which damage your electronic systems or information. It is your
responsibility to maintain virus detection systems to prevent damage to your
electronic systems and information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200428/b57da0ad/attachment-0001.html>

On Tue, 28 Apr 2020, Tom Velozo wrote:
> Hi Everyone,
> I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine,
connected via a USB cable. I installed Nut 2.7.4 from the Mint
> package repository via sudo apt update && sudo apt install nut.
Everything works great: NUT issues low battery warning when it reaches the
> set low battery point and then issues shutdown commands...computer shuts
down..then the UPS shuts down a few seconds after that (i hear a
> 'clunk' noise from the outlets)...BUT...after the UPS has shut
down, I hear another clunk noise and the computer starts to power back on.
> Since the UPS battery is about dead at this point, the computer starts to
boot up only till the UPS completely dies since its batteries
> are depleted.  This is what is happening:
> 
> - Low Battery setpoint reached --> issue computer shutdown
> - Shutdown commands sent --> computer starts shutting down
> - At some point, /etc/killpower is sent before computer fully shuts down
> - Computer shuts down
> - A few seconds later, I hear a clunk in the UPS (UPS powers off... I used
a multimeter to verify no AC voltage on the UPS output outlets)
> - Another few seconds later, I hear another clunk in the UPS -->
computer starts to power on --> AC voltage is present on the UPS output
> outlets
> - A few seconds later the battery in the UPS depletes --> computer dies
while booting up
> 
> The computer BIOS is obviously set to turn back on when AC is restored.
What could be causing the UPS to turn back on after a few seconds
> of being off ?? As testing, I grabbed my Linux laptop (a separate machine)
and installed Nut 2.7.4 via sudo apt install nut. I then
> manually issued the command "sudo upsdrvctl shutdown". There is a
big clunk noise and the UPS immediately turns off its outlets...and
> after a few seconds there is a clunk and the ups outlets are back on. I
don't understand why the UPS is not staying off when issuing the
> command /etc/killpower or via sudo upsdrvctl shutdown. 
> 
> ups.conf:
> 
> [Tripp_Lite]
> driver = usbhid-ups
> port = auto
> pollinterval = 10
> desc = "Tripp-Lite SMART1500LCD"
> vendorid = 09ae
> ignorelb
> override.battery.charge.low = 10
>
----------------------------------------------------------------------------
> ------------------------------------------------------------------------
> 
> Here is the output from "upsc Tripp_Lite"
> 
> ...
> ups.delay.shutdown: 20
It's just a shot in the dark, but a report for the TrippLite SMART1500LCD at
https://alioth-lists.debian.net/pipermail/nut-upsuser/2017-August/010892.html 
had parameters offdelay and ondelay set in ups.conf. Your upsc does not report a
ups.delay.start and you have no "offdelay = xx" or "ondelay =
yy". I wondered if
setting them had any effect?

Roger