Alert: REPLBATT active after battery replacement and requires reboot to clear

[vyasa8]

CONFIGURATION:

A Powerware PW9120 3000i, on a network configuration with a server and a couple of slaves.

The nut-server OS is Debian 12 (6.1.0-37-amd64). Nut was installed from the Debian repo with version 2.8.0-7 amd64, and client has the same version.

The driver used was:
Network UPS Tools - UPS driver controller 2.8.0
Network UPS Tools - BCMXCP UPS driver 0.32 (2.8.0)

UPS is connected with a standard RS232 serial connection, and works with all standard commands and functionality.

Command "upscmd -l upsname" provides the following, where I have successfully used test.battery.start and test.system.start:

beeper.disable - Disable the UPS beeper
beeper.enable - Enable the UPS beeper
beeper.mute - Temporarily mute the UPS beeper
load.on - Turn on the load immediately
outlet.1.load.off - Turn off the load on outlet 1 immediately
outlet.1.load.on - Turn on the load on outlet 1 immediately
outlet.1.shutdown.return - Turn off the outlet 1 and return when power is back
outlet.2.load.off - Turn off the load on outlet 2 immediately
outlet.2.load.on - Turn on the load on outlet 2 immediately
outlet.2.shutdown.return - Turn off the outlet 2 and return when power is back
shutdown.return - Turn off the load and return when power is back
shutdown.stayoff - Turn off the load and remain off
test.battery.start - Start a battery test
test.system.start - Start a system test

ISSUE:

The Alert: REPLBATT or RB won't clear unless the BCMXCP driver is restarted (upsdrvsvcctl/upsdrvctl) or system is rebooted. I simulated the fault , by putting the UPS in bypass and disconnecting the battery. This caused the RB alert again. With this I then reconnected battery, restored UPS to normal operating condition. Then used upsdrvctl to STOP and START the driver.

Generating alert condition for simulating RB:
Alert type: REPLBATT
.....................
ups.status: ALARM OL BYPASS RB
ups.test.result: Done and error

Alert cleared on UPS, and alert condition with RB persisting on NUT-SERVER:
Alert type: ONLINE
.................
ups.status: OL RB
ups.test.result: Done and passed

Restarting using upsdrvctl start/stop command clears RB:
Alert type: COMMOK
..................
ups.status: OL
ups.test.result: Done and passed

Clearly it seems that bcmxcp will "latch" the alert until driver restart or server reboot.

It has been suggested that there might be an oversight in the code where bcmxcp_status.alarm_replace_battery=1 is not properly initialized to 0.