TTN Mapper version 2021.01.14 and private TTNv3

Hello to everyone,

A few days ago our Android TTNMapper updated to the new build 28. I notice there is one option now to choose between three LoraWAN network servers, amongst one, namely The Things Stack v3.
We have our private TTSv3 at the DingNet of Leuven :
When I want to link our Adeunis Field Tester with the new stack and I fill out the public address with the above instance, there is no MQTT connection possible, allthough the API Keys and authentication are correct (double checked).
Can only be used as lorawan network server (LNS) and no other LNS besides the TTI?

@jpmeijers Did you foresee it or do you have to redevelop with our private LNS server?

Thanks for answering.

@wdebbaut thanks for the bug report.

I developed the feature against an * instance. It is quite possible that there is a difference between a private hosted version and the cloud hosted one. Most likely the json that is received from your instance is slightly different from the cloud hosted version. I have seen a crash report regarding a v3 json message that could not be parsed.

If you can send me details for a device on your private instance that is transmitting messages, then I can use that to test, debug and fix the issue. Please send me details like this in private, like on the TTN Slack, or email

Gents, will you make sure not to include mapping for private instances on the public map? That might confuse people no end.
Exception is of course when the private instance connects to the packet broker to make it useable for the community as well.

1 Like

@jpmeijers Sent you a DM message on

@kersing What do you exactly mean by your question?

If mapping data for private networks gets on to users of the community network might expect coverage of the community network where there is a private network. So I hope there won’t be any private networks included on the public map.

Ok @kersing , I understand. A couple of our private gateways have the TTN NWS as packet forwarder. So these will appear on the community network so that everyone can see in Leuven if there is TTN coverage.

@kersing no this is not a problem. Even if someone uploads coverage from a private network, the backend will filter the data depending on the mqtt broker the data came from.

This is a new feature that was implemented on the backend in conjunction with the added network server support in the android app. For now non-ttn data is dropped, but the plan is to support multiple networks in the future with a “cloud hosted” coverage map under a more generic domain than “”.


hi @jpmeijers I am on the pulic TTN V3 now, but I do not see an integration with TTN Mapper. Will there be one? Or must I make it myself with a webhook?

1 Like

Unfortunately it isn’t as simple as adding a webhook. TTN Mapper wouldn’t know where the data comes from. We need to get the ticket linked to in the one above solved first.

For now the Android app should work, but I’ve only tested it on private networks, not the public TTNv3 yet. Best is to hang on for a couple of days and if you need to map use TTNv2.


JP, I will hang on for days… weeks. months… but I hope TTN Mapper will stay available in/on V#


This is something we’re also interested in - am about to rollout 60+ gateways to our County together with a ttnmapper application to map their coverage but it would be great to get everything moved to V3 before doing this to save on work later on.

1 Like

Sounds good but the problem is that packetbroker is anonymizing the gateway and stripping metadata (location) from the data and makes the data un-useable for TTNMapper. This solution is only usable for applications that do not rely on gateway metadata.


We’re gonna support this. Please subscribe to Include gateway identifier in metadata · Issue #23 · packetbroker/api · GitHub and keep an eye on referenced issues in The Things Stack.


This topic was automatically closed after 30 days. New replies are no longer allowed.