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
  • Choosing the Right Decoder
Export as PDF
  1. Platform
  2. Functions

Decoder Function

Decoder Functions in Qubitro allow you to decode incoming payloads.

PreviousFunctionsNextLoRaWAN Device Template Decoder

Last updated 2 months ago

Overview

Decoder Functions in Qubitro allow you to decode incoming payloads before storing data.

Depending on your device type and data format, you can choose from different decoder options to ensure data is structured correctly.

Once a decoder function is created, it runs automatically for incoming data without requiring manual activation.

If needed, the function can be disabled from the functions list under the device’s Functions tab without deleting it.

Choosing the Right Decoder

Qubitro provides three types of decoders, each suited for different integration needs:

LoRaWAN Device Template Decoder

Use this option if your LoRaWAN device has a predefined template in Qubitro. It allows you to automatically decode incoming payloads without writing custom logic.

If you use the LoRaWAN Device Template Decoder, device templates for dashboards will work automatically, enabling instant visualization of decoded data.

LoRaWAN Custom Device Decoder

Use this option if your LoRaWAN device does not have a predefined template. You can write custom JavaScript to decode payloads manually.

HEX Payload Decoder

Use this option if your device sends data in hex-encoded format instead of JSON. It converts hex-encoded strings into structured JSON.

Works with non-LoRaWAN devices, including , , , and more.

LoRaWAN Device Template Decoder
LoRaWAN Custom Decoder
MQTT
HTTP
Onomondo
Hex Payload Decoder