Device Alarm Parsing

We parse alarms for every telemetry data record of your devices and put the parsing results in the alarms field of the telemetry data. You can use the alarm codes appearing in alarms to determine which alarms the device triggered at that moment.

1. Alarms are divided into 3 severity levels:
   • Fault: E001, ...
   • Warning: W303, ...
   • Info: I413, ...

Alarm Code List

See the Device Alarm Code List.

Usage Scenarios

Scenario ①: Subscribe to device running data via MQTT, and you can find the alarm field "alarms" in the device messages.

For example, the device triggered two alarms, E432 and E400, at that moment.

{
    "metric": {
        "rtcTime": "2025-09-11 08:09:19",
        "creationDate": "2025-09-11 06:09:20 +0000",
        "dataLoggerSN": "A1L24001014000A9",
        "dataLoggerTime": "2025-09-11 06:09:20 +0000",
        "alarms": [
            "E432",
            "E400"
        ],
        "backupAf": 0,
        "backupAi": 1.1,
        ...
    },
    "resumeType": 0,
    "tag": {
        "sn": "A11240020184005A",
        "modelType": "M2HS-6K-30"
    },
    "timestamp": 1757570960954
}

Scenario ②: Retrieve the latest device running data via the REST API, and you can find the alarm field "alarms" in the returned JSON.

{
    "errorCode": 0,
    "info": null,
    "body": {
        "invSn": "A11240020184005A",
        "alarms": [
            "E432"
        ],
        ...
    },
    "successful": true
}

Scenario ③: Retrieve historical device running data via the REST API, and you can find the alarm field "alarms" in the returned JSON.

{
    "errorCode": 0,
    "info": null,
    "body": [
        {
            "invSn": null,
            "alarms": [
                "E432"
            ],
           ...
        }
    ],
    "successful": true
}