Azure IoT Device lifecycle events Part 2: modules

In my previous blog post, I showed how to use the Azure IoT device lifecycle events.

These events are emitted by the Azure IoT Hub as routing events next to the regular incoming device-to-cloud messages. Routing these device lifecycle events makes it possible for both persisting and reacting at the behavior of devices (creation, deletion, connected, disconnected) and registration changes (device identity twin changes).

This was first demonstrated using a regular direct internet-connected device.

But what about Azure IoT modules?

Advertentie

Adding an array to your ModuleTwin desired properties

The IoT Modules can be modified using the Azure portal. Microsoft provides two methods to change modules ‘over the air’:

1. Module Identity Twin
2. Direct Method

Direct methods have a name, payload, and configurable connection and method timeouts. Direct methods represent a request-reply interaction with a module.

The Module Identity twin is simply a JSON document which contains information about the module: tags, desired properties, and reported properties.

In this article, we focus on the Module twin and especially the desired properties.

Most examples show how to pass a simple value (like an integer value or a string).

But what if we want to pass an array?