Changes for page ThingsBoard

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (1 modified, 15 added, 0 removed)
  • add-integration-connection.png
  • Screenshot 2025-03-16 at 18.38.59.png
  • Screenshot 2025-03-16 at 18.39.12.png
  • Screenshot 2025-03-18 at 09.23.10.png
  • dashboard-3.png
  • dashboard-4.png
  • dashboard-5.png
  • emqx.png
  • image-4.png
  • ins1.png
  • integration-dl-skip.png
  • mqtt-uplink.png
  • new-device.png
  • timeseries-1.png
  • timeseries-3.png
  • timeseries-4.png

Details

Page properties

Content

...	...	@@ -22,7 +22,10 @@
22	22	To complete this tutorial, you need to have the following:
23	23
24	24	* ThingsBoard cloud account
25		-* HiveMQ Cloud account
	25	+* MQTT Broker (public or private) such as,
	26	+** **[[HiveMQ Cloud>>https://www.hivemq.com]] - You can create a free account to try it or subscribe for a paid account. - We use HiveMQ Cloud as the MQTT broker to build example in this tutorial.**
	27	+** [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] - The public MQTT server is only used for MOTT learning and testing, and should not be used in the production environment.
	28	+** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
26	26
27	27	== 2.1 ThingsBoard Cloud ==
28	28
...	...	@@ -66,7 +66,9 @@
66	66
67	67	== 2.2 HiveMQ Cloud ==
68	68
	72	+=== 2.2.1 HiveMQ Cloud ===
69	69
	74	+
70	70	Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
71	71
72	72	Click on the **Start Free** button.
...	...	@@ -141,126 +141,195 @@
141	141	You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
142	142
143	143
144		-= 3. Data Converters =
	149	+=== 2.2.2 emqx ===
145	145
146	146
147		-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.
	152	+The [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] public MQTT server is only used for MOTT learning and testing, and should not be used in the production environment.
148	148
149	149
150		-== 3.1 Uplink ==
	155	+[[image:emqx.png||height="420" width="500"]]
151	151
152	152
153		-In the left navigation, click **Integrations center**, and then click **Data converters**.
	158	+=== 2.2.3 Ins1.thingseye.io ===
154	154
	160	+[[lns1.thingseye.io>>http://lns1.thingseye.io/]] is the Dragino's MQTT broker, which requires a CA certificate file, Certificate file, and the Private key file to use.
155	155
	162	+If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
156	156
157		-[[image:data-converters-list-empty.png]]
	164	+[[image:ins1.png||height="310" width="500"]]
158	158
159	159
160		-On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
	167	+(% class="wikigeneratedid" %)
	168	+= 3. Creating Devices =
161	161
162	162
	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.
163	163
164		-[[image:create-new-converter-menu.png||height="259" width="500"]]
165	165
	174	+In the left navigation, click Entities -> Devices.
166	166
167		-The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
	176	+Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
168	168
169		-Click on the **TBEL** button if not selected it by default. Delete the existing decoder function in the code editor. Now copy and paste the following decoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
	178	+In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
170	170
171		-{{code language="JavaScript"}}
172		-/** Decoder **/
	180	+Click the **Add** button.
173	173
174		-// decode payload to string
175		-var payloadStr = decodeToString(payload);
176		-var data = JSON.parse(payloadStr);
	182	+Skip the **connectivity testing** by clicking the **Close** button.
177	177
178		-var deviceName = metadata.topic.split("/")[3];
179		-// decode payload to JSON
180		-var deviceType = 'sensor';
	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.
181	181
182		-// Result object with device attributes/telemetry data
183		-var result = {
184		- deviceName: deviceName,
185		- deviceType: deviceType,
186		- attributes: {
187		- integrationName: metadata['integrationName'],
188		- },
189		- telemetry: {
190		- temperature: data.temperature,
191		- humidity: data.humidity,
192		- }
193		-};
194	194
195		-/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
	187	+= 4. Data Converters =
196	196
197		-return result;
198		-{{/code}}
199	199
	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.
200	200
201		-Click on the **Add** button.
202	202
	193	+== 4.1 Uplink ==
203	203
204	204
205		-[[image:add-uplink-data-converter.png||height="529" width="500"]]
	196	+In the left navigation, click **Integrations center**, and then click **Data converters**.
206	206
207	207
208		-You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
	199	+[[image:data-converters-list-empty.png]]
209	209
210		-[[image:data-converter-list-showing-uplink-dc.png]]
211	211
212		-
213		-
214		-== 3.2 Downlink ==
215		-
216		-
217	217	On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
218	218
219	219
220		-[[image:create-new-converter-menu.png||width="500"]]
221	221
	206	+[[image:create-new-converter-menu.png||height="259" width="500"]]
222	222
223	223
224		-The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
	209	+The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
225	225
226		-Click on the **TBEL** button if not selected it by default. Now copy and paste the following encoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This encoder function is compatible for both NB and CB series devices.
	211	+Click on the **JavaScript** button.
227	227
	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.
228	228
	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	+
229	229	{{code language="JavaScript"}}
230		-// Encode downlink data from incoming Rule Engine message
	220	+//Version: 0.1
	221	+// decode payload to string
	222	+var payloadStr = decodeToString(payload);
231	231
232		-// msg - JSON message payload downlink message json
233		-// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
234		-// metadata - list of key-value pairs with additional data about the message
235		-// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
	224	+// decode payload to JSON
	225	+var objdata = {};
	226	+var obj1 = {};
	227	+var data = decodeToJson(payload);
	228	+var deviceName = data.IMEI;
	229	+delete data.IMEI;
	230	+var modelname = "Dragino " + data.Model;
	231	+//var mod = data.mod
	232	+delete data.Model;
	233	+//delete data.mod
	234	+var timestamp = new Date().getTime();
236	236
237		-/** Encoder **/
	236	+for (var key in data) {
	237	+
	238	+ if (Number(key)) {
	239	+ obj1[key] = data[key];
	240	+ obj1[key][obj1[key].length - 1] = Number(new Date(
	241	+ obj1[key][obj1[key].length - 1]));
238	238
239		-var data = {};
240		-
241		-// Process data from incoming message and metadata
242		-
243		-data.tempFreq = msg.temperatureUploadFrequency;
244		-data.humFreq = msg.humidityUploadFrequency;
245		-
246		-data.devSerialNumber = metadata['ss_serialNumber'];
247		-
248		-// Result object with encoded downlink payload
	243	+ }
	244	+//Alec submitted25/02/25
	245	+//turn old key into new
	246	+ else if (key === "Reading") {
	247	+ objdata["reading"] = data[key];
	248	+ } else if (key === "work mode") {
	249	+ objdata["work_mode"] = data[key];
	250	+ } else if (key === "hum") {
	251	+ objdata["humidity"] = data[key];
	252	+ }else if (key === "hum2") {
	253	+ objdata["humidity2"] = data[key];
	254	+ } else if (key === "hum3") {
	255	+ objdata["humidity3"] = data[key];
	256	+ } else if (key === "tem") {
	257	+ objdata["temperature"] = data[key];
	258	+ } else if (key === "tem2") {
	259	+ objdata["temperature2"] = data[key];
	260	+ } else if (key === "tem3") {
	261	+ objdata["temperature3"] = data[key];
	262	+ } else if (key === "DS18B20_Temp") {
	263	+ objdata["temperature_pro"] = data[key];
	264	+ } else if (key === "ds18b20_temperature") {
	265	+ objdata["temperature_pro"] = data[key];
	266	+ } else if (key === "DS18B20_temperature_pro") {
	267	+ objdata["temperature_pro"] = data[key];
	268	+ } else if (key === "tdc send flag") {
	269	+ objdata["tdc_send_flag"] = data[key];
	270	+ } else if (key === "trigger mode") {
	271	+ objdata["trigger_mode"] = data[key];
	272	+ } else if (key === "soil dielectric constant") {
	273	+ objdata["soil_dielectric_constant"] = data[key];
	274	+ } else if (key === "door open num") {
	275	+ objdata["door_open_num"] = data[key];
	276	+ } else if (key === "door duration") {
	277	+ objdata["door_duration"] = data[key];
	278	+ } else if (key === "count time") {
	279	+ objdata["count_time"] = data[key];
	280	+ } else if (key === "last open time2") {
	281	+ objdata["last_open_time2"] = data[key];
	282	+ } else if (key === "last open time3") {
	283	+ objdata["last_open_time3"] = data[key];
	284	+ }
	285	+//Alec submitted25/02/25
	286	+ else {
	287	+ objdata[key] = data[key]
	288	+ }
	289	+}
	290	+var listdata = [{
	291	+ "ts": timestamp,
	292	+ "values": objdata
	293	+}]
	294	+for (var key1 in obj1) {
	295	+ if (modelname == "Dragino RS485-NB") {
	296	+ listdata.push({
	297	+ "ts": obj1[key1][obj1[key1].length - 1],
	298	+ "values": {
	299	+ "Payload": obj1[key1][0],
	300	+ }
	301	+ })
	302	+ } else {
	303	+ listdata.push({
	304	+ "ts": obj1[key1][obj1[key1].length - 1],
	305	+ "values": {
	306	+ "values": obj1[key1]
	307	+ },
	308	+ })
	309	+ }
	310	+}
249	249	var result = {
250	250
251		- // downlink data content type: JSON, TEXT or BINARY (base64 format)
252		- contentType: "JSON",
	313	+ deviceName: deviceName,
	314	+ deviceType: modelname,
	315	+ attributes: {
	316	+ model: modelname,
	317	+ //customerName: "NB-CB",
	318	+ //groupName: "NB-CB",
	319	+ //integrationName: metadata['integrationName']
253	253
254		- // downlink data
255		- data: JSON.stringify(data),
	321	+ },
	322	+ telemetry: listdata
	323	+}
256	256
257		- // Optional metadata object presented in key/value format
258		- metadata: {
259		- topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
260		- }
	325	+function decodeToString(payload) {
	326	+ return String.fromCharCode.apply(String, payload);
	327	+}
261	261
262		-};
	329	+function decodeToJson(payload) {
	330	+ // covert payload to string.
	331	+ var str = decodeToString(payload);
263	263
	333	+ // parse string to JSON
	334	+ var data = JSON.parse(str);
	335	+ return data;
	336	+}
	337	+
264	264	return result;
265	265	{{/code}}
266	266
...	...	@@ -268,20 +268,19 @@
268	268	Click on the **Add** button.
269	269
270	270
	345	+[[image:mqtt-uplink.png||width="500"]]
271	271
272		-[[image:add-downlink-data-converter.png||height="529" width="500"]]
273	273
274	274
275		-You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
	349	+You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
276	276
277	277
278		-[[image:data-converters-list.png]]
	352	+[[image:data-converter-list-showing-uplink-dc.png]]
279	279
280	280
	355	+= 5. Add Integration =
281	281
282		-= 4. Add Integration =
283	283
284		-
285	285	In the left navigation, click **Integrations center**, and then click **Integrations**.
286	286
287	287
...	...	@@ -306,7 +306,6 @@
306	306	Click **Next** button.
307	307
308	308
309		-
310	310	[[image:add-integration-basic-settings.png||height="511" width="500"]]
311	311
312	312
...	...	@@ -318,40 +318,41 @@
318	318	Click **Next** button.
319	319
320	320
321		-
322	322	[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
323	323
324	324
325	325	**Downlink data converter:**
326	326
327		-* Click on the **Select existing** button.
328		-* **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.
329	329
330		-Click **Next** button.
	400	+* Click on the **Skip **button in the Downlink data converter section.
331	331
	402	+Click **Skip** button.
332	332
333	333
334		-[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
	405	+[[image:integration-dl-skip.png||height="511" width="500"]]
335	335
336	336
	408	+
337	337	**Connection:**
338	338
339		-* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
	411	+* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
340	340	* **Port**: 8883
341	341	* **Credentials**: Basic
342	342	* **Enable SSL**: YES
343	343	* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
344	344	* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
345		-* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices 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.)
346	346	* **QoS:** 0-At most once
347	347
	420	+
348	348	[[image:add-integration-connection.png||height="511" width="500"]]
349	349
350	350
351	351	Click on the **Advanced settings** button.
352	352
353		-* **Clean session:** NO
354		-* **Retained**: NO
	426	+* **Clean session:** YES
	427	+* **Retained**: YES
355	355
356	356	[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
357	357
...	...	@@ -375,47 +375,201 @@
375	375	Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
376	376
377	377
378		-
379	379	[[image:new-integration-pending.png]]
380	380
381	381
382		-= 5. Verifying the receipt of data from virtual devices =
	454	+= 6. Verifying the receipt of data from virtual devices =
383	383
384	384
385		-== 5.1 How does it work? ==
	457	+== 6.1 How does it work? ==
386	386
	459	+
387	387	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.
388	388
389		-The Mosquitto client publishes messages on the topic v1/devices/[device_name]/telemetry. The [device_name]placeholder can be replaced with any device name, for example, 'S31B-NB'. Then, the MQTT topic would be v1/devices/S31B-NB/telemetry.
	462	+The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
390	390
391		-On the ThingsBoard side, we configure the MQTT topic subscription as v1/devices/+/telemetry. The + wildcard represents any device name and allows ThingsBoard to automatically create (provision) a device with that name, such as S31B-NB, for example.
	464	+(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows, which is common for all **~-~-NB** and **~-~-CB** series devices. The **IMEI** field is mandatory and is used to provision a new device with the name assigned to it in ThingsBoard.
392	392
	466	+{{code language="none"}}
	467	+{"IMEI": "S31B-NB", "temperature": 27, ......}
	468	+{{/code}}
393	393
394		-**The new device is created the first time the MQTT topic is received. For subsequent MQTT topics with the same device name, no duplicate devices will be created.**
	470	+Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
395	395
396	396
397		-For example, if you send two MQTT messages with different device names in the topic:
	473	+== 5.2 Sending messages ==
398	398
399		-1. v1/devices/**S31B-NB**/telemetry
400		-1. v1/devices/**S31B-CB**/telemetry
401	401
402		-ThingsBoard will create two devices named **S31B-NB** and **S31B-CB** in the **//Devices//** section.
	476	+On the terminal, issue the following MQTT command which simulates the device S31B-NB. The message payload contains the fields temperature and humidity, which hold the values S31B-NB and 27, respectively. This payload is also (technically) known as telemetry.
403	403
404		-
405		-The MQTT payload format is as follows, for example:
406		-
407	407	{{code language="none"}}
408		-{"temperature":10.4, "humidity":85}
	479	+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}'
409	409	{{/code}}
410	410
	482	+If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
411	411
412		-== 5.2 Sending messages ==
413	413
	485	+[[image:integration-active.png]]
414	414
415		-On the terminal, issue the following MQTT command which simulates the device S31B-NB. The message payload contains the fields temperature and humidity, which hold the values 10.4 and 85, respectively. This payload is also (technically) known as telemetry.
416	416
	488	+Also, a new device named **S31B-NB** will appear under **//Entities -> Devices -> All//**. This means the first MQTT message triggers ThingsBoard to provision a device named **S31B-NB**.
	489	+
	490	+
	491	+[[image:new-device.png]]
	492	+
	493	+
	494	+== 6.3 Viewing messages ==
	495	+
	496	+
	497	+Go back to the **Integrations** page.
	498	+
	499	+Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
	500	+
	501	+Click on the **Edit** button (//**pen icon**//).
	502	+
	503	+Click on the **Disabled** button in the upper-right corner.
	504	+
	505	+Turn on the **All messages (15 min)** option. This will enable displaying all messages in the **Events** tab. This setting will expire in 15 minutes, and you will need to repeat the same steps if you want to view the messages in the Events tab later.
	506	+
	507	+Click on the **Apply** button.
	508	+
	509	+Then click on the **Apply changes** (//**tick icon**//) button.
	510	+
	511	+
	512	+[[image:Screenshot 2025-03-18 at 09.23.10.png]]
	513	+
	514	+
	515	+Now go to the **Events** tab.
	516	+
	517	+Select the Event type as **Debug** from the dropdown list.
	518	+
	519	+Now you can see all the Uplink messages you are simulating through the MQTT broker. The status should be OK if there is no errors in your integration.
	520	+
	521	+
	522	+[[image:Screenshot 2025-03-16 at 18.38.59.png]]
	523	+
	524	+
	525	+Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
	526	+
	527	+
	528	+[[image:Screenshot 2025-03-16 at 18.39.12.png]]
	529	+
	530	+
	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	+
	533	+
	534	+= 7. Creating a Dashboard =
	535	+
	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	+
	538	+
	539	+This section guides you on how to create a dashboard to display temperature and humidity data from the device on a time-series chart. You may also use other widgets in ThingsBoard to display data according to your requirements.
	540	+
	541	+
	542	+First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
	543	+
	544	+{{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}}
	545	+
	546	+
	547	+In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
	548	+
	549	+
	550	+[[image:dashboard-1.png]]
	551	+
	552	+
	553	+In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
	554	+
	555	+Click on the **Add** button.
	556	+
	557	+
	558	+[[image:dashboard-2.png||height="526" width="500"]]
	559	+
	560	+
	561	+Click on the **Add widget / Add new widget** button.
	562	+
	563	+
	564	+[[image:dashboard-3.png]]
	565	+
	566	+
	567	+In the **Select widgets bundle** window, click **Charts**.
	568	+
	569	+
	570	+[[image:dashboard-4.png||height="537" width="700"]]
	571	+
	572	+
	573	+
	574	+In the **Charts: select widget** window, click **Time series chart**.
	575	+
	576	+
	577	+[[image:dashboard-5.png||height="525" width="700"]]
	578	+
	579	+
	580	+Configure the **Time series chart** widget as follows:
	581	+
	582	+* **Datasource** - select S31B-NB device you provisioned.
	583	+* **Series**:
	584	+** **temperature** - you can see this key by default.
	585	+** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
	586	+* Click on the **Add** button.
	587	+
	588	+[[image:timeseries-1.png||height="491" width="700"]]
	589	+
	590	+
	591	+The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
	592	+
	593	+Click the **Save** button to add the widget to the dashboard.
	594	+
	595	+
	596	+[[image:timeseries-3.png||height="347" width="700"]]
	597	+
	598	+
	599	+Now send the following MQTT messages from the terminal to simulate the data.
	600	+
	601	+
417	417	{{code language="none"}}
418		-mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/SN-001/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":10.4, "humidity":85}'
	603	+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}'
	604	+
	605	+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}'
	606	+
	607	+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}'
	608	+
419	419	{{/code}}
420	420
421		-If the integration was performed without errors, after the transmission of the first telemetry, a new device with the name “S31B-NB” will appear in the Devices → All. Also, you can verify the input and output data, respectively, before and after conversion in Data converters → UDP Uplink Converter NB/CB → Events.
	611	+The chart will update with the values in realtime, as shown in the below image.
	612	+
	613	+
	614	+[[image:timeseries-4.png||height="316" width="700"]]
	615	+
	616	+
	617	+= 8. Configure NB-IoT Sensor =
	618	+
	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**.
	621	+
	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	+
	624	+
	625	+**AT Commands**
	626	+
	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**
	629	+* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
	630	+* **AT+CLIENT=null**
	631	+* **AT+UNAME=<MQTT Username>**
	632	+* **AT+PWD=<MQTT Password>**
	633	+* **AT+SERVADDR=<Broker address, Port>**
	634	+
	635	+Test your uplink by pressing the ACT button for 1 second.
	636	+
	637	+
	638	+
	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	+
	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	+[[image:image-4.png]]
	646	+
	647	+
	648	+

add-integration-connection.png

Size

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

Content

Screenshot 2025-03-16 at 18.38.59.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+221.2 KB

Content

Screenshot 2025-03-16 at 18.39.12.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

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

Content

Screenshot 2025-03-18 at 09.23.10.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+78.7 KB

Content

dashboard-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+141.3 KB

Content

dashboard-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+803.7 KB

Content

dashboard-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+476.1 KB

Content

emqx.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+39.1 KB

Content

image-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+96.0 KB

Content

ins1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+28.8 KB

Content

integration-dl-skip.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+105.5 KB

Content

mqtt-uplink.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+175.1 KB

Content

new-device.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+143.3 KB

Content

timeseries-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+179.1 KB

Content

timeseries-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+174.2 KB

Content

timeseries-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+159.0 KB

Content