Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 143.1
edited by Dilisi S
on 2025/03/09 04:03
Change comment: Uploaded new attachment "dashboard-5.png", version {1}
To version 20.1
edited by Dilisi S
on 2025/03/04 04:18
Change comment: Uploaded new attachment "Data-converter-list-uplink-only.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -6,258 +6,217 @@
6 6  Draft Document
7 7  {{/warning}}
8 8  
9 += Introduction =
9 9  
11 +This document guides you on integrating Dragino -NB and -CB series devices data with ThingsBoard. For this guide, we use ThingsBoard Cloud, which is one of the ThingsBoard versions that allows you to try it for free.
10 10  
13 +The NB series devices end with the suffix -NB, and the CB series devices end with the suffix -CB. For example, S31B-NB is an NB device, and S31-CB is a CB device.
11 11  
12 -= 1. Introduction =
13 13  
16 += Add New Device =
14 14  
15 -This document guides you on integrating Dragino **-NB** and **-CB** series devices data with ThingsBoard. For this guide, we use ThingsBoard Cloud, which is one of the ThingsBoard versions that allows you to try it for free.
18 +In the left navigation, click **Entities** and then click **Devices**.
16 16  
17 -The **NB series** devices end with the suffix **-NB**, and the **CB series** devices end with the suffix **-CB**. For example, **S31B-NB** is an **NB device**, and **S31-CB** is a **CB device**.
18 18  
21 +[[image:ThingsBoard-Device.png]]
19 19  
20 -= 2. Prerequisites =
21 21  
22 -To complete this tutorial, you need to have the following:
24 +On the ‘**Devices**’ page, click on the ‘**+**’ button, and then click on the ‘**Add new device**’ from the dropdown menu.
23 23  
24 -* ThingsBoard cloud account
25 -* HiveMQ Cloud account
26 26  
27 -== 2.1 ThingsBoard Cloud ==
27 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
28 28  
29 29  
30 -Go to [[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]]
31 31  
32 -Click on the **Try it now**.
31 += Data Converters =
33 33  
34 34  
35 -[[image:thingsboard-1.png]]
34 +== Uplink ==
36 36  
36 +In the left navigation, click ‘Integrations center’, and then click ‘Data converters’.
37 37  
38 -Select either the **North America** or **Europe** region. Here, we use the Europe region.
39 39  
40 -[[image:thingsboard-2.png]]
39 +[[image:ThingsBoard-Data-Converters.png]]
41 41  
42 42  
43 -You can sign up with your **Google**, **GitHub**, **Facebook**, or **Apple** account. If not you can create an account with providing your **name**, **email address** and a **password**.
42 +On the ‘Data converters’ page, click on the ‘+’ button, and then click on the ‘Create new converter’ from the dropdown menu.
44 44  
45 -Click on the **Sign up** button.
46 46  
47 -[[image:thingsboard-3.png||height="651" width="500"]]
45 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
48 48  
49 49  
50 -You will be navigated to the following page.
48 +The ‘Add data converter’ window will appear. Name it ‘**UDP Uplink Converter NB/CB**’ and select the Type as ‘Uplink’.
51 51  
52 -[[image:thingsboard-5.png||height="109" width="500"]]
50 +Click on the ‘JavaScript’ button. Now copy and paste the following script to the ‘Decoder function’ section:
53 53  
54 -
55 -simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button.
56 -
57 -
58 -[[image:thingsboard-4.png||height="249" width="500"]]
59 -
60 -
61 -Now losing to the account using your credentials:
62 -
63 -
64 -[[image:thingsboard-6.png||height="244" width="500"]]
65 -
66 -
67 -== 2.2 HiveMQ Cloud ==
68 -
69 -
70 -Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
71 -
72 -Click on the **Start Free** button.
73 -
74 -[[image:hivwmq-1.png]]
75 -
76 -
77 -Click on the **Sign Up FREE Now** button in the **HIVEMQ CLOUD** section.
78 -
79 -[[image:hivemq-2.png]]
80 -
81 -
82 -Click on the **Sign Up** button.
83 -
84 -You can sign up with HiveMQ using your **GitHub**, **Google**, or **LinkedIn** account.
85 -
86 -If not, provide your **email address** and a **password** to create an account by clicking on the **Sign Up** button.
87 -
88 -
89 -[[image:hivemq-3.png]]
90 -
91 -
92 -You will receive an email to verify your email address. Click on the **Confirm my account** button.
93 -
94 -
95 -[[image:hivemq-4.jpg||height="889" width="400"]]
96 -
97 -
98 -You will be redirected to a page asking you to complete your profile. Once done, click the **Continue** button.
99 -
100 -
101 -[[image:hivemq-5.png||height="655" width="700"]]
102 -
103 -
104 -Select the CloudMQ Cloud plan you need. For testing purposes, select the **Serverless FREE** plan by clicking on the **Create Serverless Cluster** button.
105 -
106 -
107 -[[image:hivemq-6.png]]
108 -
109 -
110 -You will be navigated to the **Your Clusters** page. Click on the **Manage Cluster** button.
111 -
112 -[[image:hivemq-7.png]]
113 -
114 -
115 -In your cluster page, you can find some useful parameters you need to create a MQTT connection.
116 -
117 -**URL**: This is the host name. Click on the copy button to copy it.
118 -
119 -**Port**: 8883
120 -
121 -
122 -Click on the **Getting Started** tab to setup the username and the password as the connection credentials.
123 -
124 -
125 -[[image:hivemq-8.png]]
126 -
127 -
128 -In the '**Create Connection Credentials**' section, provide a **username** and **password**, then click the **Add** button.
129 -
130 -
131 -[[image:hivemq-9.png]]
132 -
133 -
134 -
135 -If everything is successful, you will see the following message.
136 -
137 -
138 -[[image:hivemq-10.png||height="206" width="500"]]
139 -
140 -
141 -You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
142 -
143 -
144 -= 3. Data Converters =
145 -
146 -
147 -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.
148 -
149 -
150 -== 3.1 Uplink ==
151 -
152 -
153 -In the left navigation, click **Integrations center**, and then click **Data converters**.
154 -
155 -
156 -
157 -[[image:data-converters-list-empty.png]]
158 -
159 -
160 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
161 -
162 -
163 -
164 -[[image:create-new-converter-menu.png||height="259" width="500"]]
165 -
166 -
167 -The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
168 -
169 -Click on the **TBEL** button if not selected it by default. Delete the existing decoder function in the code editor. Now copy and paste the following decoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
170 -
171 171  {{code language="JavaScript"}}
172 -/** Decoder **/
173 -
53 +//Version: 0.1
174 174  // decode payload to string
175 175  var payloadStr = decodeToString(payload);
176 -var data = JSON.parse(payloadStr);
177 177  
178 -var deviceName = metadata.topic.split("/")[3];
179 179  // decode payload to JSON
180 -var deviceType = 'sensor';
58 +var objdata = {};
59 +var obj1 = {};
60 +var data = decodeToJson(payload);
61 +var deviceName = data.IMEI;
62 +delete data.IMEI;
63 +var modelname = "Dragino " + data.Model;
64 +//var mod = data.mod
65 +delete data.Model;
66 +//delete data.mod
67 +var timestamp = new Date().getTime();
181 181  
182 -// Result object with device attributes/telemetry data
69 +for (var key in data) {
70 +
71 + if (Number(key)) {
72 + obj1[key] = data[key];
73 + obj1[key][obj1[key].length - 1] = Number(new Date(
74 + obj1[key][obj1[key].length - 1]));
75 +
76 + }
77 +//Alec submitted25/02/25
78 +//turn old key into new
79 + else if (key === "Reading") {
80 + objdata["reading"] = data[key];
81 + } else if (key === "work mode") {
82 + objdata["work_mode"] = data[key];
83 + } else if (key === "hum") {
84 + objdata["humidity"] = data[key];
85 + }else if (key === "hum2") {
86 + objdata["humidity2"] = data[key];
87 + } else if (key === "hum3") {
88 + objdata["humidity3"] = data[key];
89 + } else if (key === "tem") {
90 + objdata["temperature"] = data[key];
91 + } else if (key === "tem2") {
92 + objdata["temperature2"] = data[key];
93 + } else if (key === "tem3") {
94 + objdata["temperature3"] = data[key];
95 + } else if (key === "DS18B20_Temp") {
96 + objdata["temperature_pro"] = data[key];
97 + } else if (key === "ds18b20_temperature") {
98 + objdata["temperature_pro"] = data[key];
99 + } else if (key === "DS18B20_temperature_pro") {
100 + objdata["temperature_pro"] = data[key];
101 + } else if (key === "tdc send flag") {
102 + objdata["tdc_send_flag"] = data[key];
103 + } else if (key === "trigger mode") {
104 + objdata["trigger_mode"] = data[key];
105 + } else if (key === "soil dielectric constant") {
106 + objdata["soil_dielectric_constant"] = data[key];
107 + } else if (key === "door open num") {
108 + objdata["door_open_num"] = data[key];
109 + } else if (key === "door duration") {
110 + objdata["door_duration"] = data[key];
111 + } else if (key === "count time") {
112 + objdata["count_time"] = data[key];
113 + } else if (key === "last open time2") {
114 + objdata["last_open_time2"] = data[key];
115 + } else if (key === "last open time3") {
116 + objdata["last_open_time3"] = data[key];
117 + }
118 +//Alec submitted25/02/25
119 + else {
120 + objdata[key] = data[key]
121 + }
122 +}
123 +var listdata = [{
124 + "ts": timestamp,
125 + "values": objdata
126 +}]
127 +for (var key1 in obj1) {
128 + if (modelname == "Dragino RS485-NB") {
129 + listdata.push({
130 + "ts": obj1[key1][obj1[key1].length - 1],
131 + "values": {
132 + "Payload": obj1[key1][0],
133 + }
134 + })
135 + } else {
136 + listdata.push({
137 + "ts": obj1[key1][obj1[key1].length - 1],
138 + "values": {
139 + "values": obj1[key1]
140 + },
141 + })
142 + }
143 +}
183 183  var result = {
145 +
184 184   deviceName: deviceName,
185 - deviceType: deviceType,
147 + deviceType: modelname,
186 186   attributes: {
187 - integrationName: metadata['integrationName'],
149 + model: modelname,
150 + //customerName: "NB-CB",
151 + //groupName: "NB-CB",
152 + //integrationName: metadata['integrationName']
153 +
188 188   },
189 - telemetry: {
190 - temperature: data.temperature,
191 - humidity: data.humidity,
192 - }
193 -};
155 + telemetry: listdata
156 +}
194 194  
195 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
158 +function decodeToString(payload) {
159 + return String.fromCharCode.apply(String, payload);
160 +}
196 196  
197 -return result;
198 -{{/code}}
162 +function decodeToJson(payload) {
163 + // covert payload to string.
164 + var str = decodeToString(payload);
199 199  
166 + // parse string to JSON
167 + var data = JSON.parse(str);
168 + return data;
169 +}
200 200  
201 -Click on the **Add** button.
171 +return result;
202 202  
173 +{{/code}}
203 203  
175 +Click on the ‘Add’ button.
204 204  
205 -[[image:add-uplink-data-converter.png||height="529" width="500"]]
206 206  
178 +[[image:ThingsBoard-add-data-converter-uplink.png||width="500"]]
207 207  
208 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
209 209  
210 -[[image:data-converter-list-showing-uplink-dc.png]]
181 +The uplink data converter is added to ThingsBoard and appears on the ‘Data Converters’ page
211 211  
212 212  
184 +== Downlink ==
213 213  
214 -== 3.2 Downlink ==
186 +On the ‘Data converters’ page, click on the ‘+’ button, and then click on the ‘Create new converter’ from the dropdown menu.
215 215  
216 216  
217 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
189 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
218 218  
219 219  
220 -[[image:create-new-converter-menu.png||width="500"]]
192 +The ‘**Add data converter**’ window will appear. Name it ‘**UDP Downlink Converter NB/CB**’ and select the Type as ‘**Downlink**’.
221 221  
194 +Click on the ‘**JavaScript**’ button. Now copy and paste the following script to the ‘**Encoder function**’ section:
222 222  
223 223  
224 -The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
225 -
226 -Click on the **TBEL** button if not selected it by default. Now copy and paste the following encoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This encoder function is compatible for both NB and CB series devices.
227 -
228 -
229 229  {{code language="JavaScript"}}
230 -// Encode downlink data from incoming Rule Engine message
198 +function hexToBase64(hexString) {
199 + // 将16进制字符串两个字符转换为一个字节
200 + var bytes = hexString.match(/.{2}/g);
201 + // 对每个字节进行解析，并转换为对应的字符
202 + var binaryString = bytes.map(function(byte) {
203 + return String.fromCharCode(parseInt(byte, 16));
204 + }).join('');
205 +
206 + // 使用btoa进行base64编码
207 + return btoa(binaryString);
208 +}
231 231  
232 -// msg - JSON message payload downlink message json
233 -// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
234 -// metadata - list of key-value pairs with additional data about the message
235 -// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
236 -
237 -/** Encoder **/
238 -
239 -var data = {};
240 -
241 -// Process data from incoming message and metadata
242 -
243 -data.tempFreq = msg.temperatureUploadFrequency;
244 -data.humFreq = msg.humidityUploadFrequency;
245 -
246 -data.devSerialNumber = metadata['ss_serialNumber'];
247 -
248 248  // Result object with encoded downlink payload
249 249  var result = {
250 -
251 251   // downlink data content type: JSON, TEXT or BINARY (base64 format)
252 - contentType: "JSON",
213 + contentType: "BINARY",
253 253  
254 254   // downlink data
255 - data: JSON.stringify(data),
216 + data:hexToBase64(metadata.shared_value)
256 256  
257 257   // Optional metadata object presented in key/value format
258 - metadata: {
259 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
260 - }
219 + //metadata: {}
261 261  
262 262  };
263 263  
... ... @@ -268,221 +268,79 @@
268 268  Click on the **Add** button.
269 269  
270 270  
230 +[[image:ThingsBoard-add-data-converter-downlink.png||height="532" width="500"]]
271 271  
272 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
273 273  
233 += Add Integration =
274 274  
275 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
235 +In the left navigation, click ‘Integrations center’, and then click ‘Integrations’.
276 276  
237 +On the ‘Integrations’ page, click on the “+” button.
277 277  
278 -[[image:data-converters-list.png]]
279 279  
240 +[[image:ThingsBoard-add-integration.png]]
280 280  
281 281  
282 -= 4. Add Integration =
243 +The ‘Add integration’ window appears.
283 283  
245 +In the Add Integration window, configure the following settings:
284 284  
285 -In the left navigation, click **Integrations center**, and then click **Integrations**.
286 -
287 -
288 -[[image:integrations-list-empty.png]]
289 -
290 -
291 -On the **Integrations** page, click on the '**+**' button.
292 -
293 -
294 -The **Add integration** window appears.
295 -
296 -In the **Add integration** window, configure the following settings:
297 -
298 -
299 299  **Basic settings:**
300 300  
301 -* **Integration type**: MQTT
302 -* **Name**: MQTT integration NB/CB
303 -* **Enable integration**: YES
304 -* **Allows create devices or assets**: YES
249 +* **Integration type**: UDP
250 +* **Name**: UDP Integration NB/CB
305 305  
306 306  Click **Next** button.
307 307  
308 308  
309 -
310 310  [[image:add-integration-basic-settings.png||height="511" width="500"]]
311 311  
312 312  
313 313  **Uplink data converter:**
314 314  
315 -* Click on the **Select existing** button.
316 -* **Uplink data converter**: Select **MQTT Uplink Converter NB/CB **from the dropdown list.
260 +* Click on the ‘**Select existing**’ button.
261 +* Uplink data converter: Select ‘**UDP Uplink Converter NB/CB**’ from the dropdown list.
317 317  
318 318  Click **Next** button.
319 319  
320 320  
321 -
322 322  [[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
323 323  
324 324  
325 325  **Downlink data converter:**
326 326  
327 -* Click on the **Select existing** button.
328 -* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
271 +* Click on the ‘**Select existing**’ button.
272 +* Downlink data converter: Select ‘**UDP Downlink Converter NB/CB**’ from the dropdown list.
329 329  
330 330  Click **Next** button.
331 331  
332 332  
277 +[[image:add-integration-downlink-data-converter.png||height="512" width="500"]]
333 333  
334 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
335 335  
336 -
337 337  **Connection:**
338 338  
339 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
340 -* **Port**: 8883
341 -* **Credentials**: Basic
342 -* **Enable SSL**: YES
343 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
344 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
345 -* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
346 -* **QoS:** 0-At most once
282 +**Port**: 11582
347 347  
348 -[[image:add-integration-connection.png||height="511" width="500"]]
284 +**Size of the buffer for inbound socket (in KB)**: 64
349 349  
286 +**Cache Size**: 10000000
350 350  
351 -Click on the **Advanced settings** button.
288 +**Cache time to live in minutes**: 1440
352 352  
353 -* **Clean session:** NO
354 -* **Retained**: NO
355 355  
356 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
291 +Copy the two keys, **Integration key** and **Integration secret** into a text editor, as you will need them in the section ‘xxxxx’.
357 357  
358 -
359 -Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
360 -
361 -
362 -[[image:check-connection.png||height="83" width="300"]]
363 -
364 -
365 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
366 -
367 -
368 -[[image:connection-success.png||height="511" width="500"]]
369 -
370 -
371 371  Click on the **Add** button.
372 372  
373 -You should see that the newly added integration is listed on the **Integrations** page.
374 374  
375 -Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
296 +[[image:add-integration-connection.png||height="511" width="500"]]
376 376  
377 377  
378 378  
379 -[[image:new-integration-pending.png]]
300 += Verifying the receipt of data from the device =
380 380  
302 +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.
381 381  
382 -= 5. Verifying the receipt of data from virtual devices =
383 383  
384 -
385 -== 5.1 How does it work? ==
386 -
387 -
388 -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.
389 -
390 -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.
391 -
392 -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.
393 -
394 -
395 -**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.**
396 -
397 -
398 -For example, if you send two MQTT messages with different device names in the topic:
399 -
400 -1. v1/devices/**S31B-NB**/telemetry
401 -1. v1/devices/**LDS25-NB**/telemetry
402 -
403 -ThingsBoard will create two devices named **S31B-NB** and **LDS25-NB** in the **//Devices//** section.
404 -
405 -
406 -The MQTT payload format is as follows, which is common for all ~-~-NB and ~-~-CB series devices:
407 -
408 -{{code language="none"}}
409 -{"temperature":10.4, "humidity":85}
410 -{{/code}}
411 -
412 -
413 -== 5.2 Sending messages ==
414 -
415 -
416 -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.
417 -
418 -{{code language="none"}}
419 -mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":10.4, "humidity":85}'
420 -{{/code}}
421 -
422 -If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
423 -
424 -
425 -[[image:integration-active.png]]
426 -
427 -
428 -Also, a new device named **S31B-NB** will appear under **//Entities -> Devices -> All//**. This means the first MQTT message triggers ThingsBoard to provision a device named **S31B-NB**.
429 -
430 -
431 -[[image:device-provision-1.png]]
432 -
433 -
434 -Click on the device S31B-NB on the devices list to see its details.
435 -
436 -Then go to the **Latest telemetry** tab.
437 -
438 -You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
439 -
440 -
441 -[[image:telemetry-1.png]]
442 -
443 -
444 -Now, change the values of the fields and send the MQTT message again. For example, set temperature to 20 and humidity to 70. Observe how the values update in //Latest Telemetry//.
445 -
446 -
447 -[[image:telemetry-2.png]]
448 -
449 -
450 -Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
451 -
452 -
453 -{{code language="none"}}
454 -mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/LDS25-NB/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":11, "humidity":87}'
455 -{{/code}}
456 -
457 -Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
458 -
459 -
460 -[[image:device-provision-2.png]]
461 -
462 -
463 -= 6. Creating a Dashboard =
464 -
465 -
466 -In ThingsBoard, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
467 -
468 -
469 -[[image:dashboard-1.png]]
470 -
471 -
472 -In the **Title** text box, enter **NB/CB Test Dashboard** as the title of the dashboard.
473 -
474 -Click on the **Add** button.
475 -
476 -
477 -[[image:dashboard-2.png||height="526" width="500"]]
478 -
479 -
480 -Click on the **Add widget / Add new widget** button.
481 -
482 -
483 -[[image:dashboard-3.png]]
484 -
485 -
486 -
487 -
488 488  
add-downlink-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -175.2 KB
Content
add-integration-connection-advanced-settings.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -155.2 KB
Content
add-uplink-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -174.1 KB
Content
check-connection.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content
connection-success.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -90.0 KB
Content
create-new-converter-menu.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -31.5 KB
Content
dashboard-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -271.1 KB
Content
dashboard-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -112.2 KB
Content
dashboard-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -141.3 KB
Content
dashboard-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -803.7 KB
Content
dashboard-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -476.1 KB
Content
data-converter-list-showing-uplink-dc.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -194.9 KB
Content
data-converters-list-empty.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -260.7 KB
Content
data-converters-list.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -212.2 KB
Content
device-provision-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -265.7 KB
Content
device-provision-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -213.9 KB
Content
hivemq-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -82.7 KB
Content
hivemq-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -300.7 KB
Content
hivemq-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -535.2 KB
Content
hivemq-4.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -309.8 KB
Content
hivemq-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -115.0 KB
Content
hivemq-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -321.0 KB
Content
hivemq-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -203.5 KB
Content
hivemq-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -268.7 KB
Content
hivemq-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -303.7 KB
Content
hivwmq-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -380.3 KB
Content
integration-active.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -64.2 KB
Content
integrations-list-empty.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -264.5 KB
Content
new-integration-pending.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -199.7 KB
Content
telemetry-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -191.9 KB
Content
telemetry-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -185.1 KB
Content
thingsboard-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -1.9 MB
Content
thingsboard-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -901.1 KB
Content
thingsboard-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -146.3 KB
Content
thingsboard-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -122.1 KB
Content
thingsboard-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -106.7 KB
Content
thingsboard-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -119.3 KB
Content
Data-converter-list-uplink-only.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
Data-converter-list.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-Data-Converters.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +100.3 KB
Content
ThingsBoard-Device.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +225.5 KB
Content
ThingsBoard-add-data-converter-downlink.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-data-converter-uplink.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-integration.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
ThingsBoard-add-new-device.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +89.7 KB
Content
ThingsBoard-new-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +100.3 KB
Content