The relayr MQTT Broker allows your IoT devices to communicate with the relayr Cloud using the MQTT protocol.
On the relayr broker, messages can be published with QoS
0 or 1. The data published to the broker can be raw JSON data or compressed gzip
JSON data for all topics.
Generated on Mon Oct 16 2023 15:54:57 GMT+0000 (Coordinated Universal Time)
MQTT broker ingestion
Username and password obtained from the Cloud MQTT endpoints
X.509 Certificate
MQTT broker ingestion
Username and password obtained from the Cloud MQTT endpoints
X.509 Certificate
Resource identifier
Accepts the following message:
Publish alert(s)
Optional alert message
Name of the alert defined in device-model
State of the alert (set/clear)
Date and time of the message. We don't store data with higher precision than millisecond. Measurements sent for the same millisecond will overwrite each other. If it is a "number" it should be Unix timestamp in milliseconds. If it is a string, it should be ISO 8601 format.
Additional items are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Publish command response(s)
Command identifier
Optional response message
Command status
Date and time of the message. We don't store data with higher precision than millisecond. Measurements sent for the same millisecond will overwrite each other. If it is a "number" it should be Unix timestamp in milliseconds. If it is a string, it should be ISO 8601 format.
Additional items are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Subscribe to device commands
Commands can be sent and executed on devices through the Cloud command import endpoint and command execution endpoint.
Device identifier
Command identifier
Name of the command defined in device-model
Parameter of the command (depending on device-model can be optional)
Additional properties are allowed.
Additional items are allowed.
Date and time of the message. We don't store data with higher precision than millisecond. Measurements sent for the same millisecond will overwrite each other. If it is a "number" it should be Unix timestamp in milliseconds. If it is a string, it should be ISO 8601 format.
Additional properties are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Publish configuration request
Date and time of the message. We don't store data with higher precision than millisecond. Measurements sent for the same millisecond will overwrite each other. If it is a "number" it should be Unix timestamp in milliseconds. If it is a string, it should be ISO 8601 format.
Additional items are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Publish configuration response(s)
Optional response message
Status of the configuration
Date and time of the message. We don't store data with higher precision than millisecond. Measurements sent for the same millisecond will overwrite each other. If it is a "number" it should be Unix timestamp in milliseconds. If it is a string, it should be ISO 8601 format.
Version of the configuration
Additional items are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Subscribe to device configurations
Configurations can be sent to devices through the Cloud configuration endpoints.
Payload of the configuration (any valid JSON)
Device identifier
Version of the configuration
Additional properties are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Subscribe to device errors
When malformed message is published it will be filtered out and rejected.
Reason for rejection can be obtained from the /errors topic.
Human-readable error message
Id of the message (for tracking purposes)
Payload of the message that caused the error (stringified)
Topic to which the malformed message was sent
Additional properties are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Publish configuration response(s)
Installation identifier
Optional response message
Status of the installation
Date and time of the message. We don't store data with higher precision than millisecond. Measurements sent for the same millisecond will overwrite each other. If it is a "number" it should be Unix timestamp in milliseconds. If it is a string, it should be ISO 8601 format.
Additional items are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Subscribe to device installations
Installations can be sent to devices through the Cloud software installation endpoints.
a build stamp of the software to be installed
Optional file description
Device identifier
Name of the installation file
Installation identifier
Location (url) of the installation file
Signature of the installation file
Type of the file signature
Size of the installation file (bytes)
Date and time of the message. We don't store data with higher precision than millisecond. Measurements sent for the same millisecond will overwrite each other. If it is a "number" it should be Unix timestamp in milliseconds. If it is a string, it should be ISO 8601 format.
Type of the installation file
Additional properties are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Location of the device
Device location is received from the device through MQTT and published to Kafka. Location service receives the Kafka message and updates the device location.
address of device location
city of device location
Country code from ISO 3166-1 alpha-2 standard
number of degrees north
number of degrees east
Date and time of the message. We don't store data with higher precision than millisecond. Measurements sent for the same millisecond will overwrite each other. If it is a "number" it should be Unix timestamp in milliseconds. If it is a string, it should be ISO 8601 format.
zipCode of device location
Additional items are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Publish device log(s)
Level of log severity (0 - 5) 5 = trace 4 = debug 3 = minor 2 = major 1 = error 0 = critical
Log message
Date and time of the message. We don't store data with higher precision than millisecond. Measurements sent for the same millisecond will overwrite each other. If it is a "number" it should be Unix timestamp in milliseconds. If it is a string, it should be ISO 8601 format.
Additional items are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.
Resource identifier
Accepts the following message:
Publish measurement(s)
Measurements are sent in an array which contains one or more measurements for a single device. Measurements must be defined in the device model version.
Name of the measurement defined in device-model
Date and time of the message. We don't store data with higher precision than millisecond. Measurements sent for the same millisecond will overwrite each other. If it is a "number" it should be Unix timestamp in milliseconds. If it is a string, it should be ISO 8601 format.
Value of the measurement
Additional items are allowed.
Quality of Service (0 - 1)
Additional properties are allowed.