MQTT
Also called MQ Telemetry Transport.
Publish and subscribe messaging designed for unreliable links and small devices. Nothing talks to anything directly: publishers send to a topic on a broker and subscribers ask the broker for topics they care about, which decouples every device from every other. The default plumbing of connected-device work, and increasingly of show integration glue.
Discovery, monitoring, configuration, backups, updates. Useful, and none of it has a deadline of its own.
What kills it. Nothing kills it. That is the problem: with no deadline it has no manners, and it will happily starve everything that does have one. Putting it on a show VLAN is the commonest self-inflicted wound in the industry.
Why this one, and not what the category suggests. A message broker. In a venue it carries telemetry and status far more often than anything with a deadline.
Ports
What goes wrong
What speaks MQTT (2)
| Product | Direction | Notes |
|---|---|---|
| Home Assistant Open Home Foundation |
bidirectional | First-class. |
| Node-RED OpenJS Foundation |
bidirectional | First-class, and the reason many people install it. |
Typical use
- Sensors, environmental monitoring and building systems reporting into a show or an installation.
- Glue between show control and things that were never designed to be on a show network.
- Status and telemetry from devices where a dropped message is survivable.
Sources
- MQTT — OASIS primary
Known gaps on this entry: implementations. If you can source one of them, that is a ten minute pull request.
Edit this entry on GitHub — one file, editable in your browser, and your handle goes on it permanently.
Work at OASIS? Confirm or correct this entry — it is free, it stays free, and nothing about it is for sale.