Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 176.1
edited by Dilisi S
on 2025/03/26 20:27
Change comment: Mar 26 edits - part 1
To version 171.1
edited by Dilisi S
on 2025/03/20 15:24
Change comment: Uploaded new attachment "integration-dl-skip.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -164,33 +164,13 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 -(% class="wikigeneratedid" %)
168 -= 3. Creating Devices =
167 += 3. Data Converters =
169 169  
170 170  
171 -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.
172 -
173 -
174 -In the left navigation, click Entities -> Devices.
175 -
176 -Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
177 -
178 -In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
179 -
180 -Click the **Add** button.
181 -
182 -Skip the **connectivity testing** by clicking the **Close** button.
183 -
184 -The device is created and listed on the **Devices** page. Note that its initial state is **Inactive** because it has not received any data yet.
185 -
186 -
187 -= 4. Data Converters =
188 -
189 -
190 190  In **ThingsBoard**, **Data Converters** are components used to transform incoming or outgoing data between different formats, typically to convert raw telemetry data from devices into a structured format that ThingsBoard can understand, or vice versa.
191 191  
192 192  
193 -== 4.1 Uplink ==
173 +== 3.1 Uplink ==
194 194  
195 195  
196 196  In the left navigation, click **Integrations center**, and then click **Data converters**.
... ... @@ -212,9 +212,6 @@
212 212  
213 213  Delete the default decoder function in the code editor. Now copy and paste the following decoder function written in **JavaScript** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
214 214  
215 -{{info}}
216 -Please note that the value assigned to the IMEI field in the payload will be used by ThingsBoard to create a device on the platform with the same name.
217 -{{/info}}
218 218  
219 219  {{code language="JavaScript"}}
220 220  //Version: 0.1
... ... @@ -352,9 +352,13 @@
352 352  [[image:data-converter-list-showing-uplink-dc.png]]
353 353  
354 354  
355 -= 5. Add Integration =
356 356  
357 357  
334 +
335 +
336 += 4. Add Integration =
337 +
338 +
358 358  In the left navigation, click **Integrations center**, and then click **Integrations**.
359 359  
360 360  
... ... @@ -395,17 +395,15 @@
395 395  
396 396  **Downlink data converter:**
397 397  
398 -Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
379 +* Click on the **Select existing** button.
380 +* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
399 399  
400 -* Click on the **Skip **button in the Downlink data converter section.
382 +Click **Next** button.
401 401  
402 -Click **Skip** button.
403 403  
385 +[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
404 404  
405 -[[image:integration-dl-skip.png||height="511" width="500"]]
406 406  
407 -
408 -
409 409  **Connection:**
410 410  
411 411  * **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
... ... @@ -414,10 +414,9 @@
414 414  * **Enable SSL**: YES
415 415  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
416 416  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
417 -* **Topic: v1/devices/me/telemetry** (The topic can be anything; you can even use just the device name. For example, you can use your device name here, such as S31B-NB.)
396 +* **Topic: v1/devices/+/telemetry** (the + replaces any 'device name' will create a device in the Entities -> Devices)
418 418  * **QoS:** 0-At most once
419 419  
420 -
421 421  [[image:add-integration-connection.png||height="511" width="500"]]
422 422  
423 423  
... ... @@ -448,13 +448,14 @@
448 448  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
449 449  
450 450  
429 +
451 451  [[image:new-integration-pending.png]]
452 452  
453 453  
454 -= 6. Verifying the receipt of data from virtual devices =
433 += 5. Verifying the receipt of data from virtual devices =
455 455  
456 456  
457 -== 6.1 How does it work? ==
436 +== 5.1 How does it work? ==
458 458  
459 459  
460 460  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.
... ... @@ -491,7 +491,7 @@
491 491  [[image:new-device.png]]
492 492  
493 493  
494 -== 6.3 Viewing messages ==
473 +== 5.3 Viewing messages ==
495 495  
496 496  
497 497  Go back to the **Integrations** page.
... ... @@ -531,7 +531,7 @@
531 531  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.
532 532  
533 533  
534 -= 7. Creating a Dashboard =
513 += 6. Creating a Dashboard =
535 535  
536 536  ThingsBoard **Dashboards** provide a powerful way to visualize and monitor real-time and historical data from connected devices. They allow users to create interactive, customizable panels displaying telemetry data, device status, and other key metrics. With a variety of widgets, including charts, maps, and tables, dashboards help users gain insights, track trends, and manage IoT deployments efficiently.
537 537  
... ... @@ -614,10 +614,10 @@
614 614  [[image:timeseries-4.png||height="316" width="700"]]
615 615  
616 616  
617 -= 8. Configure NB-IoT Sensor =
596 += 7. Configure NB-IoT Sensor =
618 618  
619 619  
620 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
599 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
621 621  
622 622  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
623 623  
... ... @@ -625,7 +625,7 @@
625 625  **AT Commands**
626 626  
627 627  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
628 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
607 +* **AT+SUBTOPIC=<MQTT subscribe topic> **
629 629  * **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
630 630  * **AT+CLIENT=null**
631 631  * **AT+UNAME=<MQTT Username>**
... ... @@ -633,15 +633,10 @@
633 633  * **AT+SERVADDR=<Broker address, Port>**
634 634  
635 635  Test your uplink by pressing the ACT button for 1 second.
636 -
637 637  
638 638  
639 639  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**.
640 640  
641 -{{info}}
642 -The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
643 -{{/info}}
644 -
645 645  [[image:image-4.png]]
646 646  
647 647  
Screenshot 2025-03-16 at 18.39.12.png
Size
... ... @@ -1,1 +1,1 @@
1 -211.9 KB
1 +277.0 KB
Content
add-integration-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -158.1 KB
1 +153.2 KB
Content