Broker Setup
This section uses Mosquitto — a free, open-source message broker software developed by IBM — as an example to describe how to quickly set up a Broker server for private deployment.
Mosquitto fully supports the MQTT 3.1.1 protocol used by devices. It is lightweight and stable, making it the recommended choice for the platform!
If you already have a configured Broker, you can skip this section as long as the Broker supports the MQTT 3.1.1 protocol.Preparation
The Broker service runs on a server. First, prepare a server that meets the following requirements:
| Requirement | Description |
|---|---|
| Hardware | For testing: CPU with 2 cores (2 threads) or higher, and RAM of 4GB or higher. For production environments, specifications depend on the number of devices. |
| System | Can be Windows or Linux. The choice depends on the operations staff's familiarity with the system and the requirements of the Broker software. |
| Network | Can be deployed in an internal or external network. Must have a fixed IP address and be interconnected with the wireless network that the device will connect to. |
| Availability | The device maintains a persistent connection with the Broker service. If the Broker service stops, remote control of the device will be unavailable. |
Broker Selection
There are many types of Broker software. When selecting one, consider the following factors:
| Number of Devices | Choose one that supports the current and expected number of devices. There is no need to unnecessarily pursue large-scale Broker software. |
| Operating System | Most Broker software is cross-platform. It is recommended to consult the operations staff for their input when making a selection. |
The selected Broker may support multiple protocols, but it must support the MQTT 3.1.1 protocol used by UNI IoT devices.
Related Resources
Project Homepage: Link