[Nut-upsuser] Strange LOWBATT and REPLBATT from BX950MI

[fRANz]

Hi all,
brand new APC Backup UPS 950 VA BX950MI here, controlled by nut 2.8.0
(Debian package version 2.8.0-7) on Debian 12.8
Current nut scenario and config:

# nut-scanner -U
Scanning USB bus.
[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "051D"
productid = "0002"
product = "Back-UPS BX950MI"
serial = "9B24xxxxxxxx"
vendor = "American Power Conversion"
bus = "001"
---
/etc/nut/nut.conf file
...
#MODE=none
MODE=standalone
---
/etc/nut/ups.conf file
...
[bx950mi]
driver = "usbhid-ups"
port = "auto"
desc = "Back-UPS BX950MI"
---
/etc/nut/upsd.conf file
...
# LISTEN <IP address or name> [<port>]
LISTEN 127.0.0.1 3493
...
---
/etc/nut/upsd.users file
...
[nutro]
password = xxx
upsmon primary

[nutadm]
password = xxx
actions = SET
instcmds = ALL
---
/etc/nut/upsmon.conf file
...
RUN_AS_USER root

MONITOR bx950mi at localhost 1 nutro xxx primary

NOTIFYCMD "/root/tg.sh"

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 ONLINE     SYSLOG+EXEC
NOTIFYFLAG ONBATT     SYSLOG+EXEC
NOTIFYFLAG LOWBATT    SYSLOG+EXEC
NOTIFYFLAG FSD        SYSLOG+EXEC
NOTIFYFLAG COMMOK     SYSLOG+EXEC
NOTIFYFLAG COMMBAD    SYSLOG+EXEC
NOTIFYFLAG SHUTDOWN   SYSLOG+EXEC
NOTIFYFLAG REPLBATT   SYSLOG+EXEC
NOTIFYFLAG NOCOMM     SYSLOG+EXEC
NOTIFYFLAG NOPARENT   SYSLOG+EXEC
---
UPSLOG command:
upslog -s bx950mi at localhost -f '%TIME @Y at m@d @H at M@S% %VAR battery.charge%
%VAR input.voltage% %VAR ups.load% [%VAR ups.status%] %VAR ups.temperature%
%VAR input.frequency% %VAR battery.runtime%' -l /var/log/nutupslog
---

tg.sh is a simple bash script in order to get NUT notifications on
Telegram; I still receiving a lot of LOWBATT and REPLBATT even if battery
seems charged as per upslog. For example:

Telegram notifications:
Sun Dec  1 05:39:51 AM CET 2024
Notify type: LOWBATT
Notify message: UPS bx950mi at localhost battery is low
Sun Dec  1 05:39:51 AM CET 2024
Notify type: REPLBATT
Notify message: UPS bx950mi at localhost battery needs to be replaced
...
Sun Dec  1 12:05:17 PM CET 2024
Notify type: LOWBATT
Notify message: UPS bx950mi at localhost battery is low

UPSLOG output during the same window:
20241201 053909 99 224.0 0 [OL CHRG] NA NA 3548
20241201 053939 99 224.0 0 [OL CHRG] NA NA 3548
20241201 054009 99 219.0 0 [OL CHRG] NA NA 3548
...
20241201 120509 100 221.0 0 [OL CHRG] NA NA 3584
20241201 120539 100 221.0 0 [ALARM OL] NA NA 3584
20241201 120609 100 221.0 0 [OL CHRG] NA NA 3584

It's unclear for me if these notifications are due to a bad NUT
configuration I applied (so please suggest needed tweaks) or it could be a
faulty UPS so I'll ask for a replacement.
Thanks for any help.
-f
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20241201/afea3715/attachment.htm>