Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 2 removed)
  • mqtt-command-2.png
  • new-device-telemetry-test.png

Details

Page properties

Content

...	...	@@ -15,12 +15,10 @@
15	15
16	16	= Add New Device =
17	17
18		-First, we will add a device to simulate data using MQTT. This device does not represent a real physical device but serves as a common virtual device for all Dragino NB/CB devices.
19		-
20	20	In the left navigation, click **Entities** and then click **Devices**.
21	21
22	22
23		-[[image:device-list-empty.png]]
	21	+[[image:ThingsBoard-Device.png]]
24	24
25	25
26	26	On the **Devices **page, click on the ‘**+**’ button, and then click on the **Add new device **from the dropdown menu.
...	...	@@ -29,58 +29,7 @@
29	29	[[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
30	30
31	31
32		-The **Add new device** window appears. Name the device, for example '**Virtual NB/CB device**'.
33	33
34		-Click on the **Next: Credentials** button.
35		-
36		-
37		-[[image:new-device-device-details.png||height="529" width="500"]]
38		-
39		-
40		-Click the **Access token** button if it is not selected by default.
41		-
42		-Copy the **Access token** to a text editor, as you will need it in the section **'Sending data from an MQTT client'**.
43		-
44		-Click on the **Add** button.
45		-
46		-[[image:new-device-access-token.png||height="528" width="500"]]
47		-
48		-
49		-Click on the **MQTT** button.
50		-
51		-Then, select the operating system you are going to use with the **Mosquitto MQTT Broker**. This example shows sending a command from a computer running **MacOS**. First, install the necessary client tools on your computer.
52		-
53		-Copy the MQTT pub command in the '**Execute the following command**' section.
54		-
55		-{{code language="none"}}
56		-mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/me/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:25}"
57		-{{/code}}
58		-
59		-Note that the **State** is still shown as **'Inactive'** in the **Latest telemetry** section.
60		-
61		-[[image:new-device-check-connectivity.png||height="522" width="500"]]
62		-
63		-
64		-On the terminal, enter the command you copied. This command sends the MQTT payload **{temperature:25}** as telemetry data from a virtual device named **'me'**. Of course, you can replace **'me'** with a device name or use the wildcard character **'+'** to match any device name.
65		-
66		-
67		-[[image:mqtt-command-1.png||height="228" width="700"]]
68		-
69		-
70		-If the command is successful, you can see the telemetry data you sent under the **Latest telemetry** section.
71		-
72		-
73		-[[image:new-device-telemetry-test.png||height="520" width="500"]]
74		-
75		-
76		-Send the same command again, only changing the **temperature** value, to see how the **Latest telemetry** section updates its data.
77		-
78		-Once you are done experimenting with this, close the window by clicking the **Close** button.
79		-
80		-
81		-[[image:mqtt-command-2.png||height="227" width="700"]]
82		-
83		-
84	84	= Data Converters =
85	85
86	86	In **ThingsBoard**, **Data Converters** are components used to transform incoming or outgoing data between different formats, typically to convert raw telemetry data from devices into a structured format that ThingsBoard can understand, or vice versa.
...	...	@@ -354,7 +354,7 @@
354	354	* **Credentials**: Basic
355	355	* **Username**: Access token (This is the access token you copied from the device)
356	356	* **Password** - Leave it as blank
357		-* **Topic** - v1/devices/+/telemetry (sightly modify the topic 'v1/devices/me/telemetry' you copied from the device to enable receiving data from any 'device name')
	304	+* **Topic** - v1/devices/+/telemetry (sightly modify the topic 'v1/devices/me/telemetry' you copied for the device to enable receiving data from any 'device name')
358	358	* **QoS** - 0-At most once
359	359
360	360	Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
...	...	@@ -371,15 +371,18 @@
371	371	[[image:add-connection-success.png||height="511" width="500"]]
372	372
373	373
374		-You should see that the newly added integration is listed on the **Integrations** page.
375	375
376		-Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
377	377
378	378
379	379
380		-[[image:integrations-list-added-pending.png]]
381	381
	326	+You should see that the newly added integration is listed on the **Integrations** page.
382	382
	328	+Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
	329	+
	330	+[[image:Integrations-list.png]]
	331	+
	332	+
383	383	= Verifying the receipt of data from the device =
384	384
385	385	Connect **S31B-NB** to transfer information. If the integration was performed without errors, after the transmission of the first telemetry, a new device with the name “xxxxx” 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.

mqtt-command-2.png

Author

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

Size

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

Content

new-device-telemetry-test.png

Author

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

Size

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

Content