Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • integration-active.png

Details

Page properties

Content

...	...	@@ -379,13 +379,43 @@
379	379	[[image:new-integration-pending.png]]
380	380
381	381
382		-= 5. Verifying the receipt of data from the device =
	382	+= 5. Verifying the receipt of data from virtual devices =
383	383
384	384
385		-On the terminal, issue the following MQTT command which simulates the device S31B-NB.
	385	+== 5.1 How does it work? ==
386	386
	387	+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.
	388	+
	389	+The Mosquitto client publishes messages on the topic v1/devices/[device_name]/telemetry. The [device_name]placeholder can be replaced with any device name, for example, 'S31B-NB'. Then, the MQTT topic would be v1/devices/S31B-NB/telemetry.
	390	+
	391	+On the ThingsBoard side, we configure the MQTT topic subscription as v1/devices/+/telemetry. The + wildcard represents any device name and allows ThingsBoard to automatically create (provision) a device with that name, such as S31B-NB, for example.
	392	+
	393	+
	394	+**The new device is created the first time the MQTT topic is received. For subsequent MQTT topics with the same device name, no duplicate devices will be created.**
	395	+
	396	+
	397	+For example, if you send two MQTT messages with different device names in the topic:
	398	+
	399	+1. v1/devices/**S31B-NB**/telemetry
	400	+1. v1/devices/**S31B-CB**/telemetry
	401	+
	402	+ThingsBoard will create two devices named **S31B-NB** and **S31B-CB** in the **//Devices//** section.
	403	+
	404	+
	405	+The MQTT payload format is as follows, for example:
	406	+
387	387	{{code language="none"}}
388		-mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
	408	+{"temperature":10.4, "humidity":85}
389	389	{{/code}}
390	390
	411	+
	412	+== 5.2 Sending messages ==
	413	+
	414	+
	415	+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 10.4 and 85, respectively. This payload is also (technically) known as telemetry.
	416	+
	417	+{{code language="none"}}
	418	+mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/SN-001/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":10.4, "humidity":85}'
	419	+{{/code}}
	420	+
391	391	If the integration was performed without errors, after the transmission of the first telemetry, a new device with the name “S31B-NB” will appear in the Devices → All. Also, you can verify the input and output data, respectively, before and after conversion in Data converters → UDP Uplink Converter NB/CB → Events.

integration-active.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+64.2 KB

Content