Where is the world map?

The Configuring MQTT docs mention:

The simplest option is to connect your mesh to the official Meshtastic MQTT broker. This makes your devices appear on the world map, and provides a copy of your mesh traffic, translated into JSON.

Where is this world map? I found https://map.meshtastic.org/ from a search engine - is this the one being referred to? If so, I assume this is linked to from the site somewhere and I’ve glossed over it (where?).

1 Like

Good question. I was also wondering. The link to https://map.meshtastic.org/ does not work at the moment. DNS record does not exist.

I believe @sachaw took it down as it needs to be updated to be compatible with 2.0+.

For now, a similar experience can be had via the webUI, but only for a selected channel, all you need is an MQTT connected node: https://client.meshtastic.org/
I will be writing a new version in the future with expanded functionality, but will likely be part of a larger overhaul of MQTT & external routing


I want to do this for my own mesh, so figured a good place to start would be grabbing positions by subscribing an MQTT client to mqtt.meshtastic.org. It’s only been running a few minutes, but I’ve already seen 33 nodes show up:

Nothing much to say about that other than it’s very cool!

1 Like

Until the official one is back up and running, I put a version of the map up on https://map.technicallyrural.com/ so it’s publicly available. It’s… minimalist, but :person_shrugging:. Might add some more to it over time.

It currently shows all the 29 publicly broadcast GPS coordinates I’ve encountered that are not (0, 0).

1 Like

Thank you for this! I was looking for an easy way to check in on my MQTT connected nodes.

If you can get the battery percentave value in there, that would be all I would need.

Just a disclaimer, this map should not be relied on (at least in the short term).

To peel back the curtain so the limitations are clear: I have an MQTT subscriber that listens intermittently (still disconnects every now and then for a variety of reasons), and I re-subscribe it when I happen to notice. It records the user id, latitude and longitude, and timestamp from any PositionApp protobuf messages that show up on msh/2/c/LongFast/#.

Every so often I go and (Edit: automated) Every 5 minutes a program will go and query the DB for the latest position for each user ID and replace the contents of the static HTML file that’s being served. I exclude any nodes that report being at (0, 0) because that’s boring to include on a map. You can view the page source and see everything in all it’s incredible glory (there’s not much).

I’ll automate the update from the DB so I don’t have to be in the loop, without which battery info wouldn’t be helpful because it’d always be out of date, and see about adding the battery info.

I don’t necessarily want to make this a real thing though as I was more thinking of it as a placeholder until the official one resurfaces. That said, as long as it keeps being fun/aligning with what I want personally I’m game to keep mucking with it. Location history is a big one that I’d love to tackle, nodes like 2223539108 broadcast position super frequently though I’ll give a think for what would actually make sense there.

I’ve changed it so that the map is updated every 5 minutes. The map is still static data, but there don’t appear to be so many nodes that that really matters and it seems kinda nice to expose the data in case anyone else wants to use it for stuff.

1 Like

I’ve added the battery percentage and voltage to the map (if present). I don’t have anything reporting currently, so please let me know if it’s showing up for you. I just started collecting the telemetry now so it’ll take a bit to populate. I’m seeing some on there though:


Works great for me! I own the nodes in Los Angeles.

1 Like