Skip to main content

Direct Device Analyzer for GSM/SMS

Read What is an Analyzer? and Writing a Direct Device Analyzer first.

The SMS Analyzer uses the same AirNgin logical Operation/Command mapping as the Direct Device MQTT Analyzer. SMS is a different transport; it does not create a second logical command model.

Device-to-server SMS​

The current Device framing begins with:

CC:Data

The Analyzer receives the SMS payload, extracts the producer-defined data, and maps it to AirNgin logical state.

Example output structure:

{
  "result": "OK",
  "status": [
    {"key": "ch1", "value": "on"}
  ]
}

Server-to-device SMS​

The server-side Direct Device Analyzer receives the same logical command identity used by MQTT:

{
  "deviceSerial": "AIRN1234567890",
  "operationName": "ch1",
  "value": "on"
}

Your Analyzer converts this logical command to the payload understood by your GSM Device.

Do not use this Direct Device bidirectional Analyzer model for Gateway Child downlink translation; Gateway Drivers own that path.