Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 201.1
edited by Dilisi S
on 2025/04/15 23:13
Change comment: There is no comment for this version
To version 197.1
edited by Dilisi S
on 2025/03/31 13:04
Change comment: Uploaded new attachment "Screenshot 2025-03-31 at 06.51.15.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -167,7 +167,7 @@
167 167  = 3. Creating Devices (Optional) =
168 168  
169 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.**
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 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.
... ... @@ -222,7 +222,7 @@
222 222  //var data = decodeToJson(payload)//
223 223  
224 224  
225 -* **Line 13**: Assign your device name to the **deviceName** field. - We used **Device A** as it is to match with our device, **Device A **in the **Devices **section.
225 +* **Line 13**: Assign your device name to the **deviceName** field. - We used **Device A** as it is to match with our device, **Device A **in the Devices section.
226 226  * From **line 38**: Modify the telemetry section to allow parsed data to be assigned to the fields.
227 227  
228 228  //telemetry: {
... ... @@ -321,7 +321,7 @@
321 321  * **Integration type**: MQTT
322 322  * **Name**: MQTT integration - Device A
323 323  * **Enable integration**: YES
324 -* **Allow create devices or assets**: YES
324 +* **Allows create devices or assets**: YES
325 325  
326 326  Click **Next** button.
327 327  
... ... @@ -540,13 +540,9 @@
540 540  ** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
541 541  * Click on the **Add** button.
542 542  
543 -{{info}}
544 -You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
545 -{{/info}}
543 +[[image:timeseries-1.png||height="491" width="700"]]
546 546  
547 -[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
548 548  
549 -
550 550  The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
551 551  
552 552  Click the **Save** button to add the widget to the dashboard.
... ... @@ -572,7 +572,7 @@
572 572  [[image:timeseries-4.png||height="316" width="700"]]
573 573  
574 574  
575 -= 8. Configure Physical NB-IoT Sensor =
571 += 8. Configure NB-IoT Sensor =
576 576  
577 577  
578 578  Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
... ... @@ -596,5 +596,8 @@
596 596  
597 597  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.
598 598  
595 +{{info}}
596 +The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
597 +{{/info}}
599 599  
600 600  [[image:image-4.png]]