Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 127.1
edited by Dilisi S
on 2025/03/08 21:57
Change comment: Uploaded new attachment "thingsboard-5.png", version {1}
To version 141.1
edited by Dilisi S
on 2025/03/09 03:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -40,11 +40,30 @@
40 40  [[image:thingsboard-2.png]]
41 41  
42 42  
43 -You can sign up with your Google, GitHub, Facebook, or Apple account. If not you can create an account with providing your name, email address and a password.
43 +You can sign up with your **Google**, **GitHub**, **Facebook**, or **Apple** account. If not you can create an account with providing your **name**, **email address** and a **password**.
44 44  
45 +Click on the **Sign up** button.
46 +
45 45  [[image:thingsboard-3.png||height="651" width="500"]]
46 46  
47 47  
50 +You will be navigated to the following page.
51 +
52 +[[image:thingsboard-5.png||height="109" width="500"]]
53 +
54 +
55 +simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button.
56 +
57 +
58 +[[image:thingsboard-4.png||height="249" width="500"]]
59 +
60 +
61 +Now losing to the account using your credentials:
62 +
63 +
64 +[[image:thingsboard-6.png||height="244" width="500"]]
65 +
66 +
48 48  == 2.2 HiveMQ Cloud ==
49 49  
50 50  
... ... @@ -360,13 +360,110 @@
360 360  [[image:new-integration-pending.png]]
361 361  
362 362  
363 -= 5. Verifying the receipt of data from the device =
382 += 5. Verifying the receipt of data from virtual devices =
364 364  
365 365  
366 -On the terminal, issue the following MQTT command which simulates the device S31B-NB.
385 +== 5.1 How does it work? ==
367 367  
387 +
388 +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.
389 +
390 +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.
391 +
392 +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.
393 +
394 +
395 +**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.**
396 +
397 +
398 +For example, if you send two MQTT messages with different device names in the topic:
399 +
400 +1. v1/devices/**S31B-NB**/telemetry
401 +1. v1/devices/**LDS25-NB**/telemetry
402 +
403 +ThingsBoard will create two devices named **S31B-NB** and **LDS25-NB** in the **//Devices//** section.
404 +
405 +
406 +The MQTT payload format is as follows, which is common for all ~-~-NB and ~-~-CB series devices:
407 +
368 368  {{code language="none"}}
369 -mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
409 +{"temperature":10.4, "humidity":85}
370 370  {{/code}}
371 371  
372 -If the integration was performed without errors, after the transmission of the first telemetry, a new device with the name “S31B-NB” will appear in the Devices → All. Also, you can verify the input and output data, respectively, before and after conversion in Data converters → UDP Uplink Converter NB/CB → Events.
412 +
413 +== 5.2 Sending messages ==
414 +
415 +
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 10.4 and 85, respectively. This payload is also (technically) known as telemetry.
417 +
418 +{{code language="none"}}
419 +mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":10.4, "humidity":85}'
420 +{{/code}}
421 +
422 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
423 +
424 +
425 +[[image:integration-active.png]]
426 +
427 +
428 +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**.
429 +
430 +
431 +[[image:device-provision-1.png]]
432 +
433 +
434 +Click on the device S31B-NB on the devices list to see its details.
435 +
436 +Then go to the **Latest telemetry** tab.
437 +
438 +You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
439 +
440 +
441 +[[image:telemetry-1.png]]
442 +
443 +
444 +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//.
445 +
446 +
447 +[[image:telemetry-2.png]]
448 +
449 +
450 +Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
451 +
452 +
453 +{{code language="none"}}
454 +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}'
455 +{{/code}}
456 +
457 +Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
458 +
459 +
460 +[[image:device-provision-2.png]]
461 +
462 +
463 += 6. Creating a Dashboard =
464 +
465 +
466 +In ThingsBoard, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
467 +
468 +
469 +[[image:dashboard-1.png]]
470 +
471 +
472 +In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
473 +
474 +Click on the **Add** button.
475 +
476 +
477 +[[image:dashboard-2.png||height="526" width="500"]]
478 +
479 +
480 +Click on the **Add widget / Add new widget** button.
481 +
482 +
483 +[[image:dashboard-3.png]]
484 +
485 +
486 +
487 +
488 +
dashboard-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +271.1 KB
Content
dashboard-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +112.2 KB
Content
dashboard-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +141.3 KB
Content
device-provision-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +265.7 KB
Content
device-provision-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +213.9 KB
Content
integration-active.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +64.2 KB
Content
telemetry-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +191.9 KB
Content
telemetry-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +185.1 KB
Content
thingsboard-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +119.3 KB
Content