Setting up a TTN application and adding devices

Creating an Account

To use TTN, you need an account.

1. Create an account.
2. Select Console from the top menu.

Adding an Application in the Console

To add a TTN Application:

1. In the Console, click add application

• For Application ID, choose a unique ID of lower case, alphanumeric characters and nonconsecutive - and _ (e.g., hi-world).
• For Description, enter anything you like (e.g. Hi, World!).

2. Click Add application to finish.

   You will be redirected to the newly added application, where you can find the generated Application EUI and default Access Key which we'll need later.

If the Application ID is already taken, you will end up at the Applications overview with the following error. Simply go back and try another ID.

Register a Device

The Things Network supports the two LoRaWAN mechanisms to register devices: Over The Air Activation (OTAA) and Activation By Personalization (ABP). OTAA is more reliable because the activation will be confirmed and more secure because the session keys will be negotiated with every activation. ABP is useful for workshops because you don't have to wait for a downlink window to become available to confirm the activation.

1. On the Application screen, scroll down to the Devices box and click register device.

• As Device ID, choose a unique ID (for this application) of lower case, alphanumeric characters and nonconsecutive - and _ (e.g., my-device1).
• As Device EUI, you have to use the value you get by executing in your LoPy the code in GitHub directory code/lab3/getdevEUI.py soccer skills world cup

2. Click Register.

   You will be redirected to the newly registered device.

3. On the device screen, select Settings from the top right menu.

• You can give your device a description like My first TTN device
• Check that Activation method is set to OTAA.
• Uncheck Frame counter checks at the bottom of the page.

Note: This allows you to restart your device for development purposes without the routing services keeping track of the frame counter. This does make your application vulnerable for replay attacks, e.g. sending messages with a frame counter equal or lower than the latest received. Please do not disable it in production.

4. Click Save to finish.

   You will be redirected to the device, where you can find the Device Address, Network Session Key and App Session Key that we'll need next.