Azure IoT supports cloud-to-device messaging with Direct Methods. This is an important tool when you want to control your devices real-time or if you want to execute logic on the device real-time.
In the past I have written about Direct Methods a couple of times. like this blog. I then wrote about IoT Edge supporting Direct Methods too. To be more specific, Modules in an IoT Edge support Direct Methods.
But my colleague Heindirk pointed me at a little gem unknown to me.
The same logic used to communicate from Azure cloud to a module can also be used to communicate from one module to another module without IoT Edge routes!
This makes several new IoT strategies possible!
Let’s check out this gem.
Doorgaan met het lezen van “Inter-module messaging without IoT Edge routing”
The Visual Studio 2017 Connected Service for Azure IoT Hub has received an update a couple of months ago.
This update had some visual updates and now supports a Singleton pattern for the Device client too.
But it also included support for both Device twins and Direct Methods. The latter feature looks a lot like the Commands method but there are some fundamental changes.
Yes, both solutions (Command and Direct Method) can execute code on a remote IoT Hub client. But the remote method just passes a message to the client. The Direct method can pass a message in a certain context. It calls a specific method (a client can have multiple methods registered) and passes the JSON parameter.
If you execute a Command, it feels like fire-and-forget. There is no descriptive response. But the caller of a Direct Method can wait until a response is accepted and a JSON value is returned.
Let’s check out Direct Methods.
Doorgaan met het lezen van “Direct methods support in the IoT Hub Connected Service”