Qubitro has no-code source integration support for LoRaWAN™ network server providers.

The integration allows you to synchronize devices and ingest sensor data into Qubitro. There are standard and server-specific feature offerings built in.

Reference Guide

Payload Formatters

Available Source Integrations

A Payload Formater takes a buffer as well as the port of the message and normalizes data on-the-fly to be stored.

Getting started

First, for Qubitro to be able to decode the data coming from integration, you need to create an uplink payload formatter. Payload formatter can be created on Qubitro.

The example uplink payload formatter is shown below.

function decodeUplink(input) {
  return {
    data: {
      temperature: input.bytes[0],
      humidity: input.bytes[1]
    }
  };
}

JavaScript Payload Formatter

Qubitro supports JavaScript payload formatter. You can find further documentation down below.

Examples

Once the payload formatter is set up correctly, it is possible to utilize all Qubitro features, including visualizing data and building custom applications with Qubitro APIs and make your life much easier.

You can find some of the examples and documentation down below.

Working with APIs

It is possible to utilize Qubitro APIs for various scenarios. Visit API documentation below to learn more.

Javascript payload formatters allow you to write your own functions to encode or decode messages. Javascript functions are executed using an JavaScript ECMAScript 5.1 engine.

Payload formatters use ECMAScript 5 (2009), which has some distinct differences compared to newer, commonly used ECMAScript revisions. See here for a quick comparison. Notably, let, const, and arrow functions are not supported by ES5.

There are three different types of Qubitro JavaScript payload formatters:

Read the documentations to further learn about these formatters and find associated examples.

Support and Feedback

If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.

The encodeDownlink() function is called when a downlink message, with a payload in JSON format, is scheduled to be sent to the end device. The encodeDownlink() function encodes the JSON object of the downlink message to binary payload that gets transmitted to the end device.

Downlink Encoder feature will be available soon in .

Support and Feedback

If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .

You can quickly and easily create your payload formatter with .

Creating Payload Formatter

To create a payload formetter for Uplink, select your device and choose the Formatter tab.

Validate Payload Formatter

You can validate your data under the Data tab.

The Javascript decodeUplink() function is called when a data uplink message is received from a device. This function decodes the binary payload received from the end device to a human-readable JSON object that gets send upstream to the application.

You only need these two requirements to make possible proper no-code integration. You can automatically synchronize the sensor values and other platform-specific information to visualize on .

An example function:

function decodeUplink(input) {
  return {
    data: {
      temperature: input.bytes[0],
      humidity: input.bytes[1]
    },
    warnings: [],
    errors: []
  };
}

Creating Payload Formatter

The decodeDownlink() function is called to decode a downlink message to JSON format, if it was scheduled with payload as bytes, or if it was scheduled with human-readable JSON payload but also was encoded with the encodeDownlink() function.

Downlink messages sent upstream as part of events or downlink queue operations are therefore decoded, just like uplink messages (see Uplink Decoder).

Downlink Decoder feature will be available soon in Qubitro Portal.

Support and Feedback

If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.

Working with Data

Once the payload formatter is set up correctly, it is possible to utilize all Qubitro features, including visualizing data and building custom applications with Qubitro APIs and make your life much more easier.

Visualizing Data

You can easily visualize your data with our widgets from the Monitoring section on the left side of our portal or under the Analytics tab in your project. Multiple charts are also can be added under a specific device.

Filtering your Data

Also, you can quickly filter your data by clicking the calendar under Data or Analytics.

Working with APIs

It is possible to utilize Qubitro APIs for various scenarios. Visit API documentation below to learn more.

Qubitro has no-code source integration support for Actility ThingPark.

Configure Source Integration

Get Credentials

1. Select a project from the left navigation menu and click New source at the top right of the toolbar.

2. Select ThingPark in the LoraWAN section and click Continue.

3. This is where you get the required credentials. Keep the popup open and go to the ThingPark console.

Configure ThingPark Connection

4. Select Qubitro from the ThingPark IoT Flow connections list.

5. Enter or paste credentials into the corresponding fields and click Create.

6. Select any device and click Add a Connection button and choose Qubitro connection.

Verify Integration

7. In the connections list, choose Qubitro integration. You can verify metrics and event logs.

8. On the project detail page, refresh the device list at the top right of the toolbar. Qubitro automatically provisions all devices that connection added on the ThingPark console.

Payload Formatting

If devices use the driver to convert bytes into JSON data, Qubitro automatically understands and stores by default.

Alternatively, Qubitro has built-in payload formatter support for non-formatted binary data.

Qubitro has no-code source integration support for Loriot.

Configure Source Integration

1. Select a project from the left navigation menu and click New source at the top right of the toolbar.

