Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Before getting started, make sure that required libraries are installed by visiting the setup page
Include the required libraries and define objects on top of the page.
Define the required variables.
Qubitro currently has support for key-value paired JSON objects as a data type. Nested values are not supported yet.
An example : "{\"Temp\":33}"
Set client id for identification
Set device id and token for authentication
Connect to the Qubitro broker
Subscribe to the topic
Set onMessage method to listen subscribed topic
Publish data to the subscribed topic
Print whenever message received
The following example :
Connects to the broker
Subscribes to the topic (the device itself in this example)
Publishes data in a loop with a delay of 2 seconds.
Prints message and subscribed topic (the device itself in this example)
Example output:
Before getting started, make sure that required libraries are installed by visiting the setup page
Include the required libraries and define objects on top of the page.
Define the required variables.
Qubitro currently has support for key-value paired JSON objects as a data type. Nested values are not supported yet.
An example : "{\"Temp\":33}"
Set client id for identification
Set device id and token for authentication
Connect to the Qubitro broker
Subscribe to the topic
Set onMessage method to listen subscribed topic
Publish data to the subscribed topic
Print whenever message received
The following example :
Connects to the broker
Subscribes to the topic (the device itself in this example)
Publishes data in a loop with a delay of 2 seconds.
Prints message and subscribed topic (the device itself in this example)
Example output:
Before getting started, make sure that required libraries are installed by visiting the setup page
Include the required libraries and define objects on top of the page.
Define the required variables.
Qubitro currently has support for key-value paired JSON objects as a data type. Nested values are not supported yet.
An example : "{\"Temp\":33}"
Set client id for identification
Set device id and token for authentication
Connect to the Qubitro broker
Subscribe to the topic
Set onMessage method to listen subscribed topic
Publish data to the subscribed topic
Print whenever message received
The following example :
Connects to the broker
Subscribes to the topic (the device itself in this example)
Publishes data in a loop with a delay of 2 seconds.
Prints message and subscribed topic (the device itself in this example)
Example output:
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.
Description
Value
Host
broker.qubitro.com
Secure port
8883
Insecure port (for test purpose)
1883
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.
Example: tcp://broker.qubitro.com - tls://broker.qubitro.com or broker.qubitro.com
Any MQTT client library that supports username-password authentication can be used to connect Qubitro.
Device ID and Device Token are both unique, generated automatically, and located under the device settings tab in Qubitro Portal.
Value Name
Qubitro Equivalent
Username
Device ID
Password
Device Token
Qubitro offers customized MQTT libraries for some languages and platforms in which username and password methods are replaced with proper method names. Example: See Ruby client.
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.
Value Name
Qubitro Equivalent
Client ID
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.
Value Name
Description
QoS 0
Delivered at most once
QoS 1
Delivered at least once
QoS 2
Delivered exactly once
Qubitro currently has support for key-value paired JSON objects as the data type. Nested values are not supported yet.
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 .
The Toit Qubitro MQTT connector package.
The offers built-in security and an enhanced MQTT connectivity experience.
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.
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.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
Connect ESP32-based boards with the Qubitro MQTT package.
This example uses that offers a custom naming convention for easier development. It is possible to use any 3rd party MQTT Client with the following requirements.
For example, it is possible to use the library to connect MQTT over TLS with 8883 port.
The helpful naming conventions for 3rd party MQTT libraries.
The following code connects to your wireless network, generates simulated sensor values, and publishes them to the Qubitro.
Example output:
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 .
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 invitation link.
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 .
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this .
Quick guide for Go library.
Visit the MQTT overview page for conventions, authentication, and more information.
This documentation uses the Paho MQTT
library. This library is open-source, so you can check it on GitHub.
Installing the packages
Then import it and initialize it with the required packages. Of course, you’ll want to replace DEVICE_ID
and DEVICE_TOKEN
with your actual device credentials which you can find under your device settings on Qubitro Portal.
Add the following code to the top of your page
Define callbacks depending on your scenario.
See the examples below or visit the package documentation.
We strongly recommend using the 8883 port for MQTT over TLS connectivity.
Value Name
Qubitro Equivalent
User Name
Device ID
User Password
Device Token
Client ID
Device ID
Production port
8883
Development/Test port
1883
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
Quick guide for Ruby library.
Visit the MQTT overview page for conventions, authentication, and more information.
This library is open-source so you can check it out on GitHub.
Install the packages
Then import it and initialize it with the required packages. Of course, you’ll want to replace DEVICE_ID
and DEVICE_TOKEN
with your actual device credentials which you can find under your device settings on Qubitro Portal.
Minimum configuration required to connect to the broker.
We strongly recommend using the 8883 port for MQTT over TLS connectivity.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
Quick guide for C library.
Visit the MQTT overview page for conventions, authentication, and more information.
This documentation uses the Paho MQTT
library. This library is open-source, so you can check it out on GitHub.
Install the packages
Set client options and connect to the broker.
Publish data:
Optional: Close the connection to the broker:
We strongly recommend using the 8883 port for MQTT over TLS connectivity.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
Quick guide for JavaScript library.
Visit the MQTT overview page for conventions, authentication, and more information.
This documentation uses npm MQTT library. This library is open-source, so you can check it out on GitHub.
Install the packages
Import libraries
Then import it and initialize it with the required packages. Of course, you’ll want to replace DEVICE_ID
and DEVICE_TOKEN
with your actual device credentials which you can find under your device settings on Qubitro Portal.
We strongly recommend using the 8883 port for MQTT over TLS connectivity.
An example of publishing data.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
Quick guide for Pyhton library.
Visit the MQTT overview page for conventions, authentication, and more information.
This documentation uses the Paho MQTT
library. This library is open-source, so that you can check it out on GitHub.
Then import it and initialize it with the required packages. Of course, you’ll want to replace DEVICE_ID
and DEVICE_TOKEN
with your actual device credentials which you can find under your device settings on Qubitro Portal.
We strongly recommend using the 8883 port for MQTT over TLS connectivity.
An example of publishing data.
An example of subscribing to a topic and receiving the message.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.
Quick guide for Rust library.
Visit the MQTT overview page for conventions, authentication, and more information.
This documentation uses the Paho MQTT
library. This library is open-source, so you can check it out on GitHub.
Install the packages
Then import it and initialize it with the required packages. Of course, you’ll want to replace DEVICE_ID
and DEVICE_TOKEN
with your actual device credentials which you can find under your device settings on Qubitro Portal.
Client Options:
MQTT Client:
We strongly recommend using the 8883 port for MQTT over TLS connectivity.
If you have further questions or suggestions, feel free to join -> Qubitro Community Discord via this invitation link.