Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -164,13 +164,33 @@
164	164	[[image:ins1.png||height="310" width="500"]]
165	165
166	166
167		-= 3. Data Converters =
	167	+(% class="wikigeneratedid" %)
	168	+= 3. Creating Devices =
168	168
169	169
	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	+
170	170	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.
171	171
172	172
173		-== 3.1 Uplink ==
	193	+== 4.1 Uplink ==
174	174
175	175
176	176	In the left navigation, click **Integrations center**, and then click **Data converters**.
...	...	@@ -192,6 +192,9 @@
192	192
193	193	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.
194	194
	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}}
195	195
196	196	{{code language="JavaScript"}}
197	197	//Version: 0.1
...	...	@@ -329,13 +329,9 @@
329	329	[[image:data-converter-list-showing-uplink-dc.png]]
330	330
331	331
	355	+= 5. Add Integration =
332	332
333	333
334		-
335		-
336		-= 4. Add Integration =
337		-
338		-
339	339	In the left navigation, click **Integrations center**, and then click **Integrations**.
340	340
341	341
...	...	@@ -395,9 +395,10 @@
395	395	* **Enable SSL**: YES
396	396	* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
397	397	* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
398		-* **Topic: v1/devices/me/telemetry** (The topic can be anything, even you can use just the device name, for example ts02-nb)
	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.)
399	399	* **QoS:** 0-At most once
400	400
	420	+
401	401	[[image:add-integration-connection.png||height="511" width="500"]]
402	402
403	403
...	...	@@ -428,14 +428,13 @@
428	428	Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
429	429
430	430
431		-
432	432	[[image:new-integration-pending.png]]
433	433
434	434
435		-= 5. Verifying the receipt of data from virtual devices =
	454	+= 6. Verifying the receipt of data from virtual devices =
436	436
437	437
438		-== 5.1 How does it work? ==
	457	+== 6.1 How does it work? ==
439	439
440	440
441	441	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.
...	...	@@ -472,7 +472,7 @@
472	472	[[image:new-device.png]]
473	473
474	474
475		-== 5.3 Viewing messages ==
	494	+== 6.3 Viewing messages ==
476	476
477	477
478	478	Go back to the **Integrations** page.
...	...	@@ -512,7 +512,7 @@
512	512	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.
513	513
514	514
515		-= 6. Creating a Dashboard =
	534	+= 7. Creating a Dashboard =
516	516
517	517	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.
518	518
...	...	@@ -595,7 +595,7 @@
595	595	[[image:timeseries-4.png||height="316" width="700"]]
596	596
597	597
598		-= 7. Configure NB-IoT Sensor =
	617	+= 8. Configure NB-IoT Sensor =
599	599
600	600
601	601	Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
...	...	@@ -606,7 +606,7 @@
606	606	**AT Commands**
607	607
608	608	* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
609		-* **AT+SUBTOPIC=<MQTT subscribe topic> **
	628	+* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
610	610	* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
611	611	* **AT+CLIENT=null**
612	612	* **AT+UNAME=<MQTT Username>**