Last modified by Mengting Qiu on 2025/03/08 11:33
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -232,7 +232,7 @@ 232 232 233 233 == 3.4 Datacake == 234 234 235 -== =3.4.1 Define Product ===235 +== 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. ... ... @@ -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 ||height="859" width="1290"]]250 +[[image:image-20230802112413-15.png]] 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 ||height="495" width="1310"]]262 +[[image:image-20230802112413-16.png]] 263 263 264 -[[image:image-20230802112413-17.png ||height="741" width="1303"]]264 +[[image:image-20230802112413-17.png]] 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 ||height="878" width="1305"]]270 +[[image:image-20230802112413-18.png]] 271 271 272 272 [[image:image-20230802112413-19.png]] 273 273 ... ... @@ -287,14 +287,13 @@ 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 291 -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. 292 292 293 - *(% style="color:blue" %)**AT+CLIENT=“Any value”**292 +(% style="color:blue" %)**AT+CLIENT=“Any value”** 294 294 295 - *(% style="color:blue" %)**AT+UNAME=Token**294 +(% style="color:blue" %)**AT+UNAME=Token** 296 296 297 - *(% style="color:blue" %)**AT+PWD=Token**296 +(% style="color:blue" %)**AT+PWD=Token** 298 298 299 299 [[image:image-20230802112413-21.png]] 300 300 ... ... @@ -304,8 +304,10 @@ 304 304 305 305 (% style="color:blue" %)**Subscribe** 306 306 307 -Data is published according to the following structure: (% style="color:blue" %)**dtck~/~//**(%%)** **306 +Data is published according to the following structure: 308 308 308 +dtck~/~// 309 + 309 309 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. 310 310 311 311 ... ... @@ -332,8 +332,10 @@ 332 332 333 333 To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure. 334 334 335 -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: 336 336 338 +dtck-pub~/~// 339 + 337 337 (% style="color:blue" %)**example:** 338 338 339 339 AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature ... ... @@ -353,10 +353,8 @@ 353 353 354 354 === 3.5.1 Configure Node-Red === 355 355 356 - 357 357 [[image:image-20230802112413-29.png]] 358 358 359 - 360 360 [[image:image-20230802112413-30.png]] 361 361 362 362 ... ... @@ -369,7 +369,7 @@ 369 369 === 3.5.3 Configure NB-IoT Sensors === 370 370 371 371 372 -* (% 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 373 373 374 374 * (% style="color:blue" %)**AT+CLIENT=any value** 375 375 ... ... @@ -381,8 +381,6 @@ 381 381 382 382 * (% style="color:blue" %)**AT+SUBTOPIC=any value** 383 383 384 - 385 - 386 386 == 3.6 ThingsBoard.Cloud (via MQTT) == 387 387 388 388 === 3.6.1 Configure ThingsBoard === ... ... @@ -389,7 +389,6 @@ 389 389 390 390 ==== 3.6.1.1 Create Device ==== 391 391 392 - 393 393 Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. 394 394 395 395 [[image:image-20230802112413-32.png]] ... ... @@ -397,14 +397,13 @@ 397 397 398 398 ==== 3.6.1.2 Create Uplink & Downlink Converter ==== 399 399 400 - 401 401 (% style="color:blue" %)**Uplink Converter** 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”**(%%)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. 406 406 407 -[[image:image-20230802112413-33.png ||height="732" width="1302"]]404 +[[image:image-20230802112413-33.png]] 408 408 409 409 410 410 (% style="color:blue" %)**Downlink Converter** ... ... @@ -411,7 +411,7 @@ 411 411 412 412 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke 413 413 414 -[[image:image-20230802112413-34.png ||height="734" width="1305"]]411 +[[image:image-20230802112413-34.png]] 415 415 416 416 (% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.** 417 417 ... ... @@ -419,30 +419,28 @@ 419 419 ==== 3.6.1.3 MQTT Integration Setup ==== 420 420 421 421 422 -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**;419 +Go to the Integrations center -> Integrations page and click **“plus”** icon to add a new integration. Name it “MQTT Integration”, select type MQTT; 423 423 424 -[[image:image-20230802112413-35.png ||height="738" width="1312"]]421 +[[image:image-20230802112413-35.png]] 425 425 426 - 427 427 * The next steps is to add the recently created uplink and downlink converters; 428 428 429 -[[image:image-20230802112413-36.png ||height="736" width="1308"]]425 +[[image:image-20230802112413-36.png]] 430 430 431 -[[image:image-20230802112413-37.png ||height="735" width="1307"]]427 +[[image:image-20230802112413-37.png]] 432 432 433 - 434 434 (% style="color:blue" %)**Add a topic filter:** 435 435 431 + 436 436 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 440 -[[image:image-20230802112413-38.png ||height="731" width="1300"]]436 +[[image:image-20230802112413-38.png]] 441 441 442 442 443 443 === 3.6.2 Simulate with MQTT.fx === 444 444 445 - 446 446 [[image:image-20230802112413-39.png]] 447 447 448 448 [[image:image-20230802112413-40.png]] ... ... @@ -504,19 +504,16 @@ 504 504 505 505 * (% style="color:blue" %)**Client ID: “Any value”** 506 506 507 -On the section User credentials, set the following information: 502 +On the section User credentials, set the following information:(这边加一个截图) 508 508 509 -* (% 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 510 510 511 -* (% style="color:blue" %)**Password: “Your device token”**506 +* **Password: “Your device token”** 512 512 513 -* (% style="color:blue" %)**PUBTOPIC: “Any value”**508 +* **PUBTOPIC: “Any value”** 514 514 515 -* (% style="color:blue" %)**SUBTOPIC: “Any value”**510 +* **SUBTOPIC: “Any value”** 516 516 517 - 518 - 519 - 520 520 === 3.7.2 Simulate with MQTT.fx === 521 521 522 522 ... ... @@ -524,7 +524,7 @@ 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 529 [[image:image-20230802112413-49.png]] 530 530 ... ... @@ -554,7 +554,7 @@ 554 554 555 555 * (% style="color:blue" %)**Client ID: “Any value”** 556 556 557 -* (% 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 558 558 559 559 * (% style="color:blue" %)**Password: “Your device token”** 560 560