<
From version < 150.1 >
edited by Kilight Cao
on 2023/05/31 16:37
To version < 140.1 >
edited by Kilight Cao
on 2023/05/27 11:57
>
Change comment: Uploaded new attachment "image-20230527115750-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -569,13 +569,11 @@
569 569  )))
570 570  
571 571  
572 -== 6.4  Add the decode function in Chirpstack for the payload ==
572 +== 6.3  Add the decode function in Chirpstack for the payload ==
573 573  
574 574  
575 575  User enters the payload code according to the steps.
576 576  
577 -Add the node device decoder you are using. The decoder for each node device is different. The decoder is found in this link: **[[decoder for dragino end node>>https://github.com/dragino/dragino-end-node-decoder]]**
578 -
579 579  [[image:image-20220531173754-15.png||height="474" width="1334"]]
580 580  
581 581  
... ... @@ -800,64 +800,12 @@
800 800  
801 801  [[image:image-20221012173639-1.png]]
802 802  
803 -= 9.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
804 804  
802 += 9.  Trouble Shooting =
805 805  
806 -LPS8v2 includes a local TTN 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:
804 +== 9. MIC Mismatch or MIC Failed ==
807 807  
808 -* LHT65N register on LPS8v2 Built-In ChirpStack server already
809 -* The user is able to see the data on the built-in ChirpStack server device page.
810 810  
811 -Below are the steps to plot the sensor data on LPS8v2 Node-Red.
812 -
813 -
814 -== 9.1 Link Node-Red to Local ChirpStack ==
815 -
816 -
817 -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"]]**
818 -
819 -For more information on importing Input Flow, check out this link: **[[Import Input Flow for Dragino Sensors>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0ImportInputFlowforDraginoSensors]]**
820 -
821 -After importing the Input Flow is complete, the user needs to edit the MQTT in the node
822 -
823 -
824 -(% style="color:blue" %)**1. Change the Topic**
825 -
826 -Topic modifies it to the following format:
827 -
828 -**application/(% style="color:red" %)Application ID(%%)/device/(% style="color:red" %)End device ID(%%)/event/up**
829 -
830 -[[image:image-20230527143923-1.png||height="588" width="1132"]]
831 -
832 -
833 -
834 -(% style="color:blue" %)**2. Enter the MQTT configuration information**
835 -
836 -[[image:image-20230527144206-2.png||height="590" width="1136"]]
837 -
838 -
839 -(% style="color:blue" %)3. **Finally, click "Update" and Deploy**
840 -
841 -"Connected" indicates that the Link Node-red to Local Chirpstack is normal.
842 -
843 -[[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"]]
844 -
845 -
846 -== 9.2 Check result. ==
847 -
848 -
849 -Users can check logs by adding debug.
850 -
851 -Browser access: **Node-Red-Server-Address:1880/ui**
852 -
853 -[[image:image-20230529150923-1.png||height="424" width="1118"]]
854 -
855 -
856 -= 10.  Trouble Shooting =
857 -
858 -== 10.1  MIC Mismatch or MIC Failed ==
859 -
860 -
861 861  (((
862 862  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
863 863  )))
image-20230527143923-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -222.4 KB
Content
image-20230527144206-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -224.2 KB
Content
image-20230529150923-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -87.2 KB
Content
image-20230531162943-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -84.6 KB
Content
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0