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
  • FAQs
Export as PDF
  1. Data Sources
  2. No-Code Integrations

Actility ThingPark

The Qubitro and Actility (ThingPark) integration enables you to automatically sync LoRaWAN devices and their data from ThingPark to Qubitro.

PreviousAWS IoT Core LoRaWANNextChirpstack

Last updated 2 months ago

Overview

The Qubitro and Actility (ThingPark) integration enables you to automatically sync LoRaWAN devices and their data from ThingPark to Qubitro without writing any code.

When your devices send data to Actility (ThingPark), a corresponding device with its unique DevEUI is automatically created in Qubitro.

Qubitro automatically decodes incoming data. If additional modifications are necessary, Transformation Functions can be applied before storing the 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 The Things Stack and Qubitro without manual HTTP or MQTT forwarding.

Prerequisites

How It Works

If a Transformation Function is enabled, data will be processed before storage. Qubitro automatically applies built-in Decoder Functions, including Device Templates, and any defined Transformation Functions.

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 Actility from the available sources.

This page will display your PROJECT ID and WEBHOOK SIGNING KEY for Actility (ThingPark) configuration. Keep it open for the next step.

2

Set Up Actility (ThingPark) IoT Flow

  1. Log in to your Actility (ThingPark) Portal.

  2. Navigate to the Connections menu and click on Create.

  3. Choose Qubitro from the available IoT Flow connection options.

  4. Copy and paste the values provided in the previous step on the Qubitro Portal:

Field
Value

PROJECT ID

(copied from Qubitro Portal)

WEBHOOK SIGNING KEY

(copied from Qubitro Portal)

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

  1. Click on Create to complete the IoT Flow configuration.

3

Assign Connection to Devices

  1. Select a registered LoRaWAN device from your device list in the Actility Portal.

  2. Click the Add a Connection button.

  3. Select the newly created Qubitro integration connection from the list.

  4. Save the configuration.

4

Verify the Integration

  1. Return to the Qubitro Portal.

  2. Click Go to project.

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

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

FAQs

Do I need additional MQTT or HTTP forwarding for this integration?

No. Data flows automatically between Actility (ThingPark) and Qubitro without manual configuration.

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

No. Once data is sent to Actility (ThingPark), it is automatically forwarded to Qubitro via integration.

How is incoming data decoded?
Can I group devices under different Qubitro projects?

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

Are there additional fees associated with this integration?

No. There are no hidden costs or additional data transfer (egress) fees associated with the Qubitro <-> Actility integration.

Qubitro uses its built-in , including to decode the payloads. Additional can be applied as needed.

Decoder Functions
Device Templates
Transformation Functions