SigFox Integration

The Sigfox integration connects ThingsBoard to the Sigfox Backend over HTTP. Use it to bring data from Sigfox-connected devices into ThingsBoard for monitoring and rule-based automation — including sending commands back to those devices.

A Sigfox device transmits an uplink to the Sigfox Backend, which forwards it over HTTP to the integration’s endpoint through a custom callback. The uplink converter decodes the payload into telemetry and attributes, and the ThingsBoard Core Service stores the data, creating the device automatically on first contact. For downlink, the Rule Engine hands a message to the integration; the downlink converter encodes it, and the Sigfox Backend delivers it to the device.

Before creating the integration, ensure:

• You have access to ThingsBoard Cloud with integration functionality enabled for your tenant.
• You have permissions to create integrations and data converters in ThingsBoard.
• You have a Sigfox Backend account with administrative access to your device type.
• You have at least one Sigfox device registered in the Sigfox Backend.
• Your ThingsBoard integration’s HTTP endpoint is reachable from the public internet over HTTPS — the Sigfox Backend must be able to reach it to deliver callbacks. If your instance isn’t directly reachable, use Remote Integration instead.

The uplink converter decodes the incoming Sigfox callback message (JSON with the device, time, and data fields you define in the callback body) and maps it to the ThingsBoard data model — it resolves the target device and extracts fields into telemetry and attributes. For the full decoder function reference, see Uplink data converter.

A Sigfox uplink message delivered to the ThingsBoard endpoint looks like this:

{
  "device": "1CB0F1",
  "time": "1661868952",
  "data": "2502af2102462a",
  "seqNumber": "3737"
}

The device field identifies the transmitting device and maps to the device name. The time field is the Unix timestamp (seconds). The data field is a hex-encoded sensor reading whose byte layout is device-specific — in this example the first byte holds configuration flags (stored as attributes) and the remaining bytes encode temperature, humidity, CO₂, and the CO₂ baseline.

1. Go to Integrations center ⇾ Data converters.
2. Click + Add data converter ⇾ Create new converter.

In the Add data converter dialog:

