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

Getting weather information and predictions from Azure Maps API

If you think about an Azure service named Azure Maps, what is the main purpose that comes into your mind?

That should be map tiles, of course. And that is ok. Azure maps has many features for representing spatial data in all kinds of interactive maps.

Still, Azure Maps has much more to offer. There are also multiple APIs you can use to make calls against like Mobility or Weather.

The information used to create weather maps like these are also available for you using REST API calls:

Let’s check out how we can consume this interface.

Visualize Azure IoT Edge device routes as a flowchart in Asp.Net MVC

If you look at the routes page in Azure IoT Edge configuration wizard, what do you prefer?

The current notation:

Or do you prefer a flow chart like this:

The routes in Azure IoT edge are a clever solution to describe how messages from one module are sent to another. But the JSON notation can become less readable once you add more (up to twenty) modules. That could end up eg. nineteen routes or more!

Just as an experiment I was thinking about how the ease the experience using a graphical interface.

I prefer the second solution, probably just like you.

So let’s look at how you can create the same experience with your routes of your IoT Edge device.