Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 179.1
edited by Dilisi S
on 2025/03/27 01:21
Change comment: There is no comment for this version
To version 221.1
edited by Dilisi S
on 2025/04/23 01:38
Change comment: April 22 edits

Summary

Details

Page properties
Content
... ... @@ -23,8 +23,9 @@
23 23  
24 24  * ThingsBoard cloud account
25 25  * MQTT Broker (public or private) such as,
26 +** [[ThingsBoard MQTT broker>>https://thingsboard.io/docs/mqtt-broker/]] (TBMQ)
26 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 +** [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] - The public MQTT server is only used for MQTT learning and testing, and should not be used in the production environment.
28 28  ** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
29 29  
30 30  == 2.1 ThingsBoard Cloud ==
... ... @@ -67,11 +67,19 @@
67 67  [[image:thingsboard-6.png||height="244" width="500"]]
68 68  
69 69  
70 -== 2.2 HiveMQ Cloud ==
71 +== 2.2 MQTT Brokers ==
71 71  
72 -=== 2.2.1 HiveMQ Cloud ===
73 +This section introduces some MQTT brokers that you can use to publish messages from the device side and subscribe from the ThingsBoard side.
73 73  
74 74  
76 +=== 2.2.1 ThingsBoard MQTT broker (TBMQ) ===
77 +
78 +The complete instructions for installing, configuring, and using the TBMQ can be found [[here>>https://thingsboard.io/docs/mqtt-broker/getting-started/]].
79 +
80 +
81 +=== 2.2.2 HiveMQ Cloud ===
82 +
83 +
75 75  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
76 76  
77 77  Click on the **Start Free** button.
... ... @@ -146,7 +146,7 @@
146 146  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
147 147  
148 148  
149 -=== 2.2.2 emqx ===
158 +=== 2.2.3 emqx ===
150 150  
151 151  
152 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.
... ... @@ -155,7 +155,7 @@
155 155  [[image:emqx.png||height="420" width="500"]]
156 156  
157 157  
158 -=== 2.2.3 Ins1.thingseye.io ===
167 +=== 2.2.4 Ins1.thingseye.io ===
159 159  
160 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 161  
... ... @@ -164,34 +164,18 @@
164 164  [[image:ins1.png||height="310" width="500"]]
165 165  
166 166  
167 -= 3. Creating Devices =
168 168  
177 += 3. Data Converters =
169 169  
170 -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.
171 171  
172 -
173 -In the left navigation, click Entities -> Devices.
174 -
175 -Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
176 -
177 -In the **Add new device** dialog box, enter the device name in the **Name** text box. For example, we will use **Device A**.
178 -
179 -Click the **Add** button.
180 -
181 -Skip the **connectivity testing** by clicking the **Close** button.
182 -
183 -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.
184 -
185 -
186 -= 4. Data Converters =
187 -
188 -
189 189  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.
190 190  
182 +**In this section, you will create a universal uplink data converter for all Dragino NB-IoT devices. The uplink decoder converts any MQTT message coming from a device into key-value pairs that can be used to display and visualize data using various widgets on the dashboard**.
191 191  
192 -== 4.1 Uplink ==
193 193  
185 +== 3.1 Uplink ==
194 194  
187 +
195 195  In the left navigation, click **Integrations center**, and then click **Data converters**.
196 196  
197 197  
... ... @@ -198,7 +198,7 @@
198 198  [[image:data-converters-list-empty.png]]
199 199  
200 200  
201 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
194 +On the **Data converters** page, click on the ‘**+**’ button, and then click on **Create new converter** from the dropdown menu.
202 202  
203 203  
204 204  
... ... @@ -205,98 +205,75 @@
205 205  [[image:create-new-converter-menu.png||height="259" width="500"]]
206 206  
207 207  
208 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
201 +The **Add data converter** window appears.
209 209  
203 +Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
204 +
210 210  Click on the **TBEL** button if it has not been selected by default.
211 211  
212 -Modify the default TBEL function to match with your device as described below:
207 +Replace the default TBEL decoder function with the following universal TBEL decoder function, which decodes MQTT payload from any Dragino NB-IoT device.
213 213  
214 214  
215 -~1. Uncomment line 11:
216 -
217 -var data = decodeToJson(payload)
218 -
219 -[[image:Screenshot 2025-03-26 at 18.15.08.png||height="219" width="500"]]
220 -
221 -
222 -3. Modify the telemetry section to allow parsed data to be assigned to the fields.
223 -
224 -telemetry: {
225 - temperature: data.temperature,
226 - humidity: data.humidity,
227 - rawData: payloadStr
228 - }
229 -
230 -
231 -
232 232  {{code language="JavaScript"}}
233 -// Decode an uplink message from a buffer
234 -// payload - array of bytes
235 -// metadata - key/value object
236 -
237 -/** Decoder **/
238 -
239 -// decode payload to string
240 -var payloadStr = decodeToString(payload);
241 -
242 242  // decode payload to JSON
212 +var pattern = "yyyy/MM/dd HH:mm:ss";
213 +var objdata = {};
214 +var obj1 = {};
243 243  var data = decodeToJson(payload);
244 -
245 -var deviceName = 'Device B';
246 -var deviceType = 'thermostat';
247 -var customerName = 'Customer C';
248 -var groupName = 'thermostat devices';
249 -var manufacturer = 'Example corporation';
250 -// use assetName and assetType instead of deviceName and deviceType
251 -// to automatically create assets instead of devices.
252 -// var assetName = 'Asset A';
253 -// var assetType = 'building';
254 -
255 -// Result object with device/asset attributes/telemetry data
256 -var result = {
257 -// Use deviceName and deviceType or assetName and assetType, but not both.
258 - deviceName: deviceName,
259 - deviceType: deviceType,
260 -// assetName: assetName,
261 -// assetType: assetType,
262 -// customerName: customerName,
263 - groupName: groupName,
264 - attributes: {
265 - model: 'Model A',
266 - serialNumber: 'SN111',
267 - integrationName: metadata['integrationName'],
268 - manufacturer: manufacturer
269 - },
270 - telemetry: {
271 - temperature: data.temperature,
272 - humidity: data.humidity,
273 - rawData: payloadStr
274 - }
216 +var deviceName = data.IMEI;
217 +data.remove("IMEI");
218 +var modelname = "Dragino "+ data.Model;
219 +//var mod = data.mod
220 +data.remove("Model");
221 +//delete data.mod
222 +var timestamp = new Date().getTime();
223 +foreach (entry: data.entrySet()) {
224 + var key = entry.getKey();
225 + var value = entry.getValue();
226 + //objdata[key] = data[key]
227 + if(key.matches("^-?\\d+$")){ //is number
228 + obj1[key]=data[key];
229 + var index = obj1[key].length-1;
230 + obj1[key][index]=new Date(obj1[key][index],pattern).getTime();
231 + }
232 + else if (key==="bat"||key==="BAT"){
233 + objdata["battery"] = data[key];
234 + }
235 + else{
236 + objdata[key] = data[key];
237 +}}
238 +var listdata = [{"ts":timestamp,"values":objdata}];
239 +foreach ( entry1: obj1.entrySet()){
240 + var key1 = entry1.getKey();
241 + var value1 = entry1.getValue();
242 + var index = obj1[key1].length-1;
243 + var ts = obj1[key1][index];
244 + if (modelname=="Dragino RS485-NB"){
245 + listdata.push({"ts":ts,"values":{"Payload":obj1[key1][0]}});
246 + }
247 + else{
248 + listdata.push({"ts":ts,"values":{"values":obj1[key1]}});
249 + }
250 +}
251 + var result = {
252 + deviceName: deviceName,
253 + deviceType: modelname,
254 + attributes: {
255 + model: modelname
256 + //customerName: "NB-CB",
257 + //groupName: "NB-CB",
258 + //integrationName: metadata['integrationName']
259 + },
260 + telemetry: listdata
275 275  };
276 -
277 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
278 -
279 279  return result;
280 280  {{/code}}
281 281  
282 -We use the same decoder function for all our devices. However, you need to modify a few things for each device. Among these, **deviceName** is a **mandatory** field. You should assign a device name to the **deviceName** field that matches the name of your device in the **Devices** section.
283 283  
284 -For example, if your device name is **Device B**, you can change **Device A** to **Device B**.
285 -
286 -
287 -{{code language="JavaScript"}}
288 -var deviceName = 'Device A';
289 -var deviceType = 'thermostat';
290 -var customerName = 'Customer C';
291 -var groupName = 'thermostat devices';
292 -var manufacturer = 'Example corporation';
293 -{{/code}}
294 -
295 -
296 296  Once you modify the decoder function, click on the **Add** button.
297 297  
298 298  
299 -[[image:mqtt-uplink.png||width="500"]]
269 +[[image:mqtt-uplink-converter.png||height="498" width="500"]]
300 300  
301 301  
302 302  
... ... @@ -303,12 +303,13 @@
303 303  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
304 304  
305 305  
306 -[[image:data-converter-list-showing-uplink-dc.png]]
307 307  
277 +[[image:data-converters-list.png]]
308 308  
309 -= 5. Add Integration =
310 310  
280 += 4. Add Integration =
311 311  
282 +
312 312  In the left navigation, click **Integrations center**, and then click **Integrations**.
313 313  
314 314  
... ... @@ -326,16 +326,17 @@
326 326  **Basic settings:**
327 327  
328 328  * **Integration type**: MQTT
329 -* **Name**: MQTT integration NB/CB
300 +* **Name**: MQTT integration
330 330  * **Enable integration**: YES
331 -* **Allows create devices or assets**: YES
302 +* **Allow create devices or assets**: YES
332 332  
333 333  Click **Next** button.
334 334  
335 335  
336 -[[image:add-integration-basic-settings.png||height="511" width="500"]]
337 337  
308 +[[image:add-integration-part-1.png||height="483" width="500"]]
338 338  
310 +
339 339  **Uplink data converter:**
340 340  
341 341  * Click on the **Select existing** button.
... ... @@ -344,9 +344,10 @@
344 344  Click **Next** button.
345 345  
346 346  
347 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
348 348  
320 +[[image:add-integration-part-2.png||height="484" width="500"]]
349 349  
322 +
350 350  **Downlink data converter:**
351 351  
352 352  Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
... ... @@ -362,16 +362,16 @@
362 362  
363 363  **Connection:**
364 364  
365 -* **Host**: Cluster URL (Eg. **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
366 -* **Port**: 8883
367 -* **Credentials**: Basic
368 -* **Enable SSL**: YES
338 +* **Host**: Host URL (Eg, **//011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud//**)
339 +* **Port**: 8883 (the port number may differ based on your MQTT broker)
340 +* **Credentials type**: Basic
369 369  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
370 370  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
371 -* **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 devices/a/telemetry.)
343 +* **Enable SSL**: YES
344 +* **Topic**: # (the # symbol indicates that it filters all topics).
372 372  * **QoS:** 0-At most once
373 373  
374 -[[image:add-integration-connection.png||height="511" width="500"]]
347 +[[image:add-integration-4.png||height="484" width="500"]]
375 375  
376 376  
377 377  Click on the **Advanced settings** button.
... ... @@ -401,55 +401,59 @@
401 401  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
402 402  
403 403  
404 -[[image:new-integration-pending.png]]
405 405  
378 +[[image:integrations-pending.png]]
406 406  
407 -= 6. Verifying the receipt of data from virtual devices =
408 408  
381 += 5. Verifying the receipt of data from virtual devices =
409 409  
410 -== 6.1 How does it work? ==
411 411  
384 +== 5.1 How does it work? ==
412 412  
386 +
413 413  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.
414 414  
415 -The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
389 +The Mosquitto client publishes messages (payloads) to a topic - for example, # or device/ts01-nb. You can, of course, use any topic you prefer.
416 416  
417 -(% 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.
418 418  
392 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows. The **IMEI **and **Model **are mandatory fields. For other fields, you can use any number of key-value pairs.
393 +
419 419  {{code language="none"}}
420 -{"IMEI": "S31B-NB", "temperature": 27, ......}
395 +{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
421 421  {{/code}}
422 422  
423 -Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
424 424  
425 -
426 426  == 5.2 Sending messages ==
427 427  
428 428  
429 -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.
402 +On your computer's terminal, issue the following MQTT command, which simulates the device named '**350693903995577'**. The message payload contains the fields IMEI, Model, temperature, humidity, and pressure, which hold the values 350693903995577,  TS01-NB, 30, 80, and 1005 respectively. This payload is also (technically) known as telemetry.
430 430  
431 431  {{code language="none"}}
432 -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}'
405 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/350693903995577" -m '{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}'
433 433  {{/code}}
434 434  
435 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
408 +If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
436 436  
437 437  
438 -[[image:integration-active.png]]
411 +[[image:new-device-1.png]]
439 439  
440 440  
441 -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**.
414 +The status of the integration also changes to '**Active**' after the first telemetry transmission.
442 442  
443 443  
444 -[[image:new-device.png]]
417 +[[image:Screenshot 2025-04-21 122154.png]]
445 445  
446 446  
447 -== 6.3 Viewing messages ==
448 448  
421 +**When ThingsBoard receives this message for the first time, it will automatically create a new device named '350693903995577' in the Devices section. The device name is based on the IMEI number. For subsequent messages with the same IMEI, no duplicate devices will be created. Each new IMEI number will result in a unique entry in the Devices section, representing a physical device.**
449 449  
423 +
424 +== 5.3 Viewing messages ==
425 +
426 +
450 450  Go back to the **Integrations** page.
451 451  
452 -Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
429 +Click on the **MQTT integration** in the **Integrations** page to see its details.
453 453  
454 454  Click on the **Edit** button (//**pen icon**//).
455 455  
... ... @@ -462,29 +462,34 @@
462 462  Then click on the **Apply changes** (//**tick icon**//) button.
463 463  
464 464  
465 -[[image:Screenshot 2025-03-18 at 09.23.10.png]]
466 466  
443 +[[image:Screenshot 2025-04-21 122936.png||height="247" width="500"]]
467 467  
445 +
468 468  Now go to the **Events** tab.
469 469  
470 -Select the Event type as **Debug** from the dropdown list.
448 +Select the **Event type** as **Debug** from the dropdown list.
471 471  
472 -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.
450 +Publish another message (of course, you can repeat the previous message by pressing the UP arrow on your keyboard and then press Enter key) to your MQTT broker from your terminal, for example:
473 473  
452 +{{code language="none"}}
453 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/350693903995577" -m '{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":82, "pressure":1005}'
454 +{{/code}}
474 474  
475 -[[image:Screenshot 2025-03-16 at 18.38.59.png]]
456 +Now you can see that uplink message in the **Events** tab (Click the **refresh** button if you didn't see any messages in the Events tab). The status should be **OK **if there is no errors in your integration.
476 476  
477 477  
478 478  Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
479 479  
480 480  
481 -[[image:Screenshot 2025-03-16 at 18.39.12.png]]
482 482  
463 +[[image:Screenshot 2025-04-21 122909.png]]
483 483  
465 +
484 484  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.
485 485  
486 486  
487 -= 7. Creating a Dashboard =
469 += 6. Creating a Dashboard =
488 488  
489 489  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.
490 490  
... ... @@ -492,11 +492,6 @@
492 492  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.
493 493  
494 494  
495 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
496 -
497 -{{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}}
498 -
499 -
500 500  In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
501 501  
502 502  
... ... @@ -532,44 +532,41 @@
532 532  
533 533  Configure the **Time series chart** widget as follows:
534 534  
535 -* **Datasource** - select S31B-NB device you provisioned.
512 +* **Datasource** - select **350693903995577 **you provisioned.
536 536  * **Series**:
537 537  ** **temperature** - you can see this key by default.
538 -** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
515 +** **humidity** - Click **Add series** button. Then choose **humidity** for the key, and then type **%** as its unit.
516 +** pressure -  Click **Add series** button. Then choose **humidity** for the key, and then type Pa as its unit.
539 539  * Click on the **Add** button.
540 540  
541 -[[image:timeseries-1.png||height="491" width="700"]]
519 +{{info}}
520 +You can add only the relevant fields from the device's payload to display data on a widget. These fields are called 'keys'.
521 +{{/info}}
542 542  
543 543  
544 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
545 545  
546 -Click the **Save** button to add the widget to the dashboard.
525 +[[image:Screenshot 2025-04-21 123647.png||height="466" width="700"]]
547 547  
548 548  
549 -[[image:timeseries-3.png||height="347" width="700"]]
528 +The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
550 550  
530 +Click the **Save** button to add the widget to the dashboard.
551 551  
552 -Now send the following MQTT messages from the terminal to simulate the data.
553 553  
533 +[[image:Screenshot 2025-04-21 124145.png||height="443" width="700"]]
554 554  
555 -{{code language="none"}}
556 -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}'
557 557  
558 -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}'
536 +**Now send a few MQTT messages from the terminal to simulate the data. Use different values for temperature, humidity, and pressure in each message.**
559 559  
560 -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}'
538 +**The chart will update with the values in real time, and you will see a live chart similar to this:**
561 561  
562 -{{/code}}
563 563  
564 -The chart will update with the values in realtime, as shown in the below image.
541 +[[image:Screenshot 2025-04-21 124054.png||height="441" width="700"]]
565 565  
566 566  
567 -[[image:timeseries-4.png||height="316" width="700"]]
544 += 8. Configure Physical NB-IoT Sensor =
568 568  
569 569  
570 -= 8. Configure NB-IoT Sensor =
571 -
572 -
573 573  Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
574 574  
575 575  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
... ... @@ -578,8 +578,8 @@
578 578  **AT Commands**
579 579  
580 580  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
581 -* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: TS01-NB**
582 -* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
555 +* **AT+SUBTOPIC=<MQTT subscribe topic> Eg: # -  **You can leave the SUBTOPIC configuration as it is, since we are not sending downlink messages to the device at the moment.
556 +* **AT+PUBTOPIC=<MQTT publish topic> Eg: #**
583 583  * **AT+CLIENT=null**
584 584  * **AT+UNAME=<MQTT Username>**
585 585  * **AT+PWD=<MQTT Password>**
... ... @@ -588,14 +588,7 @@
588 588  Test your uplink by pressing the ACT button for 1 second.
589 589  
590 590  
565 +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.
591 591  
592 -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**.
593 593  
594 -{{info}}
595 -The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
596 -{{/info}}
597 -
598 598  [[image:image-4.png]]
599 -
600 -
601 -
add-integration-basic-settings.png
Size
... ... @@ -1,1 +1,1 @@
1 -122.5 KB
1 +123.8 KB
Content
data-converters-list.png
Size
... ... @@ -1,1 +1,1 @@
1 -212.2 KB
1 +19.0 KB
Content
integration-active.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.2 KB
1 +64.1 KB
Content
Screenshot 2025-03-26 at 19.47.52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.4 KB
Content
Screenshot 2025-03-26 at 19.49.31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +133.0 KB
Content
Screenshot 2025-03-31 at 06.51.15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +179.5 KB
Content
Screenshot 2025-04-21 122154.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +21.2 KB
Content
Screenshot 2025-04-21 122909.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +59.9 KB
Content
Screenshot 2025-04-21 122936.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +72.0 KB
Content
Screenshot 2025-04-21 123647.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +77.9 KB
Content
Screenshot 2025-04-21 124054.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +60.4 KB
Content
Screenshot 2025-04-21 124145.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +50.9 KB
Content
add-integartion-connection.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +110.3 KB
Content
add-integartion-connetcion.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +146.0 KB
Content
add-integration-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +63.1 KB
Content
add-integration-part-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +48.6 KB
Content
add-integration-part-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +47.7 KB
Content
add-integration-ul-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +121.2 KB
Content
debug-enabled.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.3 KB
Content
device-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +34.5 KB
Content
integration-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +196.2 KB
Content
integrations-pending.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +19.8 KB
Content
mqtt-uplink-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +75.3 KB
Content
new-device-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +34.7 KB
Content
ul-data-converter-added.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +189.4 KB
Content
ul-data-converter-device-a.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +168.3 KB
Content