Azure IoT Edge
Click Azure IoT Edge. You can enable/ disable the Azure IoT Edge. You can enroll the device via manual setting or DPS (Device Provisioning Service).
Note that you will need to register an Azure account to manage the Azure IoT Edge service for your IoT application.
To create Azure IoT Edge connectivity manually, following the steps below:
- Enable Azure IoT Edge.
- Select Manual.
- Enter Device Connection String (copied from Azure IoT Hub).
- Click SUBMIT.
To create Azure IoT Edge connectivity via DPS, following the steps below:
- Enable Azure IoT Edge.
- Select DPS.
- Select TPM, Symmetric encryption, or X.509 certificate (depends on what your device registered in Azure IoT Hub; TPM attestation is only available for the devices built-in TPM module).
- Fill Registration ID and Endorsement Key in Azure IoT Hub Device Provisioning Service
- Enter Registration ID and Symmetric Key for Symmetric encryption or
- Upload X.509 Certificate and Private Key for X.509
- Click SUBMIT
More information about Azure DPS configuration in Azure IoT Hub, pleaser refer to Set up a DPS.
If you want to check Azure IoT Edge configurations and connectivities for commonly issues, click Azure IoT Edge > AIE Checks and click CHECK. ThingsPro Edge checks the configurations and provides a result. More information about AIE Checks: https://github.com/Azure/iotedge/blob/master/doc/troubleshoot-checks.md
We recommend fixing the edgeAgent and edgeHub modules to version
1.1.4
from the Azure IoT Hub when using Azure IoT Edge on ThingsPro Edge 2.2.1.
If there is an unexpected situation occured when you upgraded/ downgraded to a certain version of Azure IoT Edge, you can restore Azure IoT Edge by clicking RESTORE in the Provisioning Settings. The existing settings including Message Group, Store and Forward, Device Management, Downstream/ Upstream credentials will be removed.
Note that if you want to restore Azure IoT Edge to the default version from the version 1.2.x or above, you need to remove Azure IoT Edge manually by the commands below.
$ sudo apt-get remove aziot-edge --purge
$ dpkg -P aziot-identity-service
Telemetry Message
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:
- In the CLOUD CONNECTIVITY section, select a cloud service provider.
- Click on the Telemetry Message tab.
- Specify an Output Topic name.
- Enter the Polling Interval in seconds.
- Setup a threshold by file size (bytes) or time interval (seconds).
- Click NEXT.
7. Select tags from provides (e.g., Modbus Master).
8. (Optional) Enable custom payload by using the jq filter.
9. Click NEXT.
10. (Optional) Enter Property Key and Value.
11. Click SUBMIT.
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 (https://stedolan.github.io/jq/manual/).
Device Management
Enabling this feature allows cloud service providers manage IoT devices remotely throughout Device Twin and Direct Method technology.
Downstream Certificate
To prevent your device from connecting to potentially malicious gateways (Azure IoT Edge inside), you can upload an X.509 certificate, Private Key and Trusted CA Certificate. These certificates can be generated via ThingsPro Edge in addition to your private certificate. More information about Downastream Certificate.
Last updated on 2022-02-16 by alfredli