Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 129.1
edited by Dilisi S
on 2025/03/08 22:02
Change comment: There is no comment for this version
To version 175.1
edited by Dilisi S
on 2025/03/20 16:51
Change comment: Mar 20 edits - part 2

Summary

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,6 +141,24 @@
141 141  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
142 142  
143 143  
149 +=== 2.2.2 emqx ===
150 +
151 +
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.
153 +
154 +
155 +[[image:emqx.png||height="420" width="500"]]
156 +
157 +
158 +=== 2.2.3 Ins1.thingseye.io ===
159 +
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.
161 +
162 +If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
163 +
164 +[[image:ins1.png||height="310" width="500"]]
165 +
166 +
144 144  = 3. Data Converters =
145 145  
146 146  
... ... @@ -153,7 +153,6 @@
153 153  In the left navigation, click **Integrations center**, and then click **Data converters**.
154 154  
155 155  
156 -
157 157  [[image:data-converters-list-empty.png]]
158 158  
159 159  
... ... @@ -166,34 +166,133 @@
166 166  
167 167  The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
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.
191 +Click on the **JavaScript** button.
170 170  
171 -{{code language="JavaScript"}}
172 -/** Decoder **/
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.
173 173  
195 +{{info}}
196 +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.
197 +{{/info}}
198 +
199 +{{code language="JavaScript"}}
200 +//Version: 0.1
174 174  // decode payload to string
175 175  var payloadStr = decodeToString(payload);
176 -var data = JSON.parse(payloadStr);
177 177  
178 -var deviceName = metadata.topic.split("/")[3];
179 179  // decode payload to JSON
180 -var deviceType = 'sensor';
205 +var objdata = {};
206 +var obj1 = {};
207 +var data = decodeToJson(payload);
208 +var deviceName = data.IMEI;
209 +delete data.IMEI;
210 +var modelname = "Dragino " + data.Model;
211 +//var mod = data.mod
212 +delete data.Model;
213 +//delete data.mod
214 +var timestamp = new Date().getTime();
181 181  
182 -// Result object with device attributes/telemetry data
216 +for (var key in data) {
217 +
218 + if (Number(key)) {
219 + obj1[key] = data[key];
220 + obj1[key][obj1[key].length - 1] = Number(new Date(
221 + obj1[key][obj1[key].length - 1]));
222 +
223 + }
224 +//Alec submitted25/02/25
225 +//turn old key into new
226 + else if (key === "Reading") {
227 + objdata["reading"] = data[key];
228 + } else if (key === "work mode") {
229 + objdata["work_mode"] = data[key];
230 + } else if (key === "hum") {
231 + objdata["humidity"] = data[key];
232 + }else if (key === "hum2") {
233 + objdata["humidity2"] = data[key];
234 + } else if (key === "hum3") {
235 + objdata["humidity3"] = data[key];
236 + } else if (key === "tem") {
237 + objdata["temperature"] = data[key];
238 + } else if (key === "tem2") {
239 + objdata["temperature2"] = data[key];
240 + } else if (key === "tem3") {
241 + objdata["temperature3"] = data[key];
242 + } else if (key === "DS18B20_Temp") {
243 + objdata["temperature_pro"] = data[key];
244 + } else if (key === "ds18b20_temperature") {
245 + objdata["temperature_pro"] = data[key];
246 + } else if (key === "DS18B20_temperature_pro") {
247 + objdata["temperature_pro"] = data[key];
248 + } else if (key === "tdc send flag") {
249 + objdata["tdc_send_flag"] = data[key];
250 + } else if (key === "trigger mode") {
251 + objdata["trigger_mode"] = data[key];
252 + } else if (key === "soil dielectric constant") {
253 + objdata["soil_dielectric_constant"] = data[key];
254 + } else if (key === "door open num") {
255 + objdata["door_open_num"] = data[key];
256 + } else if (key === "door duration") {
257 + objdata["door_duration"] = data[key];
258 + } else if (key === "count time") {
259 + objdata["count_time"] = data[key];
260 + } else if (key === "last open time2") {
261 + objdata["last_open_time2"] = data[key];
262 + } else if (key === "last open time3") {
263 + objdata["last_open_time3"] = data[key];
264 + }
265 +//Alec submitted25/02/25
266 + else {
267 + objdata[key] = data[key]
268 + }
269 +}
270 +var listdata = [{
271 + "ts": timestamp,
272 + "values": objdata
273 +}]
274 +for (var key1 in obj1) {
275 + if (modelname == "Dragino RS485-NB") {
276 + listdata.push({
277 + "ts": obj1[key1][obj1[key1].length - 1],
278 + "values": {
279 + "Payload": obj1[key1][0],
280 + }
281 + })
282 + } else {
283 + listdata.push({
284 + "ts": obj1[key1][obj1[key1].length - 1],
285 + "values": {
286 + "values": obj1[key1]
287 + },
288 + })
289 + }
290 +}
183 183  var result = {
292 +
184 184   deviceName: deviceName,
185 - deviceType: deviceType,
294 + deviceType: modelname,
186 186   attributes: {
187 - integrationName: metadata['integrationName'],
296 + model: modelname,
297 + //customerName: "NB-CB",
298 + //groupName: "NB-CB",
299 + //integrationName: metadata['integrationName']
300 +
188 188   },
189 - telemetry: {
190 - temperature: data.temperature,
191 - humidity: data.humidity,
192 - }
193 -};
302 + telemetry: listdata
303 +}
194 194  
195 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
305 +function decodeToString(payload) {
306 + return String.fromCharCode.apply(String, payload);
307 +}
196 196  
309 +function decodeToJson(payload) {
310 + // covert payload to string.
311 + var str = decodeToString(payload);
312 +
313 + // parse string to JSON
314 + var data = JSON.parse(str);
315 + return data;
316 +}
317 +
197 197  return result;
198 198  {{/code}}
199 199  
... ... @@ -201,191 +201,308 @@
201 201  Click on the **Add** button.
202 202  
203 203  
325 +[[image:mqtt-uplink.png||width="500"]]
204 204  
205 -[[image:add-uplink-data-converter.png||height="529" width="500"]]
206 206  
207 207  
208 208  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
209 209  
331 +
210 210  [[image:data-converter-list-showing-uplink-dc.png]]
211 211  
212 212  
335 += 4. Add Integration =
213 213  
214 -== 3.2 Downlink ==
215 215  
338 +In the left navigation, click **Integrations center**, and then click **Integrations**.
216 216  
217 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
218 218  
341 +[[image:integrations-list-empty.png]]
219 219  
220 -[[image:create-new-converter-menu.png||width="500"]]
221 221  
344 +On the **Integrations** page, click on the '**+**' button.
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**.
347 +The **Add integration** window appears.
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.
349 +In the **Add integration** window, configure the following settings:
227 227  
228 228  
229 -{{code language="JavaScript"}}
230 -// Encode downlink data from incoming Rule Engine message
352 +**Basic settings:**
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
354 +* **Integration type**: MQTT
355 +* **Name**: MQTT integration NB/CB
356 +* **Enable integration**: YES
357 +* **Allows create devices or assets**: YES
236 236  
237 -/** Encoder **/
359 +Click **Next** button.
238 238  
239 -var data = {};
240 240  
241 -// Process data from incoming message and metadata
362 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
242 242  
243 -data.tempFreq = msg.temperatureUploadFrequency;
244 -data.humFreq = msg.humidityUploadFrequency;
245 245  
246 -data.devSerialNumber = metadata['ss_serialNumber'];
365 +**Uplink data converter:**
247 247  
248 -// Result object with encoded downlink payload
249 -var result = {
367 +* Click on the **Select existing** button.
368 +* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
250 250  
251 - // downlink data content type: JSON, TEXT or BINARY (base64 format)
252 - contentType: "JSON",
370 +Click **Next** button.
253 253  
254 - // downlink data
255 - data: JSON.stringify(data),
256 256  
257 - // Optional metadata object presented in key/value format
258 - metadata: {
259 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
260 - }
373 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
261 261  
262 -};
263 263  
264 -return result;
265 -{{/code}}
376 +**Downlink data converter:**
266 266  
378 +Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
267 267  
380 +* Click on the **Skip **button in the Downlink data converter section.
381 +
382 +Click **Skip** button.
383 +
384 +
385 +[[image:integration-dl-skip.png||height="511" width="500"]]
386 +
387 +
388 +
389 +**Connection:**
390 +
391 +* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
392 +* **Port**: 8883
393 +* **Credentials**: Basic
394 +* **Enable SSL**: YES
395 +* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
396 +* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
397 +* **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.)
398 +* **QoS:** 0-At most once
399 +
400 +
401 +
402 +[[image:add-integration-connection.png||height="511" width="500"]]
403 +
404 +
405 +Click on the **Advanced settings** button.
406 +
407 +* **Clean session:** YES
408 +* **Retained**: YES
409 +
410 +[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
411 +
412 +
413 +Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
414 +
415 +
416 +[[image:check-connection.png||height="83" width="300"]]
417 +
418 +
419 +If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
420 +
421 +
422 +[[image:connection-success.png||height="511" width="500"]]
423 +
424 +
268 268  Click on the **Add** button.
269 269  
427 +You should see that the newly added integration is listed on the **Integrations** page.
270 270  
429 +Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
271 271  
272 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
273 273  
432 +[[image:new-integration-pending.png]]
274 274  
275 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
276 276  
435 += 5. Verifying the receipt of data from virtual devices =
277 277  
278 -[[image:data-converters-list.png]]
279 279  
438 +== 5.1 How does it work? ==
280 280  
281 281  
282 -= 4. Add Integration =
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.
283 283  
443 +The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
284 284  
285 -In the left navigation, click **Integrations center**, and then click **Integrations**.
445 +(% 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.
286 286  
447 +{{code language="none"}}
448 +{"IMEI": "S31B-NB", "temperature": 27, ......}
449 +{{/code}}
287 287  
288 -[[image:integrations-list-empty.png]]
451 +Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
289 289  
290 290  
291 -On the **Integrations** page, click on the '**+**' button.
454 +== 5.2 Sending messages ==
292 292  
293 293  
294 -The **Add integration** window appears.
457 +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.
295 295  
296 -In the **Add integration** window, configure the following settings:
459 +{{code language="none"}}
460 +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}'
461 +{{/code}}
297 297  
463 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
298 298  
299 -**Basic settings:**
300 300  
301 -* **Integration type**: MQTT
302 -* **Name**: MQTT integration NB/CB
303 -* **Enable integration**: YES
304 -* **Allows create devices or assets**: YES
466 +[[image:integration-active.png]]
305 305  
306 -Click **Next** button.
307 307  
469 +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**.
308 308  
309 309  
310 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
472 +[[image:new-device.png]]
311 311  
312 312  
313 -**Uplink data converter:**
475 +== 5.3 Viewing messages ==
314 314  
315 -* Click on the **Select existing** button.
316 -* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
317 317  
318 -Click **Next** button.
478 +Go back to the **Integrations** page.
319 319  
480 +Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
320 320  
482 +Click on the **Edit** button (//**pen icon**//).
321 321  
322 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
484 +Click on the **Disabled** button in the upper-right corner.
323 323  
486 +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.
324 324  
325 -**Downlink data converter:**
488 +Click on the **Apply** button.
326 326  
327 -* Click on the **Select existing** button.
328 -* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
490 +Then click on the **Apply changes** (//**tick icon**//) button.
329 329  
330 -Click **Next** button.
331 331  
493 +[[image:Screenshot 2025-03-18 at 09.23.10.png]]
332 332  
333 333  
334 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
496 +Now go to the **Events** tab.
335 335  
498 +Select the Event type as **Debug** from the dropdown list.
336 336  
337 -**Connection:**
500 +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.
338 338  
339 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
340 -* **Port**: 8883
341 -* **Credentials**: Basic
342 -* **Enable SSL**: YES
343 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
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)
346 -* **QoS:** 0-At most once
347 347  
348 -[[image:add-integration-connection.png||height="511" width="500"]]
503 +[[image:Screenshot 2025-03-16 at 18.38.59.png]]
349 349  
350 350  
351 -Click on the **Advanced settings** button.
506 +Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
352 352  
353 -* **Clean session:** NO
354 -* **Retained**: NO
355 355  
356 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
509 +[[image:Screenshot 2025-03-16 at 18.39.12.png]]
357 357  
358 358  
359 -Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
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.
360 360  
361 361  
362 -[[image:check-connection.png||height="83" width="300"]]
515 += 6. Creating a Dashboard =
363 363  
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.
364 364  
365 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
366 366  
520 +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.
367 367  
368 -[[image:connection-success.png||height="511" width="500"]]
369 369  
523 +First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
370 370  
525 +{{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}}
526 +
527 +
528 +In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
529 +
530 +
531 +[[image:dashboard-1.png]]
532 +
533 +
534 +In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
535 +
371 371  Click on the **Add** button.
372 372  
373 -You should see that the newly added integration is listed on the **Integrations** page.
374 374  
375 -Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
539 +[[image:dashboard-2.png||height="526" width="500"]]
376 376  
377 377  
542 +Click on the **Add widget / Add new widget** button.
378 378  
379 -[[image:new-integration-pending.png]]
380 380  
545 +[[image:dashboard-3.png]]
381 381  
382 -= 5. Verifying the receipt of data from the device =
383 383  
548 +In the **Select widgets bundle** window, click **Charts**.
384 384  
385 -On the terminal, issue the following MQTT command which simulates the device S31B-NB.
386 386  
551 +[[image:dashboard-4.png||height="537" width="700"]]
552 +
553 +
554 +
555 +In the **Charts: select widget** window, click **Time series chart**.
556 +
557 +
558 +[[image:dashboard-5.png||height="525" width="700"]]
559 +
560 +
561 +Configure the **Time series chart** widget as follows:
562 +
563 +* **Datasource** - select S31B-NB device you provisioned.
564 +* **Series**:
565 +** **temperature** - you can see this key by default.
566 +** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
567 +* Click on the **Add** button.
568 +
569 +[[image:timeseries-1.png||height="491" width="700"]]
570 +
571 +
572 +The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
573 +
574 +Click the **Save** button to add the widget to the dashboard.
575 +
576 +
577 +[[image:timeseries-3.png||height="347" width="700"]]
578 +
579 +
580 +Now send the following MQTT messages from the terminal to simulate the data.
581 +
582 +
387 387  {{code language="none"}}
388 -mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
584 +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}'
585 +
586 +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}'
587 +
588 +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}'
589 +
389 389  {{/code}}
390 390  
391 -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.
592 +The chart will update with the values in realtime, as shown in the below image.
593 +
594 +
595 +[[image:timeseries-4.png||height="316" width="700"]]
596 +
597 +
598 += 7. Configure NB-IoT Sensor =
599 +
600 +
601 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
602 +
603 +First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
604 +
605 +
606 +**AT Commands**
607 +
608 +* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
609 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
610 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
611 +* **AT+CLIENT=null**
612 +* **AT+UNAME=<MQTT Username>**
613 +* **AT+PWD=<MQTT Password>**
614 +* **AT+SERVADDR=<Broker address, Port>**
615 +
616 +Test your uplink by pressing the ACT button for 1 second.
617 +
618 +
619 +
620 +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**.
621 +
622 +{{info}}
623 +The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
624 +{{/info}}
625 +
626 +[[image:image-4.png]]
627 +
628 +
629 +
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-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +271.1 KB
Content
dashboard-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +112.2 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
device-provision-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +265.7 KB
Content
device-provision-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +213.9 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-active.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +64.2 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
telemetry-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +191.9 KB
Content
telemetry-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +185.1 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