Versions Compared


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


  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
    dev_ids=("dev1", "dev2")
    for dev_id in ${dev_ids[@]}
       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"

    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.