Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 220.1
edited by Dilisi S
on 2025/04/21 18:49
Change comment: April 17 edits - part final
To version 212.1
edited by Dilisi S
on 2025/04/21 18:22
Change comment: Uploaded new attachment "Screenshot 2025-04-21 122154.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -335,6 +335,8 @@
335 335  * **Topic**: # (the # symbol indicates that it filters all topics).
336 336  * **QoS:** 0-At most once
337 337  
338 +
339 +
338 338  [[image:add-integration-4.png||height="484" width="500"]]
339 339  
340 340  
... ... @@ -365,8 +365,8 @@
365 365  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
366 366  
367 367  
370 +[[image:integration-added.png]]
368 368  
369 -[[image:integrations-pending.png]]
370 370  
371 371  
372 372  = 5. Verifying the receipt of data from virtual devices =
... ... @@ -377,47 +377,38 @@
377 377  
378 378  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.
379 379  
380 -The Mosquitto client publishes messages (payloads) to a topic - for example, # or device/ts01-nb. You can, of course, use any topic you prefer.
382 +The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
381 381  
384 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
382 382  
383 -(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows. The **IMEI **and **Model **are mandatory fields. For other fields, you can use any number of key-value pairs.
384 -
385 385  {{code language="none"}}
386 -{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
387 +{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
387 387  {{/code}}
388 388  
390 +Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
389 389  
392 +
390 390  == 5.2 Sending messages ==
391 391  
392 392  
393 -On your computer's terminal, issue the following MQTT command, which simulates the device named '**350693903995577'**. The message payload contains the fields IMEI, Model, temperature, humidity, and pressure, which hold the values 350693903995577,  TS01-NB, 30, 80, and 1005 respectively. This payload is also (technically) known as telemetry.
396 +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.
394 394  
395 395  {{code language="none"}}
396 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/350693903995577" -m '{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}'
399 +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}'
397 397  {{/code}}
398 398  
399 -If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
402 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
400 400  
401 401  
402 -[[image:new-device-1.png]]
405 +[[image:integration-active.png]]
403 403  
404 404  
405 -The status of the integration also changes to '**Active**' after the first telemetry transmission.
406 -
407 -
408 -[[image:Screenshot 2025-04-21 122154.png]]
409 -
410 -
411 -
412 -**When ThingsBoard receives this message for the first time, it will automatically create a new device named '350693903995577' in the Devices section. The device name is based on the IMEI number. For subsequent messages with the same IMEI, no duplicate devices will be created. Each new IMEI number will result in a unique entry in the Devices section, representing a physical device.**
413 -
414 -
415 415  == 5.3 Viewing messages ==
416 416  
417 417  
418 418  Go back to the **Integrations** page.
419 419  
420 -Click on the **MQTT integration** in the **Integrations** page to see its details.
413 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
421 421  
422 422  Click on the **Edit** button (//**pen icon**//).
423 423  
... ... @@ -430,10 +430,11 @@
430 430  Then click on the **Apply changes** (//**tick icon**//) button.
431 431  
432 432  
426 +[[image:debug-enabled.png||height="301" width="700"]]
433 433  
434 -[[image:Screenshot 2025-04-21 122936.png||height="247" width="500"]]
435 435  
436 436  
430 +
437 437  Now go to the **Events** tab.
438 438  
439 439  Select the **Event type** as **Debug** from the dropdown list.
... ... @@ -441,19 +441,24 @@
441 441  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:
442 442  
443 443  {{code language="none"}}
444 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/350693903995577" -m '{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":82, "pressure":1005}'
438 +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}'
445 445  {{/code}}
446 446  
447 447  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.
448 448  
449 449  
444 +[[image:Screenshot 2025-03-26 at 19.49.31.png]]
445 +
446 +
447 +
450 450  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
451 451  
452 452  
451 +[[image:Screenshot 2025-03-26 at 19.47.52.png]]
453 453  
454 -[[image:Screenshot 2025-04-21 122909.png]]
455 455  
456 456  
455 +
457 457  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.
458 458  
459 459  
... ... @@ -465,6 +465,11 @@
465 465  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.
466 466  
467 467  
467 +First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
468 +
469 +{{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}}
470 +
471 +
468 468  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
469 469  
470 470  
... ... @@ -500,11 +500,10 @@
500 500  
501 501  Configure the **Time series chart** widget as follows:
502 502  
503 -* **Datasource** - select **350693903995577 **you provisioned.
507 +* **Datasource** - select **Device A** device you provisioned.
504 504  * **Series**:
505 505  ** **temperature** - you can see this key by default.
506 -** **humidity** - Click **Add series** button. Then choose **humidity** for the key, and then type **%** as its unit.
507 -** pressure -  Click **Add series** button. Then choose **humidity** for the key, and then type Pa as its unit.
510 +** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
508 508  * Click on the **Add** button.
509 509  
510 510  {{info}}
... ... @@ -511,27 +511,34 @@
511 511  You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
512 512  {{/info}}
513 513  
517 +[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
514 514  
515 515  
516 -[[image:Screenshot 2025-04-21 123647.png||height="466" width="700"]]
517 -
518 -
519 519  The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
520 520  
521 521  Click the **Save** button to add the widget to the dashboard.
522 522  
523 523  
524 -[[image:Screenshot 2025-04-21 124145.png||height="443" width="700"]]
525 +[[image:timeseries-3.png||height="347" width="700"]]
525 525  
526 526  
527 -**Now send a few MQTT messages from the terminal to simulate the data. Use different values for temperature, humidity, and pressure in each message.**
528 +Now send the following MQTT messages from the terminal to simulate the data.
528 528  
529 -**The chart will update with the values in real time, and you will see a live chart similar to this:**
530 530  
531 +{{code language="none"}}
532 +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}'
531 531  
532 -[[image:Screenshot 2025-04-21 124054.png||height="441" width="700"]]
534 +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}'
533 533  
536 +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}'
537 +{{/code}}
534 534  
539 +The chart will update with the values in realtime, as shown in the below image.
540 +
541 +
542 +[[image:timeseries-4.png||height="316" width="700"]]
543 +
544 +
535 535  = 8. Configure Physical NB-IoT Sensor =
536 536  
537 537  
... ... @@ -543,17 +543,17 @@
543 543  **AT Commands**
544 544  
545 545  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
546 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: # -  **You can leave the SUBTOPIC configuration as it is, since we are not sending downlink messages to the device at the moment.
547 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: #**
556 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
557 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
548 548  * **AT+CLIENT=null**
549 549  * **AT+UNAME=<MQTT Username>**
550 550  * **AT+PWD=<MQTT Password>**
551 551  * **AT+SERVADDR=<Broker address, Port>**
552 552  
553 -
554 554  Test your uplink by pressing the ACT button for 1 second.
555 555  
556 556  
566 +
557 557  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.
558 558  
559 559  
Screenshot 2025-04-21 122909.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -59.9 KB
Content
Screenshot 2025-04-21 122936.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
Screenshot 2025-04-21 123647.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
Screenshot 2025-04-21 124054.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -60.4 KB
Content
Screenshot 2025-04-21 124145.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -50.9 KB
Content