Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 212.1
edited by Dilisi S
on 2025/04/21 18:22
Change comment: Uploaded new attachment "Screenshot 2025-04-21 122154.png", version {1}
To version 213.1
edited by Dilisi S
on 2025/04/21 18:23
Change comment: April 17 edits - part 2

Summary

Details

Page properties
Content
... ... @@ -336,7 +336,6 @@
336 336  * **QoS:** 0-At most once
337 337  
338 338  
339 -
340 340  [[image:add-integration-4.png||height="484" width="500"]]
341 341  
342 342  
... ... @@ -367,8 +367,8 @@
367 367  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
368 368  
369 369  
370 -[[image:integration-added.png]]
371 371  
370 +[[image:integrations-pending.png]]
372 372  
373 373  
374 374  = 5. Verifying the receipt of data from virtual devices =
... ... @@ -379,32 +379,41 @@
379 379  
380 380  We use the Mosquitto MQTT client to simulate MQTT messages, acting as a virtual device. First, install the Mosquitto client on your computer from [[this link>>url:https://mosquitto.org/download/]]. The Mosquitto client publishes messages to the MQTT broker (HiveMQ) on a specified MQTT topic. ThingsBoard subscribes to these messages using the same topic.
381 381  
382 -The Mosquitto client publishes messages (payloads) on the topic **/device/a**. Of course, you can use any topic for testing.
381 +The Mosquitto client publishes messages (payloads) to a topic - for example, # or device/ts01-nb. You can, of course, use any topic you prefer.
383 383  
384 -(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows:
385 385  
384 +(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows. The **IMEI **and **Model **are mandatory fields. For other fields, you can use any number of key-value pairs.
385 +
386 386  {{code language="none"}}
387 -{"IMEI": "350693903995577", "temperature":25, "humidity":80, "pressure":1005}
387 +{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}
388 388  {{/code}}
389 389  
390 -Once ThingsBoard receives this message, it forwards this payload to the matching device through the integration.
391 391  
392 -
393 393  == 5.2 Sending messages ==
394 394  
395 395  
396 -On your computer's terminal, issue the following MQTT command which simulates the device '**Device A'**. The message payload contains the fields IMEI, temperature, humidity, and pressure, which hold the values 350693903995577, 30, 80, and 1005 respectively. This payload is also (technically) known as telemetry.
394 +On your computer's terminal, issue the following MQTT command, which simulates the device named '**350693903995577'**. The message payload contains the fields IMEI, Model, temperature, humidity, and pressure, which hold the values 350693903995577,  TS01-NB, 30, 80, and 1005 respectively. This payload is also (technically) known as telemetry.
397 397  
398 398  {{code language="none"}}
399 -mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/a" -m '{"IMEI":"350693903995577", "temperature":30, "humidity":80, "pressure":1005}'
397 +mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -u "xxxxx" -P "xxxxx" -t "device/350693903995577" -m '{"IMEI":"350693903995577", "Model":"TS01-NB", "temperature":30, "humidity":80, "pressure":1005}'
400 400  {{/code}}
401 401  
402 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
400 +If the integration was performed without errors, a new device named **350693903995577 **is created in the **Devices **section.
403 403  
404 404  
405 -[[image:integration-active.png]]
403 +[[image:new-device-1.png]]
406 406  
407 407  
406 +The status of the integration also changes to '**Active**' after the first telemetry transmission.
407 +
408 +
409 +[[image:Screenshot 2025-04-21 122154.png]]
410 +
411 +
412 +
413 +**When ThingsBoard receives this message for the first time, it will automatically create a new device named '350693903995577' in the Devices section. The device name is based on the IMEI number. For subsequent messages with the same IMEI, no duplicate devices will be created. Each new IMEI number will result in a unique entry in the Devices section, representing a physical device.**
414 +
415 +
408 408  == 5.3 Viewing messages ==
409 409  
410 410