Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -170,7 +170,7 @@
170	170	First, you need to create devices in ThingsBoard to represent your physical devices. For example, you can name it **Device A**, and the second device could be **Device B** or any name you prefer. The device name should be unique within the **Devices** space.
171	171
172	172
173		-In the left navigation, click **Entities -> Devices**.
	173	+In the left navigation, click Entities -> Devices.
174	174
175	175	Click the **Add Device** button (the button with the **+** sign), and from the dropdown menu, click **Add new device**.
176	176
...	...	@@ -364,6 +364,8 @@
364	364	* **Topic: device/a** (The topic can be anything; you can even use just the device name.)
365	365	* **QoS:** 0-At most once
366	366
	367	+
	368	+
367	367	[[image:add-integartion-connection.png||height="505" width="500"]]
368	368
369	369
...	...	@@ -394,10 +394,9 @@
394	394	Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
395	395
396	396
397		-[[image:integration-added.png]]
	399	+[[image:new-integration-pending.png]]
398	398
399	399
400		-
401	401	= 6. Verifying the receipt of data from virtual devices =
402	402
403	403
...	...	@@ -420,7 +420,7 @@
420	420	== 5.2 Sending messages ==
421	421
422	422
423		-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.
	424	+On the terminal, issue the following MQTT command which simulates the device S31B-NB. The message payload contains the fields temperature and humidity, which hold the values S31B-NB and 27, respectively. This payload is also (technically) known as telemetry.
424	424
425	425	{{code language="none"}}
426	426	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}'
...	...	@@ -432,6 +432,8 @@
432	432	[[image:integration-active.png]]
433	433
434	434
	436	+
	437	+
435	435	== 6.3 Viewing messages ==
436	436
437	437
...	...	@@ -450,28 +450,21 @@
450	450	Then click on the **Apply changes** (//**tick icon**//) button.
451	451
452	452
453		-[[image:debug-enabled.png||height="301" width="700"]]
	456	+[[image:Screenshot 2025-03-18 at 09.23.10.png]]
454	454
455	455
456		-
457		-
458	458	Now go to the **Events** tab.
459	459
460		-Select the **Event type** as **Debug** from the dropdown list.
	461	+Select the Event type as **Debug** from the dropdown list.
461	461
462		-Publish another message (of course, you can repeat the previous message by pressing the UP arrow on your keyboard and then press Enter key) to your MQTT broker from your terminal, for example:
	463	+Now you can see all the Uplink messages you are simulating through the MQTT broker. The status should be **OK **if there is no errors in your integration.
463	463
464		-{{code language="none"}}
465		-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}'
466		-{{/code}}
467	467
468		-Now you can see that uplink message in the **Events** tab (Click the **refresh** button if you didn't see any messages in the Events tab). The status should be **OK **if there is no errors in your integration.
469		-
470		-
471	471	[[image:Screenshot 2025-03-26 at 19.49.31.png]]
472	472
473	473
474	474
	470	+
475	475	Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
476	476
477	477
...	...	@@ -595,3 +595,5 @@
595	595	{{/info}}
596	596
597	597	[[image:image-4.png]]
	594	+
	595	+