Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -848,14 +848,28 @@
848	848	[[image:image-20221012173639-1.png||height="273" width="1206"]]
849	849
850	850
851		-How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server
	851	+= 11. How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
852	852
853	853	The following example is based on the built-in ChirpStack server for LPS8V2
854	854
	855	+[[image:image-20231201174640-1.png||height="584" width="1148"]]
855	855
856		-= 11.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
857	857
	858	+**11.1 Generate API Tokens**
858	858
	860	+Access the built-in chirpstack , click "API Key" and "Add API Key".
	861	+
	862	+[[image:image-20231201175118-2.png||height="597" width="1156"]]
	863	+
	864	+Save the generated API Tokens
	865	+
	866	+[[image:image-20231201175648-3.png||height="596" width="1155"]]
	867	+
	868	+[[image:image-20231201180103-4.png||height="413" width="1151"]]
	869	+
	870	+= 12.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
	871	+
	872	+
859	859	LPS8v2 includes a local ChirpStack Server and Node-Red. This example shows how to configure LHT65N to use with the local Node-Red server. This example assumes users already have:
860	860
861	861	* LHT65N register on LPS8v2 Built-In ChirpStack server already
...	...	@@ -864,7 +864,7 @@
864	864	Below are the steps to plot the sensor data on LPS8v2 Node-Red.
865	865
866	866
867		-== 11.1 Link Node-Red to Local ChirpStack ==
	881	+== 12.1 Link Node-Red to Local ChirpStack ==
868	868
869	869
870	870	Users can download the Node-Red decoder from this link and import it into the Node-Red platform:  **[[attach:LHT65N-ChirpStack-node-red.json||target="_blank"]]**
...	...	@@ -898,7 +898,7 @@
898	898	[[image:http://wiki.dragino.com/xwiki/bin/download/Main/Notes%20for%20TTN/WebHome/image-20220914140918-5.png?width=1121&height=602&rev=1.1||alt="image-20220914140918-5.png"]]
899	899
900	900
901		-== 11.2 Check result. ==
	915	+== 12.2 Check result. ==
902	902
903	903
904	904	Users can check logs by adding debug.
...	...	@@ -908,9 +908,9 @@
908	908	[[image:image-20230529150923-1.png||height="424" width="1118"]]
909	909
910	910
911		-= 12.  Trouble Shooting =
	925	+= 13.  Trouble Shooting =
912	912
913		-== 12.1  MIC Mismatch or MIC Failed ==
	927	+== 13.1  MIC Mismatch or MIC Failed ==
914	914
915	915
916	916	(((
...	...	@@ -921,7 +921,7 @@
921	921	Under normal circumstances, users need to change the APPKEY to solve this problem.
922	922
923	923
924		-== 12.2  The node is very close to the gateway, but the signal is poor ==
	938	+== 13.2  The node is very close to the gateway, but the signal is poor ==
925	925
926	926
927	927	If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink