Missing Topics for GSM Troubles (MG5000)

Alarm system

Magellan MG5000 with IP150S, PCS250G and two RPT1, access mode (IP150S)

Environment

Linux, Docker

Git branch

Docker latest

Describe the bug

From time to time I see different log entries like the next (data is different):

2024-09-10 16:55:30,771 - ERROR    - PAI.paradox.lib.handlers - No handler for message 5
Detail: Container: 
    fields = Container: 
        data = b'R\x00\x80\x00\x02\x02\x10\x00\x00\x14\x18\t\n\x106\xcf'... (truncated, total 36)
        value = Container: 
            po = Container: 
                command = 5
                status = Container: 
                    reserved = False
                    alarm_reporting_pending = False
                    Winload_connected = True
                    NeWare_connected = False
            validation = 128
            address = 0
            data = b'\x02\x02\x10\x00\x00\x14\x18\t\n\x106\xcf\x9c\x97N\x00'... (truncated, total 32)
        offset1 = 0
        offset2 = 36
        length = 36
    checksum = b'\xbb' (total 1)

To Reproduce

I have no exact idea what triggers these log entries. I assume that they come from missing implementation for GSM troubles. Indeed I'm missing the topics of these GSM troubles:

• GSM RF Jamming Supervision
• GSM Service Failure Options

Logs

n.a.

First of all it would be helpful to have the complete data within the logfile. Currently it's truncated.

Start at the PAI.paradox.lib.handlers log entry for unhandled message 5 and inspect how the logged payload is truncated. Use the reported command-5 data and the GSM RF Jamming Supervision and GSM Service Failure Options topics to determine the missing behavior; done means the complete data is available in logs and those GSM troubles are handled.