Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Qubitro Loriot source integration.
Qubitro has no-code source integration support for Loriot.
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.
You can access the webhook signing key and project id from the API Keys page and project settings tab, respectively.
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.
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.
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.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
Twilio is a cloud-based communication platform that enables developers to build, scale, and operate communication applications using a variety of channels, including voice, SMS, and chat. It provides APIs and pre-built libraries for popular programming languages, as well as a range of tools for managing and analyzing communication data.
You must create a Twilio Account. After you create your new account, get your credentials for Qubitro.
You have to go to Credentials in Qubitro Portal. Create a new credential and choose Twilio. Fill in all the requirements.
Go to your Device on Qubitro Portal and choose Rules. When you go to create a new rule, choose Twilio.
Once you fill in the requirements, you have to configure your trigger event, and then all done.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
Output connectors will be available soon.
Qubitro REST API
The Qubitro REST API lets you programmatically access device data and manage resources on Qubitro Portal using conventional HTTP requests.
The available endpoints may differ from available actions on Qubitro Portal and offer more flexibility if any.
Qubitro Data Payload reference guide.
Qubitro supports any valid JSON data format to be stored and accessed via REST APIs, MQTT topics, or WebSocket API.
However, some features, such as Dashboards and Rule Actions, work only with key-value JSON structured data payloads. JSON strings with nested JSON Objects are not supported for Portal features.
Publish key-value structured JSON data payloads when possible for better compatibility.
Strip out extraneous information. Publish data as compactly as possible, whether JSON or Binary data.
Use shorter key names.
Be careful with naming. Qubitro is key-sensitive. Temperature is not equal to temperature.
Qubitro LoRaWAN™ platform sources.
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.
Qubitro creates and synchronizes all devices when the first Uplink message is received.
Binary Data Payload reference guide.
Qubitro supports binary payload conversion with payload formatters for LoRaWAN data source integrations. Payload Formatters allows you to write your custom payload formatters in JavaScript.
JSON Data Payload reference guide.
The data published to the Qubitro must be a JSON string following the JSON notation.
An example JSON string:
or
Keys must be strings, and values must be valid JSON data types following String,
Number,
Object,
Array,
Boolean,
or Null
.
Valid and %100 compatible.
Each key is automatically separated into a column with corresponding values.
Valid but not %100 compatible.
Each key is automatically separated into a column with corresponding values; however, because SensorReadings is a nested JSON Object, Temperature and Humidity keys cannot be parsed into a correct column.
Payload Formatter for LoRaWAN™ platform sources.
A Payload Formater takes a buffer as well as the port of the message and normalizes data on-the-fly to be stored.
Device payload formatters allow you to specify a unique payload formatter for each device.
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.
The returned value must be a JSON object with the 'data' key.
Qubitro supports JavaScript payload formatter. You can find further documentation down below.
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.
It is possible to utilize Qubitro APIs for various scenarios. Visit API documentation below to learn more.
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.
The returned value must be a JSON object with the 'data' key and the function name must be 'decodeUplink' with a single parameter.
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 Qubitro Portal.
An example function:
You can quickly and easily create your payload formatter with Qubitro Portal.
To create a payload formetter for Uplink, select your device and choose the Formatter tab.
The function name must be 'decodeUplink' and must accept only a single parameter.
You can validate your data under the Data tab.
An introduction to the Qubitro device data platform.
💎 Qubitro is a Device Data Platform (DDP) built for a hyper-connected world.
💡 Learn more about Qubitro on our website.
In Qubitro, you can connect a source (or more than one!) to the same or different project for each platform or connectivity option you want to ingest data from.
In case the source is not yet supported on Qubitro Portal, consider sharing feedback.
If the action or connector is not yet supported on Qubitro Portal, consider sharing feedback.
See https://qubitro.com/resources/ for a complete list of knowledge resources and support options.
Qubitro ThingPark integration.
Qubitro has no-code source integration support for Actility ThingPark.
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.
You can access the webhook signing key and project id from the API Keys page and project settings tab, respectively.
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.
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.
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.
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.
The payload formatters should be simple and lightweight.
There are three different types of Qubitro JavaScript payload formatters:
The payload formatters should be simple and lightweight.
Read the documentations to further learn about these formatters and find associated examples.
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.
You can find some examples for utilizing features and 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.
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.
Also, you can quickly filter your data by clicking the calendar under Data or Analytics.
It is possible to utilize Qubitro APIs for various scenarios. Visit API documentation below to learn more.
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.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
Payload formatters use ECMAScript 5 (2009), which has some distinct differences compared to newer, commonly used ECMAScript revisions. See for a quick comparison. Notably, let
, const
, and arrow functions are not supported by ES5.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
Downlink Encoder feature will be available soon in .
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
Downlink messages sent upstream as part of events or downlink queue operations are therefore decoded, just like uplink messages (see ).
Downlink Decoder feature will be available soon in .
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
Qubitro and Chirpstack integration.
ChirpStack, an open-source LoRaWAN® Network Server stack, provides open-source components for LoRaWAN networks.
This guide will help you integrate ChirpStack devices with Qubitro.
You can easily integrate your ChirpStack devices with Qubitro in several steps. All you have to do is follow our guide steps.
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.
If you already have a project, you can get your credentials under the Settings tab.
After logging in to our portal, click on the new project from the top left.
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.
Click on the Integrations tab under the project and click on ADD or EDIT button on the HTTP:// option.
Choose JSON under the Payload marshaler option.
The endpoint URL is https://webhook.qubitro.com/integrations/chirpstack
Copy keys exactlypreciselyme as below and use values that you copied from Qubitro Portal.
Example screenshot
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.
The Toit Qubitro MQTT connector package.
1. Select a project from the left navigation menu and click New source at the top right of the toolbar.
2. Select Toit in the MQTT section and click Continue.
3. Enter the information of your choice and click Continue.
4. This is where you get the required credentials. You can use the provided sample code or pass the credentials to your custom code.
Run the following CLI command to install the Toit Qubitro connector.
Qubitro expects key-value JSON formatted data for this source.
Qubitro provides a scalable, distributed, and fully-featured MQTT broker and does support all the behaviors specified in the MQTT v5.0, v3.1.1, and v.3.1 standards.
You can jump to client libraries and examples below if you are familiar with the MQTT libraries.
We strongly recommend using the 8883 port for MQTT over TLS connectivity.
Depending on the client library, a URL format may vary. Check our examples or contact us if you need help with the URL naming convention.
Any MQTT client library that supports username-password authentication can be used to connect Qubitro.
The client identifier (Client ID) identifies each MQTT client that connects to an MQTT broker.
Qubitro does not manage client IDs internally therefore client ID must be set with the same value as the device ID.
The MQTT specification describes three Quality of Service (QoS) levels. Qubitro has support for all QoS options ,but the default options are always 0 unless specified during the connection.
Qubitro currently has support for key-value paired JSON objects as the data type. Nested values are not supported yet.
Key | Value |
---|---|
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
The offers built-in security and an enhanced MQTT connectivity experience.
The is the best starting point for your projects.
If you need to work with binary data, reach our team to share your .
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
Example: - or
Device ID and Device Token are both unique, generated automatically, and located under the device settings tab in .
Qubitro offers customized MQTT libraries for some languages and platforms in which username and password methods are replaced with proper method names. Example: See client.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
projectId
Project ID
webhookSigningKey
Signing Key
Description | Value |
Host | broker.qubitro.com |
Secure port | 8883 |
Insecure port (for test purpose) | 1883 |
Value Name | Qubitro Equivalent |
Username | Device ID |
Password | Device Token |
Value Name | Qubitro Equivalent |
Client ID | Device ID |
Value Name | Description |
QoS 0 | Delivered at most once |
QoS 1 | Delivered at least once |
QoS 2 | Delivered exactly once |
Arduino is an open-source electronics platform based on easy-to-use hardware and software. Connect Arduino-based boards with the Qubitro MQTT package.
The Arduino Nano 33 IoT is Arduino's smallest board to get started with Internet of Things (IoT). Using the popular Arm® Cortex®-M0 32-bit SAMD21 processor, it also features the powerful u-blox NINA-W102 Wi-Fi module and the ECC608A crypto-chip for security.
The MKR WiFi 1010 is a great choice for any beginner, maker or professional to get started with Internet of Things (IoT).Using the popular Arm® Cortex®-M0 32-bit SAMD21 processor, it also features the and the ECC508 crypto-chip for security.
The MKR 1000 WiFi is a great choice for any beginner, maker or professional to get started with Internet of Things (IoT). Using the popular Arm® Cortex®-M0 32-bit SAMD21 processor, it also features the and the ECC508 crypto-chip for security.
Qubitro Senet source integration.
Qubitro has no-code source integration support for the Senet portal.
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.
You can access the webhook signing key and project id from the API Keys page and project settings tab, respectively.
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.
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.
Qubitro has built-in payload formatter support for non-formatted binary data, and it is required for this source to work expediently.
Qubitro and Helium Console integration.
Our integration with Helium Console synchronizes all devices and the device data automatically with no code.
You can easily integrate your Helium Console devices with Qubitro in several steps. All you have to do is following the steps below.
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.
You can get your credentials under the Settings tab if you already have a project.
After logging in to our portal, click on the new project from the top left.
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.
Keep this page open and jump to the Helium Console for faster integration.
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.
Qubitro supports converting binary data on the fly under the device page.
If payload formatting is enabled on Helium Console, Qubitro automatically understands JSON format and can store data without additional payload formatting.
If you want to create payload formatters on the Qubitro end, visit the related page below.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
combines powerful management tools with network server capabilities to accelerate moving data from IoT devices to the Internet over The People's Network.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
Various libraries for MQTT installation.
MQTT client libraries from various programming languages for introduction and description and provides basic function code examples for connecting, publishing, and subscribing.
We have libraries for the following languages:
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.