Azure IoT Hub
The Azure IoT Hub integration enables Litmus Edge (LE) to connect to Azure IoT Hub services via SAS Key or Device Certificate over the MQTT protocol.
Supported communication
- Outbound (Publish data from Edge to Azure IoT Hub) - Yes
- Inbound (Subscribe data from Azure IoT Hub to Edge) - Yes
Configurations
Field | Details | Required |
|---|---|---|
Name | Connector name. | Yes |
Connection Type | Authentication method: SAS Key or Device Certificate. | Yes |
Hostname | DNS name of MQTT host. It can be found in the Overview tab of your Azure IoT Hub. | Yes |
Port | Port of MQTT host. | Yes |
Device ID | ID of the device as shown in your Azure IoT account. | Yes |
Certificate | PEM certificate used to authenticate the device when Connection Type is set to certificate. | No |
Private key | Private key for the device certificate, in PEM format. Must match the Certificate field above. | No |
SAS Key | Primary or secondary shared access key. | Yes |
Integration Topic | Azure IoT Hub MQTT topic for device-to-cloud messages. | Yes |
Throttling limit | Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost. | No |
Advanced configurations
Field | Details | Required |
|---|---|---|
Parallel Publish Count | Number of messages published in parallel. Higher values increase throughput and resource usage. | No |
Token TTL (minutes) | The token expiry time in minutes. | No |
LWT topic | MQTT topic the broker publishes the Last Will message to if this client disconnects unexpectedly. | No |
LWT payload | Message content published to the LWT topic on unexpected disconnection. Typically a status or alert string. | No |
LWT payload type | Encoding of the LWT payload: string for plain text, base64 for binary data. | No |
LWT QoS | QoS level for the Last Will message: 0 = at most once, 1 = at least once, 2 = exactly once. | No |
LWT retained | When enabled, the broker retains the Last Will message and immediately delivers it to any new subscriber on that topic. | No |
Persistent storage configurations
Field | Details | Required |
|---|---|---|
Persistent storage | If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages are retained and eventually sent when the connection is restored. | No |
Persistent storage size limit | Set the size limit for storing persisted data in GB. | No |
Queue mode | Select the sequence of data transfer: FIFO or LIFO. Selecting FIFO (First In First Out) sends the earliest message first. Selecting LIFO (Last In First Out) sends the latest message first. | No |
Related topics
- Azure IoT Hub Gen 2 Integration GuideAzure IoT Hub Gen 2 Integration Guide