https://github.com/sandervandevelde/nonsdkazureiotclient

Demonstration of an Azure IoT Device Client based on MQTT only, without Azure IoT Device SDK
https://github.com/sandervandevelde/nonsdkazureiotclient

azure iot mqtt non-sdk

Last synced: about 2 months ago
JSON representation

Demonstration of an Azure IoT Device Client based on MQTT only, without Azure IoT Device SDK

• Host: GitHub
• URL: https://github.com/sandervandevelde/nonsdkazureiotclient
• Owner: sandervandevelde
• License: mit
• Created: 2022-08-09T10:33:39.000Z (over 2 years ago)
• Default Branch: master
• Last Pushed: 2022-08-11T22:29:01.000Z (over 2 years ago)
• Last Synced: 2023-03-12T07:56:45.621Z (almost 2 years ago)
• Topics: azure, iot, mqtt, non-sdk
• Language: C#
• Homepage:
• Size: 28.3 KB
• Stars: 4
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: readme.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Demonstration of Azure IoT Hub access without SDK

## Disclaimer

This repo is just a demonstration regarding the logic needed to communicate against the (limited) MQTT broker capabilities of the Azure IoT Hub.

This demonstration is not feature complete or production ready.

I personally recommend to use the Azure IoT Device SDKs if possible. 

These are production ready, production tested by many users and devices are resilient against many issues that can occur in the lifetime of an IoT device.

## Deprecated Baltimore certificate? 

This example still shows the use of the now deprecated Baltimore TLS certificate.

Please check [this post](https://sandervandevelde.wordpress.com/2023/01/25/does-your-azure-iot-edge-ubuntu-device-survive-the-baltimore-certificate-migration/) regarding the TLS certificate replacement. 

## Credits

This repo is inspired by this [blog post](https://www.petecodes.co.uk/connecting-a-raspberry-pi-pico-w-to-microsoft-azure-iot-hub-using-micropython-and-mqtt/) written by my friend Pete Gallagher @pete_codes.

## Demonstrated logic

The following logic is demonstrated

- Connecting the device to the MQTT broker as part of the IoT Hub

- Sending device messages

- Sending user properties alongside of device messages

- Receiving Direct Methods as event, and responding to it

- Receiving cloud messages as event

- Getting cloud messages on startup, being sent while the device was offline

- Receiving user properties alongside cloud messages

- Receiving desired properties as event

- Reading desired properties at the start of the application

- Sending Reported properties

## Missing logic

The following logic is missing:

- Supporting another certificate while the baltimore certificate is deprecated soon

- Creating the SAS token on the device itself so it can be refresh once the current one expires

- No error handling

## Links

### Docs

https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support

### Samples

https://github.com/Azure-Samples/IoTMQTTSample/tree/master/src