TTN Mapper alternatives

1

Feel free to test …

for now just in German .. but i am working on a English translation

5 Likes
2

How do we route data to your mapper?

3

With the demise of the TTN Mapper, and little exposure to the power of the TTN Network, is TTN Dead?

4

at least there seem to be server problems going on for some days now

5

TTN Mapper is not run by TTN/I.

It is a independent project, please read TTN Mapper Github

6

Hi, I wanted to try this, but registration and login don’t work. No mail arrives here.

And my tracker doesn’t like the webhook either. Is there anything new?

Edit: After some time the login works now

1 Like
7

Instructions are here (currently only in German), the interesting part starts at section 10: Handbuch & FAQ · TTN Mapper Anleitung · LoRa NextGEN Mapper

  1. Register for an account
  2. Create an application for your mapper in order to get your custom webhook
  3. Set up a new custom JSON webhook in TTS using the URL from the previous step, enabling only uplink message events (no additional path).

Payload format is compatible with TTNMapper. I just added the new webhook and it just worked. :slight_smile:

1 Like
8

many thanks

i am working on a english translation … will be finish on the weekend i think

9

english translation , inkl the “handbook/manual” are finished.

i hope it helps

1 Like
10

What’s New on ttnmapper.live:

ttnmapper.live runs as the “LoRa NextGEN Mapper,” an openly accessible coverage map for The Things Network and The Things Stack, operated by K&C NetFox. Like the original ttnmapper.org, it takes LoRaWAN uplinks with a GPS fix — via webhook or MQTT — and turns them into a live map of gateway and device coverage. As of this writing the public map is tracking 111 gateways and 64 active devices, with just under 49,000 uplinks logged. Development has been moving fast lately, and the latest additions are worth a closer look.

My Coverage: one map for everything you’ve connected

The standout addition is “My Coverage” (/coverage, login required) — and what makes it notable is that the whole thing, from first commit to security hardening, shipped start to finish in a single day. Until now, checking your own footprint meant looking at one connected application at a time. My Coverage instead merges every device across every TTS application tied to your account onto one map, and resolves overlapping signal data sensibly: each uplink is shown with the RSSI of the strongest gateway that actually received it, rather than whichever gateway happens to belong to a particular application. That gives a true picture of maximum reach instead of an artifact of how your apps happen to be split up.

The same push layered on a genuinely deep set of refinements: a device sidebar grouped by application with per-app show/hide toggles, an optional overlay that lights up every gateway that has ever heard one of your devices, a “per device” color mode with its own ten-color palette on top of the existing RSSI/temperature/humidity/pressure modes, a collapsible sensor filter, a small stats strip for gateways heard and best RSSI, and a toggle for showing RSSI values as map labels directly. The feature is fully bilingual (DE/EN) and, since it surfaces account-specific data, deliberately blocked from search engines via robots.txt. Development closed with a security pass worth calling out on its own: device names, DevEUIs and gateway IDs are user-supplied and visible across other users’ pages, so every map and search popup now consistently HTML-escapes that data before it’s rendered.

Earlier this month

A few smaller but useful changes landed in the weeks before that. Device pages picked up gateway markers with their own time-range filter, so you can see exactly which gateways heard a given tracker over the last 24 hours, 7 days, 30 days, or all-time. The stats page got tightened up — spreading-factor and data-rate bars now sort numerically instead of alphabetically, and chart colors and heights now respect the light/dark theme properly. A new autocomplete search box landed in the navbar for jumping straight to a device or gateway. On the data-quality side, incoming uplinks are now checked with a Haversine distance calculation against the receiving gateway’s position — uplinks claiming to be more than 500 km away get dropped instead of polluting the map with GPS “no-fix” noise.

Try it yourself

Connecting a TTS application takes a webhook URL or MQTT credentials and a few minutes — the manual walks through both, and the decoder library covers most common trackers out of the box if you don’t already have a payload formatter set up.

11

Thanks for the share and that great new mapper. Do you know if the payload decoder you share on the website for the T-1000 would work with a T-2000 ?