<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hi! Thank You!<br>
<br>
The UPS behavior are chages with NUT v.2.8.2 but more strange<br>
<br>
After this command (if power cord unpluged)<br>
/usr/local/ups/bin/usbhid-ups -DDDD -a UPS -k<br>
<br>
....<br>
0.188173 [D4] string_to_path: depth = 3<br>
0.188187 [D4] string_to_path: depth = 3<br>
0.188199 [D4] string_to_path: depth = 3<br>
0.188211 [D4] string_to_path: depth = 3<br>
0.188246 [D2] find_nut_info: unknown info type:
load.off.delay<br>
0.188267 [D2] find_nut_info: unknown info type:
load.off.delay<br>
0.188280 Initiating UPS shutdown<br>
0.188290 [D1] upsdrv_shutdown...<br>
0.188298 [D1] instcmd(shutdown.return, [NULL])<br>
0.188316 [D3] instcmd: using Path
'UPS.PowerSummary.DelayBeforeShutdown'<br>
0.188332 [D3] powercom_shutdown_nuf: value = (null), command
= 5E00<br>
0.224970 [D3] Report[set]: (3 bytes) => 0f 00 5e<br>
0.225003 [D4] Set report succeeded<br>
0.225012 [D3] instcmd: SUCCEED<br>
<br>
The UPS are start double beeping every 2 seconds, but didn't turn
off himself ( 2 minutes wait )<br>
UPS are still beeping if power are restored<br>
<br>
Status are:<br>
# upsc ups@localhost<br>
battery.charge: 100<br>
battery.charge.low: 70<br>
battery.charge.warning: 30<br>
battery.mfr.date: 2014/01/15<br>
battery.runtime: 800<br>
battery.type: PbAc<br>
device.mfr: POWERCOM Co.,LTD<br>
device.model: HID UPS Battery<br>
device.serial: 004-0D9F-000<br>
device.type: ups<br>
driver.debug: 0<br>
driver.flag.allow_killpower: 0<br>
driver.flag.ignorelb: enabled<br>
driver.name: usbhid-ups<br>
driver.parameter.offdelay: 30<br>
driver.parameter.ondelay: 60<br>
driver.parameter.override.battery.charge.low: 70<br>
driver.parameter.pollfreq: 30<br>
driver.parameter.pollinterval: 2<br>
driver.parameter.port: auto<br>
driver.parameter.productid: 0004<br>
driver.parameter.synchronous: auto<br>
driver.parameter.vendorid: 0d9f<br>
driver.state: quiet<br>
driver.version: 2.8.2<br>
driver.version.data: PowerCOM HID 0.7<br>
driver.version.internal: 0.53<br>
driver.version.usb: libusb-1.0.26 (API: 0x1000109)<br>
input.frequency: 50.0<br>
input.voltage: 224.0<br>
input.voltage.nominal: 220<br>
output.frequency: 50.0<br>
output.voltage: 224.0<br>
output.voltage.nominal: 220<br>
ups.beeper.status: enabled<br>
ups.date: 2014/01/15<br>
ups.delay.shutdown: 30<br>
ups.delay.start: 60<br>
ups.load: 1<br>
ups.mfr: POWERCOM Co.,LTD<br>
ups.model: HID UPS Battery<br>
ups.productid: 0004<br>
ups.serial: 004-0D9F-000<br>
ups.status: OL<br>
ups.test.result: Done and passed<br>
ups.timer.shutdown: 269<br>
ups.timer.start: 0<br>
ups.vendorid: 0d9f<br>
root@vTEMPLATE8:/var/log# upsc ups@localhost<br>
battery.charge: 100<br>
battery.charge.low: 70<br>
battery.charge.warning: 30<br>
battery.mfr.date: 2014/01/15<br>
battery.runtime: 800<br>
battery.type: PbAc<br>
device.mfr: POWERCOM Co.,LTD<br>
device.model: HID UPS Battery<br>
device.serial: 004-0D9F-000<br>
device.type: ups<br>
driver.debug: 0<br>
driver.flag.allow_killpower: 0<br>
driver.flag.ignorelb: enabled<br>
driver.name: usbhid-ups<br>
driver.parameter.offdelay: 30<br>
driver.parameter.ondelay: 60<br>
driver.parameter.override.battery.charge.low: 70<br>
driver.parameter.pollfreq: 30<br>
driver.parameter.pollinterval: 2<br>
driver.parameter.port: auto<br>
driver.parameter.productid: 0004<br>
driver.parameter.synchronous: auto<br>
driver.parameter.vendorid: 0d9f<br>
driver.state: quiet<br>
driver.version: 2.8.2<br>
driver.version.data: PowerCOM HID 0.7<br>
driver.version.internal: 0.53<br>
driver.version.usb: libusb-1.0.26 (API: 0x1000109)<br>
input.frequency: 50.0<br>
input.voltage: 224.0<br>
input.voltage.nominal: 220<br>
output.frequency: 50.0<br>
output.voltage: 224.0<br>
output.voltage.nominal: 220<br>
ups.beeper.status: enabled<br>
ups.date: 2014/01/15<br>
ups.delay.shutdown: 30<br>
ups.delay.start: 60<br>
ups.load: 1<br>
ups.mfr: POWERCOM Co.,LTD<br>
ups.model: HID UPS Battery<br>
ups.productid: 0004<br>
ups.serial: 004-0D9F-000<br>
ups.status: OL<br>
ups.test.result: Done and passed<br>
ups.timer.shutdown: 89<br>
ups.timer.start: 0<br>
ups.vendorid: 0d9f<br>
root@vTEMPLATE8:/var/log# upsc ups@localhost<br>
battery.charge: 100<br>
battery.charge.low: 70<br>
battery.charge.warning: 30<br>
battery.mfr.date: 2014/01/15<br>
battery.runtime: 800<br>
battery.type: PbAc<br>
device.mfr: POWERCOM Co.,LTD<br>
device.model: HID UPS Battery<br>
device.serial: 004-0D9F-000<br>
device.type: ups<br>
driver.debug: 0<br>
driver.flag.allow_killpower: 0<br>
driver.flag.ignorelb: enabled<br>
driver.name: usbhid-ups<br>
driver.parameter.offdelay: 30<br>
driver.parameter.ondelay: 60<br>
driver.parameter.override.battery.charge.low: 70<br>
driver.parameter.pollfreq: 30<br>
driver.parameter.pollinterval: 2<br>
driver.parameter.port: auto<br>
driver.parameter.productid: 0004<br>
driver.parameter.synchronous: auto<br>
driver.parameter.vendorid: 0d9f<br>
driver.state: quiet<br>
driver.version: 2.8.2<br>
driver.version.data: PowerCOM HID 0.7<br>
driver.version.internal: 0.53<br>
driver.version.usb: libusb-1.0.26 (API: 0x1000109)<br>
input.frequency: 50.0<br>
input.voltage: 226.0<br>
input.voltage.nominal: 220<br>
output.frequency: 50.0<br>
output.voltage: 226.0<br>
output.voltage.nominal: 220<br>
ups.beeper.status: enabled<br>
ups.date: 2014/01/15<br>
ups.delay.shutdown: 30<br>
ups.delay.start: 60<br>
ups.load: 1<br>
ups.mfr: POWERCOM Co.,LTD<br>
ups.model: HID UPS Battery<br>
ups.productid: 0004<br>
ups.serial: 004-0D9F-000<br>
ups.status: OL<br>
ups.test.result: Done and passed<br>
ups.timer.shutdown: 3148<br>
ups.timer.start: 0<br>
ups.vendorid: 0d9f<br>
<br>
And strange with timer parametr that are changes cycling:<br>
ups.timer.shutdown: 3570<br>
ups.timer.shutdown: 2430<br>
ups.timer.shutdown: 1710<br>
...<br>
ups.timer.shutdown: 870<br>
ups.timer.shutdown: 3629<br>
ups.timer.shutdown: 2729<br>
ups.timer.shutdown: 1829<br>
...<br>
ups.timer.shutdown: 89<br>
ups.timer.shutdown: 3148<br>
...<br>
<br>
the ups.conf are:<br>
[UPS]<br>
driver = usbhid-ups<br>
vendorid = 0d9f<br>
productid = 0004<br>
# powercom_sdcmd_byte_order_fallback<br>
port = auto<br>
# pollonly = enabled<br>
pollinterval = 2<br>
pollfreq = 30<br>
offdelay = 30<br>
ondelay = 60<br>
allow_killpower<br>
ignorelb<br>
override.battery.charge.low = 70<br>
# override.battery.runtime.low = 600<br>
<br>
<div class="moz-cite-prefix">06.05.2025 01:49, Jim Klimov:<br>
</div>
<blockquote type="cite"
cite="mid:CAJYg8vK5iKqp+hQZU=BtMHr1cOddcMR=YSFcsC7HmVFj=x0V8Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div>At least the "shutdown.return requires a parameter" part
*may* be a regression of the new "sdcommands" change in
v2.8.3,though I don't think older code passed any. Maybe
something got lost in mass-edit changes though.
<div dir="auto"><br>
</div>
<div dir="auto">Can you please double-check with 2.8.2 if its
older approach to UPS shutdown behaved better?</div>
<div dir="auto"><br>
</div>
Jim Klimov<br>
<br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Tue, May 6, 2025, 00:41
Alexey Korobeinikov <<a
href="mailto:alexey@fseafood.com" moz-do-not-send="true"
class="moz-txt-link-freetext">alexey@fseafood.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,
my UPS Model Powercom BNT400AP ( made 2017.12 ) on Linux
Devuan <br>
Daedalus and NUT v2.8.3 (install from source tarball with
"configure <br>
--with-usb --with-user=nut --with-group=nut
--with-libusb=1.0 <br>
--with-statepath=/run/nut --with-pidpath=/run/nut"
options) didn't <br>
shutdown itself after OS is shuting down by signal of UPS
battary is low.<br>
<br>
...</blockquote>
</div>
</div>
<div dir="auto">
<div class="gmail_quote gmail_quote_container">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
0.184242 Initiating UPS [UPS] shutdown<br>
0.184257 [D1] loop_shutdown_commands: call <br>
do_loop_shutdown_commands() with driver-default sdcommands<br>
0.184267 [D1] Starting <br>
do_loop_shutdown_commands(shudown.default), call depth
1...<br>
0.184280 [D1] upsdrv_shutdown...<br>
0.184289 [D1] Starting <br>
do_loop_shutdown_commands(shutdown.return,shutdown.reboot,load.off.delay,shutdown.stayoff),
<br>
call depth 2...<br>
0.184299 [D1] instcmd(shutdown.return, [NULL])<br>
0.184313 [D3] instcmd: using Path <br>
'UPS.PowerSummary.DelayBeforehutdown'<br>
0.184321 [D2] instcmd: shutdown.return requires an
explicit <br>
parameter<br>
<br>
0.184331 [D1] instcmd(shutdown.reboot, [NULL])<br>
0.184348 [D2] find_nut_info: unknown info type:
shutdown.reboot<br>
0.184358 [D3] instcmd: cmdname 'shutdown.reboot'
not found; <br>
checking for alternatives<br>
0.184371 [D2] instcmd: info element unavailable
shutdown.reboot<br>
<br>
0.184387 [D1] instcmd(load.off.delay, [NULL])<br>
0.184398 [D2] find_nut_info: unknown info type:
load.off.delay<br>
0.184407 [D3] instcmd: cmdname 'load.off.delay' not
found; <br>
checking for alternatives<br>
0.184418 [D2] instcmd: info element unavailable
load.off.delay<br>
<br>
0.184428 [D1] instcmd(shutdown.stayoff, [NULL])<br>
0.184438 [D3] instcmd: using Path <br>
'UPS.PowerSummary.DelayBeforehutdown'<br>
0.184449 [D2] instcmd: shutdown.stayoff requires an
explicit <br>
parameter<br>
<br>
0.184462 [D1] Ending <br>
do_loop_shutdown_commands(shutdown.return,shutdown.reboot,load.off.delay,shutdown.stayoff),
<br>
call<br>
depth 2: return-code 2<br>
0.184471 Shutdown failed!<br>
0.184483 [D1] set_exit_flag: raising exit flag due
to signal -1<br>
0.184493 [D1] do_loop_shutdown_commands(): command
<br>
'shutdown.default' was handled successfully<br>
0.184502 [D1] Ending
do_loop_shutdown_commands(shutdown.default), <br>
call depth 1: return-code 0<br>
0.184512 UPS [UPS]: shutdown request was successful
with <br>
'shutdown.default'<br>
0.184523 [D1] set_exit_flag: raising exit flag due
to <br>
programmatic abort: EXIT_FAILURE<br>
0.184540 [D1] upsdrv_cleanup...<br>
0.184899 [D1] upsnotify: failed to notify about
state <br>
NOTIFY_STATE_STOPPING: no notification tech defined, will
not spam more about it<br>
0.184936 [D1] On systems without service units,
consider `export <br>
NUT_QUIET_INIT_UPSNOTIFY=true`<br>
<br>
I try to use "powercom_sdcmd_byte_order_fallback" option,
with same effect.<br>
<br>
Wat's wrong with my UPS/NUT ?<br>
Thank You!<br>
<br>
-- <br>
Oleksii Korobeinikov<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">Nut-upsuser@alioth-lists.debian.net</a><br>
<a
href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
З Повагою
Коробейніков Олексій
Системний адміністратор
ТОВ "Флагман Сіфуд"
вул. Броварська 152, смт Велика Димерка
Київська область, 07442
р.+38 044 495-88-00
вн.6101
м.+38 067 994-40-48</pre>
</body>
</html>