Binary_sensor toggling back and forth

I am using the dscKeybusInterface’s HomeAssistant-MQTT example to connect my DSC alarm panel to HomeAssistant, and it has been working perfectly in reporting all the Zone states to HomeAssistant for months. But the Trouble Status looks strange in the HomeAssistant logbook. My DSC system has a persistent trouble flag because of old backup battery. In the HomeAssistant Logbook it shows Trouble status toggling between no problem/problem. every few minutes.

Detected problem
12:09:53 PM - 3 minutes ago
Cleared (no problem detected)
12:09:53 PM - 3 minutes ago
Detected problem
12:05:11 PM - 8 minutes ago
Cleared (no problem detected)
12:05:11 PM - 8 minutes ago
Detected problem
12:00:58 PM - 12 minutes ago
Cleared (no problem detected)
12:00:58 PM - 12 minutes ago

I am not sure if this is an issue with dscKeybusInterface, MQTT, or HomeAssistant.
Here is the bit of code in dscKeybusInterface/HomeAssistant-MQTT example:

const char* mqttTroubleTopic = "dsc/Get/Trouble";      // Sends trouble status

and

    if (dsc.troubleChanged) {
      dsc.troubleChanged = false;  // Resets the trouble status flag
      if (dsc.trouble) mqtt.publish(mqttTroubleTopic, "1", true);
      else mqtt.publish(mqttTroubleTopic, "0", true);
    }

And here is relevant bit in HomeAssistant configuration:

# https://www.home-assistant.io/components/alarm_control_panel.mqtt/
alarm_control_panel:
  # Security Partition 1
  - platform: mqtt
    name: "Security Partition 1"
    state_topic: "dsc/Get/Partition1"
    availability_topic: "dsc/Status"
    command_topic: "dsc/Set"
    payload_disarm: "1D"
    payload_arm_home: "1S"
    payload_arm_away: "1A"
    payload_arm_night: "1N"

# https://www.home-assistant.io/components/binary_sensor.mqtt/
binary_sensor:
  - platform: mqtt
    name: "Security Trouble"
    state_topic: "dsc/Get/Trouble"
    device_class: "problem"
    payload_on: "1"
    payload_off: "0"

As far as I can tell the dsc interface is NOT sending any dsc/Get/Trouble MQTT messages. It is in a persistent on state.
So why is the Logbook showing a toggle every few minutes? Is this something in the binary_sensor or platform mqtt implementaion/options?

Is it the Classic or PowerSeries?