Skip to Content

Wiki source code of Notes for Helium

Version 1.4 by Xiaoling on 2022/05/16 14:45
Show last authors
1 **Contents:**
2
3
4
5 = 1. Use Dragino Gateways/Hotspots with Helium =
6
7 == 1.1 Support Models ==
8
9 There are three types of hotspots that can connect to Helium. They are full-hotspot, light hotspot and data-only hotspot. Definition of these three types of hotspots can be found here: [[of Helium Hotspots>>url:https://docs.helium.com/mine-hnt%7CTypes]]. Different hotspots support different mining abilities.
10
11 Dragino has different gateway models that support different types.
12
13 (% border="1" style="background-color:#ffffcc; width:785.989px" %)
14 |(% colspan="4" style="width:783px" %)(% style="color:green" %)**Dragino Hotspots for Helium**
15 |(% style="color:green; width:203px" %)**Model**|(% style="color:green; width:162px" %)**Hotspot Types**|(% style="color:green; width:134px" %)**Mining Ability**|(% style="color:green; width:250px" %)**Configure Instruction**
16 |(% style="width:203px" %)[[LPS8>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]], [[DLOS8>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]],[[LG308>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]],[[LIG16>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]]|(% style="color:#4f81bd; width:162px" %)**Data-Only Hotspot**|(% style="width:134px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:250px" %)[[Data-Only Hotspot Instruction>>url:https://wiki.dragino.com/index.php/Notes_for_Helium#Connect_Data-Only_Hotspot_to_Helium]]
17 |(% style="width:203px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% style="color:#4f81bd; width:162px" %)**Full Hotspo**t|(% style="width:134px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/full-hotspots]]|(% style="color:green; width:250px" %)Full Hotspot Instruction-Not Finish
18
19 **Frequencies on the Helium Network**
20
21 * The frequencies currently available are CN470/EU868/US915/AU915
22
23 Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]
24
25
26 = 2. Connect Data-Only Hotspot to Helium =
27
28 == 2.1 Prerequisites ==
29
30 * Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
31
32 == 2.2 Step 1:Configure Frequency Band ==
33
34 Each country has a requirement for frequency region. Choose the right one for your area.
35
36 [[image:https://wiki.dragino.com/images/thumb/4/4b/Select_fre.png/600px-Select_fre.png||height="306" width="600"]]
37
38 Select fre
39
40 == 2.3 Step 2: Download the Helium-gateway-rs ==
41
42 Click Download Helium Server and the gateway will download the Helium-gateway-rs
43
44 [[image:https://wiki.dragino.com/images/thumb/a/ac/Start_download_the_Helium-gatewayrs_1.1.png/600px-Start_download_the_Helium-gatewayrs_1.1.png||height="332" width="600"]]
45
46 Start download the Helium-gatewayrs
47
48 [[image:https://wiki.dragino.com/images/thumb/c/cb/Helium-gatewayrs_download_success_1.1.png/600px-Helium-gatewayrs_download_success_1.1.png||height="340" width="600"]]
49
50 Helium-gatewayrs download success
51
52 If download fails, click and download again
53
54 [[image:https://wiki.dragino.com/images/thumb/2/22/Helium-gatewayrs_download_fail_1.1.png/600px-Helium-gatewayrs_download_fail_1.1.png||height="326" width="600"]]
55
56 Helium-gatewayrs download fail
57
58 == 2.4 Step 3: Install the Helium-gateway-rs ==
59
60 Click **Install Helium Server** to install gateway-rs.
61
62 [[image:https://wiki.dragino.com/images/thumb/d/d1/Start_Install_the_Helium-gatewayrs_1.1.png/600px-Start_Install_the_Helium-gatewayrs_1.1.png||height="340" width="600"]]
63
64 Install the Helium gateway-rs
65
66 Note: User will see the echo characters of Helium gateway-rs have been installed successfully.
67
68 == 2.5 Step 4: Save&start the Helium Server ==
69
70 Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.
71
72 [[image:https://wiki.dragino.com/images/thumb/0/07/Start_Helium-gatewayrs_1.1.png/600px-Start_Helium-gatewayrs_1.1.png||height="329" width="600"]]
73
74 Start Helium-gateway-rs
75
76 == 2.6 Step 5: Check Gateway Connection before onboarding ==
77
78 A hotspot can transfer data to Helium after finishing step4. We can add a device to Helium and see if the device can join Helium. For example, we add an LGT92 sensor and see below info.
79
80 Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.
81
82 [[image:https://wiki.dragino.com/images/thumb/c/c4/Data-hotspot-data_1.png/600px-Data-hotspot-data_1.png||height="192" width="600"]]
83
84 Check if the packet is transferred via LPS8
85
86 **Note:** The hotspot is not valid for search in Helium Console before onboarding.
87
88 == 2.7 Step 6: Onboarding Data-Only Hotspot ==
89
90 Note: Onboarding a Data-Only hotspot is not necessary, and it will gain very, very small awards on HNT by data-transfer .
91
92 User can refer [[this link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]] for how to onboarding a data-only hotspot. After onboarding the data-only hotspot, user can see the hotspot on Helium Console.
93
94 Below are the steps we do as per above link here.
95
96 ~1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.
97
98 {{{[root@iZt4n22vqvm7ajogrfiif6Z helium-wallet-v1.6.4-x86-64-linux]# helium-wallet info
99 +--------------------+-----------------------------------------------------+
100 | Key | Value |
101 +--------------------+-----------------------------------------------------+
102 | Address | 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux |
103 +--------------------+-----------------------------------------------------+
104 | Network | mainnet |
105 +--------------------+-----------------------------------------------------+
106 | Type | ed25519 |
107 +--------------------+-----------------------------------------------------+
108 | Sharded | false |
109 +--------------------+-----------------------------------------------------+
110 | PwHash | Argon2id13 |
111 +--------------------+-----------------------------------------------------+
112 | Balance | 18.76580626 |
113 +--------------------+-----------------------------------------------------+
114 | DC Balance | 0 |
115 +--------------------+-----------------------------------------------------+
116 | Securities Balance | 0.00000000 |
117 +--------------------+-----------------------------------------------------+}}}
118
119 Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.
120
121
122 2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.
123
124 {{{root@123123:~# helium_gateway add --owner 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux --payer 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux { "address": "146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm", "fee": 65000, "mode": "dataonly", "owner": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux", "payer": "13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux", "staking fee": 1000000, "txn": "CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=" }}}}
125
126 We got the txn info from this step.
127 \\3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step. Note, below are two commands, the command without ~-~-commit is the preview mode. Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.
128
129 {{{[root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM=
130 Password: [hidden]
131 +------------------+-----------------------------------------------------+
132 | Key | Value |
133 +------------------+-----------------------------------------------------+
134 | Address | 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm |
135 +------------------+-----------------------------------------------------+
136 | Payer | 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux |
137 +------------------+-----------------------------------------------------+
138 | Owner | 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux |
139 +------------------+-----------------------------------------------------+
140 | Fee (DC) | 65000 |
141 +------------------+-----------------------------------------------------+
142 | Staking fee (DC) | 1000000 |
143 +------------------+-----------------------------------------------------+
144 | Hash | none |
145 +------------------+-----------------------------------------------------+
146  
147 Preview mode: use --commit to submit the transaction to the network
148 [root@]# helium-wallet hotspots add CrMBCiEBcJ9JnnIW50i+xEJRtFRVqyosuR4CzJVf3m7qGEF+WZYNhVgLtajtf4elKPoA3NkvAphTQTACohAXCfSZ5yNupaL/FxaNGQgV+P9UHLWzicPhTh7YVEOl2BOMCEPUDo+wM= --commit
149 Password: [hidden]
150 +------------------+-----------------------------------------------------+
151 | Key | Value |
152 +------------------+-----------------------------------------------------+
153 | Address | 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm |
154 +------------------+-----------------------------------------------------+
155 | Payer | 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux |
156 +------------------+-----------------------------------------------------+
157 | Owner | 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux |
158 +------------------+-----------------------------------------------------+
159 | Fee (DC) | 65000 |
160 +------------------+-----------------------------------------------------+
161 | Staking fee (DC) | 1000000 |
162 +------------------+-----------------------------------------------------+
163 | Hash | i6BQAI4Ehnd7nb8zfvegprhO2fOI1rj4UEPbAVC2sWk |
164 +------------------+-----------------------------------------------------+}}}
165
166
167 4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.
168
169 {{{[root@]# helium-wallet hotspots assert --gateway 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm --lat=22.706922 --lon=114.242538 --mode dataonly
170 Password: [hidden]
171 +------------------+-----------------------------------------------------+
172 | Key | Value |
173 +------------------+-----------------------------------------------------+
174 | Address | 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm |
175 +------------------+-----------------------------------------------------+
176 | Location | 8c411c02148d7ff |
177 +------------------+-----------------------------------------------------+
178 | Payer | 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux |
179 +------------------+-----------------------------------------------------+
180 | Nonce | 1 |
181 +------------------+-----------------------------------------------------+
182 | Fee (DC) | 55000 |
183 +------------------+-----------------------------------------------------+
184 | Staking Fee (DC) | 500000 |
185 +------------------+-----------------------------------------------------+
186 | Gain (dBi) | 1.2 |
187 +------------------+-----------------------------------------------------+
188 | Elevation | 0 |
189 +------------------+-----------------------------------------------------+
190 | Hash | none |
191 +------------------+-----------------------------------------------------+
192  
193 Preview mode: use --commit to submit the transaction to the network
194 [root@]# helium-wallet hotspots assert --gateway 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm --lat=22.706922 --lon=114.242538 --mode dataonly --commit
195 Password: [hidden]
196 +------------------+-----------------------------------------------------+
197 | Key | Value |
198 +------------------+-----------------------------------------------------+
199 | Address | 146XjfUJXAkthGzBGnifwxWV4tVKyayN76JGZ21TE5jcoUNubJm |
200 +------------------+-----------------------------------------------------+
201 | Location | 8c411c02148d7ff |
202 +------------------+-----------------------------------------------------+
203 | Payer | 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux |
204 +------------------+-----------------------------------------------------+
205 | Nonce | 1 |
206 +------------------+-----------------------------------------------------+
207 | Fee (DC) | 55000 |
208 +------------------+-----------------------------------------------------+
209 | Staking Fee (DC) | 500000 |
210 +------------------+-----------------------------------------------------+
211 | Gain (dBi) | 1.2 |
212 +------------------+-----------------------------------------------------+
213 | Elevation | 0 |
214 +------------------+-----------------------------------------------------+
215 | Hash | P1P8olxrzPJ1f3HWiLxcSincdF5fDLLCt2HbpYBhWwk |
216 +------------------+-----------------------------------------------------+}}}
217
218 Note: The add hotspot and assert location step might need some time to be effect.
219
220 After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.
221
222 == 2.8 Debug Connection ==
223
224 === 2.8.1 Check pkt-fwd running Log ===
225
226 This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
227
228 Below logs shows the gateway receive two LoRaWAN packets.
229
230 {{{root@123123:~# logread -f
231 Sun Nov 14 14:28:10 2021 daemon.info lora_pkt_fwd[3145]: INFO~ [down] PULL_ACK received in 244 ms
232 Sun Nov 14 14:28:11 2021 user.notice iot_keep_alive: Internet Access OK: via eth1
233 Sun Nov 14 14:28:11 2021 user.notice iot_keep_alive: use WAN or WiFi for internet access now
234 Sun Nov 14 14:28:14 2021 daemon.info lora_pkt_fwd[3145]: PKT_FWD~ DATA_UNCONF_UP-> {"DevAddr": "1202EE72", "FCtrl": ["ADR": 1, "ADRACKReq": 0, "ACK": 0, "RFU" : "RFU", "FOptsLen": 0], "FCnt": 16390, "FPort": 2, "MIC": "3D55454B"}
235 Sun Nov 14 14:28:14 2021 daemon.info lora_pkt_fwd[3145]: RXTX~ {"rxpk":[{"tmst":312204124,"time":"2021-11-14T14:28:14.688556Z","chan":0,"rfch":1,"freq":868.100000,"stat":1,"modu":"LORA","datr":"SF12BW125","codr":"4/5","lsnr":-11.2,"rssi":-137,"size":24,"data":"QHLuAhKABkACJg8A5dKDACUrBVNLRVU9"}]}
236 Sun Nov 14 14:28:16 2021 daemon.info lora_pkt_fwd[3145]: PKT_FWD~ DATA_UNCONF_UP-> {"DevAddr": "260BDA6A", "FCtrl": ["ADR": 1, "ADRACKReq": 0, "ACK": 0, "RFU" : "RFU", "FOptsLen": 0], "FCnt": 1382, "FPort": 2, "MIC": "1CA5DAB7"}
237 Sun Nov 14 14:28:16 2021 daemon.info lora_pkt_fwd[3145]: RXTX~ {"rxpk":[{"tmst":313985732,"time":"2021-11-14T14:28:16.446560Z","chan":7,"rfch":0,"freq":867.900000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":10.2,"rssi":-93,"size":42,"data":"QGraCyaAZgUCHMiipojXTdASx9QZcIVAQApHArEe+iGqt9pMSJ232qUc"}]}
238 Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]:
239 Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]: REPORT~ ################## Report at: 2021-11-14 14:28:19 UTC ##################
240 Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]: REPORT~ ### [UPSTREAM] ###
241 Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]: REPORT~ # RF packets received by concentrator: 6
242 Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]: REPORT~ # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
243 Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]: REPORT~ # RF packets forwarded: 6 (161 bytes)
244 Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]: REPORT~ # PUSH_DATA datagrams sent: 6 (1493 bytes)
245 Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]: REPORT~ # PUSH_DATA acknowledged: 0.00%
246 Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]: REPORT~ ### [DOWNSTREAM] ###}}}
247
248
249 === 2.8.2 Check gateway-rs Log ===
250
251 SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.
252
253 [[image:https://wiki.dragino.com/images/thumb/6/6a/Helium-gatewayrs_log.png/600px-Helium-gatewayrs_log.png||height="69" width="600"]]
254
255 Helium-gatewayrs log
256
257 Note: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
258
259 === 2.8.3 View the public key address and animal name ===
260
261 {{{root@123123:~# helium_gateway key info { "address": "13KmbKLdpDfECx19kB2nX4suSzz3GskA4JVqKHAKiJ89kuyJx8T", "name": "great-mint-lizard" }}}}
262
263 [[image:https://wiki.dragino.com/images/thumb/c/ce/Hostpot_key_and_animal_name.png/600px-Hostpot_key_and_animal_name.png||height="323" width="600"]]
264
265 Hostpot key and animal name
266
267 === 2.8.4 Backup/Restor gateway-rs key ===
268
269 For the date-only hotspots, the key is the only unique identifier, the users can backup the key by the button of Download. And once the uses upgrade the gateway or the gateway lose the key, the gateway-rs will generate a new key for which the data-only hotspot is the new unit. so if the user would restore to last time which can upload your backup key to the gateway by the button of upload.
270
271 [[image:https://wiki.dragino.com/images/thumb/e/ef/Backup_and_restore_key.png/600px-Backup_and_restore_key.png||height="343" width="600"]]
272
273 Backup and restore key
274
275 == 2.9 Forward the data to the other server ==
276
277 === 2.9.1 Introduction ===
278
279 The Dragino gateway has supports the double server settings.
280
281 Users can back to the page of Semtech UDP to configure other server settings.
282
283 === 2.9.2 Example ===
284
285 The following takes The Things Network as another LoRaWAN server as an example,
286
287 ==== 2.9.2.1 Step 1: Back to Semtech UDP page ====
288
289 [[image:https://wiki.dragino.com/images/thumb/2/2c/Helium_Primary_page.png/600px-Helium_Primary_page.png||height="415" width="600"]]
290
291 Back to Semtech UDP page
292
293 ==== 2.9.2.2 Step 2: Configure the double server forwarding ====
294
295 [[image:https://wiki.dragino.com/images/thumb/0/05/TTNv3_Secondary_2.png/600px-TTNv3_Secondary_2.png||height="387" width="600"]]
296
297 Configure the double server
298
299 The user can configure the secondary server and then click the button of Save&Apply.
300
301 == 2.10 Connect Full Hotspot to Helium ==
302
303 = 3. Use Dragino Sensors with Helium =
304
305 == 3.1 How to add up user's end-node with Helium console ==
306
307 === 3.1.1 Step 1:Login the Helium console ===
308
309 User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]
310
311 [[image:https://wiki.dragino.com/images/thumb/8/81/Login_Helium_console.png/600px-Login_Helium_console.png||height="626" width="600"]]
312
313 login Helium console
314
315 === 3.1.2 Step 2:Add up your end-node's key ===
316
317 User add up end-node's key from console ~-~->dervice
318
319 [[image:https://wiki.dragino.com/images/thumb/0/05/To_add_a_device.png/600px-To_add_a_device.png||height="366" width="600"]]
320
321 To add a device
322
323 === 3.1.3 Step 3:Activate the end-node ===
324
325 Users can activate the end-node with OTAA in which the end-node will Join the network from the Helium server **Eventually you will see traffic**
326
327 [[image:https://wiki.dragino.com/images/thumb/4/45/End-node_traffic.png/600px-End-node_traffic.png||height="239" width="600"]]
328
329 end-node traffic.
330
331 == 3.2 How to use decoder ==
332
333 === 3.2.1 Step 1:Users can create decoders on functions ===
334
335 [[image:https://wiki.dragino.com/images/thumb/6/6e/LoRaWAN_Communication_Debug6.png/600px-LoRaWAN_Communication_Debug6.png||height="266" width="600"]]
336
337 Decoder.
338
339 === 3.2.2 Step 2:Add a decoder in functions and apply it to the specified label ===
340
341 [[image:https://wiki.dragino.com/images/thumb/6/60/LoRaWAN_Communication_Debug7.png/600px-LoRaWAN_Communication_Debug7.png||height="271" width="600"]]
342
343 Decoder.
344
345 [[image:https://wiki.dragino.com/images/thumb/9/9a/LoRaWAN_Communication_Debug8.png/600px-LoRaWAN_Communication_Debug8.png||height="269" width="600"]]
346
347 Decoder.
348
349 [[image:https://wiki.dragino.com/images/thumb/6/6b/LoRaWAN_Communication_Debug9.png/600px-LoRaWAN_Communication_Debug9.png||height="307" width="600"]]
350
351 Decoder.
352
353 Add decoder complete.
354
355
356 == 3.3 How to send a downlink to end device from Helium ==
357
358 The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
359
360 The Downlink command comes from this link：[[https:~~/~~/wiki.dragino.com/index.php?title=End_Device_Downlink_Command>>url:https://wiki.dragino.com/index.php?title=End_Device_Downlink_Command]]
361
362 Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
363
364 01 00 00 3C ~-~-> AQAAPA==
365
366 [[image:https://wiki.dragino.com/images/thumb/c/c5/Helium_downlink.png/600px-Helium_downlink.png||height="360" width="600"]]
367
368 Downlink
369
370
371 == 3.4 How to add integration to different IoT Servers ==
372
373 === 3.4.1 TagoIO ===
374
375 The steps to add integration are very simple. Please see the following process.
376
377 [[image:https://wiki.dragino.com/images/thumb/c/ce/Helium-togo1.jpg/600px-Helium-togo1.jpg||height="284" width="600"]]
378
379 TagoIO.
380
381 Generate the authorization code and then copy it.
382
383 [[image:https://wiki.dragino.com/images/thumb/5/5e/Helium-togo2.png/600px-Helium-togo2.png||height="197" width="600"]]
384
385 TagoIO.
386
387 Apply Integration to Label.
388
389 [[image:https://wiki.dragino.com/images/thumb/3/39/Helium-togo3.png/600px-Helium-togo3.png||height="270" width="600"]]
390
391 TagoIO.
392
393 [[image:https://wiki.dragino.com/images/thumb/a/aa/Helium-togo4.png/600px-Helium-togo4.png||height="210" width="600"]]
394
395 TagoIO.
396
397 Click LoRaWAN Helium,select the device.
398
399 [[image:https://wiki.dragino.com/images/thumb/d/d0/Helium-togo5.png/600px-Helium-togo5.png||height="338" width="600"]]
400
401 TagoIO.
402
403 Fill in DEVEUI and create my device.
404
405 [[image:https://wiki.dragino.com/images/thumb/2/20/Helium-togo6.png/600px-Helium-togo6.png||height="434" width="600"]]
406
407 TagoIO.
408
409 === 3.4.2 Cayenne ===
410
411 The process of creating devices is similar to Tago.
412
413 [[image:https://wiki.dragino.com/images/thumb/f/fa/Helium-Cayenne1.png/600px-Helium-Cayenne1.png||height="246" width="600"]]
414
415 Cayenne.
416
417 [[image:https://wiki.dragino.com/images/thumb/6/6a/Helium-Cayenne2.png/600px-Helium-Cayenne2.png||height="296" width="600"]]
418
419 Cayenne.
420
421 [[image:https://wiki.dragino.com/images/thumb/2/24/Helium-Cayenne3.png/600px-Helium-Cayenne3.png||height="276" width="600"]]
422
423 Cayenne.
424
425 [[image:https://wiki.dragino.com/images/thumb/b/b2/Helium-Cayenne4.png/600px-Helium-Cayenne4.png||height="358" width="600"]]
426
427 Cayenne.
428
429 [[image:https://wiki.dragino.com/images/thumb/3/37/Helium-Cayenne5.jpg/600px-Helium-Cayenne5.jpg||height="341" width="600"]]
430
431 Cayenne.
432
433 [[image:https://wiki.dragino.com/images/thumb/1/1d/Helium-Cayenne6.jpg/600px-Helium-Cayenne6.jpg||height="326" width="600"]]
434
435 Cayenne.
436
437 == 3.5 Trouble Shooting ==
438
439 === 3.5.1 Trouble to Join Helium ===
440
441 Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
442
443 1) You are out of Helium Gateway coverage. (If you have other end nodes, you can check whether they work and what is the signal strength you see in the platform)
444
445 2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
446
447 3) You have input the wrong keys into Helium Platform ( You can send us the screenshots for the keys and Dragino support team can check for you)
448
449
450 === 3.5.2 Packet Loss for AU915 / US915 Band ===
451
452 The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
453
454 The reason for this problem is that the node does not lock the channel after joining the network.
455
456 Solution:
457
458 (1)If the user does not have a device to upgrade the firmware, you can use the AT+CHE command or the downlink command to set the channel. It is best to turn off the adaptive rate (ADR).Reset the device after setting the channel.
459
460 * AT Command: AT+CHE
461
462 * Example:AT+CHE=1 ~/~/set channel mode to 1
463
464 * Downlink Command: 0x24
465
466 Format: Command Code (0x24) followed by 1 bytes channel value.
467
468 If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
469
470 * Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
471
472 * Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
473
474 (2)If the user has a device to upgrade the firmware, it is better to upgrade the device to the latest version. The latest version has fixed the problem that the AU915/US915 frequency does not lock the channel.
475
476 The latest firmware for end node will have this bug fixed.