Map & Network

Region and node map

Our region, US-MS-GPT (Gulfport-Biloxi: Hancock, Harrison, Jackson, Pearl River, Stone and George counties), is outlined in blue; neighboring mesh regions are dashed light gray (hover or tap one for its name). Dots are Coast repeaters and room servers (neighborhood-level only).

Active: advert heard within 7 days of the data snapshot Inactive: no advert in the last 7 days Bigger dot = several nodes at the same spot. Locations rounded to about 1 km.

Loading nodes…

How it's built: a scheduled job (for example, a daily site rebuild) downloads the official MeshCore map's public node list (https://map.meshcore.io/api/v1/nodes), keeps only nodes inside the Coast box (lat 30.1–31.0, lon −89.7 to −88.35), and saves a small data/nodes.json that a Leaflet map on this page reads. That list is about 50 MB of JSON (about 19 MB in its compact msgpack form, ?binary=1&short=1). The API only allows browser requests from map.meshcore.dev, so the download has to run server-side or at build time, not in the visitor's browser. TODO: verify terms of use

Fallback link: https://map.meshcore.io/?lat=30.5&lon=-89.0&zoom=9

Live network analyzer

Our own live view of Coast mesh traffic, fed by our own observers: packets, repeaters, and paths as they're heard. It shows traffic and metadata only, never message contents.

See live traffic on our analyzer →

Run an observer

An observer is a repeater with Wi-Fi that uploads what it hears to an MQTT server (a message relay that maps and analyzers read from). Flash observer firmware from https://observer.gessaman.com, then send the admin command:

get public.key

Give the result to the network admin so your observer shows up by name. Then set:

set radio 910.525,62.5,7,8
set name MSCM-Observer-<area>
set mqtt.iata GPT
set wifi.ssid <your wifi>
set wifi.pwd <your wifi password>
set mqtt1.preset custom
set mqtt1.server mqtt.mscoastmesh.org
set mqtt1.port 1883
set mqtt2.preset analyzer-us
reboot

Server mqtt.mscoastmesh.org, port 1883, TLS off. No username or password: leave both blank. (If you set a login earlier, it does no harm: the broker accepts any username and password.)

Note: this firmware ships with slot 1 pointed at the national LetsMesh US analyzer and slot 2 at LetsMesh EU. The commands above point slot 1 (custom) at our broker and switch slot 2 to the LetsMesh US analyzer (analyzer-us), so each observer feeds us and also contributes to the national view. LetsMesh doesn't offer a public API to pull data back out. Command syntax per the observer firmware's MQTT docs.

Privacy note

Observers upload the packets they hear. DMs and private channels stay encrypted, and our analyzer shows traffic and metadata only, not message contents (including Public and hashtag channels). Please list locations at neighborhood level.

The Public channel and hashtag channels can be read by anyone with a radio. Use a private channel or a direct message for anything personal.