Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23

From 194.1 to 193.1 From 202.1 to 201.1

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 194.1

edited by Dilisi S
on 2025/03/28 00:23

Change comment: Mar 27 edits - part 3

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- Screenshot 2025-03-31 at 06.51.15.png

Details

Page properties

Content

@@ -164,11 +164,8 @@
  [[image:ins1.png||height="310" width="500"]]
--= 3. Creating Devices (Optional) =
++= 3. Creating Devices =
--{{info}}
--**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.**
--{{/info}}
  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 @@
  //var data = decodeToJson(payload)//
--* **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.
++* **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.
  * From **line 38**: Modify the telemetry section to allow parsed data to be assigned to the fields.
  //telemetry: {
@@ -321,7 +321,7 @@
  * **Integration type**: MQTT
  * **Name**: MQTT integration - Device A
  * **Enable integration**: YES
--* **Allow create devices or assets**: YES
++* **Allows create devices or assets**: YES
  Click **Next** button.
@@ -496,7 +496,7 @@
  First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
--{{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}}
++{{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}}
  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
@@ -534,19 +534,15 @@
  Configure the **Time series chart** widget as follows:
--* **Datasource** - select **Device A** device you provisioned.
++* **Datasource** - select S31B-NB device you provisioned.
  * **Series**:
  ** **temperature** - you can see this key by default.
  ** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
  * Click on the **Add** button.
--{{info}}
--You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
--{{/info}}
++[[image:timeseries-1.png||height="491" width="700"]]
--[[image:Screenshot 2025-03-31 at 06.51.15.png||height="485" width="700"]]
--
  The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
  Click the **Save** button to add the widget to the dashboard.
@@ -559,11 +559,12 @@
  {{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":70, "pressure":1005}'
++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}'
--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}'
++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}'
--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}'
++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}'
++
  {{/code}}
  The chart will update with the values in realtime, as shown in the below image.
@@ -572,7 +572,7 @@
  [[image:timeseries-4.png||height="316" width="700"]]
--= 8. Configure Physical NB-IoT Sensor =
++= 8. Configure NB-IoT Sensor =
  Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
@@ -594,7 +594,10 @@
--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.
++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**.
++{{info}}
++The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
++{{/info}}
  [[image:image-4.png]]

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

Changes for page ThingsBoard

Summary

Details

Applications

Navigation