MQTT: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
MQTT is a ''really'' simple protocol that connected devices can use to publish and receive messages. Messages have a topic and may contain an arbitrary payload. Devices never talk to each other directly. A MQTT brokers receives published messages and distributes them to subscribers by matching message topics with subscribed-to topics. | MQTT is a ''really'' simple protocol that connected devices can use to publish and receive messages. Messages have a topic and may contain an arbitrary payload. Devices never talk to each other directly. A MQTT brokers receives published messages and distributes them to subscribers by matching message topics with subscribed-to topics. | ||
* finite state machine of the protocol | |||
* most simple application (QoS 0) | |||
* encoding and decoding | |||
* more sophistication (QoS 1, 2), limits of the Arduino environment (like, conversational state) | |||
[[IoT with AME|Home]] | [[IoT with AME|Home]] | ||
Revision as of 11:41, 3 July 2017
MQTT
MQTT is a really simple protocol that connected devices can use to publish and receive messages. Messages have a topic and may contain an arbitrary payload. Devices never talk to each other directly. A MQTT brokers receives published messages and distributes them to subscribers by matching message topics with subscribed-to topics.
- finite state machine of the protocol
- most simple application (QoS 0)
- encoding and decoding
- more sophistication (QoS 1, 2), limits of the Arduino environment (like, conversational state)