Update best practices to include re-join behaviour

TTN V2 to V3 Upgrade
5

As per the migration path in Migrating OTAA Devices from V2 to V3 you can modify the AppKey slightly in v2 (e.g. change one byte), so the current session stays alive, but new OTAA joins will be rejected by v2 (due to key mismatch) and be accepted by v3 (which has the correct key). So what I would do then:

  1. make sure the device is still on v2
  2. copy all node setting from v2 to v3, then change the AppKey in v2
  3. send the custom ‘reset’ downlink command in the v2 console
  4. wait for the OTAA to happen successfully on the v3 console
  5. delete the device on the v2 console
3 Likes