Meshtastic users propose APRS bridge for live GPS tracking

A GitHub issue opened on May 18 proposed a bridge that would take Meshtastic node GPS positions and publish them to APRS-IS, so they could show up on aprs.fi. For operators who already live in APRS maps and packet-radio workflows, that is the real appeal: keep the local mesh running on Meshtastic, but let its position data surface in a system they already watch.

The request was straightforward, but the plumbing was not. The issue said the bridge would need a ham radio callsign and an APRS-IS passcode in configuration, and it pointed to the aprslib Python package as the way to move the data. That turns the idea from a nice-to-have feature into an interoperability play, where Meshtastic stops acting like a sealed app and starts behaving like one more source of live position data in the amateur-radio stack.

That matters because Meshtastic already treats position as a first-class feature. Its radios can pull GPS data from either the hardware itself or a paired phone, and the position settings include GPS mode, GPS update interval, fixed position, smart broadcast, smart broadcast minimum distance, smart broadcast minimum interval, and broadcast interval. Smart broadcast is on by default, and when it is turned off, the default broadcast interval is 15 minutes. In other words, the bridge would not be inventing a new data stream. It would be exporting one that Meshtastic already expects to move around the mesh, with all the usual tradeoffs around how often a node speaks and how much it reveals.

The policy side is just as important as the technical side. APRS-IS is the Internet-based network that interconnects APRS radio networks worldwide, and its own rules say packets injected directly into APRS-IS should be acceptable for RF because they may be gated to or from radio. aprs.fi then collects that APRS-IS data and displays live position, weather, telemetry, and messages. That is powerful, but it also means a mesh node that felt local can become part of a much broader public tracking layer.

This was not the first Meshtastic-to-APRS experiment, either. GitHub already shows aprstastic, an APRS and Meshtastic gateway that warns legal operation requires an amateur radio license and a valid call sign, and the project lists 111 stars and 11 forks. Another bridge project, meshtastic-bridge, already lists APRS-IS among its integrations, while meshtastic-to-aprs says it can send location updates from a Meshtastic node to APRS-IS using MQTT and Docker. The new issue fits that pattern: Meshtastic is no longer just about off-grid texting. It is becoming something operators want to plug into the rest of the radio world, where live maps, licensing, and visibility all come with the territory.