Summary

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

Details

Page properties

Content

...	...	@@ -329,72 +329,10 @@
329	329	[[image:data-converter-list-showing-uplink-dc.png]]
330	330
331	331
332		-== 3.2 Downlink ==
333	333
334	334
335		-On the **Data converters** page, click on the ‘**+**’ button, and then click on the **Create new converter** from the dropdown menu.
336	336
337	337
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		-
398	398	= 4. Add Integration =
399	399
400	400
...	...	@@ -582,8 +582,7 @@
582	582
583	583	First simulate a few messages using MQTT. This time, we have added the 'humidity' field to the payload. Eg:
584	584
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}}
	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}}
587	587
588	588
589	589	In **ThingsBoard**, from the left navigation menu, click **Dashboards**. Then, click the **+** button and select **Create new dashboard** from the dropdown menu.

integration-dl-skip.png

Author

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

Size

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

Content