3. Converter type — leave Uplink (selected by default).
4. Integration type — in the search field, enter SigFox and select SigFox from the list.
5. Name — enter a converter name, for example SigFox Uplink Converter.
6. Main decoding configuration — a code editor with the function signature function decoder(payload, metadata) {. Paste the decoder function shown below. By default the editor opens in TBEL; use the TBEL / JS toggle (upper right) to switch languages.
7. Click Add.

The decoder below parses the callback JSON, resolves the device name from the Sigfox device ID, and decodes the hex data field into telemetry. Adapt the byte offsets and scaling to match your device protocol.

The decoder function used in this tutorial:

/** Decoder **/

// Decode payload to json
var payloadStr = decodeToJson(payload);

// Set general device information
var deviceName = 'Sigfox-' + payloadStr.device;
var deviceType = 'Sigfox device';
var groupName = 'Control room devices';
// var customerName = 'Customer A';
// use assetName and assetType instead of deviceName and deviceType
// to automatically create assets instead of devices.
// var assetName = 'Asset A';
// var assetType = 'building';

// Parse specific device information, it may be different, depends on device type
var attrByte = parseInt(payloadStr.data.substring(0, 2), 16); // force TBEL to convert to INT
var autoCalibration = (attrByte & 0x1) === 1 ? "on" : "off"; // bitmask for first bit
var zeroPointAdjusted = ((attrByte & 0x2) >> 1) === 1 ? true : false; // bitmask for second bit; right shift one bit to get second bit to the LSB position
var transmitPower = ((attrByte & 0x4) >> 2) === 1 ? "full" : "low"; // bitmask for third bit; right shift two bits to get third bit to the LSB position
var powerControl = ((attrByte & 0x8) >> 3) === 1 ? "on" : "off"; // bitmask for third bit; right shift three bits to get fourth bit to the LSB position
var firmwareVersion = attrByte >> 4; // shift right to bring the nibble down to the first four bits; result is INT

var data = payloadStr.data;

var temperature = null;
var humidity = null;
var co2 = null;
var co2Baseline = null;

if (data != null) {
  if (data.length() >= 6) {
    temperature = toFixed(parseInt(payloadStr.data.substring(2, 6), 16) / 10.0 - 40, 1);
  }
  if (data.length() >= 8) {
    humidity = parseInt(payloadStr.data.substring(6, 8), 16);
  }
  if (data.length() >= 12) {
    co2 = parseInt(payloadStr.data.substring(8, 12), 16);
  }

  if (data.length() >= 14) {
    var co2BaselineN = parseInt(payloadStr.data.substring(12, 14), 16);
    if (co2BaselineN === 0) {
      co2Baseline = 400;
    } else {
      co2Baseline = co2BaselineN * 10;
    }
  }
}

var result = {
  // Use deviceName and deviceType or assetName and assetType, but not both.
  deviceName: deviceName,
  deviceType: deviceType,
  //  assetName: assetName,
  //  assetType: assetType,
  //  customerName: customerName,
  groupName: groupName,
  attributes: {
    sigfoxId: payloadStr.device,
    deviceTypeId: payloadStr.deviceTypeId,
    autoCalibration: autoCalibration,
    zeroPointAdjusted: zeroPointAdjusted,
    transmitPower: transmitPower,
    powerControl: powerControl,
    fwVersion: firmwareVersion
  },
  telemetry: {
    ts: parseLong("" + payloadStr.time + "000"),
    values: {
      temperature: temperature,
      humidity: humidity,
      co2: co2,
      co2Baseline: co2Baseline,
      customData1: payloadStr["customData#int1"],
      customData2: payloadStr["customData#int2"]
    }
  }
};

return result;

/** Decoder **/

// Decode the incoming byte array into a JSON object.
var payloadStr = decodeToJson(payload);

// Set general device information.
var deviceName = "Sigfox-" + payloadStr.device;
var deviceType = "Sigfox device";
var groupName = "Control room devices";
// var customerName = "Customer A";
// Use assetName and assetType instead of deviceName and deviceType
// to automatically create an asset instead of a device.
// var assetName = "Asset A";
// var assetType = "building";

// Sigfox device payload represented as a hexadecimal string.
var data = payloadStr.data;

// Initialize decoded attributes.
var autoCalibration = null;
var zeroPointAdjusted = null;
var transmitPower = null;
var powerControl = null;
var firmwareVersion = null;

// Initialize decoded telemetry values.
var temperature = null;
var humidity = null;
var co2 = null;
var co2Baseline = null;

if (data != null && data.length >= 2) {
  // Decode the first byte containing configuration flags
  // and the firmware version.
  var attrByte = parseInt(data.substring(0, 2), 16);

  // Bit 0: automatic calibration status.
  autoCalibration = (attrByte & 0x01) === 1 ? "on" : "off";

  // Bit 1: zero-point adjustment status.
  zeroPointAdjusted = ((attrByte & 0x02) >> 1) === 1;

  // Bit 2: transmission power mode.
  transmitPower = ((attrByte & 0x04) >> 2) === 1 ? "full" : "low";

  // Bit 3: power control status.
  powerControl = ((attrByte & 0x08) >> 3) === 1 ? "on" : "off";

  // Bits 4–7: firmware version.
  firmwareVersion = attrByte >> 4;
}

if (data != null) {
  // Bytes 2–3: temperature in 0.1 °C units with a -40 °C offset.
  if (data.length >= 6) {
    var rawTemperature = parseInt(data.substring(2, 6), 16);
    temperature = Math.round((rawTemperature / 10.0 - 40) * 10) / 10;
  }

  // Byte 4: relative humidity.
  if (data.length >= 8) {
    humidity = parseInt(data.substring(6, 8), 16);
  }

  // Bytes 5–6: CO2 concentration.
  if (data.length >= 12) {
    co2 = parseInt(data.substring(8, 12), 16);
  }

  // Byte 7: CO2 baseline.
  if (data.length >= 14) {
    var rawCo2Baseline = parseInt(data.substring(12, 14), 16);
    co2Baseline = rawCo2Baseline === 0 ? 400 : rawCo2Baseline * 10;
  }
}

var result = {
  // Use deviceName and deviceType or assetName and assetType, but not both.
  deviceName: deviceName,
  deviceType: deviceType,

  // assetName: assetName,
  // assetType: assetType,
  // customerName: customerName,

  groupName: groupName,

  attributes: {
    sigfoxId: payloadStr.device,
    deviceTypeId: payloadStr.deviceTypeId,
    autoCalibration: autoCalibration,
    zeroPointAdjusted: zeroPointAdjusted,
    transmitPower: transmitPower,
    powerControl: powerControl,
    fwVersion: firmwareVersion
  },

  telemetry: {
    // Convert the Unix timestamp from seconds to milliseconds.
    ts: parseInt(payloadStr.time, 10) * 1000,

      values: {
      temperature: temperature,
      humidity: humidity,
      co2: co2,
      co2Baseline: co2Baseline,
      customData1: payloadStr["customData#int1"],
      customData2: payloadStr["customData#int2"]
    }
  }
};

/** Helper functions **/

// Convert the incoming byte array into a string.
function decodeToString(payload) {
  return String.fromCharCode.apply(String, payload);
}

// Convert the incoming byte array into a JSON object.
function decodeToJson(payload) {
  return JSON.parse(decodeToString(payload));
}

return result;

What the Converter Receives

ThingsBoard passes two variables to the decoder:

This metadata object — available to the decoder script as metadata.xxx — is separate from the Metadata column shown on the integration and converter Events tabs (see Verify Converter Events), which displays integration-level context rather than per-message fields.

Adapting the Decoder to Your Device

• Device name — change 'Sigfox-' + payloadStr.device to any identifier present in your payload.
• Payload encoding — update the substring ranges and arithmetic to match your device’s byte layout. Refer to the device datasheet for the field order, scaling factors, and offsets.
• Telemetry — add or remove keys under telemetry.values (for example, pressure: ...).
• Attributes — the first byte of payloadStr.data is decoded into device attributes. Update the bit-mask logic to match your device’s configuration-byte structure, or remove the block if your device sends no configuration flags.
• Match your payload structure — update the byte offsets, lengths, scaling, and field names to match your device’s binary specification. The data field carries up to 12 bytes.
• Add or remove fields — add more parseInt(json.data.substring(start, end), 16) calls (or bit-mask logic, string extraction, etc.) for additional sensors; remove entries your device does not transmit.
• Add more callback fields — if you include extra Sigfox variables in the callback body (for example station, lat, lng, or avgSnr), read them from the parsed object as data.<field>.
• Override device identity from the payload — set result.deviceName, result.deviceType, result.group, or result.customer to derive device identity from payload content rather than the Sigfox device ID.

1. Go to Integrations center ⇾ Integrations and click + Add integration.
2. Basic settings:
   • Set Integration type to SigFox.
   • Enter a Name for the integration, or keep the default SigFox integration.
   • Leave Enable integration and Allow create devices or assets on so a device is created automatically on first message.
   • Click Next.
3. Uplink data converter:
   • Click Select existing and choose the Sigfox Uplink Converter created above, or click Create new to define the decoder inline.
   • Click Next.
4. Downlink data converter:
   • Click Skip — a downlink converter is only needed when ThingsBoard must send commands back to devices. See Configure and Test Downlink to add one later.
5. Connection:
   • Copy the generated HTTP endpoint URL — you will paste it into the Sigfox Backend callback’s URL pattern field.
   • Optionally, enable Security (Headers filter) and add a header key-value pair to restrict access to this endpoint.
   Read more about each parameter in Connection settings.
6. Click Add to complete the integration setup.

Set Integration type to SigFox, enter a Name, leave both toggles on, and click Next Click Select existing, choose SigFox Uplink Converter, and click Next Click Skip — the downlink converter can be configured later Copy the HTTP endpoint URL; optionally enable Security to add a header filter, and click Add

Base URL

The base address of the ThingsBoard server, used to construct the HTTP endpoint URL below. Pre-filled with the current server address — change it only if the Sigfox Backend must reach ThingsBoard through a different address (for example, a reverse proxy or load balancer).

Example: https://thingsboard.cloud

HTTP Endpoint URL

The auto-generated webhook address for this integration, in the form:

https://{base-url}/api/v1/integrations/sigfox/{integration-id}

Paste this URL into the URL pattern field of the Sigfox callback (see Configure Sigfox Backend) so the Sigfox Backend forwards device uplink messages to ThingsBoard. The URL is stable for the lifetime of the integration.

Enable Security (Headers filter)

When enabled, ThingsBoard validates every incoming request against the header name-value pairs you configure and rejects requests that are missing them.

Add the same header to the callback’s Headers field so the Sigfox Backend authenticates against the endpoint.

Execute Remotely

When enabled, ThingsBoard generates an Integration key and Integration secret for running the integration outside the ThingsBoard cluster — useful when ThingsBoard is not publicly reachable from the internet. See Remote Integration.

Advanced Settings

Configure your Sigfox account to forward device messages to the ThingsBoard HTTP endpoint.

Configure your Sigfox device type to route uplink messages to the ThingsBoard HTTP endpoint URL copied in Create Sigfox Integration. In the Sigfox Backend, this is done by creating a custom callback on the device type.

1. In the Sigfox Backend, go to Device type and locate the device type associated with your device (for example, thermostats).
2. Open the row’s context menu and select Edit.
3. In the Downlink data section, set Downlink mode to CALLBACK. This lets the Sigfox Backend request the downlink payload from ThingsBoard in reply to each uplink.
4. Click Ok to save.

Sigfox Backend — open the device type context menu and click Edit Set Downlink mode to CALLBACK in the Downlink data section and click Ok

1. In the Sigfox Backend, open Device type and select the device type associated with your device.
2. Open the Callbacks tab and click New ⇾ Custom callback.
3. Configure the callback:
   • Type: DATA, Channel: URL, Subtype: BIDIR (required for downlink support).
   • Custom payload config — the format string that decodes the raw Sigfox frame into named variables for your device (for example, int1::uint:8). Leave the raw data field untouched if you decode entirely in the ThingsBoard uplink converter.
   • URL pattern — paste the ThingsBoard HTTP endpoint URL copied from the integration.
   • HTTP method: POST.
   • Headers — if Security is enabled on the integration, add the same header key-value pair here.
   • Content type: application/json.
4. Enter the message body below and click Ok.

Callback body:

{
  "device": "{device}",
  "time": "{time}",
  "data": "{data}",
  "seqNumber": "{seqNumber}"
}

The tokens in braces ({device}, {time}, {data}, {seqNumber}) are Sigfox Backend variables and are case-sensitive. The resulting JSON must match the fields your uplink converter reads. Add more variables here — such as {rssi}, {snr}, or {station} — if your converter needs them.

Sigfox Backend — Callbacks tab: click New to create a callback Select Custom callback Paste the ThingsBoard endpoint URL into URL pattern, add the security header, set the JSON message body, and click Ok

After creating the callback, click the circle in the Downlink column to designate it as the active downlink handler. The circle turns solid to indicate active status. Only one callback per device type can act as the downlink handler.

After the integration and converter are configured, and the device is transmitting through the Sigfox Backend, confirm that ThingsBoard receives, decodes, and stores the data correctly.

Wait for your device to transmit an uplink through the Sigfox Backend, or emulate one by sending an HTTP request directly to the ThingsBoard endpoint with curl — bypassing Sigfox entirely. This is useful to verify the integration and converter before connecting real hardware.

Replace $HTTP_ENDPOINT_URL with the HTTP endpoint URL copied in Create Sigfox Integration:

curl -v \
  -H "Content-Type: application/json" \
  -d '{"device":"1CB0F1","time":"1742481772","seqNumber":"512","data":"2502af2102462a","rssi":"-98.00","snr":"18.10"}' \
  "$HTTP_ENDPOINT_URL"

The data value 2502af2102462a decodes to temperature = 28.7, humidity = 33, co2 = 582, and co2Baseline = 420 — see Verify Converter Events below.

Go to Integrations center ⇾ Integrations, open the Sigfox integration, and click the Events tab. With Event type set to Debug, a row appears with Type: Uplink and Status: OK.
Click … in the Message column to inspect the raw JSON body received from the Sigfox Backend.

Integration Events tab — the test uplink appears with Type Uplink and Status OK Click … in the Message column to inspect the raw JSON body received by the integration

Go to Integrations center ⇾ Data converters, open the uplink converter you configured for this integration, and click its Events tab.
Click … in each column to inspect:

• In — the raw callback JSON payload received by the converter.
• Out — the decoded result produced by the script: deviceName, deviceType, groupName, attributes (sigfoxId, autoCalibration, zeroPointAdjusted, transmitPower, powerControl, fwVersion), and telemetry.values (temperature, humidity, co2, co2Baseline).
• Metadata — integration-level context, including integrationName.

Converter Events tab — the same uplink processed by the SigFox Uplink Converter Click … in the In column to inspect the raw payload the converter received Click … in the Out column to inspect the decoded result — device identity, attributes, and telemetry values

Go to Entities ⇾ Devices. ThingsBoard automatically provisions a new device named Sigfox-<device ID> (e.g. Sigfox-1CB0F1) on the first uplink, provided Allow create devices or assets is enabled. Open the device and check:

• Latest telemetry — temperature, humidity, co2, and co2Baseline decoded by the script.
• Client attributes — sigfoxId, autoCalibration, zeroPointAdjusted, transmitPower, powerControl, and fwVersion set by the script.

Device Client attributes — set by the uplink converter on first contact Device Latest telemetry — decoded values from the test uplink

Expected result: the device appears in Entities ⇾ Devices within seconds of the uplink, with telemetry and attributes matching the values above.

To send messages from ThingsBoard back to a Sigfox device, create a downlink converter, assign it to the integration, and add an Integration Downlink node to the Root Rule Chain. For the full encoder reference, see Downlink data converter.

Data converters translate between ThingsBoard’s data model and the Sigfox message format. The uplink converter (configured above) decodes incoming device payloads into telemetry and attributes; the downlink converter does the reverse — it encodes an outgoing Rule Engine message into the hex payload and target device ID the Sigfox Backend expects, ready to be queued for delivery.

1. Go to Integrations center ⇾ Integrations and open the SigFox integration.
2. Click the pencil icon to enter edit mode.
3. In the Downlink data converter field, click Create new.
4. In the Add data converter dialog:
   • Enter a name for the converter, for example, SigFox Downlink Converter.
   • Use the default encoder script or replace it with your own implementation.
   • Click Add.
5. Click Apply changes to save the integration.

Open the SigFox integration — the Downlink data converter field is empty; click Toggle edit mode In edit mode, click Create new in the Downlink data converter field Enter the converter name, review the encoder script, and click Add SigFox Downlink Converter is now assigned — click Apply changes to save

The encoder function used in this tutorial:

// Encode downlink data from the incoming Rule Engine message.
// msg - JSON message payload, e.g. { "downlink": "0000780001900000" }
// msgType - message type, e.g. "ATTRIBUTES_UPDATED".
// metadata.cs_sigfoxId - Sigfox device ID stored on first uplink, e.g. "1CB0F1".

var deviceId = metadata.cs_sigfoxId;
var payload = msg.downlink;

if (deviceId == null) {
  raiseError("Sigfox device ID is missing (expected metadata.cs_sigfoxId).");
}

if (payload == null) {
  raiseError("Downlink payload is missing (expected msg.downlink).");
}

// Convert the payload to a string and restore omitted leading zeros.
payload = "" + payload;

while (payload.length() < 16) {
  payload = "0" + payload;
}

if (payload.length() > 16) {
  raiseError("Sigfox downlink payload must not exceed 16 hexadecimal characters.");
}

return {
  contentType: "TEXT",
  data: payload,
  metadata: {
    device: deviceId
  }
};

// Encode downlink data from the incoming Rule Engine message.
// msg - JSON message payload, e.g. { "downlink": "0000780001900000" }
// msgType - message type, e.g. "ATTRIBUTES_UPDATED".
// metadata.cs_sigfoxId - Sigfox device ID stored on first uplink, e.g. "1CB0F1".

var deviceId = metadata.cs_sigfoxId;
var payload = msg.downlink;

if (deviceId == null) {
  throw new Error("Sigfox device ID is missing (expected metadata.cs_sigfoxId).");
}

if (payload == null) {
  throw new Error("Downlink payload is missing (expected msg.downlink).");
}

// Convert the payload to a string and restore omitted leading zeros.
payload = String(payload);

while (payload.length < 16) {
  payload = "0" + payload;
}

if (payload.length > 16) {
  throw new Error("Sigfox downlink payload must not exceed 16 hexadecimal characters.");
}

return {
  contentType: "TEXT",
  data: payload,
  metadata: {
    device: deviceId
  }
};

To adapt this encoder to your use case:

• msg.downlink — replace with the Rule Engine message field that carries the value to send (for example, msg["base-key"] when the triggering shared attribute is named base-key).
• Leading-zero padding — the script left-pads payload with "0" up to 16 hex characters (8 bytes) before sending it. This guards against ThingsBoard coercing a purely numeric attribute value into a JSON number and silently dropping leading zeros (see Test Downlink). Remove this block only if your payload is never numeric-looking, or if you cast it to a string yourself upstream.
• Length check — the script rejects payloads longer than 16 hex characters with raiseError/throw, since the Sigfox network supports up to 8 bytes of downlink payload. Adjust the 16 limit if your device’s downlink protocol uses a shorter fixed length.
• contentType — use TEXT for a plain string, JSON for a JSON object, or BINARY for a base64-encoded binary payload.
• metadata.device — populated from metadata.cs_sigfoxId, which the Fetch sigfoxId node injects (see Configure the Root Rule Chain). Change this only if you route the target device ID through a different metadata key.

To trigger a downlink when an attribute changes (for example, a shared attribute update), add two nodes to the Root Rule Chain: an Originator attributes node (Enrichment category) that reads the device sigfoxId client attribute into message metadata, and an Integration Downlink node (Action category) that forwards the encoded message to the Sigfox integration.

1. Open Rule Chains ⇾ Root Rule Chain.
2. In the node panel, search for originator attributes. The node appears under the Enrichment category. Drag it onto the canvas.
3. Configure the node:
   • Name — Fetch sigfoxId.
   • Under Client attributes, add the key sigfoxId.
   • Set Add originator attributes to to Metadata.
   • Click Add.
4. In the node panel, search for integration downlink. The node appears under the Action category. Drag it onto the canvas.
5. Configure the node:
   • Name — Downlink to Sigfox.
   • Integration — select your Sigfox integration.
   • Click Add.
6. Connect the Message Type Switch node to the Fetch sigfoxId node using the Post attributes and Attributes Updated relations.
7. Connect the Fetch sigfoxId node to the Downlink to Sigfox node using the Success relation.
8. Click Apply changes.

Search for originator attributes in the node panel — it appears under Enrichment Name the node Fetch sigfoxId, add sigfoxId under Client attributes, set the target to Metadata, and click Add Name the node Downlink to Sigfox, select the SigFox integration, and click Add The finished wiring: Message Type Switch → Fetch sigfoxId → Downlink to Sigfox. Click Apply changes to save

Adding or updating a shared attribute triggers the Attributes Updated relation, which forwards the change through Fetch sigfoxId to Downlink to Sigfox. ThingsBoard encodes the value with the downlink converter and queues it for delivery — the Sigfox Backend receives it the next time the device transmits an uplink that requests a downlink (a flag the device firmware sets; ThingsBoard cannot trigger this on its own).

1. Go to Entities ⇾ Devices and open your device.
2. Open the Attributes tab and switch to Shared attributes.
3. Click +, enter a key (for example, downlink) and a string value (for example, 0000780001900000), then click Add.

Example: increased interval (every 120 minutes) for maximum savings. Intended for sensors in long-term archives or warehouses, where readings change slowly. Sending every 2 hours instead of the default 30 minutes lets the Airwits battery last as long as possible.

HEX code: 0000780001900000

Saving the attribute immediately logs an ATTRIBUTES_UPDATED downlink event on the integration — but this only means the payload was encoded and queued, not delivered. The SigFox Downlink Converter’s own Events tab stays empty at this point, since the converter only runs again once the Sigfox Backend actually requests the downlink.

Right after saving the attribute — only the ATTRIBUTES_UPDATED event exists so far Click … in the Message column — metadata.cs_sigfoxId was already injected by Fetch sigfoxId

The downlink is only handed to the Sigfox Backend in reply to an uplink that requests one. Wait for the device’s next such transmission, or trigger one immediately by resending the same test request from Send Test Uplink:

curl -v \
  -H "Content-Type: application/json" \
  -d '{"device":"1CB0F1","time":"1742481772","seqNumber":"512","data":"2502af2102462a","rssi":"-98.00","snr":"18.10"}' \
  "$HTTP_ENDPOINT_URL"

The response body now carries the queued downlink for the device:

{"1CB0F1":{"downlinkData":"0000780001900000"}}

Go to Integrations center ⇾ Integrations, open the SigFox integration, and click the Events tab again. Alongside the earlier ATTRIBUTES_UPDATED event, an Uplink / Downlink pair now appears from the resent request — all with Status: OK.

Go to Integrations center ⇾ Data converters, open the SigFox Downlink Converter, and click its Events tab — the row that was missing before now appears:

• In — the Rule Engine message and metadata, including metadata.cs_sigfoxId set by the Fetch sigfoxId node.
• Out — the encoded result: contentType, the data payload, and metadata.device.

The converter only logs an event once the queued downlink is actually delivered In — msg.downlink arrives as 780001900000 (leading zeros dropped), metadata.cs_sigfoxId is 1CB0F1 Out — the encoder restores the full 16-character payload before it reaches the Sigfox Backend

In the Sigfox Backend, open the device Messages tab to confirm the downlink was acknowledged, and check the device type Statistics tab to see it reflected on the message chart.

Sigfox Backend — device Messages tab confirming the downlink was acknowledged Sigfox Backend — device type Statistics tab showing uplink and downlink message traffic

• Integrations overview — integration events, debug, and Remote Integration setup.
• Uplink data converter — full decoder reference: input parameters, output fields, and scripting patterns.
• Downlink data converter — full encoder reference and testing.
• Remote Integration — run the integration as a standalone process outside the ThingsBoard server.
• Rule Engine — how uplink messages are processed after the converter.
• TBEL — the recommended converter scripting language.