Before getting started, we will discuss major breaking changes between The Things Network Stack V2 and The Things Enterprise Stack , along with some guidelines to make the migration process easier to manage.
The Things Enterprise Stack is using a new architecture. See Components for a complete overview of the different components of The Things Enterprise Stack .
The Things Enterprise Stack requires the LoRaWAN version and Regional Parameters (LoRaWAN PHY version) to be set per end device. These default to LoRaWAN version 1.0.2 and LoRaWAN Regional Parameters version 1.0.2 Rev B for end devices imported from The Things Network Stack V2 , because this configuration is the most consistent with the V2.
This means that all end devices need a frequency plan. You will have to choose the frequency plan corresponding to your region. A list of supported Frequency Plan IDs is available in the lorawan-frequency-plans Github repository.
Furthermore, The Things Enterprise Stack brings full support for all LoRaWAN versions, as well as Class B and Class C modes.
The Packet Broker enables peering between networks, so traffic received by one network (e.g. the Public Community Network) but intended for a different network (The Things Enterprise Stack ) can be forwarded to and from that network. See the Peering Guide for details on Packet Broker and how to enable it for your network.
With Packet Broker enabled on both The Things Enterprise Stack and The Things Network Stack V2 , you can receive traffic on The Things Enterprise Stack without having to re-configure any of your gateways.
NOTE: Packet Broker is enabled on The Things Network Public Community Network and The Things Industries Cloud Hosted.
For private The Things Enterprise Stack deployments with Packet Broker disabled, you will need to re-configure your gateways to connect to The Things Enterprise Stack , so that you can start receiving traffic from your end devices.
In order to connect a gateway to The Things Enterprise Stack , follow instructions for Adding a Gateway in the Console or Adding a Gateway using the CLI. Then, reconfigure the gateway to connect to The Things Enterprise Stack , and regenerate its API key (if required).
Also see Gateways for instructions on configuring popular LoRaWAN gateways with The Things Enterprise Stack .
The Things Enterprise Stack uses a different data format for uplink and downlink traffic than The Things Network Stack V2 .
For details on the data format of The Things Network Stack V2 , see the documentation from The Things Network.
The data format has changed in The Things Enterprise Stack . It uses a different schema, different names, and has much richer metadata support. Read more about that in Data Formats.
When migrating to The Things Enterprise Stack , ensure your application can properly handle the new The Things Enterprise Stack data format.
Migrating the The Things Network Stack V2 payload encoder and decoder to an uplink and downlink payload formatter should be straightforward, since they have the same format.
You will need to change the MQTT server your application connects to. The Things Enterprise Stack has a new MQTT server address. You will also need to create API keys and update your MQTT credentials accordingly.
Read more on MQTT Server.
The HTTP Integration is now called HTTP Webhooks. The payload format, downlink endpoints, paths and security settings have changed.
Read more on HTTP Webhooks.
The Things Enterprise Stack does not currently support a Storage integration similar to The Things Network Stack V2 . This feature will be added in a future release.
Suggested Migration Process
First: Update applications to support the The Things Enterprise Stack data format. If you are using payload formatters, make sure to set them correctly from the Application settings page.
Second: Follow this guide in order to migrate a single end device (and gateway, if needed) to The Things Enterprise Stack . Continue by gradually migrating your end devices in small batches. Avoid migrating production workloads before you are certain that they will work as expected.
Finally: Once you are confident that your end devices are working properly, migrate the rest of your devices and gateways to The Things Enterprise Stack .