mqtt_client
- Software
- Middleware
- Tool
A ROS 2 component node that bridges ROS messages to and from an MQTT broker, so ROS and non-ROS devices or robots can exchange messages over MQTT.
Made by Institut für Kraftfahrzeuge, RWTH Aachen, ika, Germany (checked on github.com/ika-rwth-aachen (opens in a new tab)).
Source on GitHub: github.com/ika-rwth-aachen/mqtt_client (opens in a new tab). Facts read at commit 517fa53 (opens in a new tab).
Licenses
- Code
- MIT (opens in a new tab)
Read by Robotheca from LICENSE (opens in a new tab) (MIT) at commit 517fa53 (opens in a new tab), on 16 Oct 2026.
- Commercial use
- Yes
What it does
- Sends ROS messages of arbitrary types to an MQTT broker and publishes MQTT messages received from it as ROS messages.
- Exchanges primitive values and JSON-formatted messages with MQTT clients that do not run ROS.
- Can inject a timestamp into outgoing messages so the receiving side can measure transfer latency.
- Configured through a ROS parameter YAML file covering broker, TLS, client, and per-topic bridge settings.
- Can be installed from the ROS 2 package manager, built from source with colcon, or run as a Docker image.
- Includes a demo that sends ROS messages through a local Mosquitto broker to itself.
Written by Robotheca from the project's README (opens in a new tab) at commit 517fa53.
Getting started
- Difficulty
- Intermediate
- How to start
- The project's README (opens in a new tab)
Maintenance
- Status
- Active: a commit in the last 90 days
- Newest commit
- 22 Jul 2026 on main
- Latest release
- v2.5.0 (22 Jul 2026)
Checked on GitHub on 16 Oct 2026.
Links
Robots on Robotheca that use it
No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.
Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.