Changes for page ThingsBoard
Last modified by Dilisi S on 2025/04/23 19:23
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 16 added, 18 removed)
- add-downlink-data-converter.png
- add-integration-connection-advanced-settings.png
- add-uplink-data-converter.png
- check-connection.png
- connection-success.png
- create-new-converter-menu.png
- data-converters-list-empty.png
- data-converters-list.png
- hivemq-2.png
- hivemq-3.png
- hivemq-4.jpg
- hivemq-5.png
- hivemq-6.png
- hivemq-7.png
- hivemq-8.png
- hivwmq-1.png
- integrations-list-empty.png
- new-integration-pending.png
- ThingsBoard-add-data-converter.png
- ThingsBoard-add-new-device.png
- ThingsBoard-new-data-converter.png
- add-connection-success.png
- data-converter-list-page.png
- data-converter-list.png
- device-list-empty.png
- downlink-data-converter.png
- integrations-list-added-pending.png
- mqtt-command-1.png
- mqtt-command-2.png
- new-device-access-token.png
- new-device-check-connectivity.png
- new-device-device-details.png
- new-device-telemetry-test.png
- uplink-data-converter.png
Details
- Page properties
-
- Content
-
... ... @@ -6,204 +6,276 @@ 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 - Tocomplete this tutorial,youneedtohave 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 HiveMQ Cloud ==23 +[[image:device-list-empty.png]] 29 29 30 30 31 - Goto [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]26 +On the **Devices **page, click on the ‘**+**’ button, and then click on the **Add new device **from the dropdown menu. 32 32 33 -Click on the **Start Free** button. 34 34 35 -[[image:hi vwmq-1.png]]29 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]] 36 36 37 37 38 - Clickonthe **SignUpFREENow**buttoninthe **HIVEMQCLOUD**section.32 +The **Add new device** window appears. Name the device, for example '**Virtual NB/CB device**'. 39 39 40 - [[image:hivemq-2.png]]34 +Click on the **Next: Credentials** button. 41 41 42 42 43 - Click on**SignUp** button.37 +[[image:new-device-device-details.png||height="529" width="500"]] 44 44 45 -You can sign up with HiveMQ using your **GitHub**, **Google**, or **LinkedIn** account. 46 46 47 - Ifnot, provideyour**email address**and a**password**to create an accountbyclickingon the**Sign Up**button.40 +Click the **Access token** button if it is not selected by default. 48 48 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 - [[image:hivemq-3.png]]44 +Click on the **Add** button. 51 51 46 +[[image:new-device-access-token.png||height="528" width="500"]] 52 52 53 -You will receive an email to verify your email address. Click on the **Confirm my account** button. 54 54 49 +Click on the **MQTT** button. 55 55 56 - [[image:hivemq-4.jpg||height="889"width="400"]]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 53 +Copy the MQTT pub command in the '**Execute the following command**' section. 58 58 59 -You will be redirected to a page asking you to complete your profile. Once done, click the **Continue** button. 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 59 +Note that the **State** is still shown as **'Inactive'** in the **Latest telemetry** section. 61 61 62 -[[image: hivemq-5.png||height="655" width="700"]]61 +[[image:new-device-check-connectivity.png||height="522" width="500"]] 63 63 64 64 65 - Select theCloudMQ Cloud plan youneed.Fortestingpurposes,select the**ServerlessFREE**planbyclickingontheCreateServerlessCluster**button.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 67 68 -[[image: hivemq-6.png]]67 +[[image:mqtt-command-1.png||height="228" width="700"]] 69 69 70 70 71 - Youwill benavigatedto the**YourClusters**page.Clickon theManageCluster**button.70 +If the command is successful, you can see the telemetry data you sent under the **Latest telemetry** section. 72 72 73 -[[image:hivemq-7.png]] 74 74 73 +[[image:new-device-telemetry-test.png||height="520" width="500"]] 75 75 76 -In your cluster page, you can find some useful parameters you need to create a MQTT connection. 77 77 78 - **URL**:This isthehost name.Clickon thecopy buttonto copyit.76 +Send the same command again, only changing the **temperature** value, to see how the **Latest telemetry** section updates its data. 79 79 80 - **Port**: 888378 +Once you are done experimenting with this, close the window by clicking the **Close** button. 81 81 82 82 83 - Click on the **Getting Started**tabtosetup the usernameandthepassword.81 +[[image:mqtt-command-2.png||height="227" width="700"]] 84 84 85 85 86 - [[image:hivemq-8.png]]84 += Data Converters = 87 87 88 - 89 - 90 -= 2. Data Converters = 91 - 92 - 93 93 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. 94 94 95 95 96 -== 2.1Uplink ==89 +== Uplink == 97 97 98 - 99 99 In the left navigation, click **Integrations center**, and then click **Data converters**. 100 100 101 101 94 +[[image:data-converter-list-page.png]] 102 102 103 -[[image:data-converters-list-empty.png]] 104 104 97 +On the **Data converters** page, click on the ‘+’ button, and then click on the **Create new converter** from the dropdown menu. 105 105 106 -On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu. 107 107 100 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]] 108 108 109 109 110 -[[image:create-new-converter-menu.png||height="259" width="500"]] 111 - 112 - 113 113 The **Add data converter** window will appear. Name it ‘**MQTT Uplink Converter NB/CB**’ and select the Type as **Uplink**. 114 114 115 -Click on the ** TBEL** button if not selectedit by default. Delete the existing decoder function in the code editor. Now copy and paste the followingdecoderfunctionwrittenin**TBEL (ThingsBoardExpressionLanguage)** inthe**codeeditor**. This decoder function iscompatiblefor both NB and CB series devices.105 +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. 116 116 117 117 {{code language="JavaScript"}} 118 -/** Decoder **/ 119 - 108 +//Version: 0.1 120 120 // decode payload to string 121 121 var payloadStr = decodeToString(payload); 122 -var data = JSON.parse(payloadStr); 123 123 124 -var deviceName = metadata.topic.split("/")[3]; 125 125 // decode payload to JSON 126 -var deviceType = 'sensor'; 113 +var objdata = {}; 114 +var obj1 = {}; 115 +var data = decodeToJson(payload); 116 +var deviceName = data.IMEI; 117 +delete data.IMEI; 118 +var modelname = "Dragino " + data.Model; 119 +//var mod = data.mod 120 +delete data.Model; 121 +//delete data.mod 122 +var timestamp = new Date().getTime(); 127 127 128 -// Result object with device attributes/telemetry data 124 +for (var key in data) { 125 + 126 + if (Number(key)) { 127 + obj1[key] = data[key]; 128 + obj1[key][obj1[key].length - 1] = Number(new Date( 129 + obj1[key][obj1[key].length - 1])); 130 + 131 + } 132 +//Alec submitted25/02/25 133 +//turn old key into new 134 + else if (key === "Reading") { 135 + objdata["reading"] = data[key]; 136 + } else if (key === "work mode") { 137 + objdata["work_mode"] = data[key]; 138 + } else if (key === "hum") { 139 + objdata["humidity"] = data[key]; 140 + }else if (key === "hum2") { 141 + objdata["humidity2"] = data[key]; 142 + } else if (key === "hum3") { 143 + objdata["humidity3"] = data[key]; 144 + } else if (key === "tem") { 145 + objdata["temperature"] = data[key]; 146 + } else if (key === "tem2") { 147 + objdata["temperature2"] = data[key]; 148 + } else if (key === "tem3") { 149 + objdata["temperature3"] = data[key]; 150 + } else if (key === "DS18B20_Temp") { 151 + objdata["temperature_pro"] = data[key]; 152 + } else if (key === "ds18b20_temperature") { 153 + objdata["temperature_pro"] = data[key]; 154 + } else if (key === "DS18B20_temperature_pro") { 155 + objdata["temperature_pro"] = data[key]; 156 + } else if (key === "tdc send flag") { 157 + objdata["tdc_send_flag"] = data[key]; 158 + } else if (key === "trigger mode") { 159 + objdata["trigger_mode"] = data[key]; 160 + } else if (key === "soil dielectric constant") { 161 + objdata["soil_dielectric_constant"] = data[key]; 162 + } else if (key === "door open num") { 163 + objdata["door_open_num"] = data[key]; 164 + } else if (key === "door duration") { 165 + objdata["door_duration"] = data[key]; 166 + } else if (key === "count time") { 167 + objdata["count_time"] = data[key]; 168 + } else if (key === "last open time2") { 169 + objdata["last_open_time2"] = data[key]; 170 + } else if (key === "last open time3") { 171 + objdata["last_open_time3"] = data[key]; 172 + } 173 +//Alec submitted25/02/25 174 + else { 175 + objdata[key] = data[key] 176 + } 177 +} 178 +var listdata = [{ 179 + "ts": timestamp, 180 + "values": objdata 181 +}] 182 +for (var key1 in obj1) { 183 + if (modelname == "Dragino RS485-NB") { 184 + listdata.push({ 185 + "ts": obj1[key1][obj1[key1].length - 1], 186 + "values": { 187 + "Payload": obj1[key1][0], 188 + } 189 + }) 190 + } else { 191 + listdata.push({ 192 + "ts": obj1[key1][obj1[key1].length - 1], 193 + "values": { 194 + "values": obj1[key1] 195 + }, 196 + }) 197 + } 198 +} 129 129 var result = { 200 + 130 130 deviceName: deviceName, 131 - deviceType: de viceType,202 + deviceType: modelname, 132 132 attributes: { 133 - integrationName: metadata['integrationName'], 204 + model: modelname, 205 + //customerName: "NB-CB", 206 + //groupName: "NB-CB", 207 + //integrationName: metadata['integrationName'] 208 + 134 134 }, 135 - telemetry: { 136 - temperature: data.temperature, 137 - humidity: data.humidity, 138 - } 139 -}; 210 + telemetry: listdata 211 +} 140 140 141 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/ 213 +function decodeToString(payload) { 214 + return String.fromCharCode.apply(String, payload); 215 +} 142 142 217 +function decodeToJson(payload) { 218 + // covert payload to string. 219 + var str = decodeToString(payload); 220 + 221 + // parse string to JSON 222 + var data = JSON.parse(str); 223 + return data; 224 +} 225 + 143 143 return result; 227 + 144 144 {{/code}} 145 145 146 - 147 147 Click on the **Add** button. 148 148 149 149 233 +[[image:uplink-data-converter.png||height="529" width="500"]] 150 150 151 -[[image:add-uplink-data-converter.png||height="529" width="500"]] 152 152 153 153 154 -You should see that the newly added ** MQTT Uplink converterNB/CBis listed on the **Data Converters** page.237 +You should see that the newly added **uplink data converter** is listed on the **Data Converters** page. 155 155 239 + 156 156 [[image:data-converter-list-showing-uplink-dc.png]] 157 157 158 158 243 +== Downlink == 159 159 160 -== 3.2 Downlink == 161 - 162 - 163 163 On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu. 164 164 165 165 166 -[[image: create-new-converter-menu.png||width="500"]]248 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]] 167 167 168 168 169 - 170 170 The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**. 171 171 172 -Click on the ** TBEL** buttonif not selected it by default. Now copy and paste the followingencoderfunctionwrittenin**TBEL (ThingsBoardExpressionLanguage)** inthe**codeeditor**.compatiblefor both NB and CB series devices.253 +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. 173 173 174 174 175 175 {{code language="JavaScript"}} 176 -// Encode downlink data from incoming Rule Engine message 257 +function hexToBase64(hexString) { 258 + // 将16进制字符串两个字符转换为一个字节 259 + var bytes = hexString.match(/.{2}/g); 260 + // 对每个字节进行解析,并转换为对应的字符 261 + var binaryString = bytes.map(function(byte) { 262 + return String.fromCharCode(parseInt(byte, 16)); 263 + }).join(''); 264 + 265 + // 使用btoa进行base64编码 266 + return btoa(binaryString); 267 +} 177 177 178 -// msg - JSON message payload downlink message json 179 -// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc. 180 -// metadata - list of key-value pairs with additional data about the message 181 -// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter 182 - 183 -/** Encoder **/ 184 - 185 -var data = {}; 186 - 187 -// Process data from incoming message and metadata 188 - 189 -data.tempFreq = msg.temperatureUploadFrequency; 190 -data.humFreq = msg.humidityUploadFrequency; 191 - 192 -data.devSerialNumber = metadata['ss_serialNumber']; 193 - 194 194 // Result object with encoded downlink payload 195 195 var result = { 196 - 197 197 // downlink data content type: JSON, TEXT or BINARY (base64 format) 198 - contentType: " JSON",272 + contentType: "BINARY", 199 199 200 200 // downlink data 201 - data: JSON.stringify(data),275 + data:hexToBase64(metadata.shared_value) 202 202 203 203 // Optional metadata object presented in key/value format 204 - metadata: { 205 - topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload' 206 - } 278 + //metadata: {} 207 207 208 208 }; 209 209 ... ... @@ -214,29 +214,26 @@ 214 214 Click on the **Add** button. 215 215 216 216 289 +[[image:downlink-data-converter.png||height="530" width="500"]] 217 217 218 -[[image:add-downlink-data-converter.png||height="529" width="500"]] 219 219 220 220 221 -You should see that the newly added ** MQTT Downlink**ConverterNB/CBis listed on the **Data Converters** page.293 +You should see that the newly added **downlink data converter** is listed on the **Data Converters** page. 222 222 223 223 224 -[[image:data-converter s-list.png]]296 +[[image:data-converter-list.png]] 225 225 226 226 299 += Add Integration = 227 227 228 -= 3. Add Integration = 229 - 230 - 231 231 In the left navigation, click **Integrations center**, and then click **Integrations**. 232 232 303 +On the **Integrations** page, click on the '**+**' button. 233 233 234 -[[image:integrations-list-empty.png]] 235 235 306 +[[image:data-converter-list-page.png]] 236 236 237 -On the **Integrations** page, click on the '**+**' button. 238 238 239 - 240 240 The **Add integration** window appears. 241 241 242 242 In the **Add integration** window, configure the following settings: ... ... @@ -246,16 +246,14 @@ 246 246 247 247 * **Integration type**: MQTT 248 248 * **Name**: MQTT integration NB/CB 249 -* **Enable integration**: YES 250 -* **Allows create devices or assets**: YES 251 251 252 252 Click **Next** button. 253 253 254 254 255 - 256 256 [[image:add-integration-basic-settings.png||height="511" width="500"]] 257 257 258 258 325 + 259 259 **Uplink data converter:** 260 260 261 261 * Click on the **Select existing** button. ... ... @@ -264,8 +264,8 @@ 264 264 Click **Next** button. 265 265 266 266 334 +[[image:add-integration-uplink-data-converter.png||width="500"]] 267 267 268 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]] 269 269 270 270 271 271 **Downlink data converter:** ... ... @@ -276,45 +276,33 @@ 276 276 Click **Next** button. 277 277 278 278 346 +[[image:add-integration-downlink-data-converter.png||height="510" width="500"]] 279 279 280 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]] 281 281 282 282 283 283 **Connection:** 284 284 285 -* **Host**: ClusterURL(Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)286 -* **Port**: 88 83352 +* **Host**: mqtt.eu.thingsboard.cloud (This is the host name you copied from the device - See section xxxxx for more information) 353 +* **Port**: 1883 (This is the port number you copied from the device - See section xxxxx for more information) 287 287 * **Credentials**: Basic 288 -* **Enable SSL**: YES 289 -* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials) 290 -* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials) 291 -* **Topic:** tb/mqtt-integration-tutorial/sensors/+/telemetry (the + replaces any 'device name' and creates devices in the Entities -> Devices) 292 -* **QoS:** 0-At most once 355 +* **Username**: Access token (This is the access token you copied from the device) 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') 358 +* **QoS** - 0-At most once 293 293 294 -[[image:add-integration-connection.png||height="511" width="500"]] 295 - 296 - 297 -Click on the **Advanced settings** button. 298 - 299 -* **Clean session:** NO 300 -* **Retained**: NO 301 - 302 -[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]] 303 - 304 - 305 305 Click on the **Check connection** button to verify the MQTT connection using the provided parameters. 306 306 307 307 308 -[[image: check-connection.png||height="83"width="300"]]363 +[[image:add-integration-connection.png||width="500"]] 309 309 310 310 311 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.366 +If the connection is successful, you will see the **Connected** message. 312 312 368 +Click on the **Add** button. 313 313 314 -[[image:connection-success.png||height="511" width="500"]] 315 315 371 +[[image:add-connection-success.png||height="511" width="500"]] 316 316 317 -Click on the **Add** button. 318 318 319 319 You should see that the newly added integration is listed on the **Integrations** page. 320 320 ... ... @@ -322,16 +322,9 @@ 322 322 323 323 324 324 325 -[[image: new-integration-pending.png]]380 +[[image:integrations-list-added-pending.png]] 326 326 327 327 328 -= 5.Verifying the receipt of data from the device =383 += Verifying the receipt of data from the device = 329 329 330 - 331 -On the terminal, issue the following MQTT command which simulates the device S31B-NB. 332 - 333 -{{code language="none"}} 334 -mosquitto_pub -d -q 1 -h mqtt.eu.thingsboard.cloud -p 1883 -t v1/devices/S31B-NB/telemetry -u "24vk3w9h7sqdld1me5eh" -m "{temperature:20}" 335 -{{/code}} 336 - 337 -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. 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.
- 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-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
- 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