MQTT

Qubitro provides a TLS-enabled, fully-managed MQTT broker with TLS encryption which allows both subscription and recording of data.

Connecting to the Broker

Description

Value

Host

broker.qubitro.com

Development/Test port

1883

Production port

8883

Depending on the client library, a URL format may vary.

Example: tcp://broker.qubitro.com - tls://broker.qubitro.com or broker.qubitro.com

Authentication

Qubitro offers a customized Username and Password authentication. 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.

Description

Value

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.

Client ID

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 set with the same value of Device ID.

Description

Value

Client ID

Device ID

Quality of Service (QoS)

The MQTT specification describes three Quality of Service (QoS) levels

Description

Value

QoS 0

Delivered at most once

QoS 1

Delivered at least once

QoS 2

Delivered exactly once

Qubitro has support for all QoS options but the default options always 0 unless specified during the connection.

Data Structure

Qubitro currently has support for key-value paired JSON objects as the data type. Nested values are not supported yet.

{
"Key1" : "Value1",
"Key2" : true,
"Key3" : 90
...
}