2. Select Loriot in the LoraWAN section and click Continue.

3. This is where you get the required credentials. Keep the popup open and go to the Loriot application.

Configure Loriot Output

4. Click Output on the left menu, click Add new output and choose HTTP Push.

5. Enter or paste credentials into the corresponding fields and click the Accept button.

Verify Integration

On the project detail page, refresh the device list at the top right of the toolbar. Qubitro automatically provisions the device that the notification target is enabled.

Payload Formatting

Qubitro has built-in payload formatter support for non-formatted binary data, and it is required for this source to work expediently.

Once you configure and save the payload formatter, click the Data tab and refresh the data table to observe decoded data.

, an open-source LoRaWAN® Network Server stack, provides open-source components for LoRaWAN networks.

This guide will help you integrate ChirpStack devices with Qubitro.

Getting started

You can easily integrate your ChirpStack devices with Qubitro in several steps. All you have to do is follow our guide steps.

Creating a Project

First, if you don't have any current project, you need to create a new one to get the Project ID and Webhook Signing Key. These two credentials are essential for our integration steps.

After logging in to our portal, click on the new project from the top left.

Getting Credentials

When you choose devices, make sure that you select ChirpStack.

Then there will be quick details about the integration process. After clicking continue, you will get credentials for your integration. You can easily copy it right away or find it under the credentials tab from the left bar any time you need it.

Add Integration on ChirpStack

Click on the Integrations tab under the project and click on ADD or EDIT button on the HTTP:// option.

Integration configuration

Marshaler type

Choose JSON under the Payload marshaler option.

Endpoint URL

Headers

Copy keys exactlypreciselyme as below and use values that you copied from Qubitro Portal.

Example screenshot

Payload Formatting

Qubitro supports converting binary data on the fly under the device page.

If you want to create payload formatters on the Qubitro end, visit the related page below.

combines powerful management tools with network server capabilities to accelerate moving data from IoT devices to the Internet over The People's Network.

Our integration with Helium Console synchronizes all devices and the device data automatically with no code.

Getting started

You can easily integrate your Helium Console devices with Qubitro in several steps. All you have to do is following the steps below.

Creating a Project

First, if you don't have any current project, you need to create a new one to get the Project ID and Webhook Signing Key. These two credentials are essential for our integration steps.

After logging in to our portal, click on the new project from the top left.

Getting Credentials

Click the + Add source button on the top right of the project. When you choose the source, make sure that you select Helium Console. Then click Continue.

You will get credentials for your integration. You can easily copy them right away or find them under the credentials tab from the left bar at any time.

Add Integration on Helium Console

Click on the Integrations in the pane on the left, then click Add New Integration button on top, then click on HTTP.

Scroll down to the Connection Details section, then copy & paste credentials onto the corresponding fields.

Refresh the device list and make sure all devices are synchronized.

Then you can customize the device information and work with the data.

Payload Formatting

Qubitro supports converting binary data on the fly under the device page.

If you want to create payload formatters on the Qubitro end, visit the related page below.

Qubitro has no-code source integration support for the Senet portal.

Configure Source Integration

1. Select a project from the left navigation menu and click New source at the top right of the toolbar.

2. Select Senet in the LoraWAN section and click Continue.

3. This is where you get the required credentials. Keep the popup open and go to the Senet Portal.

Configure Senet Notification Target

4. Click the settings icon under the navigation menu at the top right of the device and click the Notification Target tab. Choose Qubitro over Forward to menu.

6. Enter or paste credentials into the corresponding fields and click the Save button.

Verify Integration

On the project detail page, refresh the device list at the top right of the toolbar. Qubitro automatically provisions the device that the notification target is enabled.

Payload Formatting

Qubitro has built-in payload formatter support for non-formatted binary data, and it is required for this source to work expediently.

Qubitro has no-code source integration support for The Things Stack.

Configure Source Integration

1. Select a project from the left navigation menu and click New source at the top right of the toolbar.

2. Select The Things Stack in the LoraWAN section and click Continue.

3. This is where you get the required credentials. Keep the popup open and go to The Things Stack console.

Configure The Things Stack Integration

4. Click Webhooks from the left navigation menu and click Add webhook at the top right of the page.

5. Select Qubitro from the list.

6. Enter or paste credentials into the corresponding fields and click Create Qubitro webhook.

Verify Integration

On the project detail page, refresh the device list at the top right of the toolbar. Qubitro automatically provisions all devices that are added to The Things Stack project.

Payload Formatting

If the payload formatter is enabled on The Things Stack configuration, Qubitro automatically understands and stores the decoded payload by default.

Alternatively, Qubitro has built-in payload formatter support for non-formatted binary data.