Announced during TheThingsConference 2021 this January, TheThingsNetwork console is upgrading to v3. In fact it is really more than a simple update because this consist in merging TheThingsNetwork and TheThingsIndustrie in a common environment. This upgrade is really different than a traditional upgrade because it has an impact on any gateways and any devices ; a big impact anyone needs to manage. Here are some of the currently known impacts on the networks and the different components:

• Traffic from v2 is routed to v3 but v3 is not routed to v2
• Gateway are not migrated automatically
• LoRa Application/Integration needs to be re-created in v3 to communicate over v3
• Device LoRaWan session needs to be refreshed
• Coverage map are lost
• Gateways using gRPC protocol (TTN Packet forwarder won’t relay V3 traffic over V2)
• … some more to be discovered

As the Network is managed by many different people, and not really planned and organized by TheThingsIndustry, we are going to have disconnections and fields operations to make all of this back to life.

It concerns the TTN Initiators (people deploying the network) but also the TTN users because they need to update Applications and restart/rejoin devices once the V2 has disappeared.

The currently know planning for Europe is (Other countries not yet planned)

• April 2021 – v2 console will be read-only (you won’t be able to add devices / gateways)
• September 2021 – v2 infrastructure will be switched off, no more communication on it

This blog post details my advises and experience of the migration. As I’ll do it in different waves for practical reason, this post will be updated. So please come back and refresh all along the months of February-March 2021 to get the updates, content and advice will be updated according to my progress.

Personal current advice about migration: START INVESTIGATING SINGLE DEVICE MIGRATION

I had some difficulties to migrate my first device and this has been solved by upgrading the gateway and redefining it in the TTNv2 backend. Discovering such situation earlier is important to get on time for upgrading. I recommend to start migrating 1 device to identify such situation. Migrating more than a device could still means impossible ways for some of your devices to communicate through v2 infrastructure. But it will help to prepare your infrastructure for migration.