Machine to machine communication with IoT Edge and HiveMQ

Machine to machine communication(M2M) considers two or more machines communicating with each other.
This communication can involve exchanging data, sending commands in order to regulate sensors, raise alarms, start/stop processes, etc., without human interaction.
Some of the protocols that are widely used in M2M communication are MQTT, OPC-UA, CoAP, LWM2M, etc.


In scenarios where devices/machines need to exchange data over MQTT broker, Azure IoT Edge can be useful for managing broker and other container deployments(subscribers, data processors, etc) over the cloud. Another role of IoT Edge in these scenarios is to enable a secure connection to the cloud and to send the telemetry to the cloud.
As a broker, HiveMQ broker is used, which is 100% compliant with MQTT standard(including MQTT 5.0), and makes it a perfect option for M2M communication, especially in cases where machines require specific MQTT features.
More about HiveMQ can be found here.
Following example is composed out of the following components:
– Publisher Machine, that sends the telemetry, temperature and humidity
– Subscriber Machine(also can act as a publisher if required), that subscribes to the telemetry topic and reacts on the sensor data from Publisher Machine
– IoT Edge as a module(container) deployment orchestrator and cloud communication gateway
– HiveMQ module(container) as MQTT broker
– Subscriber module, processes telemetry data, before sending to the cloud


Architecture of the sample

The architecture of the sample

As a publisher machine, MessageSender was used. This is a UWP application that can send messages to various targets, including the MQTT broker. Any other MQTT client can be used for this purpose.
Subscriber, in this case, is a simple Java application that leverages the HiveMQ library for MQTT brokers.
Following code demonstrates how the topic listener can be implemented with HiveMQ library in Java:


The core part of IoT Edge deployment is the manifest file that describes the deployment. HiveMQ can be found on the DockerHub, and the following configuration is an example of how to pull the HiveMQ docker image and start it via IoT Edge deployment.


HiveMQ needs to bind 1883 port for MQTT and 8080 for the broker dashboard.
The full code sample with ‘how to run’ instructions can be found on GitHub.
In order to make the sample working, it is required that the publisher and subscriber machines add additional ‘hosts’ configuration:

After running the sample and sending the message from the publisher, the subscriber machine console should show that the message came through the HiveMQ broker deployed on Azure IoT Edge.

Simulation of the Publisher machine


The subscriber machine console output after sending the message from the publisher

Finally, the Subscriber Module makes sure that the message ends up on the output, that is passed to the Azure IoT Hub via Routes in Azure IoT Edge Deployment manifest.



– HiveMQ documentation:
– IoT Edge documentation:

3 Comments on “Machine to machine communication with IoT Edge and HiveMQ”

  1. Hi, how to connect real device to HiveMQ?
    what is the script code for connect a real device to HiveMQ?
    it is possible to integrate HiveMQ with azure Iot Hub as a broker!

    I read some articles here and it seems response to what i want, but i dont know how to start? specialy i want for real device to device communication

  2. Hello,

    Thanks for the question!
    It is possible in a way as presented in the blog. Essentially, the idea is to install/deploy the broker to the Edge(Azure IoT Edge) and have device to device communication implemented over the HiveMQ broker. Regarding the device-to-cloud communication, the idea would be to leverage the IoT Edge Runtime with potentially a custom module that can filter/enrich the messages coming from devices before pushing to the cloud(IoT Hub).

    Please refer to github link below to find the example of IoT Edge Solution with custom module that is subscribed to specific MQTT broker topic and that forwards the messages to IoT Hub.

    Regarding HiveMQ, since it is a broker that fully implements MQTT you can use any MQTT client to send/subscribe to the topic. In the mentioned repository you can find a Java sample for a subscriber.

  3. Thank you for the answer
    who i can deploy the broker in iot Edge ? there is a documentation for that ? ( step by step )
    the devices they will be connected to iot hub or to HiveMQ ?
    i want to take this solution but i dont know how to begin ! thank you for your answers !

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.