Receive Data from Azure IoT Hub with an SAS Key

5 min

review the following guide for setting up an inbound data integration between litmus edge and azure iot hub using an sas key before you begin you must first docid\ uaw77 if2eys0lmb xtx1 step 1 add the azure iot hub using sas key connector follow the steps to docid\ ytswgweu6h6oeunhj5hw3 and select the mqtt azure iot hub using sas key provider configure the following parameters name enter a name for the connector hostname enter the ip address or server fqdn of the mqtt broker (must be reachable from your edge device) port enter the mqtt broker's port number the default value is 8883 device id copy the device id of your edge device from the iot devices page in the azure portal and paste it here sas key copy the primary or secondary shared access key from the iot devices page in the azure portal and paste it here parallel publish count the maximum number of concurrently published messages the default value is 16 integration topic the default topic to publish or subscribe to devices/\[deviceid]/messages/events/ replace \[deviceid] with the device id copied from azure token ttl the token expiry time in minutes the default value is 1440 lwt topic the topic for mqtt's last will and testament feature lwt payload the payload for mqtt's last will and testament feature lwt payload type the payload type for mqtt's last will and testament feature the options are string and base64 lwt qos the quality of service value for mqtt's last will and testament feature lwt retained select this check box to retain the value for mqtt's last will and testament feature throttling limit the maximum number of messages per second to be processed the default value is zero, which means that there is no limit persistent storage when enabled, this will cause messages to undergo a store and forward procedure messages will be stored within litmus edge when cloud providers are online queue mode select the queue mode as lifo (last in first out) or fifo (first in first out) selecting lifo means that the last data entry is processed first, and selecting fifo means the first data entry is processed first step 2 enable the connector after adding the connector, click the toggle in the connector tile to enable it if you see a failed status, you can review the docid\ beqq0sszwsv9v9rif3rhk and relevant error messages step 3 create inbound topics for connector you will now need to create inbound topics that will receive data from azure iot hub to create topics click the connector tile the connector dashboard appears click the topics tab add topics to the connector with the details below see the add a topic to a connector section in docid\ beqq0sszwsv9v9rif3rhk for more information data direction select remote to local inbound local data topic paste the raw topic for the tag created in step 2 remote data topic replace devices/\[device id]/messages/events/ with devices/\[device id]/messages/devicebound/%24 to=%2fdevices%2fmessages%2fdevicebound replace \[device id] with the device id parameter configured for the connector enable click the toggle to enable the topic click yes to add the topic after adding all required topics, navigate to the integration pane from the connector tile, ensure the connector is not disabled and still shows a connected status step 4 initiate and view inbound messages you will need to create a flow to view the inbound messages from the connector to initiate and view inbound messages follow the steps to docid\ wh4zihwf0pwmryrbazbco and add the following nodes datahub subscribe debug connect the two nodes double click the datahub subscribe node the edit datahub subscribe node dialog box appears paste the local topic you created in step 4 if needed, configure the datahub subscribe connection see the "step 3 configure connector nodes" section in docid\ wh4zihwf0pwmryrbazbco to learn more click done , and then click deploy log in to azure open the device pane and click message to device the message to device pane appears enter test message in the message body field and click send message open the flow you created in litmus edge and check the debug messages tab see the additional options section in docid\ fd9bu5dd1nbv3xvy 0xxn for more details verify that test message appears in the debug results