TTN-Mapper and Lilygo-T-Beam

[Jeff-UK]

Hi JP, sorry if there is a misundestanding here - appreciate Webhook Template may now be the/an official route under V3, I was working off your most recent posts in

TTN Mapper and how to indicate V2 vs V3 vs Private

Many questions, so let me answer the core ones. A gateway is uniquely identified by the network id and the gateway id. So there is a TTNv2 gateway with ID eui-0011223344556677, and there is a separate gateway on eu1.thethings.network (V3 eu) with ID eui-0011223344556677. These two are currently handled separately. At some point we can try and find a way to either copy old coverage data over, or merge the two. We can do this because we know TTNv2 and eu1.thethings.network are essentially the sam…

Were you said
“Mapping V3 is already possible using the Android app. It is also possible using a gps tracker and setting up a webhook integration. It’s a little tricky to do, and therefore we need a template. Issue is that the template doesn’t allow optional fields, making the “experiment” option difficult to implement. My plan is to release a template that does not have the experiment option, but one can manually add it by editing the webhook.”

and later

" You will see on https://status.thethings.network/ that the update is scheduled to be deployed on 12 April. Only after that we can see how this was implemented, and add support for the new identifiers on TTN Mapper’s side".

I may have missed but haven’t seen any specific updates to say TTN Mapper integration now done and complete so assume(d) still a work in progress and not yet fully tested/complete.

Are you saying that original request and advise in

TTN V2 to V3 migration

Packet Broker currently routes traffic from gateways connected to The Things Network V2 to V3. That is, gateway coverage of V2 is available in V3. But not the other way around : gateways already connected directly to V3 will not be available for applications in V2. As a friendly request, both as a user of TTN and as the maintainer of TTN Mapper, please keep your gateways on TTNv2, until as late as possible. People in your city that have not yet migrated their application from v2 to v3 will…

no longer holds from TTNMapper POV (still holds for other use cases and due to impact on other local community V2 users of course) and that you are happy for all to migrate to TTN Mapper using V3?

@jpmeijers

What is missing?

Speaking as a non-softie and someone who only rolls sleeves up and codes (more usually copy, paste/edits) when forced too (!) you could say what is missing is an ‘easy’ integration such as where in V2 we could ‘push the button’ for V2 integration of Cayenne/MyDevices, Data Storage, or TTN Mapper etc, where as (with exception of Data Storage) under V3 we no longer have that option… would be good to have added and that is what I may have misunderstood as missing and might be enabled by an official Template…I know there are many others like me who would like an easy path “click to enable this” option Also as highlighted by Julian above, there still seems to be some missing functionality and behaviours, which I thought indicated not yet a production solution, again apologies if I have got this wrong or misunderstood.

@jpmeijers

Processing of the data is still under development and not as trivial as with TTNv2.

Please keep us all updated on TTN Mapper development status (do we need a dedicated thread for that under the V3 Migration category so details dont get lost or peanut buttered across other discussions?)

Update: May also be worth adding a link to the docs as above to the TTN Mapper home page menus (I dont see it come up there or under any subheadings)