Project:MQTT Broker: Difference between revisions
NitramLegov (talk | contribs) m (just some rewording and formatting) |
NitramLegov (talk | contribs) (Added the FlipDot Topics) |
||
| Line 31: | Line 31: | ||
The following projects use - or will use - the MQTT Broker: | The following projects use - or will use - the MQTT Broker: | ||
* [[Project:Flip Dot Display]] | |||
* [[Project: Enhanced Door Bell]] | * [[Project: Enhanced Door Bell]] | ||
| Line 36: | Line 37: | ||
If you create a new topic, it would be great if you document it here. <br> | If you create a new topic, it would be great if you document it here. <br> | ||
Right now, the following topics exist:<br> | Right now, the following topics exist:<br> | ||
--- | {|class="wikitable" | ||
!Topic !! Description | |||
|- | |||
|/CommonRoom/FDD/Text || Send text to the FlipDot Display. It will be displayed immediately. | |||
|- | |||
|/CommonRoom/FDD/Binary || not implemented yet. Will be used to send binary data directly to the FlipDot Displays. Please note that it will be the senders responsibility to send meaningful data. Anything else will lead to rubbish being displayed. | |||
|- | |||
|} | |||
[[Category:Raspberry Pi]] | [[Category:Raspberry Pi]] | ||
Revision as of 13:56, 17 August 2018
| ProjectInfoBox MQTT Broker | |
|---|---|
| |
| Status: | done |
| Release Date: | July 2018 |
| Initiator: | Martin |
| Team: | Martin who else would like to help? |
| Tools Used: | Raspberry Pi |
| Software Used: | MQTTBroker |
MQTT Overall
MQTT (Message Queue Telemetry Transport) is a communication protocol with a strong focus on a small data footprint.
Therefore, it is perfect for communication between lightweight devices (such as microcontrollers like the ESP8266). MQTT generally runs on TCP/IP, but there is also an extension (MQTT-SN), which can be used on non-TCP networks. Further information can of course be found on Wikipedia, mqtt.org or - if you require German information - Informatik-Aktuell published a nice introduction article.
Broker
Since MQTT follows a client/server architecture, a central server is needed in order to publish messages and to subscribe to messages. This server is called broker. Since MQTT is an open protocol, multiple implementations exist, which have been compared on GitHub.
Client usage
As mentioned, MQTT is designed to run on a broad variety of devices. As of this, implementations exist for microcontrollers, regular PCs as well as smartphones.
If you want to integrate MQTT in your project, please check the selection of client libraries on GitHub.
For anything using the Arduino IDE, please also see the library provided by adafruit AdafruitMQTT.
If you want to learn more about topics, messages, subscriptions and QoS, please read this part of the mosquitto documentation.
If you want to "just use" MQTT on your device and check the messages in our network, please see this article.
MQTT in the CoMakingSpace
In order to be able to use MQTT in the CoMakingSpace, the Raspberry Pi in the common room runs an instance of mosquitto, which is an open source MQTT broker.
Our implementation runs on the same Raspberry Pi in the common room that also hosts Project:Music Station. Therefore, the hostname is comakingcontroller (having a fixed IP: 192.168.1.2). It offers its services on the standard MQTT port: 1883.
The following projects use - or will use - the MQTT Broker:
Topics
If you create a new topic, it would be great if you document it here.
Right now, the following topics exist:
| Topic | Description |
|---|---|
| /CommonRoom/FDD/Text | Send text to the FlipDot Display. It will be displayed immediately. |
| /CommonRoom/FDD/Binary | not implemented yet. Will be used to send binary data directly to the FlipDot Displays. Please note that it will be the senders responsibility to send meaningful data. Anything else will lead to rubbish being displayed. |
