Changes for page ThingsBoard
Last modified by Dilisi S on 2025/04/23 19:23
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (1 modified, 0 added, 4 removed)
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 A316 +* **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="5 04" 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="5 05" 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-integ artion-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'sterminal, issue the following MQTT command which simulates the device'**Device A'**. The message payload contains the fieldsIMEI,temperature,humidity,and pressure,which hold the values 350693903995577,30, 80,and1005respectively. 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 anothermessage (of course,you canrepeatthe previousmessagebypressing theUParrowonyourkeyboardandthen pressEnter key) toyourMQTT brokerfromyour 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 ... ... @@ -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}}484 +{{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 **DeviceA**device you provisioned.522 +* **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}'543 +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}'545 +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}' 547 +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}' 548 + 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 fieldsinthepayload, IMEI, IMSI, Model, temperature, etc**. Note that we have created a device named**TS01-NB** in the**Devices**sectioninadvance.579 +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,6 @@ 597 597 {{/info}} 598 598 599 599 [[image:image-4.png]] 586 + 587 + 588 +
- Screenshot 2025-03-31 at 06.51.15.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -179.5 KB - Content
- add-integartion-connection.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -110.3 KB - Content
- 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. 1KB1 +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