Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 196.1
edited by Dilisi S
on 2025/03/31 12:46
Change comment: There is no comment for this version
To version 192.1
edited by Dilisi S
on 2025/03/27 23:20
Change comment: Uploaded new attachment "debug-enabled.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  
... ... @@ -367,6 +367,8 @@
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  
367 +
368 +
370 370  [[image:add-integartion-connection.png||height="505" width="500"]]
371 371  
372 372  
... ... @@ -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]]
399 +[[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.
424 +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  
436 +
437 +
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"]]
456 +[[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.
461 +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:
463 +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  
470 +
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  
... ... @@ -496,7 +496,7 @@
496 496  
497 497  First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
498 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}}
492 +{{code language="none"}}mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 22, "humidity":80}'{{/code}}
500 500  
501 501  
502 502  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
... ... @@ -534,7 +534,7 @@
534 534  
535 535  Configure the **Time series chart** widget as follows:
536 536  
537 -* **Datasource** - select **Device A** device you provisioned.
530 +* **Datasource** - select S31B-NB device you provisioned.
538 538  * **Series**:
539 539  ** **temperature** - you can see this key by default.
540 540  ** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
... ... @@ -555,11 +555,12 @@
555 555  
556 556  
557 557  {{code language="none"}}
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}'
551 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 22, "humidity":70}'
559 559  
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}'
553 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 27, "humidity":72}'
561 561  
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}'
555 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 19, "humidity":80}'
556 +
563 563  {{/code}}
564 564  
565 565  The chart will update with the values in realtime, as shown in the below image.
... ... @@ -590,7 +590,7 @@
590 590  
591 591  
592 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.
587 +The following image shows the uplink payload of a real Dragino device. The publish topic is **TS01-NB**, and the device name is **861275077962896**, which is represented by the **IMEI**.
594 594  
595 595  {{info}}
596 596  The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
... ... @@ -597,3 +597,5 @@
597 597  {{/info}}
598 598  
599 599  [[image:image-4.png]]
594 +
595 +