TABLE OF CONTENTS


Description

Akenza AG is a Switzerland-based company headquartered in Zurich, founded in 2017. It specializes in providing a low-code Internet of Things (IoT) platform designed to help businesses connect, control, and manage various IoT devices. The platform supports applications in smart cities, industrial automation, and environmental monitoring. Akenza's cloud solution enables users to quickly integrate different types of sensors and network protocols.

 

This document provides a guide on how to use the UG65 gateway to connect to the Akenza platform via a third-party TheThings Stack platform. The AM308 device is used as an example, along with a basic rule configuration.


Requirement

  • Gateway Model: UG65 (UG56, UG67,UG63,SG50 also supported)
  • Sensor Model: AM308

  • Frequency Band: US915 (used in this demonstration)

  • Gateway: Must already be connected to the Internet.

  • A valid TheThings Industry Platform account is required

  • A valid Akenza Platform account is also required


Plese note that this demonstration is connected to The Things Industry platform. If you are using The Things Network platform, this tutorial can still be followed, and the steps can be referred to accordingly.



Configuration

Step 1: Gateway Integration with The Things Stack

  • If you are using UG63 or SG50, you can refer here to connect using either Basic Station or Semtech method. 
  • If you are using UG56, UG65, or UG67, you can refer here to connect using the ZTP method. 


Next, I will continue the demonstration using UG65. 

The result after the integration is as follows:

  • Gateway configuration screenshot and status:
  • TheThings Industry platform showing the gateway status, confirming that the gateway is online and reporting data properly.


Step 2: Configuration Parameters in The Things Industry

a) Creating an Application

Follow the instructions as shown in the figures:


Fill in the required information in the pop-up window:

Note: The Application ID must be unique. If it already exists, it cannot be used.


Once created, the application dashboard should appear as shown in the figure:


b) Get the User ID

Follow the steps shown in the figures:


c) Creating an API Key

Next , please follow the steps shown in the figures to create an API key:


Click "Create API Key":


In the pop-up window, click the Copy button. The API key will be copied to your clipboard. Then, click the button below to close the window.


Please note that this key will only be displayed once.

Example API Key:

NNSXS.BPLRPYANNQ2QXUVK7DLN3UWZDWWXMZAT5ZWEG5Y.RCLOBZNEHYCCM54TKI6BTS3AU3Z4NXHIHGJHWNLPDL2WD7HUPA2Q


d) Copy the Server Address information

  • If you are using The Things Network, you can skip this step and simply select your region from the drop-down list later.
  • If you are using The Things Industry, please refer to my steps to obtain it:Click the browser’s address bar and copy the front part of the address, making sure not to include https, slashes, or other symbols.


At this point, let’s summarize the information we have obtained as follows: 

User ID

lockon

API key

NNSXS.BPLR******

Server Address 

milesight-demo-use-only.eu1.cloud.thethings.industries

This information will be used in the later configuration. 


Step 3: Register an Account of Akenza and Initialize

Visit https://akenza.io/ and follow the on-screen instructions to create a temporary account (free 30-day trial). 

On your first login, you will be prompted to create an organization and a workplace. Simply follow the on-screen instructions to fill in the required information. 

Here, I created an organization named MS-ORG and a workplace named MS-WP

All subsequent operations will belong to this workplace.


The result after creation is as follows:



Step 4: Integrating Akenza with TTI Platform

Follow the steps in the figures to navigate to the integration section.


Select "TTN LoRaWAN":


If you are using The Things Network, you can select it directly here:


Since this demonstration uses The Things Industry, select Custom and enter the server address you obtained earlier. 

The result after completing the configuration is as follows:



In the Authentication option,there are three options here. You can choose based on your actual situation.

Since the key created in this demonstration is user-related, select User ID / API Key from the drop-down list:


For the User ID, just refer to the screenshot:


Then enter the Name information and click Next:

(Please note that Import Available Devices is checked by default. If you have devices on your TTI or TTN platform, keeping this checked will automatically sync their information. )


After a short wait, the platform will complete the setup, and the integration status will be displayed:


Step 5: Adding a LoRaWAN Device

Follow the steps shown in the figures:


Fill in the information as shown in the picture, here I take “am308-demo-device” as an example to configure:


Here, enter the LoRaWAN parameters for the AM308 device. If no one has modified them, you can find these parameters in the device’s user guide:


Once created, you will see the prompt as follows:


Now,the AM308 device status will be visible on Akenza:


Wait for a moment, and the device will be shown as online:


Step 6: Configuring device data flow

At this point, although our device has been added, the data cannot be parsed yet. 

We need to configure the data flow as follows: 


The result after the final configuration is as follows:


Click Save and just enter the Name. It will be used later:


Now, let's link device to the data flow under the "Devices" menu:

Wait for a moment, and you will see the actual data reported by the device:


At this point, the entire integration process is complete. Next, we will create a simple rule to trigger an alarm for testing. 


Step 7: Configuring a Rule Example

Follow the steps in the figures:


Select our target device:


Next, start configuring the logic and conditions:


Configure a simple condition to check the CO2 value:


For the final action, choose E-Mail and enter your own email address:


The result after completing all the configurations is as follows:


Once the device’s CO2 exceeds 900, an email will be triggered. The email notification is as follows:


-END-