Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 222.1
edited by Dilisi S
on 2025/04/23 19:23
Change comment: There is no comment for this version
To version 155.1
edited by Dilisi S
on 2025/03/17 00:27
Change comment: Mar 16 edits - part 1

Summary

Details

Page properties
Content
... ... @@ -23,9 +23,8 @@
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)
27 -** **[[HiveMQ Cloud>>https://www.hivemq.com]] **-** **You can create a free account to try it or subscribe for a paid account.
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.
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.
29 29  ** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
30 30  
31 31  == 2.1 ThingsBoard Cloud ==
... ... @@ -68,19 +68,12 @@
68 68  [[image:thingsboard-6.png||height="244" width="500"]]
69 69  
70 70  
71 -== 2.2 MQTT Brokers ==
70 +(% class="wikigeneratedid" %)
71 +== 2.2 HiveMQ Cloud ==
72 72  
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 +=== 2.2.1 HiveMQ Cloud ===
74 74  
75 75  
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 -
84 84  Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
85 85  
86 86  Click on the **Start Free** button.
... ... @@ -155,7 +155,7 @@
155 155  You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
156 156  
157 157  
158 -=== 2.2.3 emqx ===
150 +=== 2.2.2 emqx ===
159 159  
160 160  
161 161  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.
... ... @@ -164,7 +164,7 @@
164 164  [[image:emqx.png||height="420" width="500"]]
165 165  
166 166  
167 -=== 2.2.4 Ins1.thingseye.io ===
159 +=== 2.2.3 Ins1.thingseye.io ===
168 168  
169 169  [[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.
170 170  
... ... @@ -173,15 +173,12 @@
173 173  [[image:ins1.png||height="310" width="500"]]
174 174  
175 175  
176 -
177 177  = 3. Data Converters =
178 178  
179 179  
180 180  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.
181 181  
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**.
183 183  
184 -
185 185  == 3.1 Uplink ==
186 186  
187 187  
... ... @@ -188,10 +188,11 @@
188 188  In the left navigation, click **Integrations center**, and then click **Data converters**.
189 189  
190 190  
180 +
191 191  [[image:data-converters-list-empty.png]]
192 192  
193 193  
194 -On the **Data converters** page, click on the ‘**+**’ button, and then click on **Create new converter** from the dropdown menu.
184 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
195 195  
196 196  
197 197  
... ... @@ -198,85 +198,121 @@
198 198  [[image:create-new-converter-menu.png||height="259" width="500"]]
199 199  
200 200  
201 -The **Add data converter** window appears.
191 +The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
202 202  
203 -Name it ‘**MQTT Uplink Converter**’ and select the Type as **Uplink**.
193 +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.
204 204  
205 -Click on the **TBEL** button if it has not been selected by default.
195 +{{code language="JavaScript"}}
196 +/** Decoder **/
206 206  
207 -Replace the default TBEL decoder function with the following universal TBEL decoder function, which decodes MQTT payload from any Dragino NB-IoT device.
198 +// decode payload to string
199 +var payloadStr = decodeToString(payload);
200 +var data = JSON.parse(payloadStr);
208 208  
209 -
210 -{{code language="JavaScript"}}
202 +var deviceName = metadata.topic.split("/")[3];
211 211  // decode payload to JSON
212 -var pattern = "yyyy/MM/dd HH:mm:ss";
213 -var objdata = {};
214 -var obj1 = {};
215 -var data = decodeToJson(payload);
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 = {
204 +var deviceType = 'sensor';
205 +
206 +// Result object with device attributes/telemetry data
207 +var result = {
252 252   deviceName: deviceName,
253 - deviceType: modelname,
209 + deviceType: deviceType,
254 254   attributes: {
255 - model: modelname
256 - //customerName: "NB-CB",
257 - //groupName: "NB-CB",
258 - //integrationName: metadata['integrationName']
211 + integrationName: metadata['integrationName'],
259 259   },
260 - telemetry: listdata
213 + telemetry: {
214 + temperature: data.temperature,
215 + humidity: data.humidity,
216 + }
261 261  };
218 +
219 +/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
220 +
262 262  return result;
263 263  {{/code}}
264 264  
265 265  
266 -Once you modify the decoder function, click on the **Add** button.
225 +Click on the **Add** button.
267 267  
268 268  
269 -[[image:mqtt-uplink-converter.png||height="498" width="500"]]
270 270  
229 +[[image:add-uplink-data-converter.png||height="529" width="500"]]
271 271  
272 272  
273 273  You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
274 274  
234 +[[image:data-converter-list-showing-uplink-dc.png]]
275 275  
276 276  
237 +
238 +== 3.2 Downlink ==
239 +
240 +
241 +On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
242 +
243 +
244 +[[image:create-new-converter-menu.png||width="500"]]
245 +
246 +
247 +
248 +The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
249 +
250 +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.
251 +
252 +
253 +{{code language="JavaScript"}}
254 +// Encode downlink data from incoming Rule Engine message
255 +
256 +// msg - JSON message payload downlink message json
257 +// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
258 +// metadata - list of key-value pairs with additional data about the message
259 +// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
260 +
261 +/** Encoder **/
262 +
263 +var data = {};
264 +
265 +// Process data from incoming message and metadata
266 +
267 +data.tempFreq = msg.temperatureUploadFrequency;
268 +data.humFreq = msg.humidityUploadFrequency;
269 +
270 +data.devSerialNumber = metadata['ss_serialNumber'];
271 +
272 +// Result object with encoded downlink payload
273 +var result = {
274 +
275 + // downlink data content type: JSON, TEXT or BINARY (base64 format)
276 + contentType: "JSON",
277 +
278 + // downlink data
279 + data: JSON.stringify(data),
280 +
281 + // Optional metadata object presented in key/value format
282 + metadata: {
283 + topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
284 + }
285 +
286 +};
287 +
288 +return result;
289 +{{/code}}
290 +
291 +
292 +Click on the **Add** button.
293 +
294 +
295 +
296 +[[image:add-downlink-data-converter.png||height="529" width="500"]]
297 +
298 +
299 +You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
300 +
301 +
277 277  [[image:data-converters-list.png]]
278 278  
279 279  
305 +
280 280  = 4. Add Integration =
281 281  
282 282  
... ... @@ -297,15 +297,15 @@
297 297  **Basic settings:**
298 298  
299 299  * **Integration type**: MQTT
300 -* **Name**: MQTT integration
326 +* **Name**: MQTT integration NB/CB
301 301  * **Enable integration**: YES
302 -* **Allow create devices or assets**: YES
328 +* **Allows create devices or assets**: YES
303 303  
304 304  Click **Next** button.
305 305  
306 306  
307 307  
308 -[[image:add-integration-part-1.png||height="483" width="500"]]
334 +[[image:add-integration-basic-settings.png||height="511" width="500"]]
309 309  
310 310  
311 311  **Uplink data converter:**
... ... @@ -317,34 +317,33 @@
317 317  
318 318  
319 319  
320 -[[image:add-integration-part-2.png||height="484" width="500"]]
346 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
321 321  
322 322  
323 323  **Downlink data converter:**
324 324  
325 -Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
351 +* Click on the **Select existing** button.
352 +* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
326 326  
327 -* Click on the **Skip **button in the Downlink data converter section.
354 +Click **Next** button.
328 328  
329 -Click **Skip** button.
330 330  
331 331  
332 -[[image:integration-dl-skip.png||height="511" width="500"]]
358 +[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
333 333  
334 334  
335 -
336 336  **Connection:**
337 337  
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
363 +* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
364 +* **Port**: 8883
365 +* **Credentials**: Basic
366 +* **Enable SSL**: YES
341 341  * **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
342 342  * **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
343 -* **Enable SSL**: YES
344 -* **Topic**: # (the # symbol indicates that it filters all topics).
369 +* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
345 345  * **QoS:** 0-At most once
346 346  
347 -[[image:add-integration-4.png||height="484" width="500"]]
372 +[[image:add-integration-connection.png||height="511" width="500"]]
348 348  
349 349  
350 350  Click on the **Advanced settings** button.
... ... @@ -375,7 +375,7 @@
375 375  
376 376  
377 377  
378 -[[image:integrations-pending.png]]
403 +[[image:new-integration-pending.png]]
379 379  
380 380  
381 381  = 5. Verifying the receipt of data from virtual devices =
... ... @@ -386,86 +386,79 @@
386 386  
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 (payloads) to a topic - for example, # or device/ts01-nb. You can, of course, use any topic you prefer.
414 +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.
390 390  
416 +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.
391 391  
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 393  
394 -{{code language="none"}}
395 -{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
396 -{{/code}}
419 +**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.**
397 397  
398 398  
399 -== 5.2 Sending messages ==
422 +For example, if you send two MQTT messages with different device names in the topic:
400 400  
424 +1. v1/devices/**S31B-NB**/telemetry
425 +1. v1/devices/**LDS25-NB**/telemetry
401 401  
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.
427 +ThingsBoard will create two devices named **S31B-NB** and **LDS25-NB** in the **//Devices//** section.
403 403  
429 +
430 +The MQTT payload format is as follows, which is common for all ~-~-NB and ~-~-CB series devices:
431 +
404 404  {{code language="none"}}
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 +{"temperature":10.4, "humidity":85}
406 406  {{/code}}
407 407  
408 -If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
409 409  
437 +== 5.2 Sending messages ==
410 410  
411 -[[image:new-device-1.png]]
412 412  
440 +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.
413 413  
414 -The status of the integration also changes to '**Active**' after the first telemetry transmission.
442 +{{code language="none"}}
443 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":10.4, "humidity":85}'
444 +{{/code}}
415 415  
446 +If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
416 416  
417 -[[image:Screenshot 2025-04-21 122154.png]]
418 418  
449 +[[image:integration-active.png]]
419 419  
420 420  
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.**
452 +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**.
422 422  
423 423  
424 -== 5.3 Viewing messages ==
455 +[[image:device-provision-1.png]]
425 425  
426 426  
427 -Go back to the **Integrations** page.
458 +Click on the device S31B-NB on the devices list to see its details.
428 428  
429 -Click on the **MQTT integration** in the **Integrations** page to see its details.
460 +Then go to the **Latest telemetry** tab.
430 430  
431 -Click on the **Edit** button (//**pen icon**//).
462 +You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
432 432  
433 -Click on the **Disabled** button in the upper-right corner.
434 434  
435 -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.
465 +[[image:telemetry-1.png]]
436 436  
437 -Click on the **Apply** button.
438 438  
439 -Then click on the **Apply changes** (//**tick icon**//) button.
468 +Now, change the values of the fields and send the MQTT message again. For example, set temperature to 20 and humidity to 70. Observe how the values update in //Latest Telemetry//.
440 440  
441 441  
471 +[[image:telemetry-2.png]]
442 442  
443 -[[image:Screenshot 2025-04-21 122936.png||height="247" width="500"]]
444 444  
474 +Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
445 445  
446 -Now go to the **Events** tab.
447 447  
448 -Select the **Event type** as **Debug** from the dropdown list.
449 -
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:
451 -
452 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}'
478 +mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/LDS25-NB/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":11, "humidity":87}'
454 454  {{/code}}
455 455  
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.
481 +Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
457 457  
458 458  
459 -Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
484 +[[image:device-provision-2.png]]
460 460  
461 461  
462 -
463 -[[image:Screenshot 2025-04-21 122909.png]]
464 -
465 -
466 -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.
467 -
468 -
469 469  = 6. Creating a Dashboard =
470 470  
471 471  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.
... ... @@ -509,43 +509,46 @@
509 509  
510 510  Configure the **Time series chart** widget as follows:
511 511  
512 -* **Datasource** - select **350693903995577 **you provisioned.
530 +* **Datasource** - select S31B-NB device you provisioned.
513 513  * **Series**:
514 514  ** **temperature** - you can see this key by default.
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.
533 +** **humidity** - Click **Add series** button. Then add the **humidity** for the key and then type **%** as its unit.
517 517  * Click on the **Add** button.
518 518  
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}}
536 +[[image:timeseries-1.png||height="491" width="700"]]
522 522  
523 523  
539 +The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
524 524  
525 -[[image:Screenshot 2025-04-21 123647.png||height="466" width="700"]]
541 +Click the **Save** button to add the widget to the dashboard.
526 526  
527 527  
528 -The time-series chart will appear in edit mode. Resize it by clicking and dragging the lower-right corner.
544 +[[image:timeseries-3.png||height="347" width="700"]]
529 529  
530 -Click the **Save** button to add the widget to the dashboard.
531 531  
547 +Now send the following MQTT messages from the terminal to simulate the data.
532 532  
533 -[[image:Screenshot 2025-04-21 124145.png||height="443" width="700"]]
534 534  
550 +{{code language="none"}}
551 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":20, "humidity":70}'
535 535  
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.**
553 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":22, "humidity":71}'
537 537  
538 -**The chart will update with the values in real time, and you will see a live chart similar to this:**
555 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":18, "humidity":79}'
539 539  
557 +{{/code}}
540 540  
541 -[[image:Screenshot 2025-04-21 124054.png||height="441" width="700"]]
559 +The chart will update with the values in realtime, as shown in the below image.
542 542  
543 543  
544 -= 8. Configure Physical NB-IoT Sensor =
562 +[[image:timeseries-4.png||height="316" width="700"]]
545 545  
546 546  
547 -Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
565 += 7. Configure NB-IoT Sensor =
548 548  
567 +
568 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
569 +
549 549  First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
550 550  
551 551  
... ... @@ -552,8 +552,8 @@
552 552  **AT Commands**
553 553  
554 554  * **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
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: #**
576 +* **AT+SUBTOPIC=<MQTT topic>**
577 +* **AT+PUBTOPIC=<MQTT topic>**
557 557  * **AT+CLIENT=null**
558 558  * **AT+UNAME=<MQTT Username>**
559 559  * **AT+PWD=<MQTT Password>**
... ... @@ -560,9 +560,3 @@
560 560  * **AT+SERVADDR=<Broker address, Port>**
561 561  
562 562  Test your uplink by pressing the ACT button for 1 second.
563 -
564 -
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.
566 -
567 -
568 -[[image:image-4.png]]
Screenshot 2025-03-16 at 18.38.59.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -221.2 KB
Content
Screenshot 2025-03-16 at 18.39.12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -211.9 KB
Content
Screenshot 2025-03-18 at 09.23.10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -78.7 KB
Content
Screenshot 2025-03-26 at 18.15.08.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -92.2 KB
Content
Screenshot 2025-03-26 at 19.47.52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -168.4 KB
Content
Screenshot 2025-03-26 at 19.49.31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -133.0 KB
Content
Screenshot 2025-03-31 at 06.51.15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -179.5 KB
Content
Screenshot 2025-04-21 122154.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -21.2 KB
Content
Screenshot 2025-04-21 122909.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -59.9 KB
Content
Screenshot 2025-04-21 122936.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
Screenshot 2025-04-21 123647.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
Screenshot 2025-04-21 124054.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -60.4 KB
Content
Screenshot 2025-04-21 124145.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -50.9 KB
Content
add-integartion-connection.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -110.3 KB
Content
add-integartion-connetcion.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -146.0 KB
Content
add-integration-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -63.1 KB
Content
add-integration-basic-settings.png
Size
... ... @@ -1,1 +1,1 @@
1 -123.8 KB
1 +122.5 KB
Content
add-integration-connection.png
Size
... ... @@ -1,1 +1,1 @@
1 -158.1 KB
1 +124.4 KB
Content
add-integration-part-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -48.6 KB
Content
add-integration-part-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -47.7 KB
Content
add-integration-ul-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -121.2 KB
Content
data-converters-list.png
Size
... ... @@ -1,1 +1,1 @@
1 -19.0 KB
1 +212.2 KB
Content
debug-enabled.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -196.3 KB
Content
device-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -34.5 KB
Content
image-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -96.0 KB
Content
integration-active.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.1 KB
1 +64.2 KB
Content
integration-added.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -196.2 KB
Content
integration-dl-skip.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -105.5 KB
Content
integrations-pending.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -19.8 KB
Content
mqtt-uplink-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -75.3 KB
Content
mqtt-uplink.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -175.1 KB
Content
new-device-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -34.7 KB
Content
new-device.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
ul-data-converter-added.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -189.4 KB
Content
ul-data-converter-device-a.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -168.3 KB
Content