Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 156.1
edited by Dilisi S
on 2025/03/17 00:34
Change comment: Uploaded new attachment "mqtt-uplink.png", version {1}
To version 196.1
edited by Dilisi S
on 2025/03/31 12:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -67,7 +67,6 @@
67 67  [[image:thingsboard-6.png||height="244" width="500"]]
68 68  
69 69  
70 -(% class="wikigeneratedid" %)
71 71  == 2.2 HiveMQ Cloud ==
72 72  
73 73  === 2.2.1 HiveMQ Cloud ===
... ... @@ -165,145 +165,142 @@
165 165  [[image:ins1.png||height="310" width="500"]]
166 166  
167 167  
168 -= 3. Data Converters =
167 += 3. Creating Devices (Optional) =
169 169  
169 +{{info}}
170 +**The following procedure is optional. If you haven't created any device in ThingsBoard first, ThingsBoard will automatically create a device for you based on the integration settings (the device name defined in the uplink decoder) just after it receives the first uplink from your device.Type your information message here.**
171 +{{/info}}
170 170  
171 -In **ThingsBoard**, **Data Converters** are components used to transform incoming or outgoing data between different formats, typically to convert raw telemetry data from devices into a structured format that ThingsBoard can understand, or vice versa.
173 +First, you need to create devices in ThingsBoard to represent your physical devices. For example, you can name it **Device A**, and the second device could be **Device B** or any name you prefer. The device name should be unique within the **Devices** space.
172 172  
173 173  
174 -== 3.1 Uplink ==
176 +In the left navigation, click **Entities -> Devices**.
175 175  
178 +Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
176 176  
177 -In the left navigation, click **Integrations center**, and then click **Data converters**.
180 +In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
178 178  
182 +Click the **Add** button.
179 179  
184 +Skip the **connectivity testing** by clicking the **Close** button.
180 180  
181 -[[image:data-converters-list-empty.png]]
186 +The device is created and listed on the **Devices** page. Note that its initial state is **Inactive** because it has not received any data yet.
182 182  
183 183  
184 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
189 += 4. Data Converters =
185 185  
186 186  
192 +In **ThingsBoard**, **Data Converters** are components used to transform incoming or outgoing data between different formats, typically to convert raw telemetry data from devices into a structured format that ThingsBoard can understand, or vice versa.
187 187  
188 -[[image:create-new-converter-menu.png||height="259" width="500"]]
189 189  
195 +== 4.1 Uplink ==
190 190  
191 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
192 192  
193 -Click on the **TBEL** button if not selected it by default. Delete the existing decoder function in the code editor. Now copy and paste the following decoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
198 +In the left navigation, click **Integrations center**, and then click **Data converters**.
194 194  
195 -{{code language="JavaScript"}}
196 -/** Decoder **/
197 197  
198 -// decode payload to string
199 -var payloadStr = decodeToString(payload);
200 -var data = JSON.parse(payloadStr);
201 +[[image:data-converters-list-empty.png]]
201 201  
202 -var deviceName = metadata.topic.split("/")[3];
203 -// decode payload to JSON
204 -var deviceType = 'sensor';
205 205  
206 -// Result object with device attributes/telemetry data
207 -var result = {
208 - deviceName: deviceName,
209 - deviceType: deviceType,
210 - attributes: {
211 - integrationName: metadata['integrationName'],
212 - },
213 - telemetry: {
214 - temperature: data.temperature,
215 - humidity: data.humidity,
216 - }
217 -};
204 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
218 218  
219 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
220 220  
221 -return result;
222 -{{/code}}
223 223  
208 +[[image:create-new-converter-menu.png||height="259" width="500"]]
224 224  
225 -Click on the **Add** button.
226 226  
211 +The **Add data converter** window will appear.
227 227  
213 +Let's create an uplink data converter for the device named '**Device A**'. Name it ‘**MQTT Uplink Converter - Device A**’ and select the Type as **Uplink**.
228 228  
229 -[[image:add-uplink-data-converter.png||height="529" width="500"]]
215 +Click on the **TBEL** button if it has not been selected by default.
230 230  
217 +Modify the default TBEL function to match with your device as described below:
231 231  
232 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
233 233  
234 -[[image:data-converter-list-showing-uplink-dc.png]]
220 +* Uncomment** line 11**:
235 235  
222 +//var data = decodeToJson(payload)//
236 236  
237 237  
238 -== 3.2 Downlink ==
225 +* **Line 13**: Assign your device name to the **deviceName** field. - We used **Device A** as it is to match with our device, **Device A **in the Devices section.
226 +* From **line 38**: Modify the telemetry section to allow parsed data to be assigned to the fields.
239 239  
228 +//telemetry: {
229 + temperature: data.temperature,
230 + humidity: data.humidity,
231 + rawData: payloadStr
232 + }//
240 240  
241 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
242 242  
235 +The modified uplink decoder function to match with **Device A** is shown below.
243 243  
244 -[[image:create-new-converter-menu.png||width="500"]]
245 -
246 -
247 -
248 -The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
249 -
250 -Click on the **TBEL** button if not selected it by default. Now copy and paste the following encoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This encoder function is compatible for both NB and CB series devices.
251 -
252 -
253 253  {{code language="JavaScript"}}
254 -// Encode downlink data from incoming Rule Engine message
238 +// Decode an uplink message from a buffer
239 +// payload - array of bytes
240 +// metadata - key/value object
255 255  
256 -// msg - JSON message payload downlink message json
257 -// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
258 -// metadata - list of key-value pairs with additional data about the message
259 -// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
242 +/** Decoder **/
260 260  
261 -/** Encoder **/
244 +// decode payload to string
245 +var payloadStr = decodeToString(payload);
262 262  
263 -var data = {};
247 +// decode payload to JSON
248 +var data = decodeToJson(payload);
264 264  
265 -// Process data from incoming message and metadata
250 +var deviceName = 'Device A';
251 +var deviceType = 'thermostat';
252 +var customerName = 'Customer C';
253 +var groupName = 'thermostat devices';
254 +var manufacturer = 'Example corporation';
255 +// use assetName and assetType instead of deviceName and deviceType
256 +// to automatically create assets instead of devices.
257 +// var assetName = 'Asset A';
258 +// var assetType = 'building';
266 266  
267 -data.tempFreq = msg.temperatureUploadFrequency;
268 -data.humFreq = msg.humidityUploadFrequency;
269 -
270 -data.devSerialNumber = metadata['ss_serialNumber'];
271 -
272 -// Result object with encoded downlink payload
260 +// Result object with device/asset attributes/telemetry data
273 273  var result = {
274 -
275 - // downlink data content type: JSON, TEXT or BINARY (base64 format)
276 - contentType: "JSON",
277 -
278 - // downlink data
279 - data: JSON.stringify(data),
280 -
281 - // Optional metadata object presented in key/value format
282 - metadata: {
283 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
284 - }
285 -
262 +// Use deviceName and deviceType or assetName and assetType, but not both.
263 + deviceName: deviceName,
264 + deviceType: deviceType,
265 +// assetName: assetName,
266 +// assetType: assetType,
267 +// customerName: customerName,
268 + groupName: groupName,
269 + attributes: {
270 + model: 'Model A',
271 + serialNumber: 'SN111',
272 + integrationName: metadata['integrationName'],
273 + manufacturer: manufacturer
274 + },
275 + telemetry: {
276 + temperature: data.temperature,
277 + humidity: data.humidity,
278 + rawData: payloadStr
279 + }
286 286  };
287 287  
282 +/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
283 +
288 288  return result;
289 289  {{/code}}
290 290  
291 291  
292 -Click on the **Add** button.
288 +Once you modify the decoder function, click on the **Add** button.
293 293  
294 294  
295 295  
296 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
292 +[[image:ul-data-converter-device-a.png||height="524" width="500"]]
297 297  
298 298  
299 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
295 +You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
300 300  
301 301  
302 -[[image:data-converters-list.png]]
298 +[[image:ul-data-converter-added.png||height="257"]]
303 303  
304 304  
305 305  
306 -= 4. Add Integration =
302 += 5. Add Integration =
307 307  
308 308  
309 309  In the left navigation, click **Integrations center**, and then click **Integrations**.
... ... @@ -323,7 +323,7 @@
323 323  **Basic settings:**
324 324  
325 325  * **Integration type**: MQTT
326 -* **Name**: MQTT integration NB/CB
322 +* **Name**: MQTT integration - Device A
327 327  * **Enable integration**: YES
328 328  * **Allows create devices or assets**: YES
329 329  
... ... @@ -330,10 +330,11 @@
330 330  Click **Next** button.
331 331  
332 332  
329 +[[image:add-integration-basic-settings.png||height="504" width="500"]]
333 333  
334 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
335 335  
336 336  
333 +
337 337  **Uplink data converter:**
338 338  
339 339  * Click on the **Select existing** button.
... ... @@ -342,34 +342,35 @@
342 342  Click **Next** button.
343 343  
344 344  
342 +[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
345 345  
346 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
347 347  
348 348  
349 349  **Downlink data converter:**
350 350  
351 -* Click on the **Select existing** button.
352 -* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
348 +Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
353 353  
354 -Click **Next** button.
350 +* Click on the **Skip **button in the Downlink data converter section.
355 355  
352 +Click **Skip** button.
356 356  
357 357  
358 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
355 +[[image:integration-dl-skip.png||height="511" width="500"]]
359 359  
360 360  
358 +
361 361  **Connection:**
362 362  
363 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
361 +* **Host**: Host URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
364 364  * **Port**: 8883
365 -* **Credentials**: Basic
366 -* **Enable SSL**: YES
363 +* **Credentials type**: Basic
367 367  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
368 368  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
369 -* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
366 +* **Enable SSL**: YES
367 +* **Topic: device/a** (The topic can be anything; you can even use just the device name.)
370 370  * **QoS:** 0-At most once
371 371  
372 -[[image:add-integration-connection.png||height="511" width="500"]]
370 +[[image:add-integartion-connection.png||height="505" width="500"]]
373 373  
374 374  
375 375  Click on the **Advanced settings** button.
... ... @@ -399,48 +399,36 @@
399 399  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
400 400  
401 401  
400 +[[image:integration-added.png]]
402 402  
403 -[[image:new-integration-pending.png]]
404 404  
405 405  
406 -= 5. Verifying the receipt of data from virtual devices =
404 += 6. Verifying the receipt of data from virtual devices =
407 407  
408 408  
409 -== 5.1 How does it work? ==
407 +== 6.1 How does it work? ==
410 410  
411 411  
412 412  We use the Mosquitto MQTT client to simulate MQTT messages, acting as a virtual device. First, install the Mosquitto client on your computer from [[this link>>url:https://mosquitto.org/download/]]. The Mosquitto client publishes messages to the MQTT broker (HiveMQ) on a specified MQTT topic. ThingsBoard subscribes to these messages using the same topic.
413 413  
414 -The Mosquitto client publishes messages on the topic v1/devices/[device_name]/telemetry. The [device_name]placeholder can be replaced with any device name, for example, 'S31B-NB'. Then, the MQTT topic would be v1/devices/S31B-NB/telemetry.
412 +The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
415 415  
416 -On the ThingsBoard side, we configure the MQTT topic subscription as v1/devices/+/telemetry. The + wildcard represents any device name and allows ThingsBoard to automatically create (provision) a device with that name, such as S31B-NB, for example.
414 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
417 417  
418 -
419 -**The new device is created the first time the MQTT topic is received. For subsequent MQTT topics with the same device name, no duplicate devices will be created.**
420 -
421 -
422 -For example, if you send two MQTT messages with different device names in the topic:
423 -
424 -1. v1/devices/**S31B-NB**/telemetry
425 -1. v1/devices/**LDS25-NB**/telemetry
426 -
427 -ThingsBoard will create two devices named **S31B-NB** and **LDS25-NB** in the **//Devices//** section.
428 -
429 -
430 -The MQTT payload format is as follows, which is common for all ~-~-NB and ~-~-CB series devices:
431 -
432 432  {{code language="none"}}
433 -{"temperature":10.4, "humidity":85}
417 +{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
434 434  {{/code}}
435 435  
420 +Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
436 436  
422 +
437 437  == 5.2 Sending messages ==
438 438  
439 439  
440 -On the terminal, issue the following MQTT command which simulates the device S31B-NB. The message payload contains the fields temperature and humidity, which hold the values 10.4 and 85, respectively. This payload is also (technically) known as telemetry.
426 +On your computer's terminal, issue the following MQTT command which simulates the device '**Device A'**. The message payload contains the fields IMEI, temperature, humidity, and pressure, which hold the values 350693903995577, 30, 80, and 1005 respectively. This payload is also (technically) known as telemetry.
441 441  
442 442  {{code language="none"}}
443 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":10.4, "humidity":85}'
429 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":30, "humidity":80, "pressure":1005}'
444 444  {{/code}}
445 445  
446 446  If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
... ... @@ -449,43 +449,59 @@
449 449  [[image:integration-active.png]]
450 450  
451 451  
452 -Also, a new device named **S31B-NB** will appear under **//Entities -> Devices -> All//**. This means the first MQTT message triggers ThingsBoard to provision a device named **S31B-NB**.
438 +== 6.3 Viewing messages ==
453 453  
454 454  
455 -[[image:device-provision-1.png]]
441 +Go back to the **Integrations** page.
456 456  
443 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
457 457  
458 -Click on the device S31B-NB on the devices list to see its details.
445 +Click on the **Edit** button (//**pen icon**//).
459 459  
460 -Then go to the **Latest telemetry** tab.
447 +Click on the **Disabled** button in the upper-right corner.
461 461  
462 -You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
449 +Turn on the **All messages (15 min)** option. This will enable displaying all messages in the **Events** tab. This setting will expire in 15 minutes, and you will need to repeat the same steps if you want to view the messages in the Events tab later.
463 463  
451 +Click on the **Apply** button.
464 464  
465 -[[image:telemetry-1.png]]
453 +Then click on the **Apply changes** (//**tick icon**//) button.
466 466  
467 467  
468 -Now, change the values of the fields and send the MQTT message again. For example, set temperature to 20 and humidity to 70. Observe how the values update in //Latest Telemetry//.
456 +[[image:debug-enabled.png||height="301" width="700"]]
469 469  
470 470  
471 -[[image:telemetry-2.png]]
472 472  
473 473  
474 -Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
461 +Now go to the **Events** tab.
475 475  
463 +Select the **Event type** as **Debug** from the dropdown list.
476 476  
465 +Publish another message (of course, you can repeat the previous message by pressing the UP arrow on your keyboard and then press Enter key) to your MQTT broker from your terminal, for example:
466 +
477 477  {{code language="none"}}
478 -mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/LDS25-NB/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":11, "humidity":87}'
468 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":30, "humidity":80, "pressure":1005}'
479 479  {{/code}}
480 480  
481 -Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
471 +Now you can see that uplink message in the **Events** tab (Click the **refresh** button if you didn't see any messages in the Events tab). The status should be **OK **if there is no errors in your integration.
482 482  
483 483  
484 -[[image:device-provision-2.png]]
474 +[[image:Screenshot 2025-03-26 at 19.49.31.png]]
485 485  
486 486  
487 -= 6. Creating a Dashboard =
488 488  
478 +Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
479 +
480 +
481 +[[image:Screenshot 2025-03-26 at 19.47.52.png]]
482 +
483 +
484 +
485 +
486 +Now, you have successfully tested your integration with a simulated uplink payload and verified that it is received by ThingsBoard, and the device is provisioned.
487 +
488 +
489 += 7. Creating a Dashboard =
490 +
489 489  ThingsBoard **Dashboards** provide a powerful way to visualize and monitor real-time and historical data from connected devices. They allow users to create interactive, customizable panels displaying telemetry data, device status, and other key metrics. With a variety of widgets, including charts, maps, and tables, dashboards help users gain insights, track trends, and manage IoT deployments efficiently.
490 490  
491 491  
... ... @@ -492,6 +492,11 @@
492 492  This section guides you on how to create a dashboard to display temperature and humidity data from the device on a time-series chart. You may also use other widgets in ThingsBoard to display data according to your requirements.
493 493  
494 494  
497 +First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
498 +
499 +{{code language="none"}}mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":22, "humidity":80, "pressure":1005}'{{/code}}
500 +
501 +
495 495  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
496 496  
497 497  
... ... @@ -527,7 +527,7 @@
527 527  
528 528  Configure the **Time series chart** widget as follows:
529 529  
530 -* **Datasource** - select S31B-NB device you provisioned.
537 +* **Datasource** - select **Device A** device you provisioned.
531 531  * **Series**:
532 532  ** **temperature** - you can see this key by default.
533 533  ** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
... ... @@ -548,12 +548,11 @@
548 548  
549 549  
550 550  {{code language="none"}}
551 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":20, "humidity":70}'
558 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":22, "humidity":70, "pressure":1005}'
552 552  
553 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":22, "humidity":71}'
560 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":27, "humidity":72, "pressure":1005}'
554 554  
555 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":18, "humidity":79}'
556 -
562 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":19, "humidity":80, "pressure":1005}'
557 557  {{/code}}
558 558  
559 559  The chart will update with the values in realtime, as shown in the below image.
... ... @@ -562,10 +562,10 @@
562 562  [[image:timeseries-4.png||height="316" width="700"]]
563 563  
564 564  
565 -= 7. Configure NB-IoT Sensor =
571 += 8. Configure NB-IoT Sensor =
566 566  
567 567  
568 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
574 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
569 569  
570 570  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
571 571  
... ... @@ -573,8 +573,8 @@
573 573  **AT Commands**
574 574  
575 575  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
576 -* **AT+SUBTOPIC=<MQTT topic>**
577 -* **AT+PUBTOPIC=<MQTT topic>**
582 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
583 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
578 578  * **AT+CLIENT=null**
579 579  * **AT+UNAME=<MQTT Username>**
580 580  * **AT+PWD=<MQTT Password>**
... ... @@ -581,3 +581,13 @@
581 581  * **AT+SERVADDR=<Broker address, Port>**
582 582  
583 583  Test your uplink by pressing the ACT button for 1 second.
590 +
591 +
592 +
593 +The following image shows the uplink payload of a real Dragino device. The publish topic is '**TS01-NB' that contains fields in the payload, IMEI, IMSI, Model, temperature, etc**. Note that we have created a device named **TS01-NB** in the **Devices** section in advance.
594 +
595 +{{info}}
596 +The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
597 +{{/info}}
598 +
599 +[[image:image-4.png]]
add-integration-basic-settings.png
Size
... ... @@ -1,1 +1,1 @@
1 -122.5 KB
1 +123.8 KB
Content
add-integration-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -124.4 KB
1 +158.1 KB
Content
integration-active.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.2 KB
1 +64.1 KB
Content
Screenshot 2025-03-16 at 18.38.59.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +221.2 KB
Content
Screenshot 2025-03-16 at 18.39.12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +211.9 KB
Content
Screenshot 2025-03-18 at 09.23.10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +78.7 KB
Content
Screenshot 2025-03-26 at 18.15.08.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +92.2 KB
Content
Screenshot 2025-03-26 at 19.47.52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.4 KB
Content
Screenshot 2025-03-26 at 19.49.31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +133.0 KB
Content
add-integartion-connection.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +110.3 KB
Content
add-integartion-connetcion.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +146.0 KB
Content
add-integration-ul-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +121.2 KB
Content
debug-enabled.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.3 KB
Content
image-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +96.0 KB
Content
integration-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.2 KB
Content
integration-dl-skip.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +105.5 KB
Content
new-device.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
ul-data-converter-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +189.4 KB
Content
ul-data-converter-device-a.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.3 KB
Content