Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 195.1
edited by Dilisi S
on 2025/03/28 00:38
Change comment: Mar 17 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
... ... @@ -164,16 +164,13 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 -= 3. Creating Devices (Optional) =
167 += 3. Creating Devices =
168 168  
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}}
172 172  
173 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.
174 174  
175 175  
176 -In the left navigation, click **Entities -> Devices**.
173 +In the left navigation, click Entities -> Devices.
177 177  
178 178  Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
179 179  
... ... @@ -208,10 +208,8 @@
208 208  [[image:create-new-converter-menu.png||height="259" width="500"]]
209 209  
210 210  
211 -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**.
212 212  
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**.
214 -
215 215  Click on the **TBEL** button if it has not been selected by default.
216 216  
217 217  Modify the default TBEL function to match with your device as described below:
... ... @@ -288,17 +288,16 @@
288 288  Once you modify the decoder function, click on the **Add** button.
289 289  
290 290  
286 +[[image:mqtt-uplink.png||width="500"]]
291 291  
292 -[[image:ul-data-converter-device-a.png||height="524" width="500"]]
293 293  
294 294  
295 295  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
296 296  
297 297  
298 -[[image:ul-data-converter-added.png||height="257"]]
293 +[[image:data-converter-list-showing-uplink-dc.png]]
299 299  
300 300  
301 -
302 302  = 5. Add Integration =
303 303  
304 304  
... ... @@ -319,7 +319,7 @@
319 319  **Basic settings:**
320 320  
321 321  * **Integration type**: MQTT
322 -* **Name**: MQTT integration - Device A
316 +* **Name**: MQTT integration NB/CB
323 323  * **Enable integration**: YES
324 324  * **Allows create devices or assets**: YES
325 325  
... ... @@ -326,11 +326,9 @@
326 326  Click **Next** button.
327 327  
328 328  
329 -[[image:add-integration-basic-settings.png||height="504" width="500"]]
323 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
330 330  
331 331  
332 -
333 -
334 334  **Uplink data converter:**
335 335  
336 336  * Click on the **Select existing** button.
... ... @@ -339,10 +339,9 @@
339 339  Click **Next** button.
340 340  
341 341  
342 -[[image:add-integration-ul-data-converter.png||height="505" width="500"]]
334 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
343 343  
344 344  
345 -
346 346  **Downlink data converter:**
347 347  
348 348  Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
... ... @@ -367,7 +367,7 @@
367 367  * **Topic: device/a** (The topic can be anything; you can even use just the device name.)
368 368  * **QoS:** 0-At most once
369 369  
370 -[[image:add-integartion-connection.png||height="505" width="500"]]
361 +[[image:add-integration-connection.png||height="511" width="500"]]
371 371  
372 372  
373 373  Click on the **Advanced settings** button.
... ... @@ -397,10 +397,9 @@
397 397  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
398 398  
399 399  
400 -[[image:integration-added.png]]
391 +[[image:new-integration-pending.png]]
401 401  
402 402  
403 -
404 404  = 6. Verifying the receipt of data from virtual devices =
405 405  
406 406  
... ... @@ -423,7 +423,7 @@
423 423  == 5.2 Sending messages ==
424 424  
425 425  
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.
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.
427 427  
428 428  {{code language="none"}}
429 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}'
... ... @@ -435,6 +435,8 @@
435 435  [[image:integration-active.png]]
436 436  
437 437  
428 +
429 +
438 438  == 6.3 Viewing messages ==
439 439  
440 440  
... ... @@ -453,28 +453,21 @@
453 453  Then click on the **Apply changes** (//**tick icon**//) button.
454 454  
455 455  
456 -[[image:debug-enabled.png||height="301" width="700"]]
448 +[[image:Screenshot 2025-03-18 at 09.23.10.png]]
457 457  
458 458  
459 -
460 -
461 461  Now go to the **Events** tab.
462 462  
463 -Select the **Event type** as **Debug** from the dropdown list.
453 +Select the Event type as **Debug** from the dropdown list.
464 464  
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:
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.
466 466  
467 -{{code language="none"}}
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}'
469 -{{/code}}
470 470  
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.
472 -
473 -
474 474  [[image:Screenshot 2025-03-26 at 19.49.31.png]]
475 475  
476 476  
477 477  
462 +
478 478  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
479 479  
480 480  
... ... @@ -598,3 +598,6 @@
598 598  {{/info}}
599 599  
600 600  [[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