Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (2 modified, 0 added, 0 removed)
  • Screenshot 2025-03-16 at 18.39.12.png
  • add-integration-connection.png

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
...	...	@@ -376,15 +376,17 @@
376	376
377	377	**Downlink data converter:**
378	378
379		-* Click on the **Select existing** button.
380		-* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
	398	+Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
381	381
382		-Click **Next** button.
	400	+* Click on the **Skip **button in the Downlink data converter section.
383	383
	402	+Click **Skip** button.
384	384
385		-[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
386	386
	405	+[[image:integration-dl-skip.png||height="511" width="500"]]
387	387
	407	+
	408	+
388	388	**Connection:**
389	389
390	390	* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
...	...	@@ -393,9 +393,10 @@
393	393	* **Enable SSL**: YES
394	394	* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
395	395	* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
396		-* **Topic: v1/devices/+/telemetry** (the + replaces any 'device name' will create a device in the Entities -> Devices)
	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.)
397	397	* **QoS:** 0-At most once
398	398
	420	+
399	399	[[image:add-integration-connection.png||height="511" width="500"]]
400	400
401	401
...	...	@@ -426,14 +426,13 @@
426	426	Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
427	427
428	428
429		-
430	430	[[image:new-integration-pending.png]]
431	431
432	432
433		-= 5. Verifying the receipt of data from virtual devices =
	454	+= 6. Verifying the receipt of data from virtual devices =
434	434
435	435
436		-== 5.1 How does it work? ==
	457	+== 6.1 How does it work? ==
437	437
438	438
439	439	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.
...	...	@@ -470,7 +470,7 @@
470	470	[[image:new-device.png]]
471	471
472	472
473		-== 5.3 Viewing messages ==
	494	+== 6.3 Viewing messages ==
474	474
475	475
476	476	Go back to the **Integrations** page.
...	...	@@ -510,7 +510,7 @@
510	510	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.
511	511
512	512
513		-= 6. Creating a Dashboard =
	534	+= 7. Creating a Dashboard =
514	514
515	515	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.
516	516
...	...	@@ -593,10 +593,10 @@
593	593	[[image:timeseries-4.png||height="316" width="700"]]
594	594
595	595
596		-= 7. Configure NB-IoT Sensor =
	617	+= 8. Configure NB-IoT Sensor =
597	597
598	598
599		-Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
	620	+Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
600	600
601	601	First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
602	602
...	...	@@ -604,7 +604,7 @@
604	604	**AT Commands**
605	605
606	606	* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
607		-* **AT+SUBTOPIC=<MQTT subscribe topic> **
	628	+* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
608	608	* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
609	609	* **AT+CLIENT=null**
610	610	* **AT+UNAME=<MQTT Username>**
...	...	@@ -612,10 +612,15 @@
612	612	* **AT+SERVADDR=<Broker address, Port>**
613	613
614	614	Test your uplink by pressing the ACT button for 1 second.
	636	+
615	615
616	616
617	617	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**.
618	618
	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	+
619	619	[[image:image-4.png]]
620	620
621	621

Screenshot 2025-03-16 at 18.39.12.png

Size

...	...	@@ -1,1 +1,1 @@
1		-277.0 KB
	1	+211.9 KB

Content

add-integration-connection.png

Size

...	...	@@ -1,1 +1,1 @@
1		-153.2 KB
	1	+158.1 KB

Content