Difference between revisions of "Public MQTT Brokers"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
https://www.opensourceforu.com/2020/10/cloud-based-implementation-of-iot-using-mqtt-brokers/ | https://www.opensourceforu.com/2020/10/cloud-based-implementation-of-iot-using-mqtt-brokers/ | ||
When using public brokers, it is advised to consider encrypting traffic as standard. Both topics and payloads can be encrypted, with Node-RED providing nodes for such operations. Only devices that have the encryption key can find (subscribe) and make sense of the data. | |||
== Public MQTT Brokers == | == Public MQTT Brokers == | ||
Revision as of 11:03, 2 June 2022
Cloud Based Implementation of IoT Using MQTT Brokers
This is a useful article that sums up the various MQTT options.
https://www.opensourceforu.com/2020/10/cloud-based-implementation-of-iot-using-mqtt-brokers/
When using public brokers, it is advised to consider encrypting traffic as standard. Both topics and payloads can be encrypted, with Node-RED providing nodes for such operations. Only devices that have the encryption key can find (subscribe) and make sense of the data.
Public MQTT Brokers
| Name | Broker Address | TCP Port | TLS Port | WebSocket Port | Message Retention | Persistent Session | Sign Up Requred | Link |
|---|---|---|---|---|---|---|---|---|
| Eclipse | mqtt.eclipse.org | 1883 | N/A | 80, 443 | YES | YES | NO | http://iot.eclipse.org/sandbox.html |
| Mosquitto | test.mosquitto.org | 1883 | 8883, 8884 | 80 | YES | YES | NO | https://test.mosquitto.org/ |
| HiveMQ | broker.hivemq.com | 1883 | N/A | 8000 | YES | YES | NO | https://www.hivemq.com/try-out/ |
| Flespi | mqtt.flespi.io | 1883 | 8883 | 80, 443 | YES | YES | YES | https://flespi.com/mqtt-broker |
| Dioty | mqtt.dioty.co | 1883 | 8883 | 8080, 8880 | YES | YES | YES | http://www.dioty.co/ |
| Fluux | mqtt.fluux.io | 1883 | 8883 | N/A | N/A | N/A | NO | https://fluux.io/ |
| EMQX | broker.emqx.io | 1883 | 8883 | 8083 | YES | YES | NO | https://emqx.io/ |