MQTT Broker Bridging for Gatway networks

Suresh Thota 0 Reputation points

Hi ,

I am planning for the MQTT gateway bridging concept by using the Azure IOT.

End devices will acts a MQTT-client and communicate with the Gateway,

Gateway which acts as local mqtt broker (local server with bridge capabilities).

MQTT local broker tries to communicate with the Azure IOT MQTT broker (central server).

As a MQTT local broker with bridge capability will act as one resource to azure iot Hub (but internally it also have more connected clients let say 5 devices).

As per my understanding through azure IOT hub, only one resource can be accessed through one device.

If I create all the End devices as resources in the azure IoT hub, Can I access all these resources using single MQTT local broker which is having the bridge capabilities?

is there anyway I can handle this kind of network?



Azure IoT Hub
Azure IoT Hub
An Azure service that enables bidirectional communication between internet of things (IoT) devices and applications.
1,136 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Sander van de Velde 29,616 Reputation points MVP

    Hello @Suresh Thota,

    on May 23, there is a session at the Build event named "Build IoT solutions with MQTT in Azure Event Grid".

    Azure Event Grid is adding MQTT protocol support to enable one-to-many, many-to-one, and one-to-one communication between MQTT clients (IoT devices or cloud applications). Join this roundtable to provide your feedback on these proposed changes and tell us more about any challenges you face using Event Grid or the MQTT protocol.

    Please notice this will probably be made available as a public preview first so use it for testing purposes first.

    If you need a local MQTT broker as part of Azure IoT Edge, take a look at this post.

    If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.

    1 person found this answer helpful.
    0 comments No comments

  2. VasimTamboli 4,420 Reputation points

    you can achieve MQTT gateway bridging using Azure IoT Hub. Here's how you can handle this kind of network:

    Azure IoT Hub: Create an Azure IoT Hub instance, which will act as the central server for your MQTT network. This is where all the communication will be routed to and from.

    End Devices: Each end device acts as an MQTT client and communicates with the local MQTT broker (gateway). The local MQTT broker should be configured to handle incoming MQTT messages from the end devices.

    Local MQTT Broker: The local MQTT broker (gateway) serves as a bridge between the end devices and the Azure IoT Hub. It needs to be capable of bridging MQTT messages between the local network and the Azure IoT Hub.

    Bridge Configuration: Configure the local MQTT broker to establish a bridge connection with the Azure IoT Hub. This allows the local broker to forward MQTT messages to and receive messages from the Azure IoT Hub.

    Azure IoT Hub Device Provisioning: Provision each end device as a device in the Azure IoT Hub. This will allow you to manage and control the devices through the Azure IoT Hub.

    MQTT Bridge Connection: Configure the local MQTT broker to connect to the Azure IoT Hub using the MQTT protocol. This typically involves specifying the connection details such as the Azure IoT Hub hostname, port, and security credentials.

    Message Routing: Set up the message routing in Azure IoT Hub to handle incoming messages from the local MQTT broker. You can define routes based on message properties, device IDs, or other criteria to route the messages to the appropriate endpoints or processes within Azure.

    By following this approach, you can have a single MQTT local broker with bridge capabilities that can handle multiple end devices connected to it. Each end device is provisioned as a device in the Azure IoT Hub, allowing you to access and manage them through the Azure IoT Hub.

    Remember to consider security aspects, such as using secure connections (TLS/SSL) between the local MQTT broker and Azure IoT Hub, as well as proper authentication and authorization mechanisms for device communication.

    Additionally, keep in mind the scalability and performance considerations as your network grows, and consider any specific requirements or limitations of the MQTT broker you choose to use as the local broker.

    0 comments No comments