Changes for page ThingsBoard
Last modified by Dilisi S on 2025/04/23 19:23
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (1 modified, 8 added, 49 removed)
- 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
- add-downlink-data-converter.png
- add-integration-connection-advanced-settings.png
- add-integration-connection.png
- add-uplink-data-converter.png
- check-connection.png
- connection-success.png
- create-new-converter-menu.png
- dashboard-1.png
- dashboard-2.png
- dashboard-3.png
- dashboard-4.png
- dashboard-5.png
- data-converter-list-showing-uplink-dc.png
- data-converters-list-empty.png
- data-converters-list.png
- device-provision-1.png
- device-provision-2.png
- emqx.png
- hivemq-10.png
- hivemq-2.png
- hivemq-3.png
- hivemq-4.jpg
- hivemq-5.png
- hivemq-6.png
- hivemq-7.png
- hivemq-8.png
- hivemq-9.png
- hivwmq-1.png
- image-4.png
- ins1.png
- integration-active.png
- integration-dl-skip.png
- integrations-list-empty.png
- mqtt-uplink.png
- new-device.png
- new-integration-pending.png
- telemetry-1.png
- telemetry-2.png
- thingsboard-1.png
- thingsboard-2.png
- thingsboard-3.png
- thingsboard-4.png
- thingsboard-5.png
- thingsboard-6.png
- timeseries-1.png
- timeseries-3.png
- timeseries-4.png
- ThingsBoard-Data-Converters.png
- ThingsBoard-Device.png
- ThingsBoard-add-data-converter-downlink.png
- ThingsBoard-add-data-converter-uplink.png
- ThingsBoard-add-data-converter.png
- ThingsBoard-add-integration.png
- ThingsBoard-add-new-device.png
- ThingsBoard-new-data-converter.png
Details
- Page properties
-
- Content
-
... ... @@ -6,196 +6,47 @@ 6 6 Draft Document 7 7 {{/warning}} 8 8 9 += Introduction = 9 9 11 +This document guides you on integrating Dragino -NB and -CB series devices with ThingsBoard. For this guide, we use ThingsBoard Cloud, which is one of the ThingsBoard versions that allows you to try it for free. 10 10 11 11 12 -= 1. Introduction=14 += Add New Device = 13 13 16 +In the left navigation, click **Entities** and then click **Devices**. 14 14 15 -This document guides you on integrating Dragino **-NB** and **-CB** series devices data with ThingsBoard. For this guide, we use ThingsBoard Cloud, which is one of the ThingsBoard versions that allows you to try it for free. 16 16 17 - The **NB series** devices end withthe suffix **-NB**, and the **CBseries** devices end with the suffix **-CB**. For example, **S31B-NB** is an **NBdevice**, and **S31-CB** is a **CB device**.19 +[[image:ThingsBoard-Device.png]] 18 18 19 19 20 - =2. Prerequisites=22 +On the ‘**Devices**’ page, click on the ‘**+**’ button, and then click on the ‘**Add new device**’ from the dropdown menu. 21 21 22 -To complete this tutorial, you need to have the following: 23 23 24 -* ThingsBoard 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. 25 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]] 29 29 30 -== 2.1 ThingsBoard Cloud == 31 31 32 32 33 - Goto[[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]]29 += Data Converters = 34 34 35 -Click on the **Try it now**. 36 36 32 +== Uplink == 37 37 38 - [[image:thingsboard-1.png]]34 +In the left navigation, click ‘Integrations center’, and then click ‘Data converters’. 39 39 40 40 41 - Select either the **North America**or **Europe** region. Here, we usetheEurope region.37 +[[image:ThingsBoard-Data-Converters.png]] 42 42 43 -[[image:thingsboard-2.png]] 44 44 40 +On the ‘Data converters’ page, click on the ‘+’ button, and then click on the ‘Create new converter’ from the dropdown menu. 45 45 46 -You can sign up with your **Google**, **GitHub**, **Facebook**, or **Apple** account. If not you can create an account with providing your **name**, **email address** and a **password**. 47 47 48 - Clickon**Signup** button.43 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]] 49 49 50 -[[image:thingsboard-3.png||height="651" width="500"]] 51 51 46 +The ‘Add data converter’ window will appear. Name it ‘**UDP Uplink Converter NB/CB**’ and select the Type as ‘Uplink’. 52 52 53 - You willbenavigatedto the following page.48 +Click on the ‘JavaScript’ button. Now copy and paste the following script to the ‘Decoder function’ section: 54 54 55 -[[image:thingsboard-5.png||height="109" width="500"]] 56 - 57 - 58 -simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button. 59 - 60 - 61 -[[image:thingsboard-4.png||height="249" width="500"]] 62 - 63 - 64 -Now losing to the account using your credentials: 65 - 66 - 67 -[[image:thingsboard-6.png||height="244" width="500"]] 68 - 69 - 70 -== 2.2 HiveMQ Cloud == 71 - 72 -=== 2.2.1 HiveMQ Cloud === 73 - 74 - 75 -Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]] 76 - 77 -Click on the **Start Free** button. 78 - 79 -[[image:hivwmq-1.png]] 80 - 81 - 82 -Click on the **Sign Up FREE Now** button in the **HIVEMQ CLOUD** section. 83 - 84 -[[image:hivemq-2.png]] 85 - 86 - 87 -Click on the **Sign Up** button. 88 - 89 -You can sign up with HiveMQ using your **GitHub**, **Google**, or **LinkedIn** account. 90 - 91 -If not, provide your **email address** and a **password** to create an account by clicking on the **Sign Up** button. 92 - 93 - 94 -[[image:hivemq-3.png]] 95 - 96 - 97 -You will receive an email to verify your email address. Click on the **Confirm my account** button. 98 - 99 - 100 -[[image:hivemq-4.jpg||height="889" width="400"]] 101 - 102 - 103 -You will be redirected to a page asking you to complete your profile. Once done, click the **Continue** button. 104 - 105 - 106 -[[image:hivemq-5.png||height="655" width="700"]] 107 - 108 - 109 -Select the CloudMQ Cloud plan you need. For testing purposes, select the **Serverless FREE** plan by clicking on the **Create Serverless Cluster** button. 110 - 111 - 112 -[[image:hivemq-6.png]] 113 - 114 - 115 -You will be navigated to the **Your Clusters** page. Click on the **Manage Cluster** button. 116 - 117 -[[image:hivemq-7.png]] 118 - 119 - 120 -In your cluster page, you can find some useful parameters you need to create a MQTT connection. 121 - 122 -**URL**: This is the host name. Click on the copy button to copy it. 123 - 124 -**Port**: 8883 125 - 126 - 127 -Click on the **Getting Started** tab to setup the username and the password as the connection credentials. 128 - 129 - 130 -[[image:hivemq-8.png]] 131 - 132 - 133 -In the '**Create Connection Credentials**' section, provide a **username** and **password**, then click the **Add** button. 134 - 135 - 136 -[[image:hivemq-9.png]] 137 - 138 - 139 - 140 -If everything is successful, you will see the following message. 141 - 142 - 143 -[[image:hivemq-10.png||height="206" width="500"]] 144 - 145 - 146 -You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section. 147 - 148 - 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 - 167 -= 3. Data Converters = 168 - 169 - 170 -In **ThingsBoard**, **Data Converters** are components used to transform incoming or outgoing data between different formats, typically to convert raw telemetry data from devices into a structured format that ThingsBoard can understand, or vice versa. 171 - 172 - 173 -== 3.1 Uplink == 174 - 175 - 176 -In the left navigation, click **Integrations center**, and then click **Data converters**. 177 - 178 - 179 -[[image:data-converters-list-empty.png]] 180 - 181 - 182 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu. 183 - 184 - 185 - 186 -[[image:create-new-converter-menu.png||height="259" width="500"]] 187 - 188 - 189 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**. 190 - 191 -Click on the **JavaScript** button. 192 - 193 -Delete the default decoder function in the code editor. Now copy and paste the following decoder function written in **JavaScript** in to the **code editor**. This decoder function is compatible for both NB and CB series devices. 194 - 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 199 {{code language="JavaScript"}} 200 200 //Version: 0.1 201 201 // decode payload to string ... ... @@ -316,314 +316,138 @@ 316 316 } 317 317 318 318 return result; 170 + 319 319 {{/code}} 320 320 173 +Click on the ‘Add’ button. 321 321 322 -Click on the **Add** button. 323 323 176 +[[image:ThingsBoard-add-data-converter-uplink.png||width="500"]] 324 324 325 -[[image:mqtt-uplink.png||width="500"]] 326 326 179 +The uplink data converter is added to ThingsBoard and appears on the ‘Data Converters’ page 327 327 328 328 329 - Youshould see that the newly added **MQTT Uplinkconverter **NB/CB is listed on the **Data Converters** page.182 +== Downlink == 330 330 184 +On the ‘Data converters’ page, click on the ‘+’ button, and then click on the ‘Create new converter’ from the dropdown menu. 331 331 332 -[[image:data-converter-list-showing-uplink-dc.png]] 333 333 187 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]] 334 334 335 -= 4. Add Integration = 336 336 190 +The ‘**Add data converter**’ window will appear. Name it ‘**UDP Downlink Converter NB/CB**’ and select the Type as ‘**Downlink**’. 337 337 338 - In theleft navigation,click**Integrationscenter**,and thenclick**Integrations**.192 +Click on the ‘**JavaScript**’ button. Now copy and paste the following script to the ‘**Encoder function**’ section: 339 339 340 340 341 -[[image:integrations-list-empty.png]] 195 +{{code language="JavaScript"}} 196 +function hexToBase64(hexString) { 197 + // 将16进制字符串两个字符转换为一个字节 198 + var bytes = hexString.match(/.{2}/g); 199 + // 对每个字节进行解析,并转换为对应的字符 200 + var binaryString = bytes.map(function(byte) { 201 + return String.fromCharCode(parseInt(byte, 16)); 202 + }).join(''); 203 + 204 + // 使用btoa进行base64编码 205 + return btoa(binaryString); 206 +} 342 342 208 +// Result object with encoded downlink payload 209 +var result = { 210 + // downlink data content type: JSON, TEXT or BINARY (base64 format) 211 + contentType: "BINARY", 343 343 344 -On the **Integrations** page, click on the '**+**' button. 213 + // downlink data 214 + data:hexToBase64(metadata.shared_value) 345 345 216 + // Optional metadata object presented in key/value format 217 + //metadata: {} 346 346 347 - The **Add integration** window appears.219 +}; 348 348 349 -In the **Add integration** window, configure the following settings: 221 +return result; 222 +{{/code}} 350 350 351 351 352 -**Basic settings:** 353 - 354 -* **Integration type**: MQTT 355 -* **Name**: MQTT integration NB/CB 356 -* **Enable integration**: YES 357 -* **Allows create devices or assets**: YES 358 - 359 -Click **Next** button. 360 - 361 - 362 -[[image:add-integration-basic-settings.png||height="511" width="500"]] 363 - 364 - 365 -**Uplink data converter:** 366 - 367 -* Click on the **Select existing** button. 368 -* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list. 369 - 370 -Click **Next** button. 371 - 372 - 373 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]] 374 - 375 - 376 -**Downlink data converter:** 377 - 378 -Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step. 379 - 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 - 425 425 Click on the **Add** button. 426 426 427 -You should see that the newly added integration is listed on the **Integrations** page. 428 428 429 - Since we haven'treceivedfrom a deviceyet, theintegration**Status**is shownas **Pending.**228 +[[image:ThingsBoard-add-data-converter-downlink.png||height="532" width="500"]] 430 430 431 431 432 - [[image:new-integration-pending.png]]231 += Add Integration = 433 433 233 +In the left navigation, click ‘Integrations center’, and then click ‘Integrations’. 434 434 435 - =5.Verifyingthereceiptofdatafromvirtual devices =235 +On the ‘Integrations’ page, click on the “+” button. 436 436 437 437 438 - == 5.1 How doeswork? ==238 +[[image:ThingsBoard-add-integration.png]] 439 439 440 440 441 - We use theMosquittoMQTT clientto simulateMQTT messages, acting as a virtual device. First,install the Mosquitto clienton 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. ThingsBoardsubscribes to these messages using the same topic.241 +The ‘Add integration’ window appears. 442 442 443 - The Mosquitto clientpublishesmessages (payloads)onhepic **v1/devices/me/telemetry**. Of course,youcanseanytopicfortesting.243 +In the Add Integration window, configure the following settings: 444 444 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 ismandatory and is usedto provision a new device with the name assigned to it in ThingsBoard.245 +**Basic settings:** 446 446 447 -{{code language="none"}} 448 -{"IMEI": "S31B-NB", "temperature": 27, ......} 449 -{{/code}} 247 +* **Integration type**: UDP 248 +* **Name**: UDP Integration NB/CB 450 450 451 - Once ThingsBoard receivesthis message, itautomatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.250 +Click **Next** button. 452 452 453 453 454 - == 5.2 Sending messages ==253 +[[image:add-integration-basic-settings.png||height="511" width="500"]] 455 455 456 456 457 - On the terminal, issue the following MQTT command which simulates the device S31B-NB. The messagepayload containsthe fields temperatureand humidity,which hold thevalues S31B-NB and 27,respectively. This payload is also (technically) known as telemetry.256 +**Uplink data converter:** 458 458 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}} 258 +* Click on the ‘**Select existing**’ button. 259 +* Uplink data converter: Select ‘**UDP Uplink Converter NB/CB**’ from the dropdown list. 462 462 463 - If theintegrationwas performed withouterrors, the status ofthe integrationchanges to 'Active' after the first telemetry transmission.261 +Click **Next** button. 464 464 465 465 466 -[[image:integration-a ctive.png]]264 +[[image:add-integration-uplink-data-converter.png||height="511" width="500"]] 467 467 468 468 469 - Also, a new device named**S31B-NB**will appear under **//Entities -> Devices -> All//**. This meansthe first MQTT messagetriggers ThingsBoardtoprovisiona devicenamed**S31B-NB**.267 +**Downlink data converter:** 470 470 269 +* Click on the ‘**Select existing**’ button. 270 +* Downlink data converter: Select ‘**UDP Downlink Converter NB/CB**’ from the dropdown list. 471 471 472 -[[image:new-device.png]] 473 473 273 +Click **Next** button. 474 474 475 -== 5.3 Viewing messages == 476 476 276 +[[image:add-integration-downlink-data-converter.png||height="512" width="500"]] 477 477 478 -Go back to the **Integrations** page. 479 479 480 - Click on the**MQTT integrationNB/CB** inthe**Integrations**page to see its details.279 +**Connection:** 481 481 482 - Click on the**Edit**button (//**pen icon**//).281 +**Port**: 11582 483 483 484 - Clickonthe**Disabled**buttonintheupper-rightcorner.283 +**Size of the buffer for inbound socket (in KB)**: 64 485 485 486 - Turn on the**All messages (15 min)** option. This willenabledisplaying all messages in the**Events**tab. This setting will expire in15 minutes, and you will need to repeat the same steps if you want to view the messages in the Events tab later.285 +**Cache Size**: 10000000 487 487 488 -C lickon theApply**button.287 +**Cache time to live in minutes**: 1440 489 489 490 -Then click on the **Apply changes** (//**tick icon**//) button. 491 491 290 +Copy the two keys, **Integration key** and **Integration secret** into a text editor, as you will need them in the section ‘xxxxx’. 492 492 493 -[[image:Screenshot 2025-03-18 at 09.23.10.png]] 494 - 495 - 496 -Now go to the **Events** tab. 497 - 498 -Select the Event type as **Debug** from the dropdown list. 499 - 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. 501 - 502 - 503 -[[image:Screenshot 2025-03-16 at 18.38.59.png]] 504 - 505 - 506 -Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window. 507 - 508 - 509 -[[image:Screenshot 2025-03-16 at 18.39.12.png]] 510 - 511 - 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. 513 - 514 - 515 -= 6. Creating a Dashboard = 516 - 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. 518 - 519 - 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. 521 - 522 - 523 -First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg: 524 - 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 - 536 536 Click on the **Add** button. 537 537 538 538 539 -[[image:da shboard-2.png||height="526" width="500"]]295 +[[image:add-integration-connection.png||height="511" width="500"]] 540 540 541 541 542 -Click on the **Add widget / Add new widget** button. 543 543 299 += Verifying the receipt of data from the device = 544 544 545 - [[image:dashboard-3.png]]301 +Connect **S31B-NB** to transfer information. If the integration was performed without errors, after the transmission of the first telemetry, a new device with the name “xxxxx” 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. 546 546 547 547 548 -In the **Select widgets bundle** window, click **Charts**. 549 - 550 - 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 - 583 -{{code language="none"}} 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 - 590 -{{/code}} 591 - 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 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 -
- 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
- add-downlink-data-converter.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -175.2 KB - Content
- add-integration-connection-advanced-settings.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -155.2 KB - Content
- add-integration-connection.png
-
- Size
-
... ... @@ -1,1 +1,1 @@ 1 -1 58.1KB1 +124.4 KB - Content
- add-uplink-data-converter.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -174.1 KB - Content
- check-connection.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -14.7 KB - Content
- connection-success.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -90.0 KB - Content
- create-new-converter-menu.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.5 KB - Content
- dashboard-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -271.1 KB - Content
- dashboard-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -112.2 KB - Content
- dashboard-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -141.3 KB - Content
- dashboard-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -803.7 KB - Content
- dashboard-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -476.1 KB - Content
- data-converter-list-showing-uplink-dc.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -194.9 KB - Content
- data-converters-list-empty.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -260.7 KB - Content
- data-converters-list.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -212.2 KB - Content
- device-provision-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -265.7 KB - Content
- device-provision-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -213.9 KB - Content
- emqx.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -39.1 KB - Content
- hivemq-10.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -82.7 KB - Content
- hivemq-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -300.7 KB - Content
- hivemq-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -535.2 KB - Content
- hivemq-4.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -309.8 KB - Content
- hivemq-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -115.0 KB - Content
- hivemq-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -321.0 KB - Content
- hivemq-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -203.5 KB - Content
- hivemq-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -268.7 KB - Content
- hivemq-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -303.7 KB - Content
- hivwmq-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -380.3 KB - Content
- image-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -96.0 KB - Content
- ins1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -28.8 KB - Content
- integration-active.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.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-list-empty.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.5 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.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.3 KB - Content
- new-integration-pending.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -199.7 KB - Content
- telemetry-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -191.9 KB - Content
- telemetry-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -185.1 KB - Content
- thingsboard-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -1.9 MB - Content
- thingsboard-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -901.1 KB - Content
- thingsboard-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -146.3 KB - Content
- thingsboard-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -122.1 KB - Content
- thingsboard-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -106.7 KB - Content
- thingsboard-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -119.3 KB - Content
- timeseries-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -179.1 KB - Content
- timeseries-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -174.2 KB - Content
- timeseries-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -159.0 KB - Content
- ThingsBoard-Data-Converters.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +100.3 KB - Content
- ThingsBoard-Device.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +225.5 KB - Content
- ThingsBoard-add-data-converter-downlink.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +128.6 KB - Content
- ThingsBoard-add-data-converter-uplink.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +128.6 KB - Content
- ThingsBoard-add-data-converter.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +128.6 KB - Content
- ThingsBoard-add-integration.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +128.6 KB - Content
- ThingsBoard-add-new-device.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +89.7 KB - Content
- ThingsBoard-new-data-converter.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +100.3 KB - Content