Skip to main content
Version: 2.3.x

Azure IoT Edge

Go to Cloud Connectivity > Azure IoT Edge to configure the Azure IoT Edge settings. You can enable/disable the Azure IoT Edge service and enroll the device via manual setting or DPS (Device Provisioning Service) here.

Note: A registered Azure account is needed to manage the Azure IoT Edge service for your IoT application.

To manually create an Azure IoT Edge connection for your device, do the following:

  1. Enable the Azure IoT Edge service and click on img.

  2. Select Manual.

  3. Enter the Device Connection String.

    Copy and paste the string from the Azure IoT Hub.

  4. Click SUBMIT.

img

img

To create an Azure IoT Edge connection for your device via DPS, do the following:

  1. Enable the Azure IoT Edge service and click on img.
  2. Select DPS.
  3. Select TPM, Symmetric encryption, or X.509 certificate Select an option based on your device registered with the Azure IoT Hub.

    Note: TPM attestation is only available for devices with a built-in TPM module.

  4. For the Azure IoT Hub device provisioning service and Symmetric encryption. enter the Registration ID and Endorsement Key.
  5. For X.509, upload the X.509 Certificate and Private Key.
  6. Click SUBMIT.

img

More information about the Azure DPS configuration in the Azure IoT Hub, is available at Set up a DPS.

If you want to check the Azure IoT Edge configuration and connectivity for common issues, go to Azure IoT Edge > AIE Checks and click CHECK. ThingsPro Edge provides a result after checking for issues. For additional informatin on AIE Checks, see https://github.com/Azure/iotedge/blob/master/doc/troubleshoot-checks.md

We recommend fixing the edgeAgent and edgeHub modules to version 1.2.7 from the Azure IoT Hub when using Azure IoT Edge on ThingsPro Edge 2.3.0.

If an unexpected situation occurs when you upgrade/downgrade to a certain version of Azure IoT Edge, you can restore Azure IoT Edge by clicking RESTORE in the Provisioning Settings. Using the restore function will remove existing settings including Message Group, Store and Forward, Device Management, and Downstream/Upstream credentials.

Telemetry Message Settings​

The simplest message type for sending IoT device data to your IIoT applications is a telemetry message. To create a telemetry message, do the following:

Note: You will need to install the ThingsPro Agent to send telemetry messages. For additonal information, see ThingsProAgent

To configure the telemety message settings, do the following:

  1. Go to Cloud Connectivity > Azure IoT Edge and click on the Telemetry Message tab.
  2. Enable the Telemetry message service.
  3. Specify an Output Topic name.
  4. Enter the Polling Interval in seconds.
  5. Setup a threshold by file size (bytes) or time interval (seconds).
  6. Click NEXT.

img

  1. Select device tags from providers (e.g., Modbus Master).
  2. (optional) Enable custom payload by using the jq filter.
  3. Click NEXT.
  4. (optional) Enter Property Key and Value.
  5. Click SUBMIT.

img

img

The Device-to-Cloud (D2C) message policy allows you to transform default payload to your desired payload schema via the jq filter. For additional information, refer to the jq website at (https://stedolan.github.io/jq/manual/).

Note that if you cannot receive D2C messages, be sure that a default route of the modules is added. You can add routes in Azure IoT Hub. Log in your IoT Hub > IoT Edge > choose a device > Set modules > Routes. img

Device Management Settings​

Go to Cloud Connectivity > Azure IoT Edge and click on the Device Management tab. Enabling this feature allows cloud service providers to manage IoT devices remotely using Device Twin and Direct Method technologies.

Downstream Certificate​

To prevent your device from connecting to potentially malicious gateways (Azure IoT Edge inside), you can upload X.509 certificate, Private Key, or Trusted CA Certificate. You can generate the certificates and the private key using ThingsPro Edge. For additional information, see Downastream Certificate.

img

Known Issues​

  • Azure/iotedge/issues/5773: Verify the EdgeDeviceHostName parameter value matches the config.toml hostname setting. If it doesn't match, the edgeHub container was running when you modified and applied the configuration. To update the EdgeDeviceHostName, remove the edgeAgent container. ```bash sudo docker rm -f edgeAgent ``` The edgeAgent and edgeHub containers are recreated and started within a few minutes. Once edgeHub container is running, inspect the container and verify the EdgeDeviceHostName parameter matches the configuration file. > Microsoft Documents

Last updated on 2022-08-18 by JamesCW Kao