Changes for page Connect Devices to ThingsEye
Last modified by Hera Guo on 2025/09/25 09:23
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Content
-
... ... @@ -7,9 +7,8 @@ 7 7 8 8 = 1. Overview = 9 9 10 -Th isinstructions will show you how to connect a device that has been registered to the server to the Thingseye platform.10 +The instructions in this chapter will show you how to connect a device that has been registered to the server to the Thingseye platform. 11 11 12 - 13 13 = 2. UDP Procotol ~-~- Directly Connection = 14 14 15 15 == 2.1 UDP Interface == ... ... @@ -21,15 +21,26 @@ 21 21 22 22 Please contact ThingsEye team for detail how to forward data to client. 23 23 24 - **Note:Currentlyudpconnections require portforwarding, pleasecontact theThingsEye teamtoinform them of your device'sIMEI before connecting.**23 +== 2.2 Test UDP Interface via Socket Tool == 25 25 25 +Download the UDP Test Tool from: [[https:~~/~~/sourceforge.net/projects/sockettest/ >>https://sourceforge.net/projects/sockettest/]]. Run this tool, and input the server address and UDP port as below and click send. 26 26 27 -- ---27 +[[image:1728566363151-470.png]] 28 28 29 - ==2.2Testwith DraginoNBdevice==29 +In server side, Tenant Administrator can check this in Tenant UDP Server location. 30 30 31 - ===2.2.1 ConfigureNB-IoT EndNode===31 +[[image:1728362834430-749.png||height="510" width="1667"]] 32 32 33 +Click and see the debug info as below: 34 + 35 +[[image:1728363020699-203.png]] 36 + 37 +We can see the message arrives, but it shows ERROR because the message doesn't follow with the UDP Server format. 38 + 39 +== 2.3 Test with Dragino NB device == 40 + 41 +=== 2.3.1 Configure NB-IoT End Node === 42 + 33 33 Device here is **[[S31-NB>>https://www.dragino.com/products/temperature-humidity-sensor/item/288-s31-nb-s31b-nb.html]]** : and have been configure below 34 34 35 35 * Set to use ThingsEye UDP server: **AT+SERVADDR=server1.thingseye.io,11560** ... ... @@ -38,30 +38,19 @@ 38 38 39 39 The S31-NB's cellular module has the IMEI: **863663062789483** 40 40 41 -=== 2. 2.2 Check Uplink Data ===51 +=== 2.3.2 Check Uplink Data === 42 42 43 -Turn on debug mod 44 - 45 -[[image:1758762334133-608.png||height="494" width="1003"]] 46 - 47 ----- 48 - 49 49 Re-activate the S31-NB, and we can see it in the debug window: 50 50 51 -[[image:17 58762371290-726.png||height="528" width="1005"]]55 +[[image:1728378218744-800.png||height="431" width="1003"]] 52 52 53 -[[image:1728378218744-800.png||_mstalt="295269" height="431" width="1003"]] 54 - 55 - 56 ----- 57 - 58 58 === 2.3.3 Auto-Create Device === 59 59 60 60 The default **Tenant UDP Server** has already been configured to decode the Dragino -NB / -CB NB-IoT node. So once each end node sends a data to server. Tenant will auto create the device in the server. 61 61 62 -[[image:1728378968101-683.png|| _mstalt="297154"height="210" width="1005"]]61 +[[image:1728378968101-683.png||height="273" width="1307"]] 63 63 64 -[[image:1728379050044-764.png|| _mstalt="295282"height="326" width="1009"]]63 +[[image:1728379050044-764.png||height="424" width="1312"]] 65 65 66 66 67 67 **So we have this device in the Tenant Device List. The next step will be how to use these value to make a nice dashboard for user's application.** ... ... @@ -72,7 +72,7 @@ 72 72 73 73 The network diagram below illustrates the connection between the devices and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform. 74 74 75 -[[image:1732679444539-853.jpg|| _mstalt="296933"height="388" width="1452"]]74 +[[image:1732679444539-853.jpg||height="388" width="1452"]] 76 76 77 77 == 3.2 Creat Integration for The Things Stack. == 78 78 ... ... @@ -79,19 +79,19 @@ 79 79 (% class="lead" %) 80 80 Add Integration 81 81 82 -[[image:1728535775119-971.png|| _mstalt="297661"height="456" width="1087"]]81 +[[image:1728535775119-971.png||height="456" width="1087"]] 83 83 84 84 85 85 (% class="lead" %) 86 86 Choose Connection Type 87 87 88 -[[image:1728535857345-950.png ||_mstalt="297154"]]87 +[[image:1728535857345-950.png]] 89 89 90 90 91 91 (% class="lead" %) 92 92 Input Uplink Data Converter Code 93 93 94 -[[image:1728535941851-388.png|| _mstalt="297856"height="466" width="398"]]93 +[[image:1728535941851-388.png||height="466" width="398"]] 95 95 96 96 Demo JavaScript Code: [[https:~~/~~/raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js >>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]] 97 97 ... ... @@ -99,7 +99,7 @@ 99 99 (% class="lead" %) 100 100 Input Downlink Converter 101 101 102 -[[image:1728536142721-488.png|| _mstalt="296127"height="470" width="407"]]101 +[[image:1728536142721-488.png||height="470" width="407"]] 103 103 104 104 Example Javascript Code as below: [[https:~~/~~/raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]] 105 105 ... ... @@ -107,7 +107,7 @@ 107 107 (% class="lead" %) 108 108 Set up Connection to The Things Network application 109 109 110 -[[image:1728536305503-380.png|| _mstalt="293254"height="510" width="1206"]]109 +[[image:1728536305503-380.png||height="510" width="1206"]] 111 111 112 112 113 113 ... ... @@ -114,11 +114,11 @@ 114 114 (% class="lead" %) 115 115 Test Connection & Add iIntegration 116 116 117 -[[image:1728536374214-962.png ||_mstalt="295893"]]116 +[[image:1728536374214-962.png]] 118 118 119 119 After add , we can see the integration here: 120 120 121 -[[image:1728536420275-153.png|| _mstalt="293748"height="208" width="1404"]]120 +[[image:1728536420275-153.png||height="208" width="1404"]] 122 122 123 123 124 124 == 3.3 Test Uplink == ... ... @@ -125,10 +125,10 @@ 125 125 126 126 We can use Simulate Uplink to simulate an uplink in the things stack. Then we should be able to see the message in ThingsEye 127 127 128 -[[image:1728536524638-768.png|| _mstalt="298870"height="493" width="1071"]]127 +[[image:1728536524638-768.png||height="493" width="1071"]] 129 129 130 130 131 -[[image:1728536541040-814.png ||_mstalt="293215"]]130 +[[image:1728536541040-814.png]] 132 132 133 133 = 4.Connect chirpstack to Thingseye by way of MQTT = 134 134 ... ... @@ -138,19 +138,19 @@ 138 138 139 139 The network diagram below illustrates the connection between the devices andchirpstack, as well as how the data can be integrated with the ThingsEye IoT platform. 140 140 141 -[[image:1732679647697-982.jpg|| _mstalt="299884"height="399" width="1492"]]140 +[[image:1732679647697-982.jpg||height="399" width="1492"]] 142 142 143 143 == 4.2 Thingseye adds MQTT integration == 144 144 145 145 Go to the Integrations page in the Integrations center section. Click the plus button to start adding a new integration. Select the type "MQTT" integration and click "Next"; 146 146 147 -[[image:1 758762634175-353.png]]146 +[[image:图片1.png]] 148 148 149 149 == 4.3 Add an uplink and downlink data converter == 150 150 151 151 In the function decoder field, specify the script to parse and transform the data. 152 152 153 -[[image:图片2.png ||_mstalt="5131503"]]152 +[[image:图片2.png]] 154 154 155 155 * **Uplink——JavaScript:** 156 156 ... ... @@ -232,7 +232,7 @@ 232 232 233 233 return result; 234 234 235 -[[image:图片3.png ||_mstalt="5131620"]]234 +[[image:图片3.png]] 236 236 237 237 * **Dowblink——JavaScript:** 238 238 ... ... @@ -290,9 +290,9 @@ 290 290 291 291 They correspond to the CA certificate file, Certificate file, and Private key file on thingseye 292 292 293 -[[image:图片4.png ||_mstalt="5131737"]]292 +[[image:图片4.png]] 294 294 295 -[[image:图片5.png|| _mstalt="5131854"height="630" width="1269"]]294 +[[image:图片5.png||height="630" width="1269"]] 296 296 297 297 * Copy the contents of the certificates and paste them into the linked file below, a total of three certificates are required 298 298 ... ... @@ -308,28 +308,28 @@ 308 308 309 309 Upload the certificate and key file 310 310 311 -[[image:图片6.png ||_mstalt="5131971"]]310 +[[image:图片6.png]] 312 312 313 -[[image:图片7.png ||_mstalt="5132088"]]312 +[[image:图片7.png]] 314 314 315 315 The default for Topic is: 316 316 317 317 application/**chirpstack application id**/device/+/event/up 318 318 319 -[[image:图片8.png ||_mstalt="5132205"]]318 +[[image:图片8.png]] 320 320 321 321 322 322 (% class="wikigeneratedid" %) 323 -[[image:屏幕截图 2024-11-25 095805.png|| _mstalt="10831028"height="374" width="1272"]]322 +[[image:屏幕截图 2024-11-25 095805.png||height="374" width="1272"]] 324 324 325 325 == 4.5 Check the connection == 326 326 327 -[[image:图片9.png ||_mstalt="5132322"]]326 +[[image:图片9.png]] 328 328 329 -[[image:图片10.png ||_mstalt="5142449"]]328 +[[image:图片10.png]] 330 330 331 331 = 5. Check Data Uplink Log = 332 332 333 333 User can check the devices log in Intergration. 334 334 335 -[[image:1729562069134-315.png|| _mstalt="294190"height="587" width="723"]]334 +[[image:1729562069134-315.png||height="587" width="723"]]
- 1758762334133-608.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.hera - Size
-
... ... @@ -1,1 +1,0 @@ 1 -161.4 KB - Content
- 1758762371290-726.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.hera - Size
-
... ... @@ -1,1 +1,0 @@ 1 -215.2 KB - Content
- 1758762634175-353.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.hera - Size
-
... ... @@ -1,1 +1,0 @@ 1 -213.8 KB - Content