LogoLogo
Website
  • Overview
  • Getting started
  • Integrations
    • MQTT Integration
    • HTTPS Integration
    • LORIOT Integration
    • Swisscom LPN Integration
    • TheThingsNetwork Integration
    • TheThingsIndustries Integration
    • Sigfox Integration
    • AWS IoT Integration
    • AWS Kinesis Integration
    • Azure Event Hub Integration
    • Azure IoT Hub Integration
    • Helium Network Integration
  • Key concept
    • Entities and relations
    • Entity Groups
    • Attributes
    • Device Profiles
    • Telemetry data
    • Device alarms
    • Version control
  • Dashboards
    • Dashboards
      • Dashboard Templates
      • IAQ Template
      • Aliases
    • Widget library
      • Energy management widgets
        • Summarized annual consumption
        • Daily profile
        • XY chart
  • Rule Engine
    • Rule Engine
      • Rule Engine Templates
        • General data proccessing concept
        • Weather data feed
      • Test Javascript function
      • Predefined Message Types
      • Filter rule nodes
        • check alarm status
        • check existence fields
        • check relation
        • gps geofencing filter
        • message type filter
        • message type switch
        • originator type filter
        • originator type switch
        • script filter
        • switch script node
      • Enrichment rule nodes
        • calculate delta
        • customer attributes
        • customer details
        • originator attributes
        • originator fields
        • originator telemetry
        • related attributes
        • related Device attributes
        • tenant attributes
        • tenant details
      • Transformation rule nodes
        • change originator
        • duplicate to group
        • duplicate to related
        • script transformation
        • to email transformation
        • M-Bus decoder
      • Action rule nodes
        • Add to group
        • Remove from group
        • Generate report
        • Integration Downlink
        • REST Call Reply
        • Change owner
        • Create alarm
        • Clear alarm
        • Delay messages
        • Generator
        • Log
        • RPC Call Reply
        • RPC Call Request
        • GPS geofencing events
        • Save attributes
        • Math Function
        • Asset Profiles Feature
        • fetch device credentials
        • delete attributes
        • split array msg
        • json path
        • delete keys
        • rename keys
        • copy keys
        • Save to Custom
        • Assign To Customer
        • Unassign From Customer
        • Create Relation
        • Delete Relation
        • Push to cloud
        • Pus to edge
        • Save timeseries
      • Analytics rule nodes
        • Aggregate Latest
        • Aggregate Stream
        • Alarms Count
      • Output connectors
        • AWS SNS
        • AWS SQS
        • MQTT
        • RabbitMQ
        • Kafka
        • Azure IoT Hub
        • Rest API
        • Priva
          • Realtime Telemetry API
          • Realtime Setpoint API
          • Data Insight Metadata API
          • Data Insight History API
          • Alarm Data Api
        • SOAP API
        • send email
        • send SMS
        • send Twilio SMS
      • Flow
        • Acknowledge
        • Checkpoint
        • Rule Chain
        • Output
  • Device Type Library
    • telemetry data keys
    • attribute data keys
      • Assets
        • Property
          • Building
          • Floor
          • Room
        • Facility
          • Component
        • City Zone
      • Devices
    • relation Type keys
  • API documentation
    • Admin Controller
  • CLI Tool
    • How to install the tool
    • Dataimport
  • Dynamic QR Codes
    • Dynamic QR Code App
Powered by GitBook
On this page
  • Overview
  • Create LORIOT account
  • Create Uplink Converter
  • Example for the Uplink converter:
  • Create Integration
  • Send test Uplink message
  • Advanced Usage: Create Downlink Converter

Was this helpful?

  1. Integrations

LORIOT Integration

PreviousHTTPS IntegrationNextSwisscom LPN Integration

Last updated 2 years ago

Was this helpful?

Overview

LORIOT is LoRaWAN network designed for connecting your devices using LoRaWAN stack. After integrating LORIOT with the Tesenso IoT Cloud, you can connect, communicate, process and visualize data from devices in the Tesenso IoT Cloud.

Create LORIOT account

Choosing a package of services and server location. Then we register an account with LORIOT. For example, select the community public network server.

The LORIOT interface may change in the future.

