Send Data to Azure IoT Hub with a Device Certificate

review the following guide for setting up an outbound data integration between litmus edge and azure iot hub using a device certificate additional resources refer to the following resources for more information https //docs microsoft com/en us/azure/iot hub/iot hub devguide messaging?wt mc id=portal microsoft azure iothub#message format https //docs microsoft com/en us/azure/iot hub/iot hub mqtt support#sending device to cloud messages https //docs microsoft com/en us/azure/iot hub/iot hub mqtt support#using the mqtt protocol directly as a module before you begin you must first docid\ hjbklrq2humk ah21aex3 when you add the iot device to the hub, select x 509 self signed as the authentication type when you add the iot device in azure step 1 add a device follow the steps to docid 3eyafppweuvmblcey17sq the device will be used to store tags that will be eventually used to create outbound topics in the connector make sure to select the enable data store checkbox step 2 add tags after connecting the device in litmus edge, you can docid 8se7z3pmrfwl1nmzcwalx to the device create tags that you want to use to create outbound topics for the connector step 3 add the azure iot hub using device certificates connector follow the steps to docid\ b7emdh8ao2 noqdhwpd7y and select the mqtt azure iot hub using device certificates provider define the following parameters name enter a name for the connector hostname the ip address or server fqdn of the mqtt broker (must be reachable from your edge device) port 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 certificate copy the certificate from the mydevicekeycer pem file and paste it here for litmus edge version 3 11 0 and later, you have the option to upload a file private key copy the key from the myprivatekey pem file 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 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 4 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 5hctorlhgax3ikh lvi0a and relevant error messages step 5 create outbound topics for connector you will now need to create topics from the tags you added in step 2 before creating the topics copy the raw topic parameter for all tags you want to use for topics see docid\ g9roompc3xz4zq6cbnonc for more information 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 5hctorlhgax3ikh lvi0a for more information data direction select local to remote outbound local data topic paste the raw topic for the tag created in step 2 remote data topic enter integration raw\ outboundtest 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 6 view outbound messages you can create a flow in litmus edge to view the outbound messages of the connector to view outbound messages follow the steps to docid 7x0n7c4dxswtd61vpibza 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 7x0n7c4dxswtd61vpibza to learn more click done , and then click deploy check the debug messages tab see the additional options section in docid\ qqnwjdagecrdg0jtivulu for more details verify that outbound messages are displaying