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 ... ... @@ -232,7 +232,7 @@ 232 232 233 233 == 3.4 Datacake == 234 234 235 -== 3.4.1 Define Product == 236 +=== 3.4.1 Define Product === 236 236 237 237 238 238 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. ... ... @@ -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 === ... ... @@ -247,7 +247,7 @@ 247 247 248 248 In the second step you have to define the device which should be added to the product. 249 249 250 -[[image:image-20230802112413-15.png]] 251 +[[image:image-20230802112413-15.png||height="859" width="1290"]] 251 251 252 252 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. 253 253 ... ... @@ -259,15 +259,15 @@ 259 259 260 260 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"**. 261 261 262 -[[image:image-20230802112413-16.png]] 263 +[[image:image-20230802112413-16.png||height="495" width="1310"]] 263 263 264 -[[image:image-20230802112413-17.png]] 265 +[[image:image-20230802112413-17.png||height="741" width="1303"]] 265 265 266 266 To create a first database field, please click on the (% style="color:blue" %)**"Add Field"**(%%) button as marked in the screenshot above. 267 267 268 268 This will open another modal asking for some required input for your first field. 269 269 270 -[[image:image-20230802112413-18.png]] 271 +[[image:image-20230802112413-18.png||height="878" width="1305"]] 271 271 272 272 [[image:image-20230802112413-19.png]] 273 273 ... ... @@ -285,15 +285,17 @@ 285 285 286 286 [[image:image-20230802112413-20.png]] 287 287 289 + 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. 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. 291 291 292 -(% style="color:blue" %)**AT+CLIENT=“Any value”** 295 +* (% style="color:blue" %)**AT+CLIENT=“Any value”** 293 293 294 -(% style="color:blue" %)**AT+UNAME=Token** 297 +* (% style="color:blue" %)**AT+UNAME=Token** 295 295 296 -(% style="color:blue" %)**AT+PWD=Token** 299 +* (% style="color:blue" %)**AT+PWD=Token** 297 297 298 298 [[image:image-20230802112413-21.png]] 299 299 ... ... @@ -303,10 +303,8 @@ 303 303 304 304 (% style="color:blue" %)**Subscribe** 305 305 306 -Data is published according to the following structure: 309 +Data is published according to the following structure: (% style="color:blue" %)**dtck~/~//**(%%)** ** 307 307 308 -dtck~/~// 309 - 310 310 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. 311 311 312 312 ... ... @@ -333,10 +333,8 @@ 333 333 334 334 To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure. 335 335 336 -Due to the nature of MQTT, the topic prefix differs as follows: 337 +Due to the nature of MQTT, the topic prefix differs as follows: (% style="color:blue" %)**dtck-pub~/~//** 337 337 338 -dtck-pub~/~// 339 - 340 340 (% style="color:blue" %)**example:** 341 341 342 342 AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature ... ... @@ -356,8 +356,10 @@ 356 356 357 357 === 3.5.1 Configure Node-Red === 358 358 358 + 359 359 [[image:image-20230802112413-29.png]] 360 360 361 + 361 361 [[image:image-20230802112413-30.png]] 362 362 363 363 ... ... @@ -370,7 +370,7 @@ 370 370 === 3.5.3 Configure NB-IoT Sensors === 371 371 372 372 373 -* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%) ~/~/Set to mqtt Server and Payload 374 +* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%) ~/~/ Set to mqtt Server and Payload 374 374 375 375 * (% style="color:blue" %)**AT+CLIENT=any value** 376 376 ... ... @@ -382,6 +382,7 @@ 382 382 383 383 * (% style="color:blue" %)**AT+SUBTOPIC=any value** 384 384 386 + 385 385 == 3.6 ThingsBoard.Cloud (via MQTT) == 386 386 387 387 === 3.6.1 Configure ThingsBoard === ... ... @@ -388,6 +388,7 @@ 388 388 389 389 ==== 3.6.1.1 Create Device ==== 390 390 393 + 391 391 Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. 392 392 393 393 [[image:image-20230802112413-32.png]] ... ... @@ -395,13 +395,14 @@ 395 395 396 396 ==== 3.6.1.2 Create Uplink & Downlink Converter ==== 397 397 401 + 398 398 (% style="color:blue" %)**Uplink Converter** 399 399 400 400 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. 401 401 402 -To create an uplink converter go to the Integrations center -> Data converters page and click “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. 403 403 404 -[[image:image-20230802112413-33.png]] 408 +[[image:image-20230802112413-33.png||height="732" width="1302"]] 405 405 406 406 407 407 (% style="color:blue" %)**Downlink Converter** ... ... @@ -408,7 +408,7 @@ 408 408 409 409 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke 410 410 411 -[[image:image-20230802112413-34.png]] 415 +[[image:image-20230802112413-34.png||height="734" width="1305"]] 412 412 413 413 (% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.** 414 414 ... ... @@ -416,28 +416,30 @@ 416 416 ==== 3.6.1.3 MQTT Integration Setup ==== 417 417 418 418 419 -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**; 420 420 421 -[[image:image-20230802112413-35.png]] 425 +[[image:image-20230802112413-35.png||height="738" width="1312"]] 422 422 427 + 423 423 * The next steps is to add the recently created uplink and downlink converters; 424 424 425 -[[image:image-20230802112413-36.png]] 430 +[[image:image-20230802112413-36.png||height="736" width="1308"]] 426 426 427 -[[image:image-20230802112413-37.png]] 432 +[[image:image-20230802112413-37.png||height="735" width="1307"]] 428 428 434 + 429 429 (% style="color:blue" %)**Add a topic filter:** 430 430 437 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature **固定的? 对的。** 431 431 432 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。 433 - 434 434 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default; 435 435 436 -[[image:image-20230802112413-38.png]] 441 +[[image:image-20230802112413-38.png||height="731" width="1300"]] 437 437 438 438 439 439 === 3.6.2 Simulate with MQTT.fx === 440 440 446 + 441 441 [[image:image-20230802112413-39.png]] 442 442 443 443 [[image:image-20230802112413-40.png]] ... ... @@ -450,11 +450,11 @@ 450 450 451 451 * (% style="color:#037691" %)**AT+PRO=3,3 **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. 452 452 453 -* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的 459 +* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的** 454 454 455 -* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) ~-~-> 只需要 Device Name 吗?对的 461 +* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的** 456 456 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 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性) 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 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性)** 458 458 459 459 (% style="color:blue" %)**CLIENT :“Any value”** 460 460 ... ... @@ -489,7 +489,7 @@ 489 489 [[image:image-20230802112413-46.png]] 490 490 491 491 492 -On the Connection Profile window, set the following information: (这边加一个截图) 498 +On the Connection Profile window, set the following information: **(这边加一个截图)** 493 493 494 494 * (% style="color:blue" %)**Profile Name: “Any name”** 495 495 ... ... @@ -499,16 +499,18 @@ 499 499 500 500 * (% style="color:blue" %)**Client ID: “Any value”** 501 501 502 -On the section User credentials, set the following information:(这边加一个截图) 508 +On the section User credentials, set the following information: **(这边加一个截图)** 503 503 504 -* **User Name: “Any value”** Tago validates your user by the token only 510 +* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only 505 505 506 -* **Password: “Your device token”** 512 +* (% style="color:blue" %)**Password: “Your device token”** 507 507 508 -* **PUBTOPIC: “Any value”** 514 +* (% style="color:blue" %)**PUBTOPIC: “Any value”** 509 509 510 -* **SUBTOPIC: “Any value”** 516 +* (% style="color:blue" %)**SUBTOPIC: “Any value”** 511 511 518 + 519 + 512 512 === 3.7.2 Simulate with MQTT.fx === 513 513 514 514 ... ... @@ -516,8 +516,9 @@ 516 516 517 517 [[image:image-20230802112413-48.png]] 518 518 519 -Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format. 527 +Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**. 520 520 529 + 521 521 [[image:image-20230802112413-49.png]] 522 522 523 523 ... ... @@ -546,7 +546,7 @@ 546 546 547 547 * (% style="color:blue" %)**Client ID: “Any value”** 548 548 549 -* (% style="color:blue" %)**User Name: “Any value”** (%%) Tago validates your user by the token only 558 +* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only 550 550 551 551 * (% style="color:blue" %)**Password: “Your device token”** 552 552