Qubitro Documentation
SupportLog inSign Up
  • Documentation
  • Guides
  • Developers
  • Welcome
  • Data Sources
    • No-Code Integrations
      • Onomondo
      • Notehub
      • The Things Stack
      • Soracom
      • Loriot
      • 1NCE
      • Golioth
      • AWS IoT Core LoRaWAN
      • Actility ThingPark
      • Chirpstack
      • Particle
    • MQTT
    • HTTP
  • Platform
    • Project
      • Settings
      • Access Management
      • Roles & Permissions
    • Device
      • Settings
    • Storage
      • Time Series Storage
    • Functions
      • Decoder Function
        • LoRaWAN Device Template Decoder
        • LoRaWAN Custom Decoder
        • Hex Payload Decoder
      • Transformation Function
      • Rule Function
        • Send Email
        • Webhooks
        • Slack
        • Twilio
        • Mailgun
        • SendGrid
      • Storage Function
        • AWS Redshift
        • Google BigQuery
        • MQTT Publish
        • MongoDB Time Series
      • Scheduled Function
        • HTTP
      • Function Settings
      • Function Templates
        • Settings
    • Monitoring
      • Dashboards
        • Setup & Configuration
        • Widgets
          • Chart
          • State Timeline
          • Gauge
          • Stat
          • Headline
          • Aggregated Chart
          • Map
          • Battery
          • Image
          • Image Map
          • Table
          • Storage Table
          • Iframe
          • Blob Storage
        • Settings
        • Access Management
        • Roles & Permission
      • Blueprints
        • Setup & Configuration
        • Settings
    • Credentials
      • API Keys
      • External Credentials
        • Slack
        • Mailgun
        • SendGrid
        • Twilio
        • AWS Redshift
        • MQTT
        • MongoDB
        • The Things Stack
      • Webhook Signing Key
  • Add-Ons
    • Storage Views
    • Aggregated View
    • Archived Views
    • Blob Storage
    • Managed Email
    • Audit Log
    • MCP Server
  • Organizations
    • Overview
    • General
    • Groups
    • Members & Roles
      • Read Only
      • Read/Write
      • Admin
    • Custom Roles
    • Add-Ons
    • Billing
    • Invoices
    • White-Label
  • Account Management
    • Personal Accounts
Powered by GitBook
On this page
  • Overview
  • Prerequisites
  • How It Works
  • Configuring the Integration
  • Configuring Data Decoding
  • FAQs
Export as PDF
  1. Data Sources
  2. No-Code Integrations

Loriot

The Qubitro and Loriot integration allows you to sync all devices and their data from Loriot.

PreviousSoracomNext1NCE

Last updated 1 month ago

Overview

The Qubitro and Loriot integration allows you to sync all devices and their data from Loriot directly to Qubitro—without writing any code.

Once your LoRaWAN devices are configured and sending data to Loriot, a corresponding device is automatically created in Qubitro, representing each device with its unique DevEUI.

As Loriot does not have built-in decoding functionality, Qubitro's Decoder Functions, including Device Templates, must be used to parse and structure incoming data. Additionally, Transformation Functions can be applied if modifications are needed before storing data in Qubitro.

This integration supports all LoRaWAN devices registered in Loriot.

This integration does not require additional device-side configuration. Data flows directly between Loriot and Qubitro without manual HTTP or MQTT forwarding.

Prerequisites

How It Works

Below is the diagram that shows how the integration works.

Configuring the Integration

1

Create an Integration in Qubitro

  1. Log in to the Qubitro Portal.

  2. Select a project from the list.

  3. Click New Source.

  4. Select Loriot from the available sources.

This page will display the Webhook URL and required headers for Loriot configuration. Keep it open for the next step.

2

Set Up Webhook Integration on Loriot

  1. Log in to the Loriot Console.

  2. Click Output from the left menu.

  3. Click Add new output and select HTTP Push.

Enter the following details provided by the Qubitro Portal:

Configuration Field
Value

Target URL for POSTs

(copied from Qubitro Portal)

Authorization header value

(copied from Qubitro Portal)

You can also copy these values individually from the Project Settings and Credentials tabs in Qubitro.

  1. Click Accept to save the webhook configuration.

3

Verify the Integration

  1. Return to the Qubitro Portal.

  2. Click Go to Project.

  3. Click Refresh and verify that your Loriot-connected devices appear.

  4. Select a device and navigate to the Data tab to confirm incoming data.

Configuring Data Decoding

Because Loriot does not have built-in decoding functionality, Qubitro's Decoder Functions must be configured.

Using Qubitro's Built-in Decoder Functions

Applying Transformation Functions

If additional modifications are required before storing data, enable Transformation Functions in Qubitro to dynamically process and modify payloads.

FAQs

Do I need to set up MQTT or HTTP forwarding in Loriot?

No. The integration works directly between Loriot and Qubitro using Webhooks. No additional forwarding setup is needed.

Do I need to send data directly from my device to Qubitro?

No. Once data is sent to Loriot, it is automatically forwarded to Qubitro via the webhook integration.

How is data decoded since Loriot does not have built-in decoders?
Can I group devices under different Qubitro projects?

Yes. You can create multiple integrations to separate devices across different projects.

Are there additional fees for this integration?

No. There are no hidden costs such as data transfer (egress) fees for using the Qubitro <-> Loriot integration.

Qubitro provides built-in , including , to automatically parse and structure incoming payloads.

Qubitro provides built-in , including , which parse incoming data before storage. You can also apply for further modifications.

Decoder Functions
Device Templates
Decoder Functions
Device Templates
Transformation Functions