Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 89.1 >
edited by Xiaoye
on 2022/08/17 10:26
To version < 99.3 >
edited by Xiaoling
on 2023/03/23 17:20
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoye
1 +XWiki.Xiaoling
Content
... ... @@ -5,9 +5,9 @@
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 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.//
... ... @@ -33,17 +33,16 @@
33 33  (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
34 34  
35 35  
36 += 2.  Connect Data-Only Hotspot to Helium =
36 36  
37 -= **2.  Connect Data-Only Hotspot to Helium** =
38 +== 2.1  Prerequisites ==
38 38  
39 -== **2.1  Prerequisites** ==
40 40  
41 -
42 42  * //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
43 43  
44 44  
45 45  
46 -== **2.2  Step 1: Configure Frequency Band** ==
45 +== 2.2  Step 1: Configure Frequency Band ==
47 47  
48 48  
49 49  //Each country has a requirement for frequency region. Choose the right one for your area.//
... ... @@ -51,12 +51,12 @@
51 51  [[image:image-20220531175337-1.png]]
52 52  
53 53  
53 +== 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  
58 +
60 60  [[image:image-20220615150600-1.png||height="559" width="1045"]]
61 61  
62 62  
... ... @@ -72,10 +72,9 @@
72 72  [[image:image-20220615150717-3.png||height="605" width="1039"]]
73 73  
74 74  
74 +== 2.4  Step 3: Install the Helium-gateway-rs ==
75 75  
76 -== **2.4  Step 3: Install the Helium-gateway-rs** ==
77 77  
78 -
79 79  //Click **Install Helium Server** to install gateway-rs.//
80 80  
81 81  [[image:image-20220615150734-4.png||height="619" width="1035"]]
... ... @@ -86,10 +86,9 @@
86 86  (% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
87 87  
88 88  
87 +== 2.5  Step 4: Save&start the Helium Server ==
89 89  
90 -== **2.5  Step 4: Save&start the Helium Server** ==
91 91  
92 -
93 93  //By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
94 94  
95 95  
... ... @@ -102,10 +102,9 @@
102 102  [[image:image-20220615151057-6.png||height="580" width="1026"]]
103 103  
104 104  
102 +== 2.6  Step 5: Check Gateway Connection before onboarding ==
105 105  
106 -== **2.6  Step 5: Check Gateway Connection before onboarding** ==
107 107  
108 -
109 109  //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.//
110 110  
111 111  (((
... ... @@ -118,10 +118,9 @@
118 118  (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
119 119  
120 120  
117 +== 2.7  Step 6: Onboarding Data-Only Hotspot ==
121 121  
122 -== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
123 123  
124 -
125 125  (% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
126 126  
127 127  
... ... @@ -315,13 +315,12 @@
315 315  (((
316 316  //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
317 317  
318 -
319 319  
320 320  )))
321 321  
322 -== **2.8  Debug Connection** ==
316 +== 2.8  Debug Connection ==
323 323  
324 -=== **2.8.1  Check pkt-fwd running Log** ===
318 +=== 2.8.1  Check pkt-fwd running Log ===
325 325  
326 326  
327 327  //This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
... ... @@ -352,10 +352,9 @@
352 352  )))
353 353  
354 354  
349 +=== 2.8.2  Check gateway-rs Log ===
355 355  
356 -=== **2.8.2  Check gateway-rs Log** ===
357 357  
358 -
359 359  //SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
360 360  
361 361  [[image:image-20220531175809-7.png]]
... ... @@ -364,10 +364,9 @@
364 364  (% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
365 365  
366 366  
360 +=== 2.8.3  View the public key address and animal name ===
367 367  
368 -=== **2.8.3  View the public key address and animal name** ===
369 369  
370 -
371 371  (% class="box" %)
372 372  (((
373 373  (((
... ... @@ -389,10 +389,9 @@
389 389  Hostpot key and animal name
390 390  
391 391  
384 +=== 2.8.4  Backup/Restor gateway-rs key ===
392 392  
393 -=== **2.8.4  Backup/Restor gateway-rs key** ===
394 394  
395 -
396 396  (((
397 397  //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.//
398 398  )))
... ... @@ -400,12 +400,24 @@
400 400  [[image:image-20220531175919-9.png]]
401 401  
402 402  
394 +=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
403 403  
404 -== **2.9  Forward the data to the other server** ==
405 405  
406 -=== **2.9.1  Introduction** ===
397 +(% class="box infomessage" %)
398 +(((
399 +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]]
407 407  
401 +opkg install helium-gateway-rs-dragino.ipk
402 +)))
408 408  
404 +[[image:image-20230320141404-1.png]]
405 +
406 +
407 +== 2.9  Forward the data to the other server ==
408 +
409 +=== 2.9.1  Introduction ===
410 +
411 +
409 409  (((
410 410  //The Dragino gateway has supports the double server settings.//
411 411  )))
... ... @@ -413,11 +413,10 @@
413 413  (((
414 414  //Users can back to the page of Semtech UDP to configure other server settings.//
415 415  
416 -
417 417  
418 418  )))
419 419  
420 -=== **2.9.2  Example** ===
422 +=== 2.9.2  Example ===
421 421  
422 422  
423 423  //The following takes The Things Network as another LoRaWAN server as an example.//
... ... @@ -442,20 +442,17 @@
442 442  //The user can configure the secondary server and then click the button of **Save&Apply**.//
443 443  
444 444  
447 +== 2.10  Connect Full Hotspot to Helium ==
445 445  
446 -== **2.10  Connect Full Hotspot to Helium** ==
447 447  
448 448  
451 += 3.  Use Dragino Sensors with Helium =
449 449  
450 -= **3.  Use Dragino Sensors with Helium** =
453 +== 3.1  How to add up user's end-node with Helium console ==
451 451  
455 +=== 3.1.1  Step 1: Login the Helium console ===
452 452  
453 -== **3.1  How to add up user's end-node with Helium console** ==
454 454  
455 -
456 -=== **3.1.1  Step 1: Login the Helium console** ===
457 -
458 -
459 459  //User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
460 460  
461 461  [[image:image-20220531180150-12.png]]
... ... @@ -463,10 +463,9 @@
463 463  login Helium console
464 464  
465 465  
465 +=== 3.1.2  Step 2: Add up your end-node's key ===
466 466  
467 -=== **3.1.2  Step 2: Add up your end-node's key** ===
468 468  
469 -
470 470  //User add up end-node's key from console ~-~->dervice//
471 471  
472 472  [[image:image-20220531180224-13.png]]
... ... @@ -474,10 +474,9 @@
474 474  To add a device
475 475  
476 476  
475 +=== 3.1.3  Step 3: Activate the end-node ===
477 477  
478 -=== **3.1.3  Step 3: Activate the end-node** ===
479 479  
480 -
481 481  (((
482 482  //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**//
483 483  )))
... ... @@ -487,21 +487,27 @@
487 487  end-node traffic.
488 488  
489 489  
487 +=== 3.1.4 Check Raw Payload for End Node ===
490 490  
491 -== **3.2  How to use decoder** ==
492 492  
493 -=== **3.2.1  Step 1: Users can create decoders on functions** ===
490 +Users can check what the end node has uplinked by checking the raw payload. as below:
494 494  
492 +[[image:image-20220912161818-1.png]]
495 495  
494 +
495 +== 3.2  How to use decoder ==
496 +
497 +=== 3.2.1  Step 1: Users can create decoders on functions ===
498 +
499 +
496 496  [[image:image-20220531105325-3.png]]
497 497  
498 498  Decoder.
499 499  
500 500  
505 +=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
501 501  
502 -=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
503 503  
504 -
505 505  [[image:image-20220526095629-6.png]]
506 506  
507 507  
... ... @@ -513,19 +513,17 @@
513 513  **//Add decoder complete.//**
514 514  
515 515  
519 +=== 3.2.3  Where is the decoder？ ===
516 516  
517 -=== **3.2.3  Where is the decoder？** ===
518 518  
519 -
520 520  [[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
521 521  
522 522  [[image:image-20220617140118-1.png||height="550" width="883"]]
523 523  
524 524  
527 +== 3.3  How to send a downlink to end device from Helium ==
525 525  
526 -== **3.3  How to send a downlink to end device from Helium** ==
527 527  
528 -
529 529  (((
530 530  //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
531 531  )))
... ... @@ -548,12 +548,11 @@
548 548  Downlink
549 549  
550 550  
552 +== 3.4  How to add integration to different IoT Servers ==
551 551  
552 -== **3.4  How to add integration to different IoT Servers** ==
554 +=== 3.4.1  TagoIO ===
553 553  
554 -=== **3.4.1  TagoIO** ===
555 555  
556 -
557 557  **//The steps to add integration are very simple. Please see the following process.//**
558 558  
559 559  
... ... @@ -594,10 +594,9 @@
594 594  TagoIO.
595 595  
596 596  
597 +=== 3.4.2  Cayenne ===
597 597  
598 -=== **3.4.2  Cayenne** ===
599 599  
600 -
601 601  //The process of creating devices is similar to Tago.//
602 602  
603 603  [[image:image-20220526101616-18.png||height="456" width="1097"]]
... ... @@ -630,12 +630,31 @@
630 630  Cayenne.
631 631  
632 632  
632 +== 3.5  Trouble Shooting ==
633 633  
634 -== **3.5  Trouble Shooting** ==
634 +=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
635 635  
636 -=== **3.5.1  Trouble to Join Helium** ===
637 637  
637 +//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
638 638  
639 +
640 +1). The hotspot does not finish the onboarding to the helium blockchain.
641 +
642 + 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.
643 +
644 +
645 +=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
646 +
647 +
648 +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.
649 +
650 +
651 +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]]
652 +
653 +
654 +=== 3.5.3  Trouble to Join Helium ===
655 +
656 +
639 639  (((
640 640  **//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
641 641  
... ... @@ -653,17 +653,10 @@
653 653  (((
654 654  //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)//
655 655  
656 -4) Your gateway is not onboarding to the helium explore, after 23 versions, the data-only hotspot(Gateway) is requested onboarding to helium explore. ~-~-> Please refer to part 2.7 to do it.
657 -
658 -5). You have to use the frequency plan that is compatible with your region.
659 -
660 -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]]
661 -
662 -
663 663  
664 664  )))
665 665  
666 -=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
677 +=== 3.5.4  Packet Loss for AU915 / US915 Band ===
667 667  
668 668  
669 669  (((
... ... @@ -721,4 +721,13 @@
721 721  
722 722  (((
723 723  //The latest firmware for end node will have this bug fixed.//
735 +
736 +
737 +=== 3.5.5  ADR doesn't work in EU868 band. ===
738 +
739 +
740 +See possibility reason from this link: [[https:~~/~~/github.com/helium/router/issues/858 >>https://github.com/helium/router/issues/858]]
741 +
742 +
743 +
724 724  )))
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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0