Use Azure IoT Hub without client libraries (MQTT)

This is the second last post of the series on IoT Communication which has gone on for slightly more than a month now. In this post, I endeavor to connect an IoT device to the Azure IoT Hub without using the provided IoT libraries.


To many, this is a matter of personal preference more than it is of functionality. The Azure IoT Hub is more of a gateway than anything else. It will connect to your IoT devices while your other applications (e.g. management web interface etc.) connect to it.

My reasons for choosing it:


As with many other Azure products, the documentation is ample on authentication schemes or procedures. If you use the client libraries provided by Microsoft, you do not need this step. Unfortunately, depending on the coding environment you have, using a prebuilt library may not work. For me, it kept failing numerously until I decided to do away with it.

Each device has a set of keys (a primary and a secondary one). To authenticate a device to the hub, an SAS (Shared Access Signature) token is required. This is normally done for us in the client libraries. So I used the C# client library to understand the process of generating SAS tokens for use with Azure IoT hub and then built a simple function to handle that on my pre-existing code. The SAS token forms the password used in the CONNECT packet for MQTT.

Generating the SAS Token

The steps for doing this may seem overwhelming at first but they really are not hard.

{SharedAccessSignature sr={aud}&sig={signed}&se={exp}&skn=

The CONNECT packet for MQTT

The other fields for authentication present in the CONNECT packet are ClientId and Username. As per the docs provided, the ClientId = deviceId and the Username has the format {iot-hub-host-name}/{device-id}

That is all that is required. Once it is working alright, the Azure IoT Hub will then work like any other MQTT broker. You should, however, make note of the MQTT topics used to send/receive telemetry to/from the IoT Hub.

I have only two files to do this sas_utils.c and url_encode.c. In them, the above steps are practically done.

These two files belong to the bigger group of changes in commit 70dce2a7 where there is specific code to communicate to the IoT Hub using MQTT. It is evident that the changes from the previous commit mainly relate to the authentication of the device.

Learning to live the best life I can

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store