Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. How does migration from V2 to TTES V3 work?
    You are able to migrate applications and devices from V2 to V3 yourself. Devices cannot be present in both. This means that you have to integrate both V2 and V3 APIs concurrently to your application to avoid downtime. Device sessions will be preserved, however as V3 has more MAC settings, manual configuration may be required in the Network Server.

    Gateways need to be updated to a new server address. Until the gateways are updated, data is routed from V2 to V3 via the Packet Broker.

    Our suggested migration process:

    1. First: Update applications to support the The Things Stack data format which is different from the V2 data format. If you are using payload formatters, make sure to set them correctly from the Application settings page.

    2. Second: Migrate a single end device (and gateway, if needed) to TTES. Continue by gradually migrating your end devices in small batches. Avoid migrating production workloads before you are certain that they will work as expected. We will publish a detailed tutorial shortly.

    3. Finally: Once you are confident that your end devices are working properly, migrate the rest of your devices and gateways to TTES.

  2. Do you provide scripts to help me migrate from V2 to V3?
    Yes, we will provide DIY scripts to bulk migrate applications, devices and session data. Contact support@thethingsindustries.com to obtain these scripts.

  3. Can I migrate devices back to V2?
    No.

  4. How do I migrate my gateway to V3?
    We will offer a temporary bridging solution so that gateways work on both your existing V2 environment and the new TTES V3 environment. After that, we will update our DNS so that they will point to the new environment exclusively. However, it is highly recommended to upgrade to the Gateway Agent with V3 gateway ID and API key or update the address when using UDP.
    How can I migrate the MAC (LoRaWAN Version) and PHY (Regional Parameters) settings from V2 to V3?
    The Things 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.

  5. Can I migrate from a different network provider to TTES V3?
    Yes. As this is a specific activity, please contact us at support@thethingsindustries.com. We need some information about the devices and gateways to understand the scope of such migration.

...