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 (0 modified, 0 added, 4 removed)
Details
- Page properties
-
- Content
-
... ... @@ -22,10 +22,7 @@ 22 22 To complete this tutorial, you need to have the following: 23 23 24 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 +* HiveMQ Cloud account 29 29 30 30 == 2.1 ThingsBoard Cloud == 31 31 ... ... @@ -67,12 +67,9 @@ 67 67 [[image:thingsboard-6.png||height="244" width="500"]] 68 68 69 69 70 -(% class="wikigeneratedid" %) 71 71 == 2.2 HiveMQ Cloud == 72 72 73 -=== 2.2.1 HiveMQ Cloud === 74 74 75 - 76 76 Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]] 77 77 78 78 Click on the **Start Free** button. ... ... @@ -147,24 +147,6 @@ 147 147 You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section. 148 148 149 149 150 -=== 2.2.2 emqx === 151 - 152 - 153 -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. 154 - 155 - 156 -[[image:emqx.png||height="420" width="500"]] 157 - 158 - 159 -=== 2.2.3 Ins1.thingseye.io === 160 - 161 -[[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. 162 - 163 -If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files. 164 - 165 -[[image:ins1.png||height="310" width="500"]] 166 - 167 - 168 168 = 3. Data Converters = 169 169 170 170 ... ... @@ -374,8 +374,8 @@ 374 374 375 375 Click on the **Advanced settings** button. 376 376 377 -* **Clean session:** YES378 -* **Retained**: YES353 +* **Clean session:** NO 354 +* **Retained**: NO 379 379 380 380 [[image:add-integration-connection-advanced-settings.png||height="510" width="500"]] 381 381 ... ... @@ -440,7 +440,7 @@ 440 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. 441 441 442 442 {{code language="none"}} 443 -mosquitto_pub -d -q 1 -h 011731f7928 xxxxx.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}'419 +mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":10.4, "humidity":85}' 444 444 {{/code}} 445 445 446 446 If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission. ... ... @@ -527,57 +527,37 @@ 527 527 528 528 Configure the **Time series chart** widget as follows: 529 529 530 -* **Datasource**- select S31B-NB device you provisioned.531 -* **Series**:506 +* Datasource - select S31B-NB device you provisioned. 507 +* Series: 532 532 ** **temperature** - you can see this key by default. 533 -** **humidity** - Click **Add series** button .Thenadd the **humidity**forthe keyand then type **%** as its unit.509 +** **humidity** - Click **Add series** button to add the **humidity** and then type **%** as its unit. 534 534 * Click on the **Add** button. 535 535 536 536 [[image:timeseries-1.png||height="491" width="700"]] 537 537 538 538 539 - Thetime-series chart will appear in edit mode.Resize it by clicking and draggingthelower-right corner.515 += 7. Configure NB-IoT Sensor = 540 540 541 -Click the **Save** button to add the widget to the dashboard. 542 542 518 +Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**. 543 543 544 - [[image:timeseries-3.png||height="347"width="700"]]520 +First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use. 545 545 546 546 547 - Now send the following MQTT messages fromthe terminal to simulate thedata.523 +**AT Commands** 548 548 525 +* **AT+PRO=3,3 **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3. 549 549 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}' 527 +* **AT+SUBTOPIC=<device name>** Eg. 552 552 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}'529 +* **AT+PUBTOPIC=<device name>** 554 554 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}'531 +* **AT+CLIENT=<device name> or User Defined** 556 556 557 - {{/code}}533 +* **AT+UNAME=<device name> or User Defined** 558 558 559 - Thechart will updatewith thevaluesin realtime,as shownin thebelowimage.535 +* **AT+PWD=<device name> or User Defined** 560 560 537 +Test Uplink by click the button for 1 second 561 561 562 -[[image:timeseries-4.png||height="316" width="700"]] 563 563 564 - 565 -= 7. Configure NB-IoT Sensor = 566 - 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 - 570 -First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use. 571 - 572 - 573 -**AT Commands** 574 - 575 -* **AT+PRO=3,3 **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3. 576 -* **AT+SUBTOPIC=<MQTT topic>** 577 -* **AT+PUBTOPIC=<MQTT topic>** 578 -* **AT+CLIENT=null** 579 -* **AT+UNAME=<MQTT Username>** 580 -* **AT+PWD=<MQTT Password>** 581 -* **AT+SERVADDR=<Broker address, Port>** 582 - 583 -Test your uplink by pressing the ACT button for 1 second.
- emqx.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -39.1 KB - Content
- ins1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -28.8 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