Skip to Content

Changes for page ThingsBoard

Last modified by Dilisi S on 2025/04/23 19:23
From version 122.1
edited by Dilisi S
on 2025/03/08 20:41
Change comment: Uploaded new attachment "thingsboard-1.png", version {1}
To version 90.1
edited by Dilisi S
on 2025/03/08 03:47
Change comment: Uploaded new attachment "add-uplink-data-converter.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -17,96 +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  
25 +In the left navigation, click **Entities** and then click **Devices**.
27 27  
28 -== 2.1 ThingsBoard Cloud ==
27 +[[image:device-list-empty.png]]
29 29  
30 30  
31 -Add details here
30 +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 ==
32 +[[image:ThingsBoard-add-new-device.png||height="279" width="500"]]
34 34  
35 35  
36 -Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
35 +The **Add new device** window appears. Name the device, for example '**Virtual NB/CB device**'.
37 37  
38 -Click on the **Start Free** button.
37 +Click on the **Next: Credentials** button.
39 39  
40 -[[image:hivwmq-1.png]]
39 +[[image:new-device-device-details.png||height="529" width="500"]]
41 41  
42 42  
43 -Click on the **Sign Up FREE Now** button in the **HIVEMQ CLOUD** section.
42 +Click the **Access token** button if it is not selected by default.
44 44  
45 -[[image:hivemq-2.png]]
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  
46 +Click on the **Add** button.
47 47  
48 -Click on the **Sign Up** button.
48 +[[image:new-device-access-token.png||height="528" width="500"]]
49 49  
50 -You can sign up with HiveMQ using your **GitHub**, **Google**, or **LinkedIn** account.
51 51  
52 -If not, provide your **email address** and a **password** to create an account by clicking on the **Sign Up** button.
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 -[[image:hivemq-3.png]]
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 -You will receive an email to verify your email address. Click on the **Confirm my account** button.
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 -[[image:hivemq-4.jpg||height="889" width="400"]]
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 -You will be redirected to a page asking you to complete your profile. Once done, click the **Continue** button.
65 65  
69 +[[image:mqtt-command-1.png||height="228" width="700"]]
66 66  
67 -[[image:hivemq-5.png||height="655" width="700"]]
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 -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  
75 +[[image:new-device-telemetry-test.png||height="520" width="500"]]
72 72  
73 -[[image:hivemq-6.png]]
74 74  
78 +Send the same command again, only changing the **temperature** value, to see how the **Latest telemetry** section updates its data.
75 75  
76 -You will be navigated to the **Your Clusters** page. Click on the **Manage Cluster** button.
80 +Once you are done experimenting with this, close the window by clicking the **Close** button.
77 77  
78 -[[image:hivemq-7.png]]
79 79  
83 +[[image:mqtt-command-2.png||height="227" width="700"]]
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.
84 84  
85 -**Port**: 8883
87 +[[image:virtual-device-active.png]]
86 86  
87 87  
88 -Click on the **Getting Started** tab to setup the username and the password as the connection credentials.
89 -
90 -
91 -[[image:hivemq-8.png]]
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 110  = 3. Data Converters =
111 111  
112 112  
... ... @@ -118,112 +118,188 @@
118 118  
119 119  In the left navigation, click **Integrations center**, and then click **Data converters**.
120 120  
101 +[[image:data-converter-list-page.png]]
121 121  
122 122  
123 -[[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.
124 124  
106 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
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  
128 -
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.
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.
136 136  
137 137  {{code language="JavaScript"}}
138 -/** Decoder **/
139 -
114 +//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';
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();
147 147  
148 -// 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 +}
149 149  var result = {
206 +
150 150   deviceName: deviceName,
151 - deviceType: deviceType,
208 + deviceType: modelname,
152 152   attributes: {
153 - integrationName: metadata['integrationName'],
210 + model: modelname,
211 + //customerName: "NB-CB",
212 + //groupName: "NB-CB",
213 + //integrationName: metadata['integrationName']
214 +
154 154   },
155 - telemetry: {
156 - temperature: data.temperature,
157 - humidity: data.humidity,
158 - }
159 -};
216 + telemetry: listdata
217 +}
160 160  
161 -/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
219 +function decodeToString(payload) {
220 + return String.fromCharCode.apply(String, payload);
221 +}
162 162  
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 +
163 163  return result;
233 +
164 164  {{/code}}
165 165  
166 166  
167 167  Click on the **Add** button.
168 168  
239 +[[image:uplink-data-converter.png||height="529" width="500"]]
169 169  
170 170  
171 -[[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.
172 172  
173 -
174 -You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
175 -
176 176  [[image:data-converter-list-showing-uplink-dc.png]]
177 177  
178 178  
179 -
180 180  == 3.2 Downlink ==
181 181  
182 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  
252 +[[image:ThingsBoard-new-data-converter.png||height="282" width="500"]]
185 185  
186 -[[image:create-new-converter-menu.png||width="500"]]
187 187  
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  
... ... @@ -233,30 +233,24 @@
233 233  
234 234  Click on the **Add** button.
235 235  
292 +[[image:downlink-data-converter.png||height="530" width="500"]]
236 236  
237 237  
238 -[[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.
239 239  
297 +[[image:data-converter-list.png]]
240 240  
241 -You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
242 242  
243 -
244 -[[image:data-converters-list.png]]
245 -
246 -
247 -
248 248  = 4. Add Integration =
249 249  
250 250  
251 251  In the left navigation, click **Integrations center**, and then click **Integrations**.
252 252  
253 -
254 -[[image:integrations-list-empty.png]]
255 -
256 -
257 257  On the **Integrations** page, click on the '**+**' button.
258 258  
307 +[[image:data-converter-list-page.png]]
259 259  
309 +
260 260  The **Add integration** window appears.
261 261  
262 262  In the **Add integration** window, configure the following settings:
... ... @@ -266,13 +266,9 @@
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 -
275 -
276 276  [[image:add-integration-basic-settings.png||height="511" width="500"]]
277 277  
278 278  
... ... @@ -283,11 +283,9 @@
283 283  
284 284  Click **Next** button.
285 285  
332 +[[image:add-integration-uplink-data-converter.png||width="500"]]
286 286  
287 287  
288 -[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
289 -
290 -
291 291  **Downlink data converter:**
292 292  
293 293  * Click on the **Select existing** button.
... ... @@ -295,56 +295,38 @@
295 295  
296 296  Click **Next** button.
297 297  
342 +[[image:add-integration-downlink-data-converter.png||height="510" width="500"]]
298 298  
299 299  
300 -[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
301 -
302 -
303 303  **Connection:**
304 304  
305 -* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
306 -* **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)
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
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
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  
357 +[[image:add-integration-connection.png||width="500"]]
327 327  
328 -[[image:check-connection.png||height="83" width="300"]]
329 329  
360 +If the connection is successful, you will see the **Connected** message.
330 330  
331 -If the connection is successful, you will see the **Connected** message. If not, check your connection parameters again.
362 +Click on the **Add** button.
332 332  
364 +[[image:add-connection-success.png||height="511" width="500"]]
333 333  
334 -[[image:connection-success.png||height="511" width="500"]]
335 335  
336 -
337 -Click on the **Add** button.
338 -
339 339  You should see that the newly added integration is listed on the **Integrations** page.
340 340  
341 341  Since we haven't received data from a device yet, the integration **Status** is shown as **Pending.**
342 342  
371 +[[image:integrations-list-added-pending.png]]
343 343  
344 344  
345 -[[image:new-integration-pending.png]]
346 -
347 -
348 348  = 5. Verifying the receipt of data from the device =
349 349  
350 350  
... ... @@ -355,3 +355,5 @@
355 355  {{/code}}
356 356  
357 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.
384 +
385 +
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-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
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-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -1.9 MB
Content