Changes for page ThingsBoard

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (1 modified, 9 added, 0 removed)
  • add-integration-connection.png
  • Screenshot 2025-03-16 at 18.38.59.png
  • Screenshot 2025-03-16 at 18.39.12.png
  • Screenshot 2025-03-18 at 09.23.10.png
  • emqx.png
  • image-4.png
  • ins1.png
  • integration-dl-skip.png
  • mqtt-uplink.png
  • new-device.png

Details

Page properties

Content

...	...	@@ -22,7 +22,10 @@
22	22	To complete this tutorial, you need to have the following:
23	23
24	24	* ThingsBoard cloud account
25		-* HiveMQ Cloud account
	25	+* MQTT Broker (public or private) such as,
	26	+** **[[HiveMQ Cloud>>https://www.hivemq.com]] - You can create a free account to try it or subscribe for a paid account. - We use HiveMQ Cloud as the MQTT broker to build example in this tutorial.**
	27	+** [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] - The public MQTT server is only used for MOTT learning and testing, and should not be used in the production environment.
	28	+** [[lns1.thingseye.io>>http://lns1.thingseye.io/]] - This is Dragino's MQTT broker, which requires a CA certificate to use.
26	26
27	27	== 2.1 ThingsBoard Cloud ==
28	28
...	...	@@ -66,7 +66,9 @@
66	66
67	67	== 2.2 HiveMQ Cloud ==
68	68
	72	+=== 2.2.1 HiveMQ Cloud ===
69	69
	74	+
70	70	Go to [[https:~~/~~/www.hivemq.com>>https://www.hivemq.com]]
71	71
72	72	Click on the **Start Free** button.
...	...	@@ -141,6 +141,24 @@
141	141	You will need these MQTT connection parameters when configuring the MQTT integration in the '**Add Integration**' section.
142	142
143	143
	149	+=== 2.2.2 emqx ===
	150	+
	151	+
	152	+The [[emqx>>https://www.emqx.com/zh/mqtt/public-mqtt5-broker]] public MQTT server is only used for MOTT learning and testing, and should not be used in the production environment.
	153	+
	154	+
	155	+[[image:emqx.png||height="420" width="500"]]
	156	+
	157	+
	158	+=== 2.2.3 Ins1.thingseye.io ===
	159	+
	160	+[[lns1.thingseye.io>>http://lns1.thingseye.io/]] is the Dragino's MQTT broker, which requires a CA certificate file, Certificate file, and the Private key file to use.
	161	+
	162	+If customers need to use this MQTT connection with ThingsBoard, they need to contact the TE team to obtain three license files.
	163	+
	164	+[[image:ins1.png||height="310" width="500"]]
	165	+
	166	+
144	144	= 3. Data Converters =
145	145
146	146
...	...	@@ -153,7 +153,6 @@
153	153	In the left navigation, click **Integrations center**, and then click **Data converters**.
154	154
155	155
156		-
157	157	[[image:data-converters-list-empty.png]]
158	158
159	159
...	...	@@ -166,34 +166,130 @@
166	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.
	191	+Click on the **JavaScript** button.
170	170
171		-{{code language="JavaScript"}}
172		-/** Decoder **/
	193	+Delete the default decoder function in the code editor. Now copy and paste the following decoder function written in **JavaScript** in to the **code editor**. This decoder function is compatible for both NB and CB series devices.
173	173
	195	+
	196	+{{code language="JavaScript"}}
	197	+//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';
	202	+var objdata = {};
	203	+var obj1 = {};
	204	+var data = decodeToJson(payload);
	205	+var deviceName = data.IMEI;
	206	+delete data.IMEI;
	207	+var modelname = "Dragino " + data.Model;
	208	+//var mod = data.mod
	209	+delete data.Model;
	210	+//delete data.mod
	211	+var timestamp = new Date().getTime();
181	181
182		-// Result object with device attributes/telemetry data
	213	+for (var key in data) {
	214	+
	215	+ if (Number(key)) {
	216	+ obj1[key] = data[key];
	217	+ obj1[key][obj1[key].length - 1] = Number(new Date(
	218	+ obj1[key][obj1[key].length - 1]));
	219	+
	220	+ }
	221	+//Alec submitted25/02/25
	222	+//turn old key into new
	223	+ else if (key === "Reading") {
	224	+ objdata["reading"] = data[key];
	225	+ } else if (key === "work mode") {
	226	+ objdata["work_mode"] = data[key];
	227	+ } else if (key === "hum") {
	228	+ objdata["humidity"] = data[key];
	229	+ }else if (key === "hum2") {
	230	+ objdata["humidity2"] = data[key];
	231	+ } else if (key === "hum3") {
	232	+ objdata["humidity3"] = data[key];
	233	+ } else if (key === "tem") {
	234	+ objdata["temperature"] = data[key];
	235	+ } else if (key === "tem2") {
	236	+ objdata["temperature2"] = data[key];
	237	+ } else if (key === "tem3") {
	238	+ objdata["temperature3"] = data[key];
	239	+ } else if (key === "DS18B20_Temp") {
	240	+ objdata["temperature_pro"] = data[key];
	241	+ } else if (key === "ds18b20_temperature") {
	242	+ objdata["temperature_pro"] = data[key];
	243	+ } else if (key === "DS18B20_temperature_pro") {
	244	+ objdata["temperature_pro"] = data[key];
	245	+ } else if (key === "tdc send flag") {
	246	+ objdata["tdc_send_flag"] = data[key];
	247	+ } else if (key === "trigger mode") {
	248	+ objdata["trigger_mode"] = data[key];
	249	+ } else if (key === "soil dielectric constant") {
	250	+ objdata["soil_dielectric_constant"] = data[key];
	251	+ } else if (key === "door open num") {
	252	+ objdata["door_open_num"] = data[key];
	253	+ } else if (key === "door duration") {
	254	+ objdata["door_duration"] = data[key];
	255	+ } else if (key === "count time") {
	256	+ objdata["count_time"] = data[key];
	257	+ } else if (key === "last open time2") {
	258	+ objdata["last_open_time2"] = data[key];
	259	+ } else if (key === "last open time3") {
	260	+ objdata["last_open_time3"] = data[key];
	261	+ }
	262	+//Alec submitted25/02/25
	263	+ else {
	264	+ objdata[key] = data[key]
	265	+ }
	266	+}
	267	+var listdata = [{
	268	+ "ts": timestamp,
	269	+ "values": objdata
	270	+}]
	271	+for (var key1 in obj1) {
	272	+ if (modelname == "Dragino RS485-NB") {
	273	+ listdata.push({
	274	+ "ts": obj1[key1][obj1[key1].length - 1],
	275	+ "values": {
	276	+ "Payload": obj1[key1][0],
	277	+ }
	278	+ })
	279	+ } else {
	280	+ listdata.push({
	281	+ "ts": obj1[key1][obj1[key1].length - 1],
	282	+ "values": {
	283	+ "values": obj1[key1]
	284	+ },
	285	+ })
	286	+ }
	287	+}
183	183	var result = {
	289	+
184	184	deviceName: deviceName,
185		- deviceType: deviceType,
	291	+ deviceType: modelname,
186	186	attributes: {
187		- integrationName: metadata['integrationName'],
	293	+ model: modelname,
	294	+ //customerName: "NB-CB",
	295	+ //groupName: "NB-CB",
	296	+ //integrationName: metadata['integrationName']
	297	+
188	188	},
189		- telemetry: {
190		- temperature: data.temperature,
191		- humidity: data.humidity,
192		- }
193		-};
	299	+ telemetry: listdata
	300	+}
194	194
195		-/** Helper functions 'decodeToString' and 'decodeToJson' are already built-in **/
	302	+function decodeToString(payload) {
	303	+ return String.fromCharCode.apply(String, payload);
	304	+}
196	196
	306	+function decodeToJson(payload) {
	307	+ // covert payload to string.
	308	+ var str = decodeToString(payload);
	309	+
	310	+ // parse string to JSON
	311	+ var data = JSON.parse(str);
	312	+ return data;
	313	+}
	314	+
197	197	return result;
198	198	{{/code}}
199	199
...	...	@@ -201,84 +201,20 @@
201	201	Click on the **Add** button.
202	202
203	203
	322	+[[image:mqtt-uplink.png||width="500"]]
204	204
205		-[[image:add-uplink-data-converter.png||height="529" width="500"]]
206	206
207	207
208	208	You should see that the newly added **MQTT Uplink converter **NB/CB is listed on the **Data Converters** page.
209	209
	328	+
210	210	[[image:data-converter-list-showing-uplink-dc.png]]
211	211
212	212
213	213
214		-== 3.2 Downlink ==
215	215
216	216
217		-On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
218	218
219		-
220		-[[image:create-new-converter-menu.png||width="500"]]
221		-
222		-
223		-
224		-The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
225		-
226		-Click on the **TBEL** button if not selected it by default. Now copy and paste the following encoder function written in **TBEL (ThingsBoard Expression Language)** in to the **code editor**. This encoder function is compatible for both NB and CB series devices.
227		-
228		-
229		-{{code language="JavaScript"}}
230		-// Encode downlink data from incoming Rule Engine message
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		-// Result object with encoded downlink payload
249		-var result = {
250		-
251		- // downlink data content type: JSON, TEXT or BINARY (base64 format)
252		- contentType: "JSON",
253		-
254		- // downlink data
255		- data: JSON.stringify(data),
256		-
257		- // Optional metadata object presented in key/value format
258		- metadata: {
259		- topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
260		- }
261		-
262		-};
263		-
264		-return result;
265		-{{/code}}
266		-
267		-
268		-Click on the **Add** button.
269		-
270		-
271		-
272		-[[image:add-downlink-data-converter.png||height="529" width="500"]]
273		-
274		-
275		-You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
276		-
277		-
278		-[[image:data-converters-list.png]]
279		-
280		-
281		-
282	282	= 4. Add Integration =
283	283
284	284
...	...	@@ -306,7 +306,6 @@
306	306	Click **Next** button.
307	307
308	308
309		-
310	310	[[image:add-integration-basic-settings.png||height="511" width="500"]]
311	311
312	312
...	...	@@ -318,7 +318,6 @@
318	318	Click **Next** button.
319	319
320	320
321		-
322	322	[[image:add-integration-uplink-data-converter.png||height="511" width="500"]]
323	323
324	324
...	...	@@ -330,19 +330,18 @@
330	330	Click **Next** button.
331	331
332	332
333		-
334	334	[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
335	335
336	336
337	337	**Connection:**
338	338
339		-* **Host**: Cluster URL (Eg. 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud)
	390	+* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
340	340	* **Port**: 8883
341	341	* **Credentials**: Basic
342	342	* **Enable SSL**: YES
343	343	* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
344	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)
	396	+* **Topic: v1/devices/+/telemetry** (the + replaces any 'device name' will create a device in the Entities -> Devices)
346	346	* **QoS:** 0-At most once
347	347
348	348	[[image:add-integration-connection.png||height="511" width="500"]]
...	...	@@ -350,8 +350,8 @@
350	350
351	351	Click on the **Advanced settings** button.
352	352
353		-* **Clean session:** NO
354		-* **Retained**: NO
	404	+* **Clean session:** YES
	405	+* **Retained**: YES
355	355
356	356	[[image:add-integration-connection-advanced-settings.png||height="510" width="500"]]
357	357
...	...	@@ -387,36 +387,24 @@
387	387
388	388	We use the Mosquitto MQTT client to simulate MQTT messages, acting as a virtual device. First, install the Mosquitto client on your computer from [[this link>>url:https://mosquitto.org/download/]]. The Mosquitto client publishes messages to the MQTT broker (HiveMQ) on a specified MQTT topic. ThingsBoard subscribes to these messages using the same topic.
389	389
390		-The Mosquitto client publishes messages on the topic v1/devices/[device_name]/telemetry. The [device_name]placeholder can be replaced with any device name, for example, 'S31B-NB'. Then, the MQTT topic would be v1/devices/S31B-NB/telemetry.
	441	+The Mosquitto client publishes messages (payloads) on the topic **v1/devices/me/telemetry**. Of course, you can use any topic for testing.
391	391
392		-On the ThingsBoard side, we configure the MQTT topic subscription as v1/devices/+/telemetry. The + wildcard represents any device name and allows ThingsBoard to automatically create (provision) a device with that name, such as S31B-NB, for example.
	443	+(% id="cke_bm_37386S" style="display:none" %) (%%)The MQTT payload format is as follows, which is common for all **~-~-NB** and **~-~-CB** series devices. The **IMEI** field is mandatory and is used to provision a new device with the name assigned to it in ThingsBoard.
393	393
394		-
395		-**The new device is created the first time the MQTT topic is received. For subsequent MQTT topics with the same device name, no duplicate devices will be created.**
396		-
397		-
398		-For example, if you send two MQTT messages with different device names in the topic:
399		-
400		-1. v1/devices/**S31B-NB**/telemetry
401		-1. v1/devices/**LDS25-NB**/telemetry
402		-
403		-ThingsBoard will create two devices named **S31B-NB** and **LDS25-NB** in the **//Devices//** section.
404		-
405		-
406		-The MQTT payload format is as follows, which is common for all ~-~-NB and ~-~-CB series devices:
407		-
408	408	{{code language="none"}}
409		-{"temperature":10.4, "humidity":85}
	446	+{"IMEI": "S31B-NB", "temperature": 27, ......}
410	410	{{/code}}
411	411
	449	+Once ThingsBoard receives this message, it automatically creates (provisions) the device mentioned in the **IMEI**, for example, S31B-NB.
412	412
	451	+
413	413	== 5.2 Sending messages ==
414	414
415	415
416		-On the terminal, issue the following MQTT command which simulates the device S31B-NB. The message payload contains the fields temperature and humidity, which hold the values 10.4 and 85, respectively. This payload is also (technically) known as telemetry.
	455	+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 S31B-NB and 27, respectively. This payload is also (technically) known as telemetry.
417	417
418	418	{{code language="none"}}
419		-mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":10.4, "humidity":85}'
	458	+mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 27}'
420	420	{{/code}}
421	421
422	422	If the integration was performed without errors, the status of the integration changes to 'Active' after the first telemetry transmission.
...	...	@@ -428,38 +428,49 @@
428	428	Also, a new device named **S31B-NB** will appear under **//Entities -> Devices -> All//**. This means the first MQTT message triggers ThingsBoard to provision a device named **S31B-NB**.
429	429
430	430
431		-[[image:device-provision-1.png]]
	470	+[[image:new-device.png]]
432	432
433	433
434		-Click on the device S31B-NB on the devices list to see its details.
	473	+== 5.3 Viewing messages ==
435	435
436		-Then go to the **Latest telemetry** tab.
437	437
438		-You can see the fields temperature and humidity with the values you previously sent using the MQTT message.
	476	+Go back to the **Integrations** page.
439	439
	478	+Click on the **MQTT integration NB/CB** in the **Integrations** page to see its details.
440	440
441		-[[image:telemetry-1.png]]
	480	+Click on the **Edit** button (//**pen icon**//).
442	442
	482	+Click on the **Disabled** button in the upper-right corner.
443	443
444		-Now, change the values of the fields and send the MQTT message again. For example, set temperature to 20 and humidity to 70. Observe how the values update in //Latest Telemetry//.
	484	+Turn on the **All messages (15 min)** option. This will enable displaying all messages in the **Events** tab. This setting will expire in 15 minutes, and you will need to repeat the same steps if you want to view the messages in the Events tab later.
445	445
	486	+Click on the **Apply** button.
446	446
447		-[[image:telemetry-2.png]]
	488	+Then click on the **Apply changes** (//**tick icon**//) button.
448	448
449	449
450		-Let's provision the second device named **LDS25-NB **with initial telemetry. Use the following MQTT message.
	491	+[[image:Screenshot 2025-03-18 at 09.23.10.png]]
451	451
452	452
453		-{{code language="none"}}
454		-mosquitto_pub -d -q 1 -h 011731f7928541588a6cdfbbedfc63f4.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/LDS25-NB/telemetry" -u "pradeeka" -P "Kalpani123@" -m '{"temperature":11, "humidity":87}'
455		-{{/code}}
	494	+Now go to the **Events** tab.
456	456
457		-Now, refresh the **Devices** page, and you will see the second device, **LDS25-NB**, which was recently provisioned.
	496	+Select the Event type as **Debug** from the dropdown list.
458	458
	498	+Now you can see all the Uplink messages you are simulating through the MQTT broker. The status should be OK if there is no errors in your integration.
459	459
460		-[[image:device-provision-2.png]]
461	461
	501	+[[image:Screenshot 2025-03-16 at 18.38.59.png]]
462	462
	503	+
	504	+Then click on the **three dots (...)** in the **Message** column. You can see the uplink message's **payload** in the **Message** window.
	505	+
	506	+
	507	+[[image:Screenshot 2025-03-16 at 18.39.12.png]]
	508	+
	509	+
	510	+Now, you have successfully tested your integration with a simulated uplink payload and verified that it is received by ThingsBoard, and the device is provisioned.
	511	+
	512	+
463	463	= 6. Creating a Dashboard =
464	464
465	465	ThingsBoard **Dashboards** provide a powerful way to visualize and monitor real-time and historical data from connected devices. They allow users to create interactive, customizable panels displaying telemetry data, device status, and other key metrics. With a variety of widgets, including charts, maps, and tables, dashboards help users gain insights, track trends, and manage IoT deployments efficiently.
...	...	@@ -468,6 +468,11 @@
468	468	This section guides you on how to create a dashboard to display temperature and humidity data from the device on a time-series chart. You may also use other widgets in ThingsBoard to display data according to your requirements.
469	469
470	470
	521	+First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
	522	+
	523	+{{code language="none"}}mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 22, "humidity":80}'{{/code}}
	524	+
	525	+
471	471	In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
472	472
473	473
...	...	@@ -524,11 +524,11 @@
524	524
525	525
526	526	{{code language="none"}}
527		-mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":20, "humidity":70}'
	582	+mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 22, "humidity":70}'
528	528
529		-mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":22, "humidity":71}'
	584	+mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 27, "humidity":72}'
530	530
531		-mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "tb/mqtt-integration-tutorial/sensors/S31B-NB/telemetry" -u "xxxxx" -P "xxxxx" -m '{"temperature":18, "humidity":79}'
	586	+mosquitto_pub -d -q 1 -h 011731f7928xxxxx.s1.eu.hivemq.cloud -p 8883 -t "v1/devices/me/telemetry" -u "xxxxx" -P "xxxxx" -m '{"IMEI": "S31B-NB", "temperature": 19, "humidity":80}'
532	532
533	533	{{/code}}
534	534
...	...	@@ -549,16 +549,19 @@
549	549	**AT Commands**
550	550
551	551	* **AT+PRO=3,3    **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
	607	+* **AT+SUBTOPIC=<MQTT subscribe topic> **
	608	+* **AT+PUBTOPIC=<MQTT publish topic> Eg: TS01-NB**
	609	+* **AT+CLIENT=null**
	610	+* **AT+UNAME=<MQTT Username>**
	611	+* **AT+PWD=<MQTT Password>**
	612	+* **AT+SERVADDR=<Broker address, Port>**
552	552
553		-* **AT+SUBTOPIC=<device name>**
	614	+Test your uplink by pressing the ACT button for 1 second.
554	554
555		-* **AT+PUBTOPIC=**tb/mqtt-integration-tutorial/sensors/LDS25-NB/telemetry
556	556
557		-* **AT+CLIENT=null**
	617	+The following image shows the uplink payload of a real Dragino device. The publish topic is **TS01-NB**, and the device name is **861275077962896**, which is represented by the **IMEI**.
558	558
559		-* **AT+UNAME=<MQTT Username>**
	619	+[[image:image-4.png]]
560	560
561		-* **AT+PWD=<MQTT Password>**
562	562
563		-
564		-Test your uplink by pressing the ACT button for 1 second.
	622	+

add-integration-connection.png

Size

...	...	@@ -1,1 +1,1 @@
1		-124.4 KB
	1	+153.2 KB

Content

Screenshot 2025-03-16 at 18.38.59.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+221.2 KB

Content

Screenshot 2025-03-16 at 18.39.12.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+277.0 KB

Content

Screenshot 2025-03-18 at 09.23.10.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+78.7 KB

Content

emqx.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+39.1 KB

Content

image-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+96.0 KB

Content

ins1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+28.8 KB

Content

integration-dl-skip.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+105.5 KB

Content

mqtt-uplink.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+175.1 KB

Content

new-device.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.pradeeka

Size

...	...	@@ -1,0 +1,1 @@
	1	+143.3 KB

Content