[Nut-upsuser] POWERCOM UPS USB : UPS Shutdown
Jim Klimov
jimklimov+nut at gmail.com
Tue May 13 16:31:51 BST 2025
Check https://github.com/networkupstools/nut/pull/2955 please.
Jim
On Mon, May 12, 2025 at 12:04 PM Jim Klimov <jimklimov+nut at gmail.com> wrote:
> Hoped to look into this just today, if nobody beat me to it yet.
>
> Jim
>
> On Mon, May 12, 2025 at 11:54 AM Alexey Korobeinikov <alexey at fseafood.com>
> wrote:
>
>> Are there any chances that this error can be fixed?
>>
>> 06.05.2025 18:19, Alexey Korobeinikov:
>>
>> Hi! Thank You!
>>
>> The UPS behavior are chages with NUT v.2.8.2 but more strange
>>
>> After this command (if power cord unpluged)
>> /usr/local/ups/bin/usbhid-ups -DDDD -a UPS -k
>>
>> ....
>> 0.188173 [D4] string_to_path: depth = 3
>> 0.188187 [D4] string_to_path: depth = 3
>> 0.188199 [D4] string_to_path: depth = 3
>> 0.188211 [D4] string_to_path: depth = 3
>> 0.188246 [D2] find_nut_info: unknown info type: load.off.delay
>> 0.188267 [D2] find_nut_info: unknown info type: load.off.delay
>> 0.188280 Initiating UPS shutdown
>> 0.188290 [D1] upsdrv_shutdown...
>> 0.188298 [D1] instcmd(shutdown.return, [NULL])
>> 0.188316 [D3] instcmd: using Path
>> 'UPS.PowerSummary.DelayBeforeShutdown'
>> 0.188332 [D3] powercom_shutdown_nuf: value = (null), command = 5E00
>> 0.224970 [D3] Report[set]: (3 bytes) => 0f 00 5e
>> 0.225003 [D4] Set report succeeded
>> 0.225012 [D3] instcmd: SUCCEED
>>
>> The UPS are start double beeping every 2 seconds, but didn't turn off
>> himself ( 2 minutes wait )
>> UPS are still beeping if power are restored
>>
>> Status are:
>> # upsc ups at localhost
>> battery.charge: 100
>> battery.charge.low: 70
>> battery.charge.warning: 30
>> battery.mfr.date: 2014/01/15
>> battery.runtime: 800
>> battery.type: PbAc
>> device.mfr: POWERCOM Co.,LTD
>> device.model: HID UPS Battery
>> device.serial: 004-0D9F-000
>> device.type: ups
>> driver.debug: 0
>> driver.flag.allow_killpower: 0
>> driver.flag.ignorelb: enabled
>> driver.name: usbhid-ups
>> driver.parameter.offdelay: 30
>> driver.parameter.ondelay: 60
>> driver.parameter.override.battery.charge.low: 70
>> driver.parameter.pollfreq: 30
>> driver.parameter.pollinterval: 2
>> driver.parameter.port: auto
>> driver.parameter.productid: 0004
>> driver.parameter.synchronous: auto
>> driver.parameter.vendorid: 0d9f
>> driver.state: quiet
>> driver.version: 2.8.2
>> driver.version.data: PowerCOM HID 0.7
>> driver.version.internal: 0.53
>> driver.version.usb: libusb-1.0.26 (API: 0x1000109)
>> input.frequency: 50.0
>> input.voltage: 224.0
>> input.voltage.nominal: 220
>> output.frequency: 50.0
>> output.voltage: 224.0
>> output.voltage.nominal: 220
>> ups.beeper.status: enabled
>> ups.date: 2014/01/15
>> ups.delay.shutdown: 30
>> ups.delay.start: 60
>> ups.load: 1
>> ups.mfr: POWERCOM Co.,LTD
>> ups.model: HID UPS Battery
>> ups.productid: 0004
>> ups.serial: 004-0D9F-000
>> ups.status: OL
>> ups.test.result: Done and passed
>> ups.timer.shutdown: 269
>> ups.timer.start: 0
>> ups.vendorid: 0d9f
>> root at vTEMPLATE8:/var/log# upsc ups at localhost
>> battery.charge: 100
>> battery.charge.low: 70
>> battery.charge.warning: 30
>> battery.mfr.date: 2014/01/15
>> battery.runtime: 800
>> battery.type: PbAc
>> device.mfr: POWERCOM Co.,LTD
>> device.model: HID UPS Battery
>> device.serial: 004-0D9F-000
>> device.type: ups
>> driver.debug: 0
>> driver.flag.allow_killpower: 0
>> driver.flag.ignorelb: enabled
>> driver.name: usbhid-ups
>> driver.parameter.offdelay: 30
>> driver.parameter.ondelay: 60
>> driver.parameter.override.battery.charge.low: 70
>> driver.parameter.pollfreq: 30
>> driver.parameter.pollinterval: 2
>> driver.parameter.port: auto
>> driver.parameter.productid: 0004
>> driver.parameter.synchronous: auto
>> driver.parameter.vendorid: 0d9f
>> driver.state: quiet
>> driver.version: 2.8.2
>> driver.version.data: PowerCOM HID 0.7
>> driver.version.internal: 0.53
>> driver.version.usb: libusb-1.0.26 (API: 0x1000109)
>> input.frequency: 50.0
>> input.voltage: 224.0
>> input.voltage.nominal: 220
>> output.frequency: 50.0
>> output.voltage: 224.0
>> output.voltage.nominal: 220
>> ups.beeper.status: enabled
>> ups.date: 2014/01/15
>> ups.delay.shutdown: 30
>> ups.delay.start: 60
>> ups.load: 1
>> ups.mfr: POWERCOM Co.,LTD
>> ups.model: HID UPS Battery
>> ups.productid: 0004
>> ups.serial: 004-0D9F-000
>> ups.status: OL
>> ups.test.result: Done and passed
>> ups.timer.shutdown: 89
>> ups.timer.start: 0
>> ups.vendorid: 0d9f
>> root at vTEMPLATE8:/var/log# upsc ups at localhost
>> battery.charge: 100
>> battery.charge.low: 70
>> battery.charge.warning: 30
>> battery.mfr.date: 2014/01/15
>> battery.runtime: 800
>> battery.type: PbAc
>> device.mfr: POWERCOM Co.,LTD
>> device.model: HID UPS Battery
>> device.serial: 004-0D9F-000
>> device.type: ups
>> driver.debug: 0
>> driver.flag.allow_killpower: 0
>> driver.flag.ignorelb: enabled
>> driver.name: usbhid-ups
>> driver.parameter.offdelay: 30
>> driver.parameter.ondelay: 60
>> driver.parameter.override.battery.charge.low: 70
>> driver.parameter.pollfreq: 30
>> driver.parameter.pollinterval: 2
>> driver.parameter.port: auto
>> driver.parameter.productid: 0004
>> driver.parameter.synchronous: auto
>> driver.parameter.vendorid: 0d9f
>> driver.state: quiet
>> driver.version: 2.8.2
>> driver.version.data: PowerCOM HID 0.7
>> driver.version.internal: 0.53
>> driver.version.usb: libusb-1.0.26 (API: 0x1000109)
>> input.frequency: 50.0
>> input.voltage: 226.0
>> input.voltage.nominal: 220
>> output.frequency: 50.0
>> output.voltage: 226.0
>> output.voltage.nominal: 220
>> ups.beeper.status: enabled
>> ups.date: 2014/01/15
>> ups.delay.shutdown: 30
>> ups.delay.start: 60
>> ups.load: 1
>> ups.mfr: POWERCOM Co.,LTD
>> ups.model: HID UPS Battery
>> ups.productid: 0004
>> ups.serial: 004-0D9F-000
>> ups.status: OL
>> ups.test.result: Done and passed
>> ups.timer.shutdown: 3148
>> ups.timer.start: 0
>> ups.vendorid: 0d9f
>>
>> And strange with timer parametr that are changes cycling:
>> ups.timer.shutdown: 3570
>> ups.timer.shutdown: 2430
>> ups.timer.shutdown: 1710
>> ...
>> ups.timer.shutdown: 870
>> ups.timer.shutdown: 3629
>> ups.timer.shutdown: 2729
>> ups.timer.shutdown: 1829
>> ...
>> ups.timer.shutdown: 89
>> ups.timer.shutdown: 3148
>> ...
>>
>> the ups.conf are:
>> [UPS]
>> driver = usbhid-ups
>> vendorid = 0d9f
>> productid = 0004
>> # powercom_sdcmd_byte_order_fallback
>> port = auto
>> # pollonly = enabled
>> pollinterval = 2
>> pollfreq = 30
>> offdelay = 30
>> ondelay = 60
>> allow_killpower
>> ignorelb
>> override.battery.charge.low = 70
>> # override.battery.runtime.low = 600
>>
>> 06.05.2025 01:49, Jim Klimov:
>>
>> 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.
>>
>> Can you please double-check with 2.8.2 if its older approach to UPS
>> shutdown behaved better?
>>
>> Jim Klimov
>>
>> On Tue, May 6, 2025, 00:41 Alexey Korobeinikov <alexey at fseafood.com>
>> wrote:
>>
>>> Hi, my UPS Model Powercom BNT400AP ( made 2017.12 ) on Linux Devuan
>>> Daedalus and NUT v2.8.3 (install from source tarball with "configure
>>> --with-usb --with-user=nut --with-group=nut --with-libusb=1.0
>>> --with-statepath=/run/nut --with-pidpath=/run/nut" options) didn't
>>> shutdown itself after OS is shuting down by signal of UPS battary is low.
>>>
>>> ...
>>
>> 0.184242 Initiating UPS [UPS] shutdown
>>> 0.184257 [D1] loop_shutdown_commands: call
>>> do_loop_shutdown_commands() with driver-default sdcommands
>>> 0.184267 [D1] Starting
>>> do_loop_shutdown_commands(shudown.default), call depth 1...
>>> 0.184280 [D1] upsdrv_shutdown...
>>> 0.184289 [D1] Starting
>>> do_loop_shutdown_commands(shutdown.return,shutdown.reboot,load.off.delay,shutdown.stayoff),
>>>
>>> call depth 2...
>>> 0.184299 [D1] instcmd(shutdown.return, [NULL])
>>> 0.184313 [D3] instcmd: using Path
>>> 'UPS.PowerSummary.DelayBeforehutdown'
>>> 0.184321 [D2] instcmd: shutdown.return requires an explicit
>>> parameter
>>>
>>> 0.184331 [D1] instcmd(shutdown.reboot, [NULL])
>>> 0.184348 [D2] find_nut_info: unknown info type: shutdown.reboot
>>> 0.184358 [D3] instcmd: cmdname 'shutdown.reboot' not found;
>>> checking for alternatives
>>> 0.184371 [D2] instcmd: info element unavailable shutdown.reboot
>>>
>>> 0.184387 [D1] instcmd(load.off.delay, [NULL])
>>> 0.184398 [D2] find_nut_info: unknown info type: load.off.delay
>>> 0.184407 [D3] instcmd: cmdname 'load.off.delay' not found;
>>> checking for alternatives
>>> 0.184418 [D2] instcmd: info element unavailable load.off.delay
>>>
>>> 0.184428 [D1] instcmd(shutdown.stayoff, [NULL])
>>> 0.184438 [D3] instcmd: using Path
>>> 'UPS.PowerSummary.DelayBeforehutdown'
>>> 0.184449 [D2] instcmd: shutdown.stayoff requires an explicit
>>> parameter
>>>
>>> 0.184462 [D1] Ending
>>> do_loop_shutdown_commands(shutdown.return,shutdown.reboot,load.off.delay,shutdown.stayoff),
>>>
>>> call
>>> depth 2: return-code 2
>>> 0.184471 Shutdown failed!
>>> 0.184483 [D1] set_exit_flag: raising exit flag due to signal -1
>>> 0.184493 [D1] do_loop_shutdown_commands(): command
>>> 'shutdown.default' was handled successfully
>>> 0.184502 [D1] Ending do_loop_shutdown_commands(shutdown.default),
>>> call depth 1: return-code 0
>>> 0.184512 UPS [UPS]: shutdown request was successful with
>>> 'shutdown.default'
>>> 0.184523 [D1] set_exit_flag: raising exit flag due to
>>> programmatic abort: EXIT_FAILURE
>>> 0.184540 [D1] upsdrv_cleanup...
>>> 0.184899 [D1] upsnotify: failed to notify about state
>>> NOTIFY_STATE_STOPPING: no notification tech defined, will not spam more
>>> about it
>>> 0.184936 [D1] On systems without service units, consider `export
>>> NUT_QUIET_INIT_UPSNOTIFY=true`
>>>
>>> I try to use "powercom_sdcmd_byte_order_fallback" option, with same
>>> effect.
>>>
>>> Wat's wrong with my UPS/NUT ?
>>> Thank You!
>>>
>>> --
>>> Oleksii Korobeinikov
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Nut-upsuser mailing list
>>> Nut-upsuser at alioth-lists.debian.net
>>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>>>
>>
>> --
>> З Повагою
>> Коробейніков Олексій
>> Системний адміністратор
>>
>> ТОВ "Флагман Сіфуд"
>> вул. Броварська 152, смт Велика Димерка
>> Київська область, 07442
>> р.+38 044 495-88-00
>> вн.6101
>> м.+38 067 994-40-48
>>
>>
>> _______________________________________________
>> Nut-upsuser mailing listNut-upsuser at alioth-lists.debian.nethttps://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>>
>>
>> --
>> З Повагою
>> Коробейніков Олексій
>> Системний адміністратор
>>
>> ТОВ "Флагман Сіфуд"
>> вул. Броварська 152, смт Велика Димерка
>> Київська область, 07442
>> р.+38 044 495-88-00
>> вн.6101
>> м.+38 067 994-40-48
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20250513/3a4c6614/attachment-0001.htm>
More information about the Nut-upsuser
mailing list