Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 2 removed)
  • image-20220912161818-1.png
  • image-20230320141404-1.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Xiaoling
	1	+XWiki.Xiaoye

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,29 +33,28 @@
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 =
37	37
38		-== 2.1  Prerequisites ==
	37	+= **2.  Connect Data-Only Hotspot to Helium** =
39	39
	39	+== **2.1  Prerequisites** ==
40	40
	41	+
41	41	* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
42	42
	44	+== **2.2  Step 1: Configure Frequency Band** ==
43	43
44	44
45		-== 2.2  Step 1: Configure Frequency Band ==
46		-
47		-
48	48	//Each country has a requirement for frequency region. Choose the right one for your area.//
49	49
50	50	[[image:image-20220531175337-1.png]]
51	51
52	52
53		-== 2.3  Step 2: Download the Helium-gateway-rs ==
54	54
	53	+== **2.3  Step 2: Download the Helium-gateway-rs** ==
55	55
	55	+
56	56	//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
57	57
58		-
59	59	[[image:image-20220615150600-1.png||height="559" width="1045"]]
60	60
61	61
...	...	@@ -71,9 +71,10 @@
71	71	[[image:image-20220615150717-3.png||height="605" width="1039"]]
72	72
73	73
74		-== 2.4  Step 3: Install the Helium-gateway-rs ==
75	75
	74	+== **2.4  Step 3: Install the Helium-gateway-rs** ==
76	76
	76	+
77	77	//Click **Install Helium Server** to install gateway-rs.//
78	78
79	79	[[image:image-20220615150734-4.png||height="619" width="1035"]]
...	...	@@ -84,9 +84,10 @@
84	84	(% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
85	85
86	86
87		-== 2.5  Step 4: Save&start the Helium Server ==
88	88
	88	+== **2.5  Step 4: Save&start the Helium Server** ==
89	89
	90	+
90	90	//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
91	91
92	92
...	...	@@ -99,9 +99,10 @@
99	99	[[image:image-20220615151057-6.png||height="580" width="1026"]]
100	100
101	101
102		-== 2.6  Step 5: Check Gateway Connection before onboarding ==
103	103
	104	+== **2.6  Step 5: Check Gateway Connection before onboarding** ==
104	104
	106	+
105	105	//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.//
106	106
107	107	(((
...	...	@@ -114,9 +114,10 @@
114	114	(% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
115	115
116	116
117		-== 2.7  Step 6: Onboarding Data-Only Hotspot ==
118	118
	120	+== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
119	119
	122	+
120	120	(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
121	121
122	122
...	...	@@ -310,12 +310,13 @@
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
	316	+
313	313
314	314	)))
315	315
316		-== 2.8  Debug Connection ==
	320	+== **2.8  Debug Connection** ==
317	317
318		-=== 2.8.1  Check pkt-fwd running Log ===
	322	+=== **2.8.1  Check pkt-fwd running Log** ===
319	319
320	320
321	321	//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
...	...	@@ -346,9 +346,10 @@
346	346	)))
347	347
348	348
349		-=== 2.8.2  Check gateway-rs Log ===
350	350
	354	+=== **2.8.2  Check gateway-rs Log** ===
351	351
	356	+
