Last modified by Hera Guo on 2025/09/25 09:23
From version 24.1
edited by Hera Guo
on 2025/09/25 09:23
Change comment: There is no comment for this version
To version 17.1
edited by Hera Guo
on 2024/11/27 11:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,90 +7,95 @@
7 7  
8 8  = 1. Overview =
9 9  
10 -This instructions 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 +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.
12 12  
14 +[[image:1732679080974-799.jpg||height="444" width="1660"]]
15 +
13 13  = 2. UDP Procotol  ~-~- Directly Connection =
14 14  
15 15  == 2.1 UDP Interface ==
16 16  
17 17  * Server Address: server1.thingseye.io
18 -* Port: 11560
21 +* Port: 11562
19 19  
20 20  The data sent to above UDP interface will not go directly to client's database.
21 21  
22 22  Please contact ThingsEye team for detail how to forward data to client.
23 23  
24 -**Note：Currently udp connections require port forwarding, please contact the ThingsEye team to inform them of your device's IMEI before connecting.**
25 25  
28 +== 2.2 Test UDP Interface via Socket Tool ==
26 26  
27 -----
30 +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.
28 28  
29 -== 2.2 Test with Dragino NB device ==
32 +[[image:1728566363151-470.png]]
30 30  
31 -=== 2.2.1 Configure NB-IoT End Node ===
34 +In server side, Tenant Administrator can check this in Tenant UDP Server location.
32 32  
36 +[[image:1728362834430-749.png||height="510" width="1667"]]
37 +
38 +Click and see the debug info as below:
39 +
40 +[[image:1728363020699-203.png]]
41 +
42 +We can see the message arrives, but it shows ERROR because the message doesn't follow with the UDP Server format.
43 +
44 +
45 +== 2.3 Test with Dragino NB device ==
46 +
47 +=== 2.3.1 Configure NB-IoT End Node ===
48 +
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 -* Set to use ThingsEye UDP server: **AT+SERVADDR=server1.thingseye.io,11560**
51 +* Set to use ThingsEye UDP server: **AT+SERVADDR=server1.thingseye.io,11562**
36 36  * Use UDP Uplink & Json protocol:** AT+PRO=2,5**
37 37  * Equip with a NB-IoT SIM Card to access to NB-IoT Network.
38 38  
39 39  The S31-NB's cellular module has the IMEI: **863663062789483**
40 40  
41 -=== 2.2.2 Check Uplink Data ===
42 42  
43 -Turn on debug mod
58 +=== 2.3.2 Check Uplink Data ===
44 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:1758762371290-726.png||height="528" width="1005"]]
62 +[[image:1728378218744-800.png||height="431" width="1003"]]
52 52  
53 -[[image:1728378218744-800.png||_mstalt="295269" height="431" width="1003"]]
54 54  
55 -----
65 +=== 2.3.3 Auto-Create Device ===
56 56  
57 -=== 2.2.4 Auto-Create Device ===
58 -
59 59  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.
60 60  
61 -[[image:1728378968101-683.png||_mstalt="297154" height="210" width="1005"]]
69 +[[image:1728378968101-683.png||height="273" width="1307"]]
62 62  
63 -[[image:1728379050044-764.png||_mstalt="295282" height="326" width="1009"]]
71 +[[image:1728379050044-764.png||height="424" width="1312"]]
64 64  
65 65  
66 -----
74 +**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.**
67 67  
68 68  = 3.  Connect to The Things Stack =
69 69  
70 70  == 3.1 Network Structure ==
71 71  
72 -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.
73 73  
74 -[[image:1732679444539-853.jpg||_mstalt="296933" height="388" width="1452"]]
75 -
76 76  == 3.2 Creat Integration for The Things Stack. ==
77 77  
78 78  (% class="lead" %)
79 79  Add Integration
80 80  
81 -[[image:1728535775119-971.png||_mstalt="297661" height="423" width="1007"]]
86 +[[image:1728535775119-971.png||height="456" width="1087"]]
82 82  
83 83  
84 84  (% class="lead" %)
85 85  Choose Connection Type
86 86  
87 -[[image:1728535857345-950.png||_mstalt="297154" height="257" width="403"]]
92 +[[image:1728535857345-950.png]]
88 88  
89 89  
90 90  (% class="lead" %)
91 91  Input Uplink Data Converter Code
92 92  
93 -[[image:1728535941851-388.png||_mstalt="297856" height="466" width="398"]]
98 +[[image:1728535941851-388.png||height="466" width="398"]]
94 94  
95 95  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]]
96 96  
... ... @@ -98,7 +98,7 @@
98 98  (% class="lead" %)
99 99  Input Downlink Converter
100 100  
101 -[[image:1728536142721-488.png||_mstalt="296127" height="470" width="407"]]
106 +[[image:1728536142721-488.png||height="470" width="407"]]
102 102  
103 103  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]]
104 104  
... ... @@ -106,7 +106,7 @@
106 106  (% class="lead" %)
107 107  Set up Connection to The Things Network application
108 108  
109 -[[image:1728536305503-380.png||_mstalt="293254" height="431" width="1019"]]
114 +[[image:1728536305503-380.png||height="510" width="1206"]]
110 110  
111 111  
112 112  
... ... @@ -113,11 +113,11 @@
113 113  (% class="lead" %)
114 114  Test Connection & Add iIntegration
115 115  
116 -[[image:1728536374214-962.png||_mstalt="295893" height="380" width="1024"]]
121 +[[image:1728536374214-962.png]]
117 117  
118 118  After add , we can see the integration here:
119 119  
120 -[[image:1728536420275-153.png||_mstalt="293748" height="152" width="1026"]]
125 +[[image:1728536420275-153.png||height="208" width="1404"]]
121 121  
122 122  
123 123  == 3.3 Test Uplink ==
... ... @@ -124,35 +124,26 @@
124 124  
125 125  We can use Simulate Uplink to simulate an uplink in the things stack. Then we should be able to see the message in ThingsEye
126 126  
127 -[[image:1728536524638-768.png||_mstalt="298870" height="473" width="1028"]]
132 +[[image:1728536524638-768.png||height="493" width="1071"]]
128 128  
129 129  
130 -[[image:1728536541040-814.png||_mstalt="293215" height="424" width="1026"]]
135 +[[image:1728536541040-814.png]]
131 131  
132 -
133 -----
134 -
135 135  = 4.Connect chirpstack to Thingseye by way of MQTT =
136 136  
137 137  * **How to connect chirpstack to Thingseye by way of MQTT? The following tutorial will show you**
138 138  
139 -== 4.1 Network Structure ==
141 +== 4.1 Thingseye adds MQTT integration ==
140 140  
141 -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.
142 -
143 -[[image:1732679647697-982.jpg||_mstalt="299884" height="399" width="1492"]]
144 -
145 -== 4.2 Thingseye adds MQTT integration ==
146 -
147 147  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";
148 148  
149 -[[image:1758762634175-353.png||height="783" width="1020"]]
145 +[[image:图片1.png]]
150 150  
151 -== 4.3 Add an uplink and downlink data converter ==
147 +== 4.2 Add an uplink and downlink data converter ==
152 152  
153 -In the function decoder field, specify the uplink script to parse and transform the data.
149 +In the function decoder field, specify the script to parse and transform the data.
154 154  
155 -[[image:1758763061703-634.png||height="783" width="1020"]]
151 +[[image:图片2.png]]
156 156  
157 157  * **Uplink——JavaScript：**
158 158  
... ... @@ -234,12 +234,8 @@
234 234  
235 235  return result;
236 236  
237 -----
233 +[[image:图片3.png]]
238 238  
239 -In the function decoder field, specify the downlink script to parse and transform the data.
240 -
241 -[[image:1758763019466-819.png||height="787" width="1022"]]
242 -
243 243  * **Dowblink——JavaScript：**
244 244  
245 245  ~/~/ Encode downlink data from incoming Rule Engine message
... ... @@ -288,10 +288,8 @@
288 288  
289 289  return result;
290 290  
291 -----
283 +== 4.3 Configure the connection ==
292 292  
293 -== 4.4 Configure the connection ==
294 -
295 295  Generate MQTT certificate integrated on chirpstack
296 296  
297 297  Chirpstack generates CA certificate, TLS certificate, and TLS key respectively
... ... @@ -298,9 +298,9 @@
298 298  
299 299  They correspond to the CA certificate file, Certificate file, and Private key file on thingseye
300 300  
301 -[[image:图片4.png||_mstalt="5131737" height="504" width="1016"]]
291 +[[image:图片4.png]]
302 302  
303 -[[image:图片5.png||_mstalt="5131854" height="505" width="1017"]]
293 +[[image:图片5.png||height="630" width="1269"]]
304 304  
305 305  * Copy the contents of the certificates and paste them into the linked file below, a total of three certificates are required
306 306  
... ... @@ -316,35 +316,28 @@
316 316  
317 317  Upload the certificate and key file
318 318  
319 -[[image:图片6.png||_mstalt="5131971" height="509" width="1026"]]
309 +[[image:图片6.png]]
320 320  
321 -[[image:图片7.png||_mstalt="5132088" height="509" width="1025"]]
311 +[[image:图片7.png]]
322 322  
323 -----
324 -
325 325  The default for Topic is:
326 326  
327 327  application/**chirpstack application id**/device/+/event/up
328 328  
329 -[[image:图片8.png||_mstalt="5132205" height="508" width="1024"]]
317 +[[image:图片8.png]]
330 330  
331 331  
332 332  (% class="wikigeneratedid" %)
333 -[[image:屏幕截图 2024-11-25 095805.png||_mstalt="10831028" height="301" width="1024"]]
321 +[[image:屏幕截图 2024-11-25 095805.png||height="374" width="1272"]]
334 334  
335 -----
323 +== 4.4 Check the connection ==
336 336  
337 -== 4.5 Check the connection ==
325 +[[image:图片9.png]]
338 338  
339 -[[image:图片9.png||_mstalt="5132322" height="509" width="1025"]]
327 +[[image:图片10.png]]
340 340  
341 -[[image:图片10.png||_mstalt="5142449" height="509" width="1026"]]
342 -
343 -
344 -----
345 -
346 346  = 5. Check Data Uplink Log =
347 347  
348 348  User can check the devices log in Intergration.
349 349  
350 -[[image:1729562069134-315.png||_mstalt="294190" height="587" width="723"]]
333 +[[image:1729562069134-315.png||height="587" width="723"]]
1732679444539-853.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.hera
Size
... ... @@ -1,1 +1,0 @@
1 -180.5 KB
Content
1732679647697-982.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.hera
Size
... ... @@ -1,1 +1,0 @@
1 -179.2 KB
Content
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
1758762919291-489.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.hera
Size
... ... @@ -1,1 +1,0 @@
1 -209.4 KB
Content
1758763019466-819.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.hera
Size
... ... @@ -1,1 +1,0 @@
1 -227.9 KB
Content
1758763061703-634.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.hera
Size
... ... @@ -1,1 +1,0 @@
1 -222.0 KB
Content