Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 121.1
edited by Dilisi S
on 2025/03/08 20:30
Change comment: Mar 8 edits - part 2
To version 63.1
edited by Dilisi S
on 2025/03/06 13:29
Change comment: Mar 6 edits - part 2

Summary

Details

Page properties
Content
... ... @@ -6,224 +6,280 @@
6 6  Draft Document
7 7  {{/warning}}
8 8  
9 += Introduction =
9 9  
10 -
11 -
12 -= 1. Introduction =
13 -
14 -
15 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.
16 16  
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 =
16 += Add New Device =
21 21  
22 -To complete this tutorial, you need to have the following:
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.
23 23  
24 -* ThingsBoard cloud account
25 -* HiveMQ Cloud account
20 +In the left navigation, click **Entities** and then click **Devices**.
26 26  
27 27  
28 -== 2.1 ThingsBoard Cloud ==
23 +[[image:device-list-empty.png]]
29 29  
30 30  
31 -Add details here
26 +On the **Devices **page, click on the ‘**+**’ button, and then click on the **Add new device **from the dropdown menu.
32 32  
33 -== 2.2 HiveMQ Cloud ==
34 34  
29 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
35 35  
36 -Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
37 37  
38 -Click on the **Start Free** button.
32 +The **Add new device** window appears. Name the device, for example '**Virtual NB/CB device**'.
39 39  
40 -[[image:hivwmq-1.png]]
34 +Click on the **Next: Credentials** button.
41 41  
42 42  
43 -Click on the **Sign Up FREE Now** button in the **HIVEMQ CLOUD** section.
37 +[[image:new-device-device-details.png||height="529" width="500"]]
44 44  
45 -[[image:hivemq-2.png]]
46 46  
40 +Click the **Access token** button if it is not selected by default.
47 47  
48 -Click on the **Sign Up** button.
42 +Copy the **Access token** to a text editor, as you will need it in the section **'Sending data from an MQTT client'**.
49 49  
50 -You can sign up with HiveMQ using your **GitHub**, **Google**, or **LinkedIn** account.
44 +Click on the **Add** button.
51 51  
52 -If not, provide your **email address** and a **password** to create an account by clicking on the **Sign Up** button.
46 +[[image:new-device-access-token.png||height="528" width="500"]]
53 53  
54 54  
55 -[[image:hivemq-3.png]]
49 +Click on the **MQTT** button.
56 56  
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.
57 57  
58 -You will receive an email to verify your email address. Click on the **Confirm my account** button.
53 +Copy the MQTT pub command in the '**Execute the following command**' section.
59 59  
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}}
60 60  
61 -[[image:hivemq-4.jpg||height="889" width="400"]]
59 +Note that the **State** is still shown as **'Inactive'** in the **Latest telemetry** section.
62 62  
61 +[[image:new-device-check-connectivity.png||height="522" width="500"]]
63 63  
64 -You will be redirected to a page asking you to complete your profile. Once done, click the **Continue** button.
65 65  
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.
66 66  
67 -[[image:hivemq-5.png||height="655" width="700"]]
68 68  
67 +[[image:mqtt-command-1.png||height="228" width="700"]]
69 69  
70 -Select the CloudMQ Cloud plan you need. For testing purposes, select the **Serverless FREE** plan by clicking on the **Create Serverless Cluster** button.
71 71  
70 +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.
72 72  
73 -[[image:hivemq-6.png]]
74 74  
73 +[[image:new-device-telemetry-test.png||height="520" width="500"]]
75 75  
76 -You will be navigated to the **Your Clusters** page. Click on the **Manage Cluster** button.
77 77  
78 -[[image:hivemq-7.png]]
76 +Send the same command again, only changing the **temperature** value, to see how the **Latest telemetry** section updates its data.
79 79  
78 +Once you are done experimenting with this, close the window by clicking the **Close** button.
80 80  
81 -In your cluster page, you can find some useful parameters you need to create a MQTT connection.
82 82  
83 -**URL**: This is the host name. Click on the copy button to copy it.
81 +[[image:mqtt-command-2.png||height="227" width="700"]]
84 84  
85 -**Port**: 8883
86 86  
87 87  
88 -Click on the **Getting Started** tab to setup the username and the password as the connection credentials.
85 +[[image:virtual-device-active.png]]
89 89  
90 90  
91 -[[image:hivemq-8.png]]
88 += Data Converters =
92 92  
93 -
94 -In the '**Create Connection Credentials**' section, provide a **username** and **password**, then click the **Add** button.
95 -
96 -
97 -[[image:hivemq-9.png]]
98 -
99 -
100 -
101 -If everything is successful, you will see the following message.
102 -
103 -
104 -[[image:hivemq-10.png||height="206" width="500"]]
105 -
106 -
107 -You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
108 -
109 -
110 -= 3. Data Converters =
111 -
112 -
113 113  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.
114 114  
115 115  
116 -== 3.1 Uplink ==
93 +== Uplink ==
117 117  
118 -
119 119  In the left navigation, click **Integrations center**, and then click **Data converters**.
120 120  
121 121  
98 +[[image:data-converter-list-page.png]]
122 122  
123 -[[image:data-converters-list-empty.png]]
124 124  
101 +On the **Data converters** page, click on the ‘+’ button, and then click on the **Create new converter** from the dropdown menu.
125 125  
126 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
127 127  
104 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
128 128  
129 129  
130 -[[image:create-new-converter-menu.png||height="259" width="500"]]
131 -
132 -
133 133  The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**.
134 134  
135 -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.
109 +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.
136 136  
137 137  {{code language="JavaScript"}}
138 -/** Decoder **/
139 -
112 +//Version: 0.1
140 140  // decode payload to string
141 141  var payloadStr = decodeToString(payload);
142 -var data = JSON.parse(payloadStr);
143 143  
144 -var deviceName = metadata.topic.split("/")[3];
145 145  // decode payload to JSON
146 -var deviceType = 'sensor';
117 +var objdata = {};
118 +var obj1 = {};
119 +var data = decodeToJson(payload);
120 +var deviceName = data.IMEI;
121 +delete data.IMEI;
122 +var modelname = "Dragino " + data.Model;
123 +//var mod = data.mod
124 +delete data.Model;
125 +//delete data.mod
126 +var timestamp = new Date().getTime();
147 147  
148 -// Result object with device attributes/telemetry data
128 +for (var key in data) {
129 +
130 + if (Number(key)) {
131 + obj1[key] = data[key];
132 + obj1[key][obj1[key].length - 1] = Number(new Date(
133 + obj1[key][obj1[key].length - 1]));
134 +
135 + }
136 +//Alec submitted25/02/25
137 +//turn old key into new
138 + else if (key === "Reading") {
139 + objdata["reading"] = data[key];
140 + } else if (key === "work mode") {
141 + objdata["work_mode"] = data[key];
142 + } else if (key === "hum") {
143 + objdata["humidity"] = data[key];
144 + }else if (key === "hum2") {
145 + objdata["humidity2"] = data[key];
146 + } else if (key === "hum3") {
147 + objdata["humidity3"] = data[key];
148 + } else if (key === "tem") {
149 + objdata["temperature"] = data[key];
150 + } else if (key === "tem2") {
151 + objdata["temperature2"] = data[key];
152 + } else if (key === "tem3") {
153 + objdata["temperature3"] = data[key];
154 + } else if (key === "DS18B20_Temp") {
155 + objdata["temperature_pro"] = data[key];
156 + } else if (key === "ds18b20_temperature") {
157 + objdata["temperature_pro"] = data[key];
158 + } else if (key === "DS18B20_temperature_pro") {
159 + objdata["temperature_pro"] = data[key];
160 + } else if (key === "tdc send flag") {
161 + objdata["tdc_send_flag"] = data[key];
162 + } else if (key === "trigger mode") {
163 + objdata["trigger_mode"] = data[key];
164 + } else if (key === "soil dielectric constant") {
165 + objdata["soil_dielectric_constant"] = data[key];
166 + } else if (key === "door open num") {
167 + objdata["door_open_num"] = data[key];
168 + } else if (key === "door duration") {
169 + objdata["door_duration"] = data[key];
170 + } else if (key === "count time") {
171 + objdata["count_time"] = data[key];
172 + } else if (key === "last open time2") {
173 + objdata["last_open_time2"] = data[key];
174 + } else if (key === "last open time3") {
175 + objdata["last_open_time3"] = data[key];
176 + }
177 +//Alec submitted25/02/25
178 + else {
179 + objdata[key] = data[key]
180 + }
181 +}
182 +var listdata = [{
183 + "ts": timestamp,
184 + "values": objdata
185 +}]
186 +for (var key1 in obj1) {
187 + if (modelname == "Dragino RS485-NB") {
188 + listdata.push({
189 + "ts": obj1[key1][obj1[key1].length - 1],
190 + "values": {
191 + "Payload": obj1[key1][0],
192 + }
193 + })
194 + } else {
195 + listdata.push({
196 + "ts": obj1[key1][obj1[key1].length - 1],
197 + "values": {
198 + "values": obj1[key1]
199 + },
200 + })
201 + }
202 +}
149 149  var result = {
204 +
150 150   deviceName: deviceName,
151 - deviceType: deviceType,
206 + deviceType: modelname,
152 152   attributes: {
153 - integrationName: metadata['integrationName'],
208 + model: modelname,
209 + //customerName: "NB-CB",
210 + //groupName: "NB-CB",
211 + //integrationName: metadata['integrationName']
212 +
154 154   },
155 - telemetry: {
156 - temperature: data.temperature,
157 - humidity: data.humidity,
158 - }
159 -};
214 + telemetry: listdata
215 +}
160 160  
161 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
217 +function decodeToString(payload) {
218 + return String.fromCharCode.apply(String, payload);
219 +}
162 162  
221 +function decodeToJson(payload) {
222 + // covert payload to string.
223 + var str = decodeToString(payload);
224 +
225 + // parse string to JSON
226 + var data = JSON.parse(str);
227 + return data;
228 +}
229 +
163 163  return result;
231 +
164 164  {{/code}}
165 165  
166 -
167 167  Click on the **Add** button.
168 168  
169 169  
237 +[[image:uplink-data-converter.png||height="529" width="500"]]
170 170  
171 -[[image:add-uplink-data-converter.png||height="529" width="500"]]
172 172  
173 173  
174 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
241 +You should see that the newly added **uplink data converter** is listed on the **Data Converters** page.
175 175  
243 +
176 176  [[image:data-converter-list-showing-uplink-dc.png]]
177 177  
178 178  
247 +== Downlink ==
179 179  
180 -== 3.2 Downlink ==
181 -
182 -
183 183  On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
184 184  
185 185  
186 -[[image:create-new-converter-menu.png||width="500"]]
252 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
187 187  
188 188  
189 -
190 190  The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
191 191  
192 -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.
193 193  
194 194  
195 195  {{code language="JavaScript"}}
196 -// 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 +}
197 197  
198 -// msg - JSON message payload downlink message json
199 -// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
200 -// metadata - list of key-value pairs with additional data about the message
201 -// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
202 -
203 -/** Encoder **/
204 -
205 -var data = {};
206 -
207 -// Process data from incoming message and metadata
208 -
209 -data.tempFreq = msg.temperatureUploadFrequency;
210 -data.humFreq = msg.humidityUploadFrequency;
211 -
212 -data.devSerialNumber = metadata['ss_serialNumber'];
213 -
214 214  // Result object with encoded downlink payload
215 215  var result = {
216 -
217 217   // downlink data content type: JSON, TEXT or BINARY (base64 format)
218 - contentType: "JSON",
276 + contentType: "BINARY",
219 219  
220 220   // downlink data
221 - data: JSON.stringify(data),
279 + data:hexToBase64(metadata.shared_value)
222 222  
223 223   // Optional metadata object presented in key/value format
224 - metadata: {
225 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
226 - }
282 + //metadata: {}
227 227  
228 228  };
229 229  
... ... @@ -234,29 +234,26 @@
234 234  Click on the **Add** button.
235 235  
236 236  
293 +[[image:downlink-data-converter.png||height="530" width="500"]]
237 237  
238 -[[image:add-downlink-data-converter.png||height="529" width="500"]]
239 239  
240 240  
241 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
297 +You should see that the newly added **downlink data converter** is listed on the **Data Converters** page.
242 242  
243 243  
244 -[[image:data-converters-list.png]]
300 +[[image:data-converter-list.png]]
245 245  
246 246  
303 += Add Integration =
247 247  
248 -= 4. Add Integration =
249 -
250 -
251 251  In the left navigation, click **Integrations center**, and then click **Integrations**.
252 252  
307 +On the **Integrations** page, click on the '**+**' button.
253 253  
254 -[[image:integrations-list-empty.png]]
255 255  
310 +[[image:data-converter-list-page.png]]
256 256  
257 -On the **Integrations** page, click on the '**+**' button.
258 258  
259 -
260 260  The **Add integration** window appears.
261 261  
262 262  In the **Add integration** window, configure the following settings:
... ... @@ -266,16 +266,14 @@
266 266  
267 267  * **Integration type**: MQTT
268 268  * **Name**: MQTT integration NB/CB
269 -* **Enable integration**: YES
270 -* **Allows create devices or assets**: YES
271 271  
272 272  Click **Next** button.
273 273  
274 274  
275 -
276 276  [[image:add-integration-basic-settings.png||height="511" width="500"]]
277 277  
278 278  
329 +
279 279  **Uplink data converter:**
280 280  
281 281  * Click on the **Select existing** button.
... ... @@ -284,8 +284,8 @@
284 284  Click **Next** button.
285 285  
286 286  
338 +[[image:add-integration-uplink-data-converter.png||width="500"]]
287 287  
288 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
289 289  
290 290  
291 291  **Downlink data converter:**
... ... @@ -296,45 +296,33 @@
296 296  Click **Next** button.
297 297  
298 298  
350 +[[image:add-integration-downlink-data-converter.png||height="510" width="500"]]
299 299  
300 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
301 301  
302 302  
303 303  **Connection:**
304 304  
305 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
306 -* **Port**: 8883
356 +* **Host**: mqtt.eu.thingsboard.cloud (This is the host name you copied from the device - See section xxxxx for more information)
357 +* **Port**: 1883 (This is the port number you copied from the device - See section xxxxx for more information)
307 307  * **Credentials**: Basic
308 -* **Enable SSL**: YES
309 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
310 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
311 -* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices)
312 -* **QoS:** 0-At most once
359 +* **Username**: Access token (This is the access token you copied from the device)
360 +* **Password** - Leave it as blank
361 +* **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')
362 +* **QoS** - 0-At most once
313 313  
314 -[[image:add-integration-connection.png||height="511" width="500"]]
315 -
316 -
317 -Click on the **Advanced settings** button.
318 -
319 -* **Clean session:** NO
320 -* **Retained**: NO
321 -
322 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
323 -
324 -
325 325  Click on the **Check connection** button to verify the MQTT connection using the provided parameters.
326 326  
327 327  
328 -[[image:check-connection.png||height="83" width="300"]]
367 +[[image:add-integration-connection.png||width="500"]]
329 329  
330 330  
331 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
370 +If the connection is successful, you will see the **Connected** message.
332 332  
372 +Click on the **Add** button.
333 333  
334 -[[image:connection-success.png||height="511" width="500"]]
335 335  
375 +[[image:add-connection-success.png||height="511" width="500"]]
336 336  
337 -Click on the **Add** button.
338 338  
339 339  You should see that the newly added integration is listed on the **Integrations** page.
340 340  
... ... @@ -342,16 +342,9 @@
342 342  
343 343  
344 344  
345 -[[image:new-integration-pending.png]]
384 +[[image:integrations-list-added-pending.png]]
346 346  
347 347  
348 -= 5. Verifying the receipt of data from the device =
387 += Verifying the receipt of data from the device =
349 349  
350 -
351 -On the terminal, issue the following MQTT command which simulates the device S31B-NB.
352 -
353 -{{code language="none"}}
354 -mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}"
355 -{{/code}}
356 -
357 -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.
389 +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.
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
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
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
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-add-data-converter.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
add-connection-success.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
data-converter-list-page.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +190.8 KB
Content
data-converter-list.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
device-list-empty.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
downlink-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +207.8 KB
Content
integrations-list-added-pending.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
mqtt-command-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
mqtt-command-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
new-device-access-token.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
new-device-check-connectivity.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
new-device-device-details.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +88.4 KB
Content
new-device-telemetry-test.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content
uplink-data-converter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
virtual-device-active.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +202.8 KB
Content