MQTT V1 Integration
NOTE: that document describes version 2.0 (v2) of MQTT Integration. It contains extended list of configuration parameters.
-
Name
any unique Integration Name -
Type
Integration Type -
Data Converter
Name of the Data Converter which will be used to decode and encode payload of Devices provisioned to the current Integration. NOTE: Converter v2 is not available for use with Integration v1. -
Application address
MQTT Broker address. Domain name or IP -
Port
MQTT Broker Port -
Username/Token
provided by MQTT Broker -
Password
provided by MQTT Broker -
Push Topic
Topic where Network Server will publish UL messages -
Pull Topic
Topic on which Network Server will listen for DL messages -
Enable TLS
Enable or disable TLS / MQTTs -
Client ID
MQTT client ID
MQTT v3.1 → max len 23 symbols
MQTT v3.1.1 → max len 256 symbols -
Retry interval (seconds)
-
Send empty payload
If selected LoRa packet will be pushed to application via MQTT even if FRMPayload is empty -
Allow All Ports
Defines which LoRa ports can be used -
clientCertificate
clientCertificate can be:- passed as string
- drag-and-dropped
- uploaded file from PC
-
caCertificate
caCertificate can be:- passed as string
- drag-and-dropped
- uploaded file from PC
-
clientPrivateKey
clientPrivateKey can be:- passed as string
- drag-and-dropped
- uploaded file from PC
{
"647FDA00000000000": [
{
"ts": 1709215692677,
"values": {
"temperature": 23.2,
"humidity": 30.0,
"voltage": 2.95,
"nsGatewayCount": 2,
"nsGwId": "{gatewayId}",
"nsGateway": "{gatewayMac}",
"nsRssi": -109,
"nsFCount": 422,
"nsFPort": 10,
"nsRawPayload": "A1c16VKoCUD/OSv="
}
}
]
}
Please note: fields starting with ns
are default NS fields. The rest are custom fields, depending on the converter.
data - base64 encoded payload to be sent to the Device
{"device":"647FDA0000000000","data": {"params":{"data":"IA==", "port":100}}}