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,6 +21,7 @@ 21 21 |China Mobile| | | 22 22 23 23 24 + 24 24 == 2.1 1NCE SIM Card. == 25 25 26 26 ... ... @@ -133,7 +133,6 @@ 133 133 134 134 [[image:image-20230802112413-10.png]] 135 135 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,7 +168,6 @@ 168 168 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 169 169 170 170 171 - 172 172 ==== 3.3.3.2 Uplink Examples ==== 173 173 174 174 ... ... @@ -233,7 +233,7 @@ 233 233 234 234 == 3.4 Datacake == 235 235 236 -== =3.4.1 Define Product ===235 +== 3.4.1 Define Product == 237 237 238 238 239 239 Firstly, we need to set the MQTT mode to datacake, and we need to run(% style="color:blue" %)** AT+PRO=3,2**(%%). This command is set to datacake. After running the command, the device automatically sets the server address, port. ... ... @@ -240,7 +240,7 @@ 240 240 241 241 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"**. 242 242 243 -[[image:image-20230802112413-14.png ||height="1095" width="1302"]]242 +[[image:image-20230802112413-14.png]] 244 244 245 245 246 246 === 3.4.2 Create Device === ... ... @@ -248,7 +248,7 @@ 248 248 249 249 In the second step you have to define the device which should be added to the product. 250 250 251 -[[image:image-20230802112413-15.png ||height="859" width="1290"]]250 +[[image:image-20230802112413-15.png]] 252 252 253 253 Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the (% style="color:blue" %)**"Next"**(%%) button. 254 254 ... ... @@ -260,15 +260,15 @@ 260 260 261 261 You will then see a device view with an empty dashboard. Now, the first thing we want to do is navigate to the Device configuration. To do this, use the tab bar and click on (% style="color:blue" %)**"Configuration"**. 262 262 263 -[[image:image-20230802112413-16.png ||height="495" width="1310"]]262 +[[image:image-20230802112413-16.png]] 264 264 265 -[[image:image-20230802112413-17.png ||height="741" width="1303"]]264 +[[image:image-20230802112413-17.png]] 266 266 267 267 To create a first database field, please click on the (% style="color:blue" %)**"Add Field"**(%%) button as marked in the screenshot above. 268 268 269 269 This will open another modal asking for some required input for your first field. 270 270 271 -[[image:image-20230802112413-18.png ||height="878" width="1305"]]270 +[[image:image-20230802112413-18.png]] 272 272 273 273 [[image:image-20230802112413-19.png]] 274 274 ... ... @@ -286,17 +286,15 @@ 286 286 287 287 [[image:image-20230802112413-20.png]] 288 288 289 - 290 290 (% style="color:blue" %)**MQTT Client-ID** 291 291 292 -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 293 -specification blank. Your client then creates a randomly generated ID. 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. 294 294 295 - *(% style="color:blue" %)**AT+CLIENT=“Any value”**292 +(% style="color:blue" %)**AT+CLIENT=“Any value”** 296 296 297 - *(% style="color:blue" %)**AT+UNAME=Token**294 +(% style="color:blue" %)**AT+UNAME=Token** 298 298 299 - *(% style="color:blue" %)**AT+PWD=Token**296 +(% style="color:blue" %)**AT+PWD=Token** 300 300 301 301 [[image:image-20230802112413-21.png]] 302 302 ... ... @@ -306,8 +306,10 @@ 306 306 307 307 (% style="color:blue" %)**Subscribe** 308 308 309 -Data is published according to the following structure: (% style="color:blue" %)**dtck~/~//**(%%)** **306 +Data is published according to the following structure: 310 310 308 +dtck~/~// 309 + 311 311 Subscribe to topics using this structure to receive messages via MQTT when readings (via API or MQTT) arrive in the Datacake Cloud. Messages are published whenever there is a change to a corresponding database field. 312 312 313 313 ... ... @@ -334,8 +334,10 @@ 334 334 335 335 To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure. 336 336 337 -Due to the nature of MQTT, the topic prefix differs as follows: (% style="color:blue" %)**dtck-pub~/~//**336 +Due to the nature of MQTT, the topic prefix differs as follows: 338 338 338 +dtck-pub~/~// 339 + 339 339 (% style="color:blue" %)**example:** 340 340 341 341 AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature ... ... @@ -355,10 +355,8 @@ 355 355 356 356 === 3.5.1 Configure Node-Red === 357 357 358 - 359 359 [[image:image-20230802112413-29.png]] 360 360 361 - 362 362 [[image:image-20230802112413-30.png]] 363 363 364 364 ... ... @@ -371,7 +371,7 @@ 371 371 === 3.5.3 Configure NB-IoT Sensors === 372 372 373 373 374 -* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%) ~/~/ 373 +* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%) ~/~/Set to mqtt Server and Payload 375 375 376 376 * (% style="color:blue" %)**AT+CLIENT=any value** 377 377 ... ... @@ -383,7 +383,6 @@ 383 383 384 384 * (% style="color:blue" %)**AT+SUBTOPIC=any value** 385 385 386 - 387 387 == 3.6 ThingsBoard.Cloud (via MQTT) == 388 388 389 389 === 3.6.1 Configure ThingsBoard === ... ... @@ -390,7 +390,6 @@ 390 390 391 391 ==== 3.6.1.1 Create Device ==== 392 392 393 - 394 394 Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. 395 395 396 396 [[image:image-20230802112413-32.png]] ... ... @@ -398,14 +398,13 @@ 398 398 399 399 ==== 3.6.1.2 Create Uplink & Downlink Converter ==== 400 400 401 - 402 402 (% style="color:blue" %)**Uplink Converter** 403 403 404 404 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. 405 405 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.402 +To create an uplink converter go to the Integrations center -> Data converters page and click “plus” button. Name it “MQTT Uplink Converter” and select type Uplink. Use debug mode for now. 407 407 408 -[[image:image-20230802112413-33.png ||height="732" width="1302"]]404 +[[image:image-20230802112413-33.png]] 409 409 410 410 411 411 (% style="color:blue" %)**Downlink Converter** ... ... @@ -412,7 +412,7 @@ 412 412 413 413 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke 414 414 415 -[[image:image-20230802112413-34.png ||height="734" width="1305"]]411 +[[image:image-20230802112413-34.png]] 416 416 417 417 (% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.** 418 418 ... ... @@ -420,30 +420,28 @@ 420 420 ==== 3.6.1.3 MQTT Integration Setup ==== 421 421 422 422 423 -Go to the (% style="color:blue" %)**Integrations center**(%%)**->**(% style="color:blue" %)**Integrations**(%%)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**;419 +Go to the Integrations center -> Integrations page and click **“plus”** icon to add a new integration. Name it “MQTT Integration”, select type MQTT; 424 424 425 -[[image:image-20230802112413-35.png ||height="738" width="1312"]]421 +[[image:image-20230802112413-35.png]] 426 426 427 - 428 428 * The next steps is to add the recently created uplink and downlink converters; 429 429 430 -[[image:image-20230802112413-36.png ||height="736" width="1308"]]425 +[[image:image-20230802112413-36.png]] 431 431 432 -[[image:image-20230802112413-37.png ||height="735" width="1307"]]427 +[[image:image-20230802112413-37.png]] 433 433 434 - 435 435 (% style="color:blue" %)**Add a topic filter:** 436 436 437 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature **固定的? 对的。** 438 438 432 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。 433 + 439 439 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default; 440 440 441 -[[image:image-20230802112413-38.png ||height="731" width="1300"]]436 +[[image:image-20230802112413-38.png]] 442 442 443 443 444 444 === 3.6.2 Simulate with MQTT.fx === 445 445 446 - 447 447 [[image:image-20230802112413-39.png]] 448 448 449 449 [[image:image-20230802112413-40.png]] ... ... @@ -456,11 +456,11 @@ 456 456 457 457 * (% style="color:#037691" %)**AT+PRO=3,3 **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. 458 458 459 -* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的**453 +* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的 460 460 461 -* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的**455 +* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的 462 462 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 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性)**457 +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 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性) 464 464 465 465 (% style="color:blue" %)**CLIENT :“Any value”** 466 466 ... ... @@ -495,7 +495,7 @@ 495 495 [[image:image-20230802112413-46.png]] 496 496 497 497 498 -On the Connection Profile window, set the following information: **(这边加一个截图)**492 +On the Connection Profile window, set the following information: (这边加一个截图) 499 499 500 500 * (% style="color:blue" %)**Profile Name: “Any name”** 501 501 ... ... @@ -505,18 +505,16 @@ 505 505 506 506 * (% style="color:blue" %)**Client ID: “Any value”** 507 507 508 -On the section User credentials, set the following information: **(这边加一个截图)**502 +On the section User credentials, set the following information:(这边加一个截图) 509 509 510 -* (% style="color:blue" %)**User Name: “Any value”**(%%)~/~/Tago validates your user by the token only504 +* **User Name: “Any value”** Tago validates your user by the token only 511 511 512 -* (% style="color:blue" %)**Password: “Your device token”**506 +* **Password: “Your device token”** 513 513 514 -* (% style="color:blue" %)**PUBTOPIC: “Any value”**508 +* **PUBTOPIC: “Any value”** 515 515 516 -* (% style="color:blue" %)**SUBTOPIC: “Any value”**510 +* **SUBTOPIC: “Any value”** 517 517 518 - 519 - 520 520 === 3.7.2 Simulate with MQTT.fx === 521 521 522 522 ... ... @@ -524,9 +524,8 @@ 524 524 525 525 [[image:image-20230802112413-48.png]] 526 526 527 -Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%)command, and the payload will be converted to**JSON format**.519 +Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format. 528 528 529 - 530 530 [[image:image-20230802112413-49.png]] 531 531 532 532 ... ... @@ -555,7 +555,7 @@ 555 555 556 556 * (% style="color:blue" %)**Client ID: “Any value”** 557 557 558 -* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/Tago validates your user by the token only549 +* (% style="color:blue" %)**User Name: “Any value”** (%%) Tago validates your user by the token only 559 559 560 560 * (% style="color:blue" %)**Password: “Your device token”** 561 561