Fill in the registration fields. The registration confirmation letter will be sent to the specified email. Follow the specified link.

Create Uplink Converter

Before creating the integration, you need to create an Uplink converter in Data converters. Uplink is necessary in order to convert the incoming data from the device into the required format for displaying them in Tesenso IoT Cloud. Click on the “plus” and on “Create new converter”. To view the events, enable Debug. In the function decoder field, specify a script to parse and transform data.

NOTE Although the Debug mode is very useful for development and troubleshooting, leaving it enabled in production mode may tremendously increase the disk space, used by the database, because all the debugging data is stored there. It is highly recommended to turn the Debug mode off when done debugging.

Let’s review sample uplink message from LORIOT:

{
     "cmd"  : "rx",
     "EUI"  : "BE7A000000000552",
     "ts"   : 1470850675433,
     "ack"  : false,
     "fcnt" : 1,
     "port" : 1,
     "data" : "2A3F",
     "freq" : 868500000,
     "dr"   : "SF12 BW125 4/5",
     "rssi" : -130,
     "snr"  : 1.2
 }

As you can see the unique device id arrives in the “EUI” field. We will use it as a device name in Tesenso IoT Cloud. Device data is encoded in the “data” field. The encoded data here is:

"data": "2A3F"

Let’s convert them into temperature and humidity values.

2A is the value for temperature. In decoded form it will be 42

3F is the value for humidity. In decoded form it will be 63

In the converter it will be indicated like this:

temperature: stringToInt(payloadJson.data.substring(0,2)),
humidity: stringToInt(payloadJson.data.substring(2,4))

Example for the Uplink converter:

// V1.0, 11.08.2021, DS

/** Decoder **/

// decode payload to string and json and parse it to data
var payloadJson = decodeToJson(payload);
var dataJson = selectData(payloadJson);

var deviceName = payloadJson.EUI; 

// Result object with device/asset attributes/telemetry data
var result = {
    // Use deviceName and deviceType or assetName and assetType, but not both.
    deviceName: deviceName,
    //deviceType: deviceType,
    // assetName: assetName,
    // assetType: assetType,
    //   customerName: customerName,
    //   groupName: groupName,
    attributes: dataJson.attributes,
    telemetry: dataJson.telemetry
};


function selectData(payloadJson) {
    // TODO: Make this work for all LPN
    if (payloadJson.cmd == 'rx') {
        var decoded = {
            'telemetry':{},
            'attributes':{}
        }
        decoded.telemetry.ts = payloadJson.ts;
        decoded.telemetry.rssi = payloadJson.rssi;
        //decoded.telemetry.snr = payloadJson.snr;
        //decoded.telemetry.toa = payloadJson.toa;
        //decoded.telemetry.frequency = payloadJson.freq;
        decoded.telemetry.dr = payloadJson.dr;
        decoded.telemetry.data = payloadJson.data;
        decoded.telemetry.port = payloadJson.port;
        decoded.telemetry.bat = payloadJson.bat;
        return decoded;
    } else {
        return {};
    }
}

function decodeToString(payload) {
    return String.fromCharCode.apply(String, payload);
}

function decodeToJson(payload) {
    // covert payload to string.
    var str = decodeToString(payload);
    // parse string to JSON
    var data = JSON.parse(str);
    return data;
}

// console.log(result);
return result;

You can change the decoder function while creating the converter or after creating it. If the converter has already been created, then click on the “pencil” icon to edit it. Copy the configuration example for the converter (or your own configuration) and insert it into the decoder function. Save changes by clicking on the “checkmark” icon

Create Integration

Now that the Uplink converter has been created, it is possible to create an integration

In order for data to be transferred from LORIOT to Tesenso IoT Cloud, you need to configure an Output for your LORIOT application. You can do this manually (recommended) or Tesenso IoT Cloud Integration can do this for you (you will need to specify login and password from your LORIOT account for us to be able to automatically provision the output). Configuration the Output options

We can create Output with LORIOT or in integration by enabling the Create Loriot Application output option or specifying the “Basic” credential. LORIOT Account RecommendedBasic Credential

Then we select HTTP Push and specify the target, which is taken from the integration.

Enable security option

If necessary, you can specify additional parameters, without which the data will not be included in the integration. To do this, check the Enable security checkbox and click on the Headers filter. Specify an arbitrary value and save the changes.

Also need to specify this in LORIOT:

Once the Headers filter has been configured, it will also need to be specified in the uplink message as follows. Replace $VALUE with corresponding value.

-H “Authorization:$VALUE”

Send test Uplink message

It may be useful to “emulate” the message from device using console instead of the LORIOT server. To send an uplink message, you need a HTTP endpoint URL from the integration, port and EUI from LORIOT.

Let`s go to the Integrations tab in Tesenso IoT Cloud. Find your LORIOT integration and click on it. There you can find the HTTP endpoint URL. Click on the icon to copy the url

A port can be from 1 to 223. EUI is device EUI and is taken from the device in LORIOT.

Use this command to send message. Replace $YOUR_EUI_DEVICE and $YOUR_HTTP_ENDPOINT_URL with corresponding values.

curl -v -X POST -d "{\"EUI\":\"$YOUR_EUI_DEVICE\",\"deviceType\":\"temperature-sensor\",\"data\":\"2A3F\",\"port\":1,\"cmd\":\"rx\",\"dr\":\"SF12 BW125 4/5\",\"snr\":1.2,\"ack\":\"false\",\"freq\":868500000,\"fcnt\":1,\"rssi\":-130,\"ts\":1613745998000}" $YOUR_HTTP_ENDPOINT_URL -H "Content-Type:application/json"

With the enable security option: replace $YOUR_EUI_DEVICE, $YOUR_HTTP_ENDPOINT_URL and $VALUE with corresponding values.

curl -v -X POST -d "{\"EUI\":\"$YOUR_EUI_DEVICE\",\"deviceType\":\"temperature-sensor\",\"data\":\"2A3F\",\"port\":1,\"cmd\":\"rx\",\"dr\":\"SF12 BW125 4/5\",\"snr\":1.2,\"ack\":\"false\",\"freq\":868500000,\"fcnt\":1,\"rssi\":-130,\"ts\":1613745998000}" $YOUR_HTTP_ENDPOINT_URL -H "Content-Type:application/json" -H “Authorization:$VALUE

The created device with data can be seen in the section Device groups -> Al

Received data can be viewed in the Uplink converter. In the “In” and “Out” blocks of the Events tab.

Use the Dashboards to work with data. Dashboards are a modern format for collecting and visualizing data sets. Visibility of data presentation is achieved through a variety of widgets.

How to work with dashboards read here

Advanced Usage: Create Downlink Converter

Create Downlink in Data converters. To see events - enable Debug

You can customize the downlink according to your configuration. Let’s consider an example where we send an attribute update message. So we should change code in the downlink encoder function under line //downlink data input

data: msg.firmware

Also, indicate the required parameters in the metadata:

metadata: {
  "EUI": "$Device_EUI",
  "port": 1
}

Example for downlink converter:

// Encode downlink data from incoming Rule Engine message
// msg - JSON message payload downlink message json
// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
// metadata - list of key-value pairs with additional data about the message
// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
// Result object with encoded downlink payload
var result = {
    // downlink data content type: JSON, TEXT or BINARY (base64 format)
    contentType: "TEXT",
    // downlink data
    data: msg.firmware,
    // Optional metadata object presented in key/value format
    metadata: {
            "EUI": "BE7A000000000552",
            "port": 1
    }
};
return result;

where EUI is device EUI and is taken from the device in LORIOT. A port can be from 1 to 22

Add a converter to the integration. You can do this at the stage of creating an integration or editing it.

To send Downlink, enable the Send downlink option in the integration. Once we enable the “Send downlink” option, specify the Server, Application ID, Application Access Token in the fields

To get this data - go to your account in LORIOT.

Data to fill in the Server field = tesenso.loriot.io

Data to fill in the Application ID field

After that, go to Application and go to the Access Tokens section. Find the token that will be specified in the integration.

In LORIOT go to the Output menu and click on Add new output.

Get EUI in LORIOT in the Devices section, where the devices have already been created:

Get EUI in LORIOT in the Devices section, where the devices have already been created:

2KB
loriot_converter_all_in_one.json
Page cover image
image
image
image
image
image
image
image