Read this section if you want to make use of Packet Broker to migrate your end devices and route traffic from V2 to The Things Stack.
When migrating your devices with active sessions, it is in most cases not possible to make use of Packet Broker. Read along to learn when you can and cannot make use of Packet Broker.
| Migrate from | Migrate to | Possibility to use Packet Broker |
|---|---|---|
| The Things Network V2 | The Things Stack Community Edition | Only without persisting active device sessions |
| The Things Network V2 | The Things Stack Cloud | Only without persisting active device sessions |
| The Things Industries V2 | The Things Stack Community Edition | Only without persisting active device sessions |
| The Things Industries V2 | The Things Stack Cloud | With and without persisting active device sessions |
Note:
Remember that The Things Stack Enterprise and The Things Stack Open Source can also be configured to connect to Packet Broker. If using those deployments, end devices can be migrated from V2 via Packet Broker without persisting active sessions.Devices Address (DevAddr)
V2 DevAddr of your end device needs to be routable by Packet Broker.
OTAA devices migrated without an active session will acquire a new DevAddr from The Things Stack during the join procedure. Packet Broker will always be able to route the traffic with DevAddrs assigned by The Things Stack Community Edition or The Things Stack Cloud.
When registering ABP devices on The Things Stack, it is possible to auto-generate new DevAddr which can be routed by Packet Broker. ABP devices can be re-programmed to use this new DevAddr. This implies breaking their existing session on V2.
Migrating OTAA and ABP devices with their active sessions implies keeping their DevAddr values from V2. Packet Broker will be able to route traffic for these DevAddr values only if these devices were registered on The Things Industries V2 (SaaS) and you are migrating them to The Things Stack Cloud. If you are not using these deployments and you still want your traffic to be routed by Packet Broker, end devices can only be migrated without their active sessions.
RX1 Delay
The RX1 delay value for your end device needs to be set to 5 seconds, which is a default for The Things Stack (V2 is using 1 second).
The RX1 delay of OTAA devices migrated without their active session will be automatically set to 5 seconds without your intervention.
However, this needs to be manually set for OTAA devices migrated with an active session by configuring their MAC settings. It is also possible to re-program ABP devices to enforce the RX1 Delay of 5 seconds (this basically implies starting a new ABP session, i.e. migrating ABP devices without their active session from V2).
If devices keep on using an RX1 Delay of 1 second, downlinks routed via the Packet Broker will probably never reach the end device in time. The solution to enable downlinks is to migrate your gateway to The Things Stack too. Even if you migrate your gateways to The Things Stack, you might still experience issues if you are using a high-latency backhaul.
If DevAddr and RX1 Delay conditions stated above are not met, it is likely that you will experience difficulties in communication between your end device and The Things Stack via Packet Broker. If you are using deployments that are not connected to Packet Broker, you will have to migrate your devices as well as your gateways in order to receive the traffic from your end device on The Things Stack.
Warning:
It is possible to migrate active device sessions from The Things Network V2 (public community network) to any The Things Stack deployment. But, this is achievable only if you migrate your gateway to The Things Stack, as Packet Broker cannot route this traffic properly.
We strongly recommend to migrate devices without their active sessions, to make sure Packet Broker can route the traffic properly and that it reaches The Things Stack in time.