Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 194.1
edited by Dilisi S
on 2025/03/28 00:23
Change comment: Mar 27 edits - part 3
To version 188.1
edited by Dilisi S
on 2025/03/27 22:53
Change comment: Uploaded new attachment "add-integartion-connection.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -170,7 +170,7 @@
170 170  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.
171 171  
172 172  
173 -In the left navigation, click **Entities -> Devices**.
173 +In the left navigation, click Entities -> Devices.
174 174  
175 175  Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
176 176  
... ... @@ -205,10 +205,8 @@
205 205  [[image:create-new-converter-menu.png||height="259" width="500"]]
206 206  
207 207  
208 -The **Add data converter** window will appear.
208 +The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
209 209  
210 -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**.
211 -
212 212  Click on the **TBEL** button if it has not been selected by default.
213 213  
214 214  Modify the default TBEL function to match with your device as described below:
... ... @@ -285,17 +285,16 @@
285 285  Once you modify the decoder function, click on the **Add** button.
286 286  
287 287  
286 +[[image:mqtt-uplink.png||width="500"]]
288 288  
289 -[[image:ul-data-converter-device-a.png||height="524" width="500"]]
290 290  
291 291  
292 292  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
293 293  
294 294  
295 -[[image:ul-data-converter-added.png||height="257"]]
293 +[[image:data-converter-list-showing-uplink-dc.png]]
296 296  
297 297  
298 -
299 299  = 5. Add Integration =
300 300  
301 301  
... ... @@ -316,7 +316,7 @@
316 316  **Basic settings:**
317 317  
318 318  * **Integration type**: MQTT
319 -* **Name**: MQTT integration - Device A
316 +* **Name**: MQTT integration NB/CB
320 320  * **Enable integration**: YES
321 321  * **Allows create devices or assets**: YES
322 322  
... ... @@ -323,11 +323,9 @@
323 323  Click **Next** button.
324 324  
325 325  
326 -[[image:add-integration-basic-settings.png||height="504" width="500"]]
323 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
327 327  
328 328  
329 -
330 -
331 331  **Uplink data converter:**
332 332  
333 333  * Click on the **Select existing** button.
... ... @@ -336,10 +336,9 @@
336 336  Click **Next** button.
337 337  
338 338  
339 -[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
334 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
340 340  
341 341  
342 -
343 343  **Downlink data converter:**
344 344  
345 345  Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
... ... @@ -364,7 +364,7 @@
364 364  * **Topic: device/a** (The topic can be anything; you can even use just the device name.)
365 365  * **QoS:** 0-At most once
366 366  
367 -[[image:add-integartion-connection.png||height="505" width="500"]]
361 +[[image:add-integration-connection.png||height="511" width="500"]]
368 368  
369 369  
370 370  Click on the **Advanced settings** button.
... ... @@ -394,10 +394,9 @@
394 394  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
395 395  
396 396  
397 -[[image:integration-added.png]]
391 +[[image:new-integration-pending.png]]
398 398  
399 399  
400 -
401 401  = 6. Verifying the receipt of data from virtual devices =
402 402  
403 403  
... ... @@ -420,7 +420,7 @@
420 420  == 5.2 Sending messages ==
421 421  
422 422  
423 -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.
416 +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 S31B-NB and 27, respectively. This payload is also (technically) known as telemetry.
424 424  
425 425  {{code language="none"}}
426 426  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}'
... ... @@ -432,6 +432,8 @@
432 432  [[image:integration-active.png]]
433 433  
434 434  
428 +
429 +
435 435  == 6.3 Viewing messages ==
436 436  
437 437  
... ... @@ -450,28 +450,21 @@
450 450  Then click on the **Apply changes** (//**tick icon**//) button.
451 451  
452 452  
453 -[[image:debug-enabled.png||height="301" width="700"]]
448 +[[image:Screenshot 2025-03-18 at 09.23.10.png]]
454 454  
455 455  
456 -
457 -
458 458  Now go to the **Events** tab.
459 459  
460 -Select the **Event type** as **Debug** from the dropdown list.
453 +Select the Event type as **Debug** from the dropdown list.
461 461  
462 -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:
455 +Now you can see all the Uplink messages you are simulating through the MQTT broker. The status should be **OK **if there is no errors in your integration.
463 463  
464 -{{code language="none"}}
465 -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}'
466 -{{/code}}
467 467  
468 -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.
469 -
470 -
471 471  [[image:Screenshot 2025-03-26 at 19.49.31.png]]
472 472  
473 473  
474 474  
462 +
475 475  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
476 476  
477 477  
... ... @@ -595,3 +595,6 @@
595 595  {{/info}}
596 596  
597 597  [[image:image-4.png]]
586 +
587 +
588 +
debug-enabled.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -196.3 KB
Content
integration-active.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.1 KB
1 +64.2 KB
Content
integration-added.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -196.2 KB
Content