1-Integration via TTI

TABLE OF CONTENTS

• Description
• Requirement
• Configuration
  • Step 1: Register an Account
  • Step 2: First Login
  • Step 3: Gateway Configuration
    • a) Disable the Built-in Network Server
    • b) Connect Gateway to the TTN Platform
  • Step 4: TTN Platform Configuration
    • a) Create an Application
    • b) Add a Device
    • c) Obtaining the Platform API Key
    • d) Modify General Settings
  • Step 5: Configure LoRa API Integration
  • Step 6: Sync Device Information
  • Step 7: Create a Demo Dashboard

1-Integration via TTI

Description

Octobus is a technology company focused on the Internet of Things (IoT) and smart city solutions. It is dedicated to helping customers achieve efficient device connectivity, data collection, and intelligent analysis through advanced hardware and software platforms. Octobus offers an all-in-one service including device access, remote monitoring, data visualization, and alarm notifications, and is widely used in fields such as energy management, environmental monitoring, and industrial automation. The company greatly enhances deployment flexibility and system compatibility by supporting various communication protocols (e.g., LoRaWAN, NB-IoT, Modbus) and seamless integration with mainstream cloud platforms. In addition to its emphasis on technological innovation, Octobus is committed to providing customers with a stable, reliable, and scalable IoT infrastructure to help them advance toward digital transformation and smart management.

This document mainly describes how to connect a UG65 gateway to the OCTOBUS platform (via a third-party LNS, specifically the TTN platform), and how to synchronize an AM319 device as an example on the OCTOBUS platform.

Note: The AM319 device mentioned here is only used for demonstration purposes and does not imply that other types of sensors are unsupported. Readers should adapt the steps based on their actual situation.

Requirement

• Gateway Model: UG65 (UG56, UG67, UG63 or SG50 are also supported)

• Sensor Model: AM319

• Gateway: Must already be connected to the Internet.

Configuration

Step 1: Register an Account

Go to https://octobus.asia/ and click the “LOGIN” button:

Since this is the first visit, fill in the registration information as prompted on the page:

After submission, an activation email will be sent to your inbox. 

Click the activation link to start using the platform:

Step 2: First Login

Click the “Login” link in the email, then enter your credentials to log in.

Next, it is recommended to first create your own Organization Unit. 

All your sensors, assets, and other related information will be registered under this organization. 

The platform also supports multi-level organization hierarchies. After creation, the result should look like this:

Now your account has been prepared, and we can begin configuring the gateway and TTN platform.

Step 3: Gateway Configuration

a) Disable the Built-in Network Server

First, log into the gateway's web interface (refer to <How to Login Web GUI of Milesight Gateway>) and follow the steps in the screenshot:

Once the Embedded NS shows as Disabled and Disconnected, the disabling was successful:

b) Connect Gateway to the TTN Platform

Follow the steps in <The Things Stack-Milesight Gateway Integration via Semtech Packet Forwarder>. 

After completion, the screenshot should look like this:

Note: 

The TTN region used in this demo is NAM1.

Step 4: TTN Platform Configuration

a) Create an Application

Follow the steps as shown in the image:

Note: 

In this demo, the Application ID used is octobus-demo-use. Be sure to record this out, as it will be used later.

b) Add a Device

In this demo, we use the AM319 sensor. 

Add this device to TTN by following the steps in the screenshots:

Fill in the AM319 parameters step by step as prompted. 

Make sure to select the correct Frequency Plan as shown in the image:

After adding, you will be able to see the basic information of the device and its real-time data on TTN:

This completes the device addition on TTN.

c) Obtaining the Platform API Key

OCTOBUS requires only an API key for synchronization, which can be generated at the application, user, or organization level.

For instance, if you want to synchronize all devices across all applications within a specific organization in The Things Stack (TTS), you should create an organization-level API key.

For ease of operation, you can also refer to the following method to obtain the relevant information:

Click “Generate new API key.” 

The plaintext key will be displayed only once, so make sure to save it securely.

Here is an example plaintext key (for demo only). This is very important and will be used later:

NNSXS.RIEZLBB23I5T2QMBS5IKPNNMBXBVDCQC5YCVEVA.FRJ2NMKKL2XDLW6O65NXCW7OXIWHN3USGMZ3XCFX4T73HDJ7ONNQ

Click on it, then check all permissions as shown:

Click Save changes after checking all boxes:

d) Modify General Settings

According to the platform documentation, you also need to check “Skip payload encryption and decryption” as shown:

Click Save changes after checking:

Now the TTN MQTT key and parameters are fully configured. 

Next, return to the OCTOBUS platform to input the TTN parameters.

Step 5: Configure LoRa API Integration

Follow the steps shown in the image:

In the popup window, fill in the information obtained in the previous steps:

Parameter description:

• Server Name: Fill in as per your actual scenario
• Organization Unit:  Select the name you created in Step 2, e.g., “Milesight”
• TTN LoRaWAN host:  Choose the TTN region used in this demo, i.e., NAM1 (refer to Step 4)
• Authentication:  Select Application ID / API Key
• LoRa Application ID:  Fill in the ID created in Step 4, e.g., “octobus-demo-use”
• API Key:  Paste the plaintext key obtained in Step 4

Click Create. If the interface shows Success, it means the parameters are correct and the integration works:

Step 6: Sync Device Information

Click as shown to expand the list of all sensors under the Application on TTN:

Click the Sync button to synchronize the corresponding devices to the OCTOBUS platform. 

After that, the platform will display the device catalog, allowing the user to select the appropriate Milesight device and assign it to the correct organizational unit.

Once synchronized, OCTOBUS will automatically create Assets and Asset Types:

You can now see the real-time sensor data synced to OCTOBUS.

Below is the Asset Type information for the AM319 sensor used in the demo. 

As shown, the platform automatically created corresponding fields based on the sensor's features:

Step 7: Create a Demo Dashboard

As shown in the image, the sensor data is now reported to the OCTOBUS platform in real time, and can be visualized in charts:

-END-