Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Change comment:
Uploaded new attachment "image-20221010193621-2.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 4 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoye1 +XWiki.Edwin - Content
-
... ... @@ -212,24 +212,9 @@ 212 212 213 213 = 4. Downlink = 214 214 215 -== 4.1 C onvertHEX toBase64==215 +== 4.1 Chirpstack Downlink Note == 216 216 217 -(% style="color:red" %)**Note: Chirpstack uses base64 to downlink, the end node user manual provides HEX format of the downlink commands. So user needs to convert the HEX to Base64.** 218 218 219 -[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]: 220 - 221 -[[image:image-20221010193350-1.png]] 222 - 223 - 224 -[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]] 225 - 226 -[[image:image-20221010193621-2.png]] 227 - 228 - 229 - 230 -== 4.2 Chirpstack Downlink Note == 231 - 232 - 233 233 [[image:image-20220601102543-2.png]] 234 234 235 235 Convert the data to Base64 ... ... @@ -246,7 +246,7 @@ 246 246 247 247 248 248 249 -== 4. 3Loraserver Downlink Note ==234 +== 4.2 Loraserver Downlink Note == 250 250 251 251 252 252 User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End ... ... @@ -296,8 +296,18 @@ 296 296 MQTT Connect to ChirpStack 297 297 298 298 299 -If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB 284 +((( 285 +(% style="color:red" %)**Note: Chirpstack use base64 to downlink, so need to convert the downlink payload from HEX to base64 [[https:~~/~~/base64.us/>>url:https://base64.us/]]** 286 +))) 300 300 288 +[[image:image-20220531173601-13.png]] 289 + 290 +Choose to Use Hex for Encode 291 + 292 + 293 + 294 +If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB 295 + 301 301 [[image:image-20220531173658-14.png]] 302 302 303 303 ... ... @@ -547,57 +547,13 @@ 547 547 Finish. 548 548 549 549 550 -= **6. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. ** = 551 551 546 += 6. Trouble Shooting = 552 552 553 - Alldatais published to theMQTTtopics. if you wantto store/get thedata, you would have to createanMQTThandler andstore the data yourself.548 +== 6.1 MIC Mismatch or MIC Failed == 554 554 555 -This example will be shown how to store/get all the data in two ways: 556 556 557 -**//1). Chirpstack ~-~-> Node-red//** 558 - 559 -[[image:https://github.com/chirpstack/node-red-contrib-chirpstack/blob/master/example_flow.png?raw=true||alt="example_flow.png"]] 560 - 561 - 562 -Use MQTT in Nore-red to subscribe to topics published by chirpstack-application and then continuously write to a file 563 - 564 -[[image:image-20221012174220-2.png]] 565 - 566 - 567 -Each message is continuously logged to a specified file 568 - 569 -[[image:image-20221012174352-3.png]] 570 - 571 - 572 -**//2). MQTT Sub//** 573 - 574 -If you don't want to store the information via node-red, you can get the output via the subscribe command. 575 - 576 - 577 -**If connecting from the same machine, you can use the following command to receive data:** 578 - 579 -(% class="box infomessage" %) 580 580 ((( 581 -mosquitto_sub -h localhost -t "application/#" -v 582 -))) 583 - 584 - 585 -**Different host** 586 - 587 -(% class="box infomessage" %) 588 -((( 589 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v 590 -))) 591 - 592 -[[image:image-20221012173639-1.png]] 593 - 594 - 595 -= 7. Trouble Shooting = 596 - 597 -== 7.1 MIC Mismatch or MIC Failed == 598 - 599 - 600 -((( 601 601 When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs. 602 602 ))) 603 603
- image-20221012173639-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -56.2 KB - Content
- image-20221012174220-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -14.8 KB - Content
- image-20221012174352-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.0 KB - Content
- image-20221012184501-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.3 KB - Content