Page Comparison

...

1. When setting the Frequency Plan, what is the difference between Europe 863-870MHz and Europe 863-870 (TTN)?
   The only difference is that 863-870(TTN) uses SF9 for RX2, whereas 863-870 uses default SF12 for RX2. You can check this in the frequency plans repository.
   

2. I don't have a JoinEUI for my device. How do I register my device?
   For LoRaWAN 1.0.x devices, the JoinEUI in TTES is the same as the AppEUI in TTI V2. Devices usually come with JoinEUI (AppEUI). It is either issued from an IEEE block that you own, or you can set to 70B3D57ED0000000 if you are using the Global Join Server. You need to ensure that the (JoinEUI, DevEUI) pair is unique.
   

3. What does the External Join Server option do when I register a device?
   Using an ‘External Join Server’ like the Global Join Server provided by The Things Industries allows you to claim a device which has been pre provisioned by providing only a Join EUI and Device EUI. The Things Enterprise Stack also contains a built in Join Server, which is used if ‘External Join Server’ is NOT selected. To use the built in Join Server, you must also provide an App Key (and a Network Key for 1.1 devices).
   

4. How do I move the devices between applications?
   Here is a sample bash script to re-organize a few selected OTAA devices between applications.

   Code Block

   #!/bin/bash old_app_id="sample-application-1" new_app_id="sample-application-2" dev_ids=("dev1", "dev2") for dev_id in ${dev_ids[@]} do dev=$(ttn-lw-cli end-devices get $old_app_id $dev_id --name --description --frequency-plan-id --network-server-address --application-server-address --join-server-address --root-keys --lorawan-version --lorawan-phy-version --supports-join) ttn-lw-cli end-devices delete $old_app_id $dev_id ttn-lw-cli end-devices create $new_app_id $dev_id <<< "$dev" done

   You can also use our device claiming service. More information about this is available at the Device Claiming Documentation page.
   

5. How can I update the firmware over the air (FOTA)?
   The Things Stack supports the building blocks for FOTA: multicast, class B and class C.
   The FOTA specifications which are yet to be implemented in the Application Server are: Remote Multicast Setup (RMS), Fragmented Data Block Transfer (FDBT) and Application Layer Time Synchronization (ALTS).

   
   We are currently working on supporting the FOTA supportspecifications, but it may take another couple of months until 2021 before we fully support this feature.

...

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 scriptshere: https://enterprise.thethingsstack.io > Getting Started > Migrating from V2.
   

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

4. 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.

...