352	352	//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
353	353
354	354	[[image:image-20220531175809-7.png]]
...	...	@@ -357,9 +357,10 @@
357	357	(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
358	358
359	359
360		-=== 2.8.3  View the public key address and animal name ===
361	361
	366	+=== **2.8.3  View the public key address and animal name** ===
362	362
	368	+
363	363	(% class="box" %)
364	364	(((
365	365	(((
...	...	@@ -381,9 +381,10 @@
381	381	Hostpot key and animal name
382	382
383	383
384		-=== 2.8.4  Backup/Restor gateway-rs key ===
385	385
	391	+=== **2.8.4  Backup/Restor gateway-rs key** ===
386	386
	393	+
387	387	(((
388	388	//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.//
389	389	)))
...	...	@@ -391,24 +391,12 @@
391	391	[[image:image-20220531175919-9.png]]
392	392
393	393
394		-=== 2.8.5  How to manually download helium gateway-rs via SSH access to the gateway Linux console ===
395	395
	402	+== **2.9  Forward the data to the other server** ==
396	396
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]]
	404	+=== **2.9.1  Introduction** ===
400	400
401		-opkg install helium-gateway-rs-dragino.ipk
402		-)))
403	403
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		-
412	412	(((
413	413	//The Dragino gateway has supports the double server settings.//
414	414	)))
...	...	@@ -416,10 +416,11 @@
416	416	(((
417	417	//Users can back to the page of Semtech UDP to configure other server settings.//
418	418
	414	+
419	419
420	420	)))
421	421
422		-=== 2.9.2  Example ===
	418	+=== **2.9.2  Example** ===
423	423
424	424
425	425	//The following takes The Things Network as another LoRaWAN server as an example.//
...	...	@@ -444,17 +444,20 @@
444	444	//The user can configure the secondary server and then click the button of **Save&Apply**.//
445	445
446	446
447		-== 2.10  Connect Full Hotspot to Helium ==
448	448
	444	+== **2.10  Connect Full Hotspot to Helium** ==
449	449
450	450
451		-= 3.  Use Dragino Sensors with Helium =
452	452
453		-== 3.1  How to add up user's end-node with Helium console ==
	448	+= **3.  Use Dragino Sensors with Helium** =
454	454
455		-=== 3.1.1  Step 1: Login the Helium console ===
456	456
	451	+== **3.1  How to add up user's end-node with Helium console** ==
457	457
	453	+
	454	+=== **3.1.1  Step 1: Login the Helium console** ===
	455	+
	456	+
458	458	//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
459	459
460	460	[[image:image-20220531180150-12.png]]
...	...	@@ -462,9 +462,10 @@
462	462	login Helium console
463	463
464	464
465		-=== 3.1.2  Step 2: Add up your end-node's key ===
466	466
	465	+=== **3.1.2  Step 2: Add up your end-node's key** ===
467	467
	467	+
468	468	//User add up end-node's key from console ~-~->dervice//
469	469
470	470	[[image:image-20220531180224-13.png]]
...	...	@@ -472,9 +472,10 @@
472	472	To add a device
473	473
474	474
475		-=== 3.1.3  Step 3: Activate the end-node ===
476	476
	476	+=== **3.1.3  Step 3: Activate the end-node** ===
477	477
	478	+
478	478	(((
479	479	//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**//
480	480	)))
...	...	@@ -484,27 +484,21 @@
484	484	end-node traffic.
485	485
486	486
487		-=== 3.1.4 Check Raw Payload for End Node ===
488	488
	489	+== **3.2  How to use decoder** ==
489	489
490		-Users can check what the end node has uplinked by checking the raw payload. as below:
	491	+=== **3.2.1  Step 1: Users can create decoders on functions** ===
491	491
492		-[[image:image-20220912161818-1.png]]
493	493
494		-
495		-== 3.2  How to use decoder ==
496		-
497		-=== 3.2.1  Step 1: Users can create decoders on functions ===
498		-
499		-
500	500	[[image:image-20220531105325-3.png]]
501	501
502	502	Decoder.
503	503
504	504
505		-=== 3.2.2  Step 2: Add a decoder in functions and apply it to the specified label ===
506	506
	500	+=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
507	507
	502	+
508	508	[[image:image-20220526095629-6.png]]
509	509
510	510
...	...	@@ -516,17 +516,19 @@
516	516	**//Add decoder complete.//**
517	517
518	518
519		-=== 3.2.3  Where is the decoder？ ===
520	520
	515	+=== **3.2.3  Where is the decoder？** ===
521	521
	517	+
522	522	[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
523	523
524	524	[[image:image-20220617140118-1.png||height="550" width="883"]]
525	525
526	526
527		-== 3.3  How to send a downlink to end device from Helium ==
528	528
	524	+== **3.3  How to send a downlink to end device from Helium** ==
529	529
	526	+
530	530	(((
531	531	//The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
532	532	)))
...	...	@@ -549,11 +549,12 @@
549	549	Downlink
550	550
551	551
552		-== 3.4  How to add integration to different IoT Servers ==
553	553
554		-=== 3.4.1  TagoIO ===
	550	+== **3.4  How to add integration to different IoT Servers** ==
555	555
	552	+=== **3.4.1  TagoIO** ===
556	556
	554	+
557	557	**//The steps to add integration are very simple. Please see the following process.//**
558	558
559	559
...	...	@@ -594,9 +594,10 @@
594	594	TagoIO.
595	595
596	596
597		-=== 3.4.2  Cayenne ===
598	598
	596	+=== **3.4.2  Cayenne** ===
599	599
	598	+
600	600	//The process of creating devices is similar to Tago.//
601	601
602	602	[[image:image-20220526101616-18.png||height="456" width="1097"]]
...	...	@@ -629,31 +629,33 @@
629	629	Cayenne.
630	630
631	631
632		-== 3.5  Trouble Shooting ==
633	633
634		-=== 3.5.1  Data-Only Hotspot is not connecting to Helium console ===
	632	+== **3.5  Trouble Shooting** ==
635	635
636	636
637		-//**The Data-only hotspot has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
	635	+=== 3.5.1 Trouble connecting Helium Console ===
638	638
639	639
640		-1). The hotspot does not finish the onboarding to the helium blockchain.
	638	+//**The LPS8/LPS8N/DLOS8/DLOS8N/LG308/LG308N/LIG16/LPS8V2 has finished the software installation and confirmation, But it is not connecting to Helium Console. The possibility is:**//
641	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	643
	641	+1). The device does not finish the onboarding to the helium blockchain.
644	644
645		-=== 3.5.2  End Device can't join Helium via hotspot, stuck in cycle of Joining-Accept. ===
	643	+ after the 23 version of the gateway-rs, Helium requests the user to onboarding the devices to the blockchain, otherwise, your devices are not connecting 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.
646	646
647	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.
	646	+**//The sensor node is not joining the helium network, the helium console shows it is stuck in the cycle of joining-accept. The possibility is~://**
649	649
650	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]]
	649	+1). Your device is not using the region configuration, where you have to use the frequency plan that is compatible with your region.
652	652
	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]]
653	653
654		-=== 3.5.3  Trouble to Join Helium ===
655	655
656	656
	655	+=== **3.5.2  Trouble to Join Helium** ===
	656	+
	657	+
657	657	(((
658	658	**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
659	659
...	...	@@ -674,7 +674,7 @@
674	674
675	675	)))
676	676
677		-=== 3.5.4  Packet Loss for AU915 / US915 Band ===
	678	+=== **3.5.3  Packet Loss for AU915 / US915 Band** ===
678	678
679	679
680	680	(((
...	...	@@ -732,13 +732,4 @@
732	732
733	733	(((
734	734	//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		-
744	744	)))

image-20220912161818-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-53.7 KB

Content

image-20230320141404-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-57.8 KB

Content