Migration of Devices Without Ability to Rejoin

[bluejedi]

Based on the following information:

@johan

• It is highly recommended to migrate devices without the security session. This means that devices have to rejoin on V3. This is because we changed some LoRaWAN settings and we issue a new DevAddr that points to the V3 clusters. Packet Broker does not route traffic from the current V2 DevAddr ranges to the V3 clusters. Most devices will automatically revert to join mode when they figured out they lost link, by link check MAC commands, expecting acknowledgements sometimes, etc
• If you really need to retain your LoRaWAN security session, you need to make sure that the gateways covering your end devices are already connected to a V3 cluster, because your old DevAddr does not get routed by Packet Broker from V2 to V3. Note that migrating gateways already may break deployments from other community members

It appears that migrating devices ‘including security session’ should be possible under certain conditions. I personally have no experience with these migration tool(s), but TTI staff probably will.

And please provide detailed information about your case and devices (if necessary ask the developers). Without it this thread will only turn into a cat and mouse game.
Don’t make others have to guess and ask for more information that you can already provide yourself.