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 ... ... @@ -126,7 +126,6 @@ 126 126 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 127 127 128 128 129 - 130 130 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 131 131 132 132 ... ... @@ -167,7 +167,6 @@ 167 167 168 168 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 169 169 170 - 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]] 239 +[[image:image-20230802112413-14.png||height="1095" width="1302"]] 243 243 244 244 245 245 === 3.4.2 Create Device === ... ... @@ -287,13 +287,14 @@ 287 287 288 288 (% style="color:blue" %)**MQTT Client-ID** 289 289 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 specification blank. Your client then creates a randomly generated ID. 287 +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 288 +specification blank. Your client then creates a randomly generated ID. 291 291 292 -(% style="color:blue" %)**AT+CLIENT=“Any value”** 290 +* (% style="color:blue" %)**AT+CLIENT=“Any value”** 293 293 294 -(% style="color:blue" %)**AT+UNAME=Token** 292 +* (% style="color:blue" %)**AT+UNAME=Token** 295 295 296 -(% style="color:blue" %)**AT+PWD=Token** 294 +* (% style="color:blue" %)**AT+PWD=Token** 297 297 298 298 [[image:image-20230802112413-21.png]] 299 299 ... ... @@ -381,7 +381,6 @@ 381 381 * (% style="color:blue" %)**AT+SUBTOPIC=any value** 382 382 383 383 384 - 385 385 == 3.6 ThingsBoard.Cloud (via MQTT) == 386 386 387 387 === 3.6.1 Configure ThingsBoard === ... ... @@ -401,7 +401,7 @@ 401 401 402 402 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. 403 403 404 -To create an uplink converter go to the **Integrations center** -> **Data converters** page and click **“plus”** 401 +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. 405 405 406 406 [[image:image-20230802112413-33.png||height="732" width="1302"]] 407 407 ... ... @@ -418,7 +418,7 @@ 418 418 ==== 3.6.1.3 MQTT Integration Setup ==== 419 419 420 420 421 -Go to the **Integrations center** -> **Integrations page** and click **“plus”** icon to add a new integration. Name it **“MQTT Integration”**, select type MQTT; 418 +Go to the **Integrations center** -> **Integrations page** and click **“plus”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**; 422 422 423 423 [[image:image-20230802112413-35.png||height="738" width="1312"]] 424 424 ... ... @@ -515,7 +515,6 @@ 515 515 516 516 517 517 518 - 519 519 === 3.7.2 Simulate with MQTT.fx === 520 520 521 521 ... ... @@ -564,4 +564,3 @@ 564 564 [[image:image-20230802112413-52.png]] 565 565 566 566 567 -