Cease configuring MQTT brokers. Cease fidgeting with uplink and downlink toggles. Cease relying on a public server with a zero-hop coverage that hardly works. The Flaresat Relay Bridge offers you reside, bidirectional sync between your off-grid mesh and anybody on-line, in about 20 seconds.
The MQTT Drawback

In the event you’ve tried to bridge your Meshtastic mesh to the web, you already know the trail. Allow the MQTT module, configure uplink and downlink per channel, level every part at a dealer, and hope it holds collectively.
Meshtastic does help this, and it is gotten higher over time. Firmware 2.3.2 added MQTT Shopper Proxy mode, which lets your radio tunnel by means of your cellphone’s web connection as a substitute of needing Wi-Fi on the system itself. That was an actual enchancment, nRF52 nodes, and something with out built-in Wi-Fi can now use MQTT by means of your cellphone.
However the core issues did not go away.
The general public dealer has a zero-hop coverage. Any information injected again from the web does not propagate additional than the immediately related gateway node. When you’ve got a multi-hop mesh and also you need distant information to really unfold throughout it, the general public dealer will not do it. Immediately related nodes get it. Everybody else does not.
The general public dealer is shared infrastructure. Your group’s positions and messages cross by means of a community-maintained server below Meshtastic’s information dealing with. It is not yours, it is not non-public, and it is rate-limited to guard the broader community.
A non-public dealer means infrastructure you personal and keep. Mosquitto on a VPS, TLS certificates, port forwarding, dealer authentication, uptime accountability. If you’d like actual privateness and dependable throughput, that is the trail. It is doable, however you are now working a server to relay mesh packets.
Uplink and downlink are configured per channel and straightforward to overlook. That is the commonest failure mode. All the pieces seems configured. Nothing flows. As a result of somebody forgot to toggle uplink on the first channel, or toggled it and did not faucet save, or saved however did not push to the radio. Zero-feedback failure.
This is what the total MQTT setup truly seems like:
- Open the Meshtastic app → Settings → MQTT
- Toggle MQTT Enabled
- Toggle Proxy to Shopper Enabled (if utilizing your cellphone’s connection as a substitute of system Wi-Fi)
- Set dealer deal with, username, password
- Go to every channel you need bridged → allow Uplink and Downlink → save → push to radio
- Confirm the dealer is receiving packets (mosquitto_sub, MQTT Explorer, or comparable)
- Determine what to do with uncooked ServiceEnvelope protobufs on the opposite finish
For House Assistant dashboards, Node-RED automations, or customized integrations that eat uncooked mesh information, that is precisely the appropriate software. The format is documented, the Python library is strong, and the developer ecosystem round it’s good.
For subject coordination the place you simply want your distant teammate to see a dwell map, it is a variety of stack for the end result.
What the Relay Bridge Does As an alternative

Flaresat’s off-grid mode already makes use of your Meshtastic radio as a transport layer for a dwell group map. Pins, routes, areas, chat, every part syncs over LoRa to each member of the group. No web, no servers. If you have not learn how the off-grid side works, begin there first.
The Relay Bridge is the characteristic that connects that off-grid group to a cloud group, in each instructions, dwell.
One individual in your group has cell sign or Wi-Fi. Possibly they’re on the automobile. Possibly they’re on the trailhead. Possibly they’re the final individual with a bar of LTE earlier than everybody else drops right into a canyon. That individual runs the bridge. All the pieces the mesh does exhibits up within the linked cloud group. All the pieces added to the cloud group transmits over LoRa to the sphere group.
| Path | What syncs |
|---|---|
| Mesh → Cloud | Pins, routes, areas, messages from off-grid gadgets seem dwell within the cloud group |
| Cloud → Mesh | Cloud pins, routes, areas, messages transmit over LoRa to all off-grid gadgets |
Type modifications, edits, and deletions sync each methods. Voice notes are the one exception, these do not relay.
The bridge system is the cellphone that individual already has. Related over Bluetooth to the radio. Related over cell or WiFi to the web. When protection drops, sync pauses. When it comes again, it resumes mechanically.
Setting Up the Relay Bridge

This assumes you have already got an off-grid group and a cloud group arrange in Flaresat. In the event you do not, the Flaresat getting started guide covers that in about 2 minutes.
- Open your off-grid group on the system that has connectivity, the individual on the automobile, the trailhead, wherever sign exists.
- Faucet the Menu icon within the backside proper, go to Settings, scroll to the Cloud Relay part.
- Choose the cloud group you wish to hyperlink. Your present cloud teams are listed. Faucet the one you need and make sure. It is advisable to already be a member of it.
- Relay is dwell. From this level, the off-grid mesh and the cloud group are synced in actual time.
To cease it: Group Settings → Unlink Cloud Group → affirm. Unlinking does not delete something that already synced, it simply stops the dwell connection.
One essential factor: a number of folks can run the bridge on the similar time. If three folks in your group have sign and all three have relay lively, there are not any duplicates and no loops. Flaresat makes use of deterministic ID derivation, each bridge system generates the identical mesh ID for a similar cloud merchandise, so the mesh deduplicates on the community layer. Cloud-originated packets are tagged to forestall re-relay. Extra bridge gadgets means extra redundancy. Do not overthink it.
Why This Is Completely different
| Meshtastic MQTT | Flaresat Relay Bridge | |
|---|---|---|
| Dealer required | Sure (public or self-hosted) | No |
| Works on nRF52 | Sure (through Shopper Proxy) | Sure |
| Wi-Fi on system wanted | Just for gateway mode | No |
| Zero-hop limitation | Sure (public dealer) | No |
| Per-channel config | Uplink + downlink per channel | Choose channel as soon as in group settings |
| Multi-bridge redundancy | Handbook coordination wanted | Constructed-in, automated |
| What you see on the opposite finish | Uncooked protobufs / MQTT subjects | Reside map in a browser |
| Setup time | 15–30 min (first time) | ~20 seconds |
No zero-hop limitation. The bridge system is a full mesh participant. Information from the cloud enters the mesh at that system and propagates usually. It is not injected through a dealer with hop restrictions baked in.
Works on any {hardware}. The bridge functionality lives within the Flaresat app, not the radio firmware. ESP32, nRF52, something, does not matter. No Wi-Fi on the system wanted.
The vacation spot is already constructed. Your distant teammate opens app.flaresat.com in a browser, opens the cloud group, and sees the dwell map. That is it. No MQTT shopper to arrange on their finish. No protobuf decoding. No further tooling.
MQTT is genuinely the appropriate alternative if you happen to’re constructing developer integrations, House Assistant, Node-RED, customized telemetry pipelines. The ecosystem is strong, the format is documented, and nothing else comes shut for that use case. Preserve utilizing it.
However subject coordination is not a developer integration drawback. It is a folks drawback. Your group must know the place one another are, share a route, drop a pin on a hazard, and do it with out an IT undertaking standing between them and the map.
The Relay Bridge does not exchange your infrastructure, it means you do not want any. One individual with sign. One setting within the app. Everybody else within the subject will get a dwell, synced map the second it is lively, and your distant teammate sees the identical image from a browser tab anyplace on the earth.
Download on iOS · Download on Android · Open the Web App · Relay Bridge Docs
