Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 1 removed)
  • integration-dl-skip.png

Details

Page properties

Content

...	...	@@ -329,10 +329,72 @@
329	329	[[image:data-converter-list-showing-uplink-dc.png]]
330	330
331	331
	332	+== 3.2 Downlink ==
332	332
333	333
	335	+On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
334	334
335	335
	338	+[[image:create-new-converter-menu.png||width="500"]]
	339	+
	340	+
	341	+
	342	+The **Add data converter** window will appear. Name it ‘**MQTT Downlink Converter NB/CB**’ and select the Type as **Downlink**.
	343	+
	344	+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.
	345	+
	346	+
	347	+{{code language="JavaScript"}}
	348	+// Encode downlink data from incoming Rule Engine message
	349	+
	350	+// msg - JSON message payload downlink message json
	351	+// msgType - type of message, for ex. 'ATTRIBUTES_UPDATED', 'POST_TELEMETRY_REQUEST', etc.
	352	+// metadata - list of key-value pairs with additional data about the message
	353	+// integrationMetadata - list of key-value pairs with additional data defined in Integration executing this converter
	354	+
	355	+/** Encoder **/
	356	+
	357	+var data = {};
	358	+
	359	+// Process data from incoming message and metadata
	360	+
	361	+data.tempFreq = msg.temperatureUploadFrequency;
	362	+data.humFreq = msg.humidityUploadFrequency;
	363	+
	364	+data.devSerialNumber = metadata['ss_serialNumber'];
	365	+
	366	+// Result object with encoded downlink payload
	367	+var result = {
	368	+
	369	+ // downlink data content type: JSON, TEXT or BINARY (base64 format)
	370	+ contentType: "JSON",
	371	+
	372	+ // downlink data
	373	+ data: JSON.stringify(data),
	374	+
	375	+ // Optional metadata object presented in key/value format
	376	+ metadata: {
	377	+ topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
	378	+ }
	379	+
	380	+};
	381	+
	382	+return result;
	383	+{{/code}}
	384	+
	385	+
	386	+Click on the **Add** button.
	387	+
	388	+
	389	+[[image:add-downlink-data-converter.png||height="529" width="500"]]
	390	+
	391	+
	392	+You should see that the newly added **MQTT Downlink** Converter NB/CB is listed on the **Data Converters** page.
	393	+
	394	+
	395	+[[image:data-converters-list.png]]
	396	+
	397	+
336	336	= 4. Add Integration =
337	337
338	338
...	...	@@ -376,17 +376,15 @@
376	376
377	377	**Downlink data converter:**
378	378
379		-Dragino NB/CB devices don't require a downlink data converter to decode their payloads, so you can skip this step.
	441	+* Click on the **Select existing** button.
	442	+* **Downlink data converter**: Select **MQTT Downlink Converter NB/CB **from the dropdown list.
380	380
381		-* Click on the **Skip **button in the Downlink data converter section.
	444	+Click **Next** button.
382	382
383		-Click **Skip** button.
384	384
	447	+[[image:add-integration-downlink-data-converter.png||height="511" width="500"]]
385	385
386		-[[image:integration-dl-skip.png||height="511" width="500"]]
387	387
388		-
389		-
390	390	**Connection:**
391	391
392	392	* **Host**: Cluster URL (Eg. 011731f7xxxxxxxxxxxfbbedfc63f4.s1.eu.hivemq.cloud)
...	...	@@ -395,7 +395,7 @@
395	395	* **Enable SSL**: YES
396	396	* **Username**: Username (from your HiveMQ Cloud Cluster with your credentials)
397	397	* **Password:** Password (from your HiveMQ Cloud Cluster with your credentials)
398		-* **Topic: v1/devices/me/telemetry** (The topic can be anything, even you can use just the device name, for example ts02-nb)
	458	+* **Topic: v1/devices/+/telemetry** (the + replaces any 'device name' will create a device in the Entities -> Devices)
399	399	* **QoS:** 0-At most once
400	400
401	401	[[image:add-integration-connection.png||height="511" width="500"]]
...	...	@@ -522,7 +522,8 @@
522	522
523	523	First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
524	524
525		-{{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}}
	585	+{{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}'
	586	+{{/code}}
526	526
527	527
528	528	In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.
...	...	@@ -598,7 +598,7 @@
598	598	= 7. Configure NB-IoT Sensor =
599	599
600	600
601		-Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **TS01-NB**.
	662	+Now, let's experiment with sending data to ThingsBoard using a real NB-IoT device. For example, we will use the **S31B-NB**.
602	602
603	603	First, configure the NB-IoT device with the necessary MQTT settings using AT commands. Below is a list of AT commands you can use.
604	604
...	...	@@ -614,15 +614,10 @@
614	614	* **AT+SERVADDR=<Broker address, Port>**
615	615
616	616	Test your uplink by pressing the ACT button for 1 second.
617		-
618	618
619	619
620	620	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**.
621	621
622		-{{info}}
623		-The ThingsBoard uses the device's IMEI number included in the payload to create a device in the Devices section.
624		-{{/info}}
625		-
626	626	[[image:image-4.png]]
627	627
628	628

integration-dl-skip.png

Author

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

Size

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

Content