Documentation
Tartabit IoT-Bridge
Setup LNS Source

Setup LNS Source

Purpose of this page:

  • Setup Everynet LNS and Tartabit for HTTP Post

Setup Tartabit Service and Everynet LNS Source

This page provides details to complete the following tasks:

  • create the HTTP Post Service definition on the Tartabit IoT-Bridge
  • create a Filter on the Everynet LNS to define forwarded traffic
  • create a connection on the LNS to forward to Tartabit based on the Filter

Tartabit Data Pipeline - Components

Configure the Tartabit Service for the LNS

The LNS will use an HTTP to a webhook address to forward LoRaWAN traffic to the Tartabit Iot-Bridge for processing.

Here is an example of a configured service for a LoRaWAN Network Server using HTTP Post.

Tartabit Data Pipeline - LNS Service

The Webhook secret needs to be unique (avoid duplicating existing services unless you modify the webhook).

Create a Filter with a Device Tag

With a webhook created in the Tartabit service definition, you are ready to setup the LoRaWAN Network Server (LNS) for traffic forwarding to Tartabit. In our example we are using the Everynet LNS.

On the Everynet LoRaWAN Network Server (LNS), the best way to create a filter for forwarding traffic, is with a distinct shared tag assigned to each device.

In this application we are only processing uplinks. The options allow us to see all received frames, RF signal/noise performance, and leverage the device tags.

Everynet LNS - Filter by Tag

Tip: If your device is online, be sure (only) your targetted traffic is showing in the Live stream as shown above.

Keep the Filter ID to use in the HTTP Connection definition.

Create an HTTP Connection with Filter ID

Use the Filter ID, and the URL for the Tartabit IoT-Bridge, to forward the uplink traffic for processing.

Everynet LNS - HTTP Connection

Be sure the Service comes ONLINE. Refresh the Status as needed.