Export Configs

  • Published on Jun 13, 2025
  • 1 minute(s) read
Prev Next

This page will explain what Export Configs.

Export Config is the configuration that the user makes to direct to which platform the sensor data is going. (e.g., via MQTT, HTTP).

An Export Config can be attached to a Device Group, where all the devices within that group will use the same Export Config for data export.

Export Type parameter defines the protocol used to deliver data to the configured integration endpoint. It determines the transport technology for the Export Config.

We have the following options:

  • MQTT

  • HTTP Push

  • AWS IOT Core

  • Azure HTTP Event

  • Google Pub / Sub

  • Azure IoT Central

To better understand each options, please refer to the following page <export type page>

Export format selection is to select which payload format the user wants to send. To understand the export format, the user can refer to this page <Export Format>

These four options determine the accessibility of the export config:

  • Active on customer = This export config will be active (used) for all the customer’s devices.

  • Active on sub-customer = The export config will be active (used) by default for all the sub-customers’ devices underneath the current customer.

  • Visible to sub-customer = The export config will be visible to all the sub-customers underneath the current customer.

  • Available to the  sub-customer = The export config will be available (usable) for all the sub-customers underneath the current customer. Sub-customer will be able to activate this export config on their device group or use it in the export config group.

The next parameter is Message formats, which indicates what type of message the user wants to forward.