1-Integration via Basic Station

2-Integration via Semtech

3-Milesight LoRaWAN Device Integration

4-Integration via ZTP (recommend)

TABLE OF CONTENTS

• Description
• Requirement
• Configuration
  • Step 1: Obtain Platform Information
  • Step 2: Configure the Gateway
    • a) Disable Default Packet Forwarding Parameters
    • b) Configure Parameters
  • Step 3: Check the Results
• Frequently Asked Questions

Description

TheThings - Industry platform is a cloud-based service and management platform designed specifically for Industrial IoT (IIoT) scenarios. Built on LoRaWAN® technology, it enables full-process support from device access and network management to data visualization and business integration.

It provides enterprises with secure, scalable network services, supports centralized management of multiple sites and applications, and can be integrated with existing IT/OT systems to enable data-driven production optimization and intelligent decision-making. The platform offers high availability, flexible user and permission management, automated alerts, and multi-dimensional data analytics capabilities, making it suitable for various industry scenarios such as smart factories, energy management, environmental monitoring, and smart cities.

This document primarily describes how to connect a UG65 gateway to the TheThings - Industry platform, automatically create the gateway information on the platform, and view the gateway’s data in real-time, all completed automatically without manual intervention.

You can also refer to below video tutorial to know the steps: 

Note: 

The UG65 device mentioned in this document is used only for demonstration purposes. Please refer to the steps according to your actual situation.

Requirement

• Gateway Model: UG65 (UG67 also supported)

  • Firmware Version: v60.0.0.47 or later

• Gateway Model: UG56

  • Firmware Version: v56.0.0.7 or later

• The gateway must be connected to the internet

• A valid TheThings - Industry account

Configuration

Step 1: Obtain Platform Information

Visit: The LoRaWAN Network server for scale | The Things Industries

(If this is your first time using the platform, simply follow the on-screen instructions to register)

After completing registration and logging in for the first time, verify your credit card information, and you will see the following interface:

Then create a configuration named milesight-demo-use-only.

All demonstration information in this tutorial will be displayed under this configuration:

Click the Open Consoles button to enter the management interface:

Refer to the figure below to obtain the key information: User ID, API Key, and Server Address.

● Get User ID:In this demo, the User ID is lockon.

● Get API Key:

● Get Server Address:

Copy it directly from the browser address bar (be sure to remove https and any slashes).

At this point, the platform parameters are ready. 

Example like:

Note 1: 

If your deployment is for a large-scale project and requires bulk installation, you can provide the above parameters to us in advance. We can pre-configure them before shipping the gateways, so that the gateways can be used immediately upon power-up and network connection, greatly reducing on-site work.

Note 2:

Because the demonstration environment is in the EU region, but the current gateway frequency band is US,  this does not affect the registration or use of the gateway. Therefore, we recommend that users handle this according to their actual needs.

Step 2: Configure the Gateway

a) Disable Default Packet Forwarding Parameters

First, log in to the gateway’s management interface (refer to How to Login Web GUI of Milesight Gateway : IoT Support) and follow the screenshot instructions below:

(If it is already disabled accordingly, you can skip this step.)

After completion, the result should look like this:

b) Configure Parameters

Follow the figure below: 

Click the add button, and in the pop-up window, select The Things Industries - Auto from the Type dropdown:

Fill in the fields as prompted, all parameters come from the previous steps.

Note: 

The Server Protocol supports three types, choose the one that fits your actual use case.

After completing all configurations, the result should be as shown:

Click Save, then Save & Apply to submit the settings and wait 3-5 mins for the changes to take effect.

At this point, the entire configuration process is complete. 

If you encounter any issues, it is recommended to visit the this link for reference.

Next, verify the results.

Step 3: Check the Results

Go back to the console interface and click Gateways tab:

Filter using the gateway’s EUI. 

You should see that the gateway has been automatically registered on the platform:

Click to view details:

You can see that the platform is already receiving data reported by the gateway in real time, indicating that the gateway has successfully connected to the platform and is transmitting data.

Frequently Asked Questions

Q1: Why doesn’t my gateway have the The Things Industries - Auto option mentioned in your article?
A1: Please check the firmware version of your gateway. 

This option is only available if:

• Your gateway model is UG65 or UG67, with firmware version 60.0.0.47 or higher.
• Your gateway model is UG56, with firmware version 56.0.0.7 or higher.

Q2: My gateway is new, but when I follow your article and configure it to section “b) Configure Parameters”, it fails with the error message API Request failed. Why is this happening?
A2: Please troubleshoot step by step as follows:

• Check the platform you are using. This function only supports The Things Industries, not The Things Network.
• Check whether your The Things Industries account has sufficient gateway quota. Generally, accounts verified with a free credit card can only support up to 10 gateways (see figure below).(The message “3 of 10 gateways” in the screenshot means that you currently have 3 gateways out of a total quota of 10, so you can still add 7 more gateways. If it shows “10 of 10”, then you will encounter the issue you are facing now. )
• Check whether your API key was created correctly. It must be created under User → API Keys, not under Application → API Keys.

Q3: The first time I followed your tutorial, it worked, the gateway was successfully configured and came online. But after deleting and trying to add it again, it failed. I also tried adding it with another The Things Industries account, but that also failed, even when adding manually. Why?
A3: Since your first configuration succeeded, it means your gateway’s Gateway EUI was registered on the platform and came online successfully. However, if subsequent attempts to add it fail regardless of the method used, it indicates that during the deletion process, you did not check the "Also release entity IDs(purge)" option. So, when deleting a gateway, you must check that option to ensure that The Things Industries platform completely clears the data associated with the Gateway EUI. Otherwise, it cannot be re-added.

And f you already encountered this problem, you need to contact support@thethingsindustries.com and provide proof of ownership, such as device photos, purchase order information, etc. The The Things Industries support team will help you resolve the issue.

Q4: I have a project that is planned to be deployed in the US region. The gateway I selected uses the US915 region. However, when I followed your tutorial and reached the step “b) Configure Parameters,” it failed with an “API Request failed” error. Why is this happening? I didn’t encounter this issue when deploying a project in Europe.

A4: This is a limitation of The Things Industries platform. Our implementation relies on calling the platform’s API under the hood. According to The Things Industries troubleshooting guide, currently only eu1 is supported; nam1 is not. 

However, if project requirements allow, it is possible to configure a US915 gateway to use the eu1 The Things Industries address, and it will function correctly.

-END-