Search BackCountrySignal

    Open full search pageSearches run in your browser. Nothing you type is sent anywhere.

    Network · MQTT

    Put your node
    on the map.

    Public maps like MeshMap only show radios that report over the internet. Many Graham County nodes are on the air but invisible. Here is how to show yours, and how much to share.

    Pick one of three ways

    Map report if your node has Wi-Fi or your phone stays connected. OK to MQTT if your radio has no internet but a neighbor runs a gateway. Stay off the map if you would rather not appear. All three are fine; your radio works the same on the mesh either way.

    See the live map

    How the map gets its data

    Meshtastic radios talk to each other over LoRa with no internet. MQTT is the optional bridge: a node with an internet connection (its own Wi-Fi, or your phone through Client Proxy) can pass packets to an MQTT server. The Meshtastic project runs a public server, and maps such as MeshMap read from it. A radio that never reaches that server, directly or through a neighbor's gateway, never shows up, which is why our homepage counts run low.

    Option 1: send a map report

    A map report is a small summary your node sends to the server about once an hour. It is the most direct way to appear on the map.

    1. Give the node internet. If it has Wi-Fi (most ESP32 boards, such as the Heltec V3 and V4 or Station G2), turn on Wi-Fi under Settings → Network. If it does not (nRF52 boards such as the RAK4631, T114 and T-Echo have no Network section), turn on MQTT Client Proxy so it uses your phone's connection while the app is connected.
    2. Turn on MQTT. Under Settings → MQTT, enable MQTT. Leave the server, username and password blank to use the public server.
    3. Turn on Map Reporting in the same screen, agree to share your location there (current firmware will not send a report without that consent), and set its position precision (see below). The report goes out at most once an hour; that is the minimum interval.
    4. Make sure the node knows where it is. It needs a position from its own GPS, from your phone, or a fixed position you set. With no position, no report is sent.

    That is enough to appear. You do not need to send the mesh's messages to the internet to send a map report.

    Option 2: let a gateway relay you (OK to MQTT)

    If your radio has no internet, a nearby node that does can still forward your position. The OK to MQTT setting (under LoRa) is off by default, which asks other nodes not to forward your packets to MQTT. Turn it on to give permission. It applies on channels using the default key, such as LongFast. The project describes it as a polite request that official firmware honors, not encryption.

    What a map report shares

    Map reports are sent unencrypted, from the official MQTT module documentation.
    ItemWhat is included
    Names and node IDLong name, short name and node ID
    PositionRounded to the precision you choose, plus altitude. The default is accurate to about 1.5 km (1459 m).
    HardwareHardware model, device role and firmware version
    Radio settingsLoRa region, modem preset and primary channel name, and whether the node is reachable on the default channel
    NeighborsHow many nodes it heard over radio in the last 2 hours

    Choose your position precision

    Map reports only allow settings between roughly 730 m and 5.8 km; anything outside that range falls back to the default. Two more safety nets help: on channels with a public key, such as LongFast, the firmware caps position precision, and the public server only passes imprecise positions on the default key. Choose the setting you want anyway, rather than relying on those limits.

    Uplink and downlink: leave them off unless you need them

    Each channel also has Uplink (send the mesh's messages on that channel to the internet) and Downlink (bring internet messages onto your local mesh). Neither is needed for the map. The official docs warn that the public server's LongFast channel is busy enough to overload a device, so leave Downlink off on LongFast. If you do bridge a private channel, use your own key and, ideally, your own server; the project advises against using the default key on a private server.

    Prefer to keep internet traffic out of your own view of the mesh? The Ignore MQTT LoRa setting tells your node to ignore packets that came through MQTT anywhere along the way.

    Check it worked

    Give it an hour, then search for your node's short name on MeshMap or look near Robbinsville on our map page. Nothing yet? Confirm the app shows MQTT as connected (or that your phone app stayed open for Client Proxy) and that Map Reporting is on.

    Official sources

    Graham County settings · Network and maps · Privacy