Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 132.1
edited by Dilisi S
on 2025/03/09 03:05
Change comment: Uploaded new attachment "device-provision-1.png", version {1}
To version 92.1
edited by Dilisi S
on 2025/03/08 03:57
Change comment: Uploaded new attachment "data-converters-list.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -17,130 +17,76 @@
17 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  
19 19  
20 -= 2. Prerequisites =
20 += 2. Add New Device =
21 21  
22 -To complete this tutorial, you need to have the following:
23 23  
24 -* ThingsBoard cloud account
25 -* HiveMQ Cloud account
23 +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.
26 26  
27 -== 2.1 ThingsBoard Cloud ==
25 +In the left navigation, click **Entities** and then click **Devices**.
28 28  
27 +[[image:device-list-empty.png]]
29 29  
30 -Go to [[https:~~/~~/thingsboard.io/>>https://thingsboard.io/]]
31 31  
32 -Click on the **Try it now**.
30 +On the **Devices **page, click on the ‘**+**’ button, and then click on the **Add new device **from the dropdown menu.
33 33  
32 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
34 34  
35 -[[image:thingsboard-1.png]]
36 36  
35 +The **Add new device** window appears. Name the device, for example '**Virtual NB/CB device**'.
37 37  
38 -Select either the **North America** or **Europe** region. Here, we use the Europe region.
37 +Click on the **Next: Credentials** button.
39 39  
40 -[[image:thingsboard-2.png]]
39 +[[image:new-device-device-details.png||height="529" width="500"]]
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 +Click the **Access token** button if it is not selected by default.
44 44  
45 -Click on the **Sign up** button.
44 +Copy the **Access token** to a text editor, as you will need it in the section **'Sending data from an MQTT client'**.
46 46  
47 -[[image:thingsboard-3.png||height="651" width="500"]]
46 +Click on the **Add** button.
48 48  
48 +[[image:new-device-access-token.png||height="528" width="500"]]
49 49  
50 -You will be navigated to the following page.
51 51  
52 -[[image:thingsboard-5.png||height="109" width="500"]]
51 +Click on the **MQTT** button.
53 53  
53 +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.
54 54  
55 -simultaneously, you will receive an email to confirm your email address. Click on the **Activate Your Account** button.
55 +Copy the MQTT pub command in the '**Execute the following command**' section.
56 56  
57 +{{code language="none"}}
58 +mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/me/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:25}"
59 +{{/code}}
57 57  
58 -[[image:thingsboard-4.png||height="249" width="500"]]
61 +Note that the **State** is still shown as **'Inactive'** in the **Latest telemetry** section.
59 59  
63 +[[image:new-device-check-connectivity.png||height="522" width="500"]]
60 60  
61 -Now losing to the account using your credentials:
62 62  
66 +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.
63 63  
64 -[[image:thingsboard-6.png||height="244" width="500"]]
65 65  
69 +[[image:mqtt-command-1.png||height="228" width="700"]]
66 66  
67 -== 2.2 HiveMQ Cloud ==
68 68  
72 +If the command is successful, you can see the telemetry data you sent under the **Latest telemetry** section. Note that the **State** is now **'Active'** in the **Latest telemetry** section.
69 69  
70 -Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
71 71  
72 -Click on the **Start Free** button.
75 +[[image:new-device-telemetry-test.png||height="520" width="500"]]
73 73  
74 -[[image:hivwmq-1.png]]
75 75  
78 +Send the same command again, only changing the **temperature** value, to see how the **Latest telemetry** section updates its data.
76 76  
77 -Click on the **Sign Up FREE Now** button in the **HIVEMQ CLOUD** section.
80 +Once you are done experimenting with this, close the window by clicking the **Close** button.
78 78  
79 -[[image:hivemq-2.png]]
80 80  
83 +[[image:mqtt-command-2.png||height="227" width="700"]]
81 81  
82 -Click on the **Sign Up** button.
83 83  
84 -You can sign up with HiveMQ using your **GitHub**, **Google**, or **LinkedIn** account.
85 85  
86 -If not, provide your **email address** and a **password** to create an account by clicking on the **Sign Up** button.
87 +[[image:virtual-device-active.png]]
87 87  
88 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 144  = 3. Data Converters =
145 145  
146 146  
... ... @@ -152,112 +152,188 @@
152 152  
153 153  In the left navigation, click **Integrations center**, and then click **Data converters**.
154 154  
101 +[[image:data-converter-list-page.png]]
155 155  
156 156  
157 -[[image:data-converters-list-empty.png]]
104 +On the **Data converters** page, click on the ‘+’ button, and then click on the **Create new converter** from the dropdown menu.
158 158  
106 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
159 159  
160 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
161 161  
162 -
163 -
164 -[[image:create-new-converter-menu.png||height="259" width="500"]]
165 -
166 -
167 167  The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
168 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.
111 +Click on the **JavaScript** button. Now copy and paste the following JavaScript to the **Decoder function** section. This decoder function is valid for both NB and CB series devices.
170 170  
171 171  {{code language="JavaScript"}}
172 -/** Decoder **/
173 -
114 +//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';
119 +var objdata = {};
120 +var obj1 = {};
121 +var data = decodeToJson(payload);
122 +var deviceName = data.IMEI;
123 +delete data.IMEI;
124 +var modelname = "Dragino " + data.Model;
125 +//var mod = data.mod
126 +delete data.Model;
127 +//delete data.mod
128 +var timestamp = new Date().getTime();
181 181  
182 -// Result object with device attributes/telemetry data
130 +for (var key in data) {
131 +
132 + if (Number(key)) {
133 + obj1[key] = data[key];
134 + obj1[key][obj1[key].length - 1] = Number(new Date(
135 + obj1[key][obj1[key].length - 1]));
136 +
137 + }
138 +//Alec submitted25/02/25
139 +//turn old key into new
140 + else if (key === "Reading") {
141 + objdata["reading"] = data[key];
142 + } else if (key === "work mode") {
143 + objdata["work_mode"] = data[key];
144 + } else if (key === "hum") {
145 + objdata["humidity"] = data[key];
146 + }else if (key === "hum2") {
147 + objdata["humidity2"] = data[key];
148 + } else if (key === "hum3") {
149 + objdata["humidity3"] = data[key];
150 + } else if (key === "tem") {
151 + objdata["temperature"] = data[key];
152 + } else if (key === "tem2") {
153 + objdata["temperature2"] = data[key];
154 + } else if (key === "tem3") {
155 + objdata["temperature3"] = data[key];
156 + } else if (key === "DS18B20_Temp") {
157 + objdata["temperature_pro"] = data[key];
158 + } else if (key === "ds18b20_temperature") {
159 + objdata["temperature_pro"] = data[key];
160 + } else if (key === "DS18B20_temperature_pro") {
161 + objdata["temperature_pro"] = data[key];
162 + } else if (key === "tdc send flag") {
163 + objdata["tdc_send_flag"] = data[key];
164 + } else if (key === "trigger mode") {
165 + objdata["trigger_mode"] = data[key];
166 + } else if (key === "soil dielectric constant") {
167 + objdata["soil_dielectric_constant"] = data[key];
168 + } else if (key === "door open num") {
169 + objdata["door_open_num"] = data[key];
170 + } else if (key === "door duration") {
171 + objdata["door_duration"] = data[key];
172 + } else if (key === "count time") {
173 + objdata["count_time"] = data[key];
174 + } else if (key === "last open time2") {
175 + objdata["last_open_time2"] = data[key];
176 + } else if (key === "last open time3") {
177 + objdata["last_open_time3"] = data[key];
178 + }
179 +//Alec submitted25/02/25
180 + else {
181 + objdata[key] = data[key]
182 + }
183 +}
184 +var listdata = [{
185 + "ts": timestamp,
186 + "values": objdata
187 +}]
188 +for (var key1 in obj1) {
189 + if (modelname == "Dragino RS485-NB") {
190 + listdata.push({
191 + "ts": obj1[key1][obj1[key1].length - 1],
192 + "values": {
193 + "Payload": obj1[key1][0],
194 + }
195 + })
196 + } else {
197 + listdata.push({
198 + "ts": obj1[key1][obj1[key1].length - 1],
199 + "values": {
200 + "values": obj1[key1]
201 + },
202 + })
203 + }
204 +}
183 183  var result = {
206 +
184 184   deviceName: deviceName,
185 - deviceType: deviceType,
208 + deviceType: modelname,
186 186   attributes: {
187 - integrationName: metadata['integrationName'],
210 + model: modelname,
211 + //customerName: "NB-CB",
212 + //groupName: "NB-CB",
213 + //integrationName: metadata['integrationName']
214 +
188 188   },
189 - telemetry: {
190 - temperature: data.temperature,
191 - humidity: data.humidity,
192 - }
193 -};
216 + telemetry: listdata
217 +}
194 194  
195 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
219 +function decodeToString(payload) {
220 + return String.fromCharCode.apply(String, payload);
221 +}
196 196  
223 +function decodeToJson(payload) {
224 + // covert payload to string.
225 + var str = decodeToString(payload);
226 +
227 + // parse string to JSON
228 + var data = JSON.parse(str);
229 + return data;
230 +}
231 +
197 197  return result;
233 +
198 198  {{/code}}
199 199  
200 200  
201 201  Click on the **Add** button.
202 202  
239 +[[image:uplink-data-converter.png||height="529" width="500"]]
203 203  
204 204  
205 -[[image:add-uplink-data-converter.png||height="529" width="500"]]
242 +You should see that the newly added **uplink data converter** is listed on the **Data Converters** page.
206 206  
207 -
208 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
209 -
210 210  [[image:data-converter-list-showing-uplink-dc.png]]
211 211  
212 212  
213 -
214 214  == 3.2 Downlink ==
215 215  
216 216  
217 217  On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
218 218  
252 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
219 219  
220 -[[image:create-new-converter-menu.png||width="500"]]
221 221  
222 -
223 -
224 224  The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
225 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.
257 +Click on the **JavaScript** button. Now copy and paste the following JavaScript to the **Encoder function **section. This encoder function is valid for both NB and CB series devices.
227 227  
228 228  
229 229  {{code language="JavaScript"}}
230 -// Encode downlink data from incoming Rule Engine message
261 +function hexToBase64(hexString) {
262 + // 将16进制字符串两个字符转换为一个字节
263 + var bytes = hexString.match(/.{2}/g);
264 + // 对每个字节进行解析，并转换为对应的字符
265 + var binaryString = bytes.map(function(byte) {
266 + return String.fromCharCode(parseInt(byte, 16));
267 + }).join('');
268 +
269 + // 使用btoa进行base64编码
270 + return btoa(binaryString);
271 +}
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",
276 + contentType: "BINARY",
253 253  
254 254   // downlink data
255 - data: JSON.stringify(data),
279 + 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 - }
282 + //metadata: {}
261 261  
262 262  };
263 263  
... ... @@ -267,30 +267,24 @@
267 267  
268 268  Click on the **Add** button.
269 269  
292 +[[image:downlink-data-converter.png||height="530" width="500"]]
270 270  
271 271  
272 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
295 +You should see that the newly added **downlink data converter** is listed on the **Data Converters** page.
273 273  
297 +[[image:data-converter-list.png]]
274 274  
275 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
276 276  
277 -
278 -[[image:data-converters-list.png]]
279 -
280 -
281 -
282 282  = 4. Add Integration =
283 283  
284 284  
285 285  In the left navigation, click **Integrations center**, and then click **Integrations**.
286 286  
287 -
288 -[[image:integrations-list-empty.png]]
289 -
290 -
291 291  On the **Integrations** page, click on the '**+**' button.
292 292  
307 +[[image:data-converter-list-page.png]]
293 293  
309 +
294 294  The **Add integration** window appears.
295 295  
296 296  In the **Add integration** window, configure the following settings:
... ... @@ -300,13 +300,9 @@
300 300  
301 301  * **Integration type**: MQTT
302 302  * **Name**: MQTT integration NB/CB
303 -* **Enable integration**: YES
304 -* **Allows create devices or assets**: YES
305 305  
306 306  Click **Next** button.
307 307  
308 -
309 -
310 310  [[image:add-integration-basic-settings.png||height="511" width="500"]]
311 311  
312 312  
... ... @@ -317,11 +317,9 @@
317 317  
318 318  Click **Next** button.
319 319  
332 +[[image:add-integration-uplink-data-converter.png||width="500"]]
320 320  
321 321  
322 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
323 -
324 -
325 325  **Downlink data converter:**
326 326  
327 327  * Click on the **Select existing** button.
... ... @@ -329,93 +329,47 @@
329 329  
330 330  Click **Next** button.
331 331  
342 +[[image:add-integration-downlink-data-converter.png||height="510" width="500"]]
332 332  
333 333  
334 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
335 -
336 -
337 337  **Connection:**
338 338  
339 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
340 -* **Port**: 8883
347 +* **Host**: mqtt.eu.thingsboard.cloud (This is the host name you copied from the device - See section xxxxx for more information)
348 +* **Port**: 1883 (This is the port number you copied from the device - See section xxxxx for more information)
341 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
350 +* **Username**: Access token (This is the access token you copied from the device)
351 +* **Password** - Leave it as blank
352 +* **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')
353 +* **QoS** - 0-At most once
347 347  
348 -[[image:add-integration-connection.png||height="511" width="500"]]
349 -
350 -
351 -Click on the **Advanced settings** button.
352 -
353 -* **Clean session:** NO
354 -* **Retained**: NO
355 -
356 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
357 -
358 -
359 359  Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
360 360  
357 +[[image:add-integration-connection.png||width="500"]]
361 361  
362 -[[image:check-connection.png||height="83" width="300"]]
363 363  
360 +If the connection is successful, you will see the **Connected** message.
364 364  
365 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
362 +Click on the **Add** button.
366 366  
364 +[[image:add-connection-success.png||height="511" width="500"]]
367 367  
368 -[[image:connection-success.png||height="511" width="500"]]
369 369  
370 -
371 -Click on the **Add** button.
372 -
373 373  You should see that the newly added integration is listed on the **Integrations** page.
374 374  
375 375  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
376 376  
371 +[[image:integrations-list-added-pending.png]]
377 377  
378 378  
379 -[[image:new-integration-pending.png]]
374 += 5. Verifying the receipt of data from the device =
380 380  
381 381  
382 -= 5. Verifying the receipt of data from virtual devices =
377 +On the terminal, issue the following MQTT command which simulates the device S31B-NB.
383 383  
384 -
385 -== 5.1 How does it work? ==
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 -
407 407  {{code language="none"}}
408 -{"temperature":10.4, "humidity":85}
380 +mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
409 409  {{/code}}
410 410  
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 -
421 421  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.
384 +
385 +
add-integration-basic-settings.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -122.5 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-integration-connection.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -124.4 KB
Content
add-integration-downlink-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -123.0 KB
Content
add-integration-uplink-data-converter.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -120.7 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
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
device-provision-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -268.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
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