Changes for page Notes for Helium
Last modified by Edwin Chen on 2024/03/25 08:22
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -5,58 +5,56 @@ 5 5 6 6 7 7 8 -= **1. Use Dragino Gateways/Hotspots with Helium**=8 += 1. Use Dragino Gateways/Hotspots with Helium = 9 9 10 -== **1.1 Support Models**==10 +== 1.1 Support Models == 11 11 12 12 13 - //There are three types of hotspots that can connect to Helium. They are (% style="color:#4f81bd" %)**full-hotspot**(%%), (% style="color:#4f81bd" %)**light hotspot** (%%)and (% style="color:#4f81bd" %)**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.//13 +There are three types of hotspots that can connect to Helium. They are (% style="color:#4f81bd" %)**full-hotspot**(%%), (% style="color:#4f81bd" %)**light hotspot** (%%)and (% style="color:#4f81bd" %)**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. 14 14 15 15 ((( 16 - //Dragino has different gateway models that support different types.//16 +Dragino has different gateway models that support different types. 17 17 ))) 18 18 19 -(% border="1" style="background-color:#fff fcc; width:510px" %)20 -|(% colspan="4" style="width:589px " %)(% style="color:green" %)**Dragino Hotspots for Helium**21 -|(% style="color: green; width:132px" %)**Model**|(% style="color:green; width:126px" %)**Hotspot Types**|(% style="color:green; width:121px" %)**Mining Ability**|(% style="color:green; width:203px" %)**Configure Instruction**19 +(% border="1" style="background-color:#f2f2f2; width:510px" %) 20 +|(% colspan="4" style="width:589px;background-color:#D9E2F3;color:#0070C0" %)**Dragino Hotspots for Helium** 21 +|(% style="color:#0070C0; width:132px" %)**Model**|(% style="color:#0070C0; width:126px" %)**Hotspot Types**|(% style="color:#0070C0; width:121px" %)**Mining Ability**|(% style="color:#0070C0; width:203px" %)**Configure Instruction** 22 22 |(% style="width:132px" %)((( 23 23 [[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]], 24 24 25 25 [[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]] 26 -)))|(% style="color:#4f81bd;width:126px" %)**Data-Only Hotspot**|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:203px" %)[[Data-Only Hotspot Instruction>>||anchor="H2.A0ConnectData-OnlyHotspottoHelium"]]27 -|(% style="width:132px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% style="color:#4f81bd;width:126px" %)**Full Hotspo**t|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/full-hotspots]]|(% style="color:green; width:203px" %)[[Full Hotspot Instuction-Not Finish>>doc:Main.User Manual for All Gateway models.HP0D.WebHome]]26 +)))|(% width:126px" %)Data-Only Hotspot|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:203px" %)[[Data-Only Hotspot Instruction>>||anchor="H2.A0ConnectData-OnlyHotspottoHelium"]] 27 +|(% style="width:132px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% width:126px" %)Full Hotspot|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/full-hotspots]]|(% style="color:green; width:203px" %)[[Full Hotspot Instuction-Not Finish>>doc:Main.User Manual for All Gateway models.HP0D.WebHome]] 28 28 29 29 (% style="color:blue" %)**Frequencies on the Helium Network** 30 30 31 31 * //The frequencies currently available are CN470/EU868/US915/AU915// 32 32 33 - 34 - 35 35 (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]** 36 36 37 37 36 += 2. Connect Data-Only Hotspot to Helium = 38 38 39 -= **2.Connect Data-Only Hotspotto Helium**=38 +== 2.1 Prerequisites == 40 40 41 -== **2.1 Prerequisites** == 42 42 43 - 44 44 * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]// 45 45 46 -== **2.2 Step 1: Configure Frequency Band** == 47 47 44 +== 2.2 Step 1: Configure Frequency Band == 48 48 46 + 49 49 //Each country has a requirement for frequency region. Choose the right one for your area.// 50 50 51 51 [[image:image-20220531175337-1.png]] 52 52 53 53 52 +== 2.3 Step 2: Download the Helium-gateway-rs == 54 54 55 -== **2.3 Step 2: Download the Helium-gateway-rs** == 56 56 57 - 58 58 //Click Download Helium Server and the gateway will download the Helium-gateway-rs// 59 59 57 + 60 60 [[image:image-20220615150600-1.png||height="559" width="1045"]] 61 61 62 62 ... ... @@ -72,7 +72,7 @@ 72 72 [[image:image-20220615150717-3.png||height="605" width="1039"]] 73 73 74 74 75 -== **2.4 Step 3: Install the Helium-gateway-rs**==73 +== 2.4 Step 3: Install the Helium-gateway-rs == 76 76 77 77 78 78 //Click **Install Helium Server** to install gateway-rs.// ... ... @@ -85,24 +85,24 @@ 85 85 (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.** 86 86 87 87 86 +== 2.5 Step 4: Save&start the Helium Server == 88 88 89 -== **2.5 Step 4: Save&start the Helium Server** == 90 90 91 - 92 92 //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.// 93 93 91 + 94 94 [[image:image-20220615150903-5.png||height="592" width="1031"]] 95 95 96 96 95 + 97 97 //Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.// 98 98 99 99 [[image:image-20220615151057-6.png||height="580" width="1026"]] 100 100 101 101 101 +== 2.6 Step 5: Check Gateway Connection before onboarding == 102 102 103 -== **2.6 Step 5: Check Gateway Connection before onboarding** == 104 104 105 - 106 106 //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.// 107 107 108 108 ((( ... ... @@ -115,10 +115,9 @@ 115 115 (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.** 116 116 117 117 116 +== 2.7 Step 6: Onboarding Data-Only Hotspot == 118 118 119 -== **2.7 Step 6: Onboarding Data-Only Hotspot** == 120 120 121 - 122 122 (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .** 123 123 124 124 ... ... @@ -128,7 +128,7 @@ 128 128 129 129 130 130 ((( 131 -(% style="color: red" %)//**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.**//128 +(% style="color:blue" %)//**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.**// 132 132 ))) 133 133 134 134 (% class="box" %) ... ... @@ -155,6 +155,7 @@ 155 155 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 156 156 ))) 157 157 155 + 158 158 ((( 159 159 (% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.** 160 160 ))) ... ... @@ -162,7 +162,7 @@ 162 162 163 163 164 164 ((( 165 -(% style="color: red" %)//**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.**//163 +(% style="color:blue" %)//**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.**// 166 166 ))) 167 167 168 168 (% class="box" %) ... ... @@ -198,7 +198,7 @@ 198 198 199 199 200 200 201 -(% style="color: red" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//199 +(% style="color:blue" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**// 202 202 203 203 204 204 (% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.** ... ... @@ -249,7 +249,7 @@ 249 249 ((( 250 250 251 251 252 -(% style="color: red" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//250 +(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**// 253 253 ))) 254 254 255 255 (% class="box" %) ... ... @@ -303,6 +303,7 @@ 303 303 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+ 304 304 ))) 305 305 304 + 306 306 ((( 307 307 (% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.** 308 308 ))) ... ... @@ -310,13 +310,12 @@ 310 310 ((( 311 311 //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.// 312 312 313 - 314 314 315 315 ))) 316 316 317 -== **2.8 Debug Connection**==315 +== 2.8 Debug Connection == 318 318 319 -=== **2.8.1 Check pkt-fwd running Log**===317 +=== 2.8.1 Check pkt-fwd running Log === 320 320 321 321 322 322 //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// ... ... @@ -347,10 +347,9 @@ 347 347 ))) 348 348 349 349 348 +=== 2.8.2 Check gateway-rs Log === 350 350 351 -=== **2.8.2 Check gateway-rs Log** === 352 352 353 - 354 354 //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 355 355 356 356 [[image:image-20220531175809-7.png]] ... ... @@ -359,7 +359,7 @@ 359 359 (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.** 360 360 361 361 362 -=== **2.8.3 View the public key address and animal name**===359 +=== 2.8.3 View the public key address and animal name === 363 363 364 364 365 365 (% class="box" %) ... ... @@ -383,10 +383,9 @@ 383 383 Hostpot key and animal name 384 384 385 385 383 +=== 2.8.4 Backup/Restor gateway-rs key === 386 386 387 -=== **2.8.4 Backup/Restor gateway-rs key** === 388 388 389 - 390 390 ((( 391 391 //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.// 392 392 ))) ... ... @@ -394,12 +394,24 @@ 394 394 [[image:image-20220531175919-9.png]] 395 395 396 396 393 +=== 2.8.5 How to manually download helium gateway-rs via SSH access to the gateway Linux console === 397 397 398 -== **2.9 Forward the data to the other server** == 399 399 400 -=== **2.9.1 Introduction** === 396 +(% class="box infomessage" %) 397 +((( 398 +cd /tmp;wget -O helium-gateway-rs-dragino.ipk [[https:~~/~~/github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk>>https://github.com/helium/gateway-rs/releases/download/v1.0.0-alpha.33/helium-gateway-v1.0.0-alpha.33-dragino.ipk]] 401 401 400 +opkg install helium-gateway-rs-dragino.ipk 401 +))) 402 402 403 +[[image:image-20230320141404-1.png]] 404 + 405 + 406 +== 2.9 Forward the data to the other server == 407 + 408 +=== 2.9.1 Introduction === 409 + 410 + 403 403 ((( 404 404 //The Dragino gateway has supports the double server settings.// 405 405 ))) ... ... @@ -410,7 +410,7 @@ 410 410 411 411 ))) 412 412 413 -=== **2.9.2 Example**===421 +=== 2.9.2 Example === 414 414 415 415 416 416 //The following takes The Things Network as another LoRaWAN server as an example.// ... ... @@ -435,19 +435,17 @@ 435 435 //The user can configure the secondary server and then click the button of **Save&Apply**.// 436 436 437 437 438 -== **2.10 Connect Full Hotspot to Helium**==446 +== 2.10 Connect Full Hotspot to Helium == 439 439 440 440 441 441 442 -= **3. Use Dragino Sensors with Helium**=450 += 3. Use Dragino Sensors with Helium = 443 443 452 +== 3.1 How to add up user's end-node with Helium console == 444 444 445 -== **3.1Howto add upuser'send-node with Helium console**==454 +=== 3.1.1 Step 1: Login the Helium console === 446 446 447 447 448 -=== **3.1.1 Step 1: Login the Helium console** === 449 - 450 - 451 451 //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]// 452 452 453 453 [[image:image-20220531180150-12.png]] ... ... @@ -455,10 +455,9 @@ 455 455 login Helium console 456 456 457 457 464 +=== 3.1.2 Step 2: Add up your end-node's key === 458 458 459 -=== **3.1.2 Step 2: Add up your end-node's key** === 460 460 461 - 462 462 //User add up end-node's key from console ~-~->dervice// 463 463 464 464 [[image:image-20220531180224-13.png]] ... ... @@ -466,10 +466,9 @@ 466 466 To add a device 467 467 468 468 474 +=== 3.1.3 Step 3: Activate the end-node === 469 469 470 -=== **3.1.3 Step 3: Activate the end-node** === 471 471 472 - 473 473 ((( 474 474 //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**// 475 475 ))) ... ... @@ -479,21 +479,27 @@ 479 479 end-node traffic. 480 480 481 481 486 +=== 3.1.4 Check Raw Payload for End Node === 482 482 483 -== **3.2 How to use decoder** == 484 484 485 - === **3.2.1 Step 1:Users can createdecoderson functions**===489 +Users can check what the end node has uplinked by checking the raw payload. as below: 486 486 491 +[[image:image-20220912161818-1.png]] 487 487 493 + 494 +== 3.2 How to use decoder == 495 + 496 +=== 3.2.1 Step 1: Users can create decoders on functions === 497 + 498 + 488 488 [[image:image-20220531105325-3.png]] 489 489 490 490 Decoder. 491 491 492 492 504 +=== 3.2.2 Step 2: Add a decoder in functions and apply it to the specified label === 493 493 494 -=== **3.2.2 Step 2: Add a decoder in functions and apply it to the specified label** === 495 495 496 - 497 497 [[image:image-20220526095629-6.png]] 498 498 499 499 ... ... @@ -505,19 +505,17 @@ 505 505 **//Add decoder complete.//** 506 506 507 507 518 +=== 3.2.3 Where is the decoder? === 508 508 509 -=== **3.2.3 Where is the decoder?** === 510 510 511 - 512 512 [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]] 513 513 514 514 [[image:image-20220617140118-1.png||height="550" width="883"]] 515 515 516 516 526 +== 3.3 How to send a downlink to end device from Helium == 517 517 518 -== **3.3 How to send a downlink to end device from Helium** == 519 519 520 - 521 521 ((( 522 522 //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~:// 523 523 ))) ... ... @@ -540,12 +540,11 @@ 540 540 Downlink 541 541 542 542 551 +== 3.4 How to add integration to different IoT Servers == 543 543 544 -== **3.4How toadd integration to differentIoTServers**==553 +=== 3.4.1 TagoIO === 545 545 546 -=== **3.4.1 TagoIO** === 547 547 548 - 549 549 **//The steps to add integration are very simple. Please see the following process.//** 550 550 551 551 ... ... @@ -586,10 +586,9 @@ 586 586 TagoIO. 587 587 588 588 596 +=== 3.4.2 Cayenne === 589 589 590 -=== **3.4.2 Cayenne** === 591 591 592 - 593 593 //The process of creating devices is similar to Tago.// 594 594 595 595 [[image:image-20220526101616-18.png||height="456" width="1097"]] ... ... @@ -622,12 +622,31 @@ 622 622 Cayenne. 623 623 624 624 631 +== 3.5 Trouble Shooting == 625 625 626 -== **3.5TroubleShooting**==633 +=== 3.5.1 Data-Only Hotspot is not connecting to Helium console === 627 627 628 -=== **3.5.1 Trouble to Join Helium** === 629 629 636 +//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**// 630 630 638 + 639 +1). The hotspot does not finish the onboarding to the helium blockchain. 640 + 641 + after the 23 version of the gateway-rs, Helium requests the user to onboarding the devices to the blockchain, otherwise, your devices can't connect to the helium console. ~-~--> Please refer to [[Step 2.7>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Helium/#H2.7A0Step6:OnboardingData-OnlyHotspot]] to do it. 642 + 643 + 644 +=== 3.5.2 End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. === 645 + 646 + 647 +Make sure your blockchain region is the same as your hotspot settings. For example, as below, the blockchain is CN region, and software is configure to EU. The hotspot is able to get the OTAA Join Request from End Device on EU region. but due to block chain is CN region, Server will send the Join -Accept in CN region, so end device can't get the OTAA Join Accept. 648 + 649 + 650 +For example, if you are in USA, you have to use the US915 frequency plan. More frequency plans details on the helium network: [[https:~~/~~/docs.helium.com/lorawan-on-helium/frequency-plans>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans]] 651 + 652 + 653 +=== 3.5.3 Trouble to Join Helium === 654 + 655 + 631 631 ((( 632 632 **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 633 633 ... ... @@ -645,11 +645,10 @@ 645 645 ((( 646 646 //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)// 647 647 648 - 649 649 650 650 ))) 651 651 652 -=== **3.5.2Packet Loss for AU915 / US915 Band**===676 +=== 3.5.4 Packet Loss for AU915 / US915 Band === 653 653 654 654 655 655 ((( ... ... @@ -663,7 +663,7 @@ 663 663 ))) 664 664 665 665 ((( 666 -**Solution:** 690 +(% style="color:red" %)**Solution:** 667 667 668 668 669 669 ))) ... ... @@ -683,8 +683,6 @@ 683 683 * ((( 684 684 (% style="color:blue" %)**//Downlink Command: 0x24//** 685 685 686 - 687 - 688 688 689 689 ))) 690 690 ... ... @@ -700,7 +700,6 @@ 700 700 * ((( 701 701 //**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2// 702 702 703 - 704 704 705 705 ))) 706 706 ... ... @@ -710,4 +710,13 @@ 710 710 711 711 ((( 712 712 //The latest firmware for end node will have this bug fixed.// 734 + 735 + 736 +=== 3.5.5 ADR doesn't work in EU868 band. === 737 + 738 + 739 +See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]] 740 + 741 + 742 + 713 713 )))
- image-20220912161818-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +53.7 KB - Content
- image-20230320141404-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +57.8 KB - Content