Changes for page Notes for ChirpStack
Last modified by Kilight Cao on 2024/02/03 14:38
Change comment:
Uploaded new attachment "image-20231201180103-4.png", version {1}
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Content
-
... ... @@ -848,28 +848,14 @@ 848 848 [[image:image-20221012173639-1.png||height="273" width="1206"]] 849 849 850 850 851 - = 11.How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server=851 +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"]] 856 856 856 += 11. Example: Use Local Server ChirpStack and Node-Red in LPS8v2 = 857 857 858 -**11.1 Generate API Tokens** 859 859 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 - 873 873 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: 874 874 875 875 * LHT65N register on LPS8v2 Built-In ChirpStack server already ... ... @@ -878,7 +878,7 @@ 878 878 Below are the steps to plot the sensor data on LPS8v2 Node-Red. 879 879 880 880 881 -== 1 2.1 Link Node-Red to Local ChirpStack ==867 +== 11.1 Link Node-Red to Local ChirpStack == 882 882 883 883 884 884 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"]]** ... ... @@ -912,7 +912,7 @@ 912 912 [[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"]] 913 913 914 914 915 -== 1 2.2 Check result. ==901 +== 11.2 Check result. == 916 916 917 917 918 918 Users can check logs by adding debug. ... ... @@ -922,9 +922,9 @@ 922 922 [[image:image-20230529150923-1.png||height="424" width="1118"]] 923 923 924 924 925 -= 1 3. Trouble Shooting =911 += 12. Trouble Shooting = 926 926 927 -== 1 3.1 MIC Mismatch or MIC Failed ==913 +== 12.1 MIC Mismatch or MIC Failed == 928 928 929 929 930 930 ((( ... ... @@ -935,7 +935,7 @@ 935 935 Under normal circumstances, users need to change the APPKEY to solve this problem. 936 936 937 937 938 -== 1 3.2 The node is very close to the gateway, but the signal is poor ==924 +== 12.2 The node is very close to the gateway, but the signal is poor == 939 939 940 940 941 941 If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
- image-20231204104802-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -42.4 KB - Content
- image-20231204105201-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -33.3 KB - Content