Last modified by Mengting Qiu on 2025/03/08 11:33
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -21,7 +21,6 @@ 21 21 |China Mobile| | | 22 22 23 23 24 - 25 25 == 2.1 1NCE SIM Card. == 26 26 27 27 ... ... @@ -134,6 +134,7 @@ 134 134 135 135 [[image:image-20230802112413-10.png]] 136 136 136 + 137 137 (% style="color:blue" %)**In MQTT.fx, we can publish below info:** 138 138 139 139 * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish ... ... @@ -168,6 +168,7 @@ 168 168 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 169 169 170 170 171 + 171 171 ==== 3.3.3.2 Uplink Examples ==== 172 172 173 173 ... ... @@ -239,7 +239,7 @@ 239 239 240 240 By chosing to add the device under a (% style="color:blue" %)**"New Product"**(%%) you are required to give a name for this product. You can name it something like (% style="color:blue" %)**"My First MQTT Product"**. 241 241 242 -[[image:image-20230802112413-14.png]] 243 +[[image:image-20230802112413-14.png||height="1095" width="1302"]] 243 243 244 244 245 245 === 3.4.2 Create Device === ... ... @@ -285,6 +285,7 @@ 285 285 286 286 [[image:image-20230802112413-20.png]] 287 287 289 + 288 288 (% style="color:blue" %)**MQTT Client-ID** 289 289 290 290 The Datacake Broker manages the client IDs internally. You do not need to worry about a client ID. If your client optionally supports the specification of a client ID, please leave this ... ... @@ -382,7 +382,6 @@ 382 382 * (% style="color:blue" %)**AT+SUBTOPIC=any value** 383 383 384 384 385 - 386 386 == 3.6 ThingsBoard.Cloud (via MQTT) == 387 387 388 388 === 3.6.1 Configure ThingsBoard === ... ... @@ -402,7 +402,7 @@ 402 402 403 403 The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported. 404 404 405 -To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** 406 +To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now. 406 406 407 407 [[image:image-20230802112413-33.png||height="732" width="1302"]] 408 408 ... ... @@ -419,7 +419,7 @@ 419 419 ==== 3.6.1.3 MQTT Integration Setup ==== 420 420 421 421 422 -Go to the **Integrations center** -> **Integrations 423 +Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**; 423 423 424 424 [[image:image-20230802112413-35.png||height="738" width="1312"]] 425 425 ... ... @@ -433,7 +433,7 @@ 433 433 434 434 (% style="color:blue" %)**Add a topic filter:** 435 435 436 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。 437 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature **固定的? 对的。** 437 437 438 438 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default; 439 439 ... ... @@ -455,11 +455,11 @@ 455 455 456 456 * (% style="color:#037691" %)**AT+PRO=3,3 **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. 457 457 458 -* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的 459 +* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的** 459 459 460 -* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的 461 +* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的** 461 461 462 -Users do not need to fill in the client, username, and password. But the configuration information of the device requires setting the client, username, and password, which can be entered freely. (软件自动填充为 Device Name 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性） 463 +Users do not need to fill in the client, username, and password. But the configuration information of the device requires setting the client, username, and password, which can be entered freely.** (软件自动填充为 Device Name 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性）** 463 463 464 464 (% style="color:blue" %)**CLIENT :“Any value”** 465 465 ... ... @@ -494,7 +494,7 @@ 494 494 [[image:image-20230802112413-46.png]] 495 495 496 496 497 -On the Connection Profile window, set the following information: (这边加一个截图) 498 +On the Connection Profile window, set the following information: **(这边加一个截图)** 498 498 499 499 * (% style="color:blue" %)**Profile Name: “Any name”** 500 500 ... ... @@ -504,7 +504,7 @@ 504 504 505 505 * (% style="color:blue" %)**Client ID: “Any value”** 506 506 507 -On the section User credentials, set the following information: (这边加一个截图) 508 +On the section User credentials, set the following information: **(这边加一个截图)** 508 508 509 509 * (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only 510 510 ... ... @@ -516,7 +516,6 @@ 516 516 517 517 518 518 519 - 520 520 === 3.7.2 Simulate with MQTT.fx === 521 521 522 522 ... ... @@ -526,6 +526,7 @@ 526 526 527 527 Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**. 528 528 529 + 529 529 [[image:image-20230802112413-49.png]] 530 530 531 531