This topic created to focuss discussions around practicalities and issues arising from pending TTN V2 to TTN V3 migration, and associated V2 Sunset 2H’21
*Note TTN V2 Gateways currently forward to TTN V3 with no issues (*though you may see some GW metadata is stripped/annonymized, potentially affecting some Applications or use cases - YMMV - e.g. TTN Mapper has a know problem with V3) through PacketBroker, however, new GW’s directly connected to V3 WILL NOT forward data ‘backwards’ to V2 Applications. In addition if you migrate a V2 installed GW to V3 this too will stop forwarding to V2 applications.
Bottom line Users & Community Members need to plan and schedule their migrations carefully to avoid local disruptions and apparent ‘loss of service’ for older applications, etc.
Per @johan on the TTConf’21 chat this morning (20210126)
V2 gateways are fully connected to V3, for uplink, downlink and activations.However, gateways that are connected directly to V3 (new or migrated gateways) will not route data back to the legacy V2 environment
(*) updated to add comment
Let the discussion begin :-