Skip to main content
Skip table of contents

Actility ThingPark Wireless

Overview

An Actility ThingPark Wireless Network Server (LNS) can be integrated with ThingsHub to establish a seamless data flow between the two.

Process

  1. Create a Network Connector in ThingsHub

  2. Configure the Network Server

  3. Set up Routing

Step 1) Creating the Network Connector in ThingsHub

You need to be a tenant owner to access the tenant settings

  1. Open your thingsHub tenant, go to Tenant Settings > IoT Network Connections, then select the New Connection button.

  2. In the Connect to IoT Network dialog, enter information in the fields, as described in the parameters table below. Then press the Connect button.

    The new network connection will first be validated, and if successful, it will be created.

Parameter

Description

Name

 

Network Connector

Choose Actility Thingpark Wireless

User Name

 

Password

 

Routing profile ID

Optional - The routing profile ID of the devices in the network server

API Url

The base URL of the network server API
(for Drei ThingPark Wireless DX API this value is: https://drei.thingpark.com/thingpark/dx/)

Auth Target

The DX profile of the subscriber, which depends on the specific thingpark network server
(e.g. for Drei ThingPark Wireless DX API, the value is drei-api)

image-20240328-061635.png

Network Connector settings

Step 2) Configuring the Network Server

Setting up the Application Server

  1. Go to the Device Manager page in the network server

  2. In the sidebar go to the Application Servers menu and create a new application server. Click the Save button.

    image-20240319-133300.png

    Application Server Configuration settings:

    1. Custom headers: Custom headers can be added to each POST request the network server sends to the application server. We need to add the Authorization header with the push token here as follows:
      - Name → Authorization
      - Value → Bearer {Your Connector’s Push Token}

      image-20240330-105828.png

    2. Uplink/downlink Security

    3. [ESSENTIAL] Route:
      This is essential and defines the destination address to which data from the device is ultimately sent. The value of this should be the webhook address generated in the network connector config.

      image-20240319-133911.png

      Adding multiple destinations
      Multiple webhook destinations can be added to send data to. For this the routing strategy must be set to Burst.

Step 3) Setting up Routing

  1. Go to the AS Routing Profile menu in the sidebar of the network server interface.

  2. Add a Destination under Destinations.

    1. The Type and Destination can be configured for each Routing profile

    2. To associate this routing profile to the Application Server created earlier, the Type must be set to Local Application Server and the Destination to the name of the application server

  3. Saving this will create a new routing profile that routes data to the application server.

Assigning the device with this Routing Profile

This is the last piece needed to connect the device to thingsHub.

  1. Go to a particular device in the Devices menu through the sidebar

    image-20240319-134952.png

     

  2. Under Network routing, set the routing profile to the one created earlier

  3. Save the profile.

The device is now connected to thingsHub.

 

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.