MeshCore MQTT Bridge
A robust bridge service that connects MeshCore devices to MQTT brokers, enabling seamless integration with IoT platforms and message processing systems.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
44/100 Fair
- Maintained
- 36last commit 369 days ago
- Popular
- 3447 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 83no serious findings, 2 minor, CI, tests
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 20 days ago
- GitHub stars
- 47
- Open issues
- 13
- Last commit
- 2025-11-16
- Latest release
- v0.1.1
- License
- GPL-3.0
- Activity
- stale
Checked today - source: GitHub (ipnet-mesh/meshcore-mqtt)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Send App Start before other radio commands When the MQTT bridge first connects to a MeshCore radio, it should send the App Start handshake (the command that tells the radio the app is ready) before any other commands. Without it, the radio will not send the self-info reply needed to finish connecting. source
- Save region changes with region save If you create regions (named areas used by MeshCore) in the CLI, run `region save` after your `region def` commands. If you skip this, the new layout is not written to storage and the old regions come back on restart. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Can the MeshCore MQTT bridge connect to a radio over serial, BLE, or TCP?
Yes, it is described as a companion app over Serial, BLE, and TCP.
Should the MeshCore-to-MQTT logging app run on a companion device?
The app is used on repeaters and room servers rather than companions. It logs packets for MeshCore Packet Analyzer and configured MQTT endpoints.
What handshake does the MQTT bridge need before sending other radio commands?
It should send App Start first. Without that command, the radio will not send the self-info reply needed to finish connecting.
Can the MQTT bridge uplink packets to more than one broker?
Yes, the observer MQTT bridge implementation lets MeshCore repeaters uplink packet data to multiple MQTT brokers. It assumes the device is flashed with observer MQTT firmware and has WiFi credentials and console access.
Answers sourced from forum.letsmesh.net, github.com, github.com, observer.gessaman.com
Community
- Homebridge embedded MQTT Broker : r/homebridge - Reddit (reddit)
- MeshCore Firmware with wifi, ntp, and packet logging to the MeshCore ... (forum)
- Updates to meshcoretomqtt - Apps & Firmware - LetsMesh Forum (forum)
Collected 49 days ago - public community threads