Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -258,7 +258,7 @@ 258 258 259 259 (% class="box infomessage" %) 260 260 ((( 261 - **/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge configfile > /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml**261 +/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge configfile > /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 262 262 ))) 263 263 264 264 ... ... @@ -268,7 +268,7 @@ 268 268 269 269 (% class="box infomessage" %) 270 270 ((( 271 - **vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml**271 +vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 272 272 ))) 273 273 274 274 [[image:image-20230415165254-1.png||height="583" width="956"]] ... ... @@ -281,7 +281,7 @@ 281 281 282 282 (% class="box infomessage" %) 283 283 ((( 284 - **/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge ~-~-config /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml**284 +/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge ~-~-config /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 285 285 ))) 286 286 287 287 If the gateway-bridge connection is normal, the debug log displays **"connected to mqtt broker"**. ... ... @@ -341,8 +341,7 @@ 341 341 342 342 In the Dragino gateway web interface, you need to configure the Packet Forwarder so that it forwards its data to the port. localhost:1700 or 127.0.0.1:1700 343 343 344 -* In the (% style="color:blue" %)**LoRaWAN**(%%) menu, click on (% style="color:blue" %)**LoRaWAN ~-~- Semtech UDP** 345 - 344 +* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP** 346 346 * Make sure the following settings are set: 347 347 ** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 348 348 ** **LoRaWAN Server Address:** //localhost or 127.0.0.1// ... ... @@ -349,7 +349,7 @@ 349 349 ** **Server port for upstream:** //1700// 350 350 ** **Server port for downstream:** //1700// 351 351 352 - Click (% style="color:blue" %)**Save & Apply**.351 + Click **Save & Apply**. 353 353 354 354 [[image:image-20221222114220-2.png||height="748" width="931"]] 355 355 ... ... @@ -369,7 +369,7 @@ 369 369 370 370 (% class="box infomessage" %) 371 371 ((( 372 - **root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml**371 +root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 373 373 ))) 374 374 375 375 [[image:image-20221222113302-1.png]] ... ... @@ -757,7 +757,7 @@ 757 757 758 758 This example will be shown how to store/get all the data in two ways: 759 759 760 - (% style="color:blue" %)**//1). Chirpstack ~-~-> Node-red//**759 +**//1). Chirpstack ~-~-> Node-red//** 761 761 762 762 763 763 [[image:image-20221012184501-1.png]] ... ... @@ -776,7 +776,7 @@ 776 776 [[image:image-20221012174352-3.png]] 777 777 778 778 779 - (% style="color:blue" %)**//2). MQTT Sub//**778 +**//2). MQTT Sub//** 780 780 781 781 If you don't want to store the information via node-red, you can get the output via the subscribe command. 782 782 ... ... @@ -785,15 +785,15 @@ 785 785 786 786 (% class="box infomessage" %) 787 787 ((( 788 - **mosquitto_sub -h localhost -t "application/#" -v**787 +mosquitto_sub -h localhost -t "application/#" -v 789 789 ))) 790 790 791 791 792 - (% style="color:blue" %)**Different host**791 +**Different host** 793 793 794 794 (% class="box infomessage" %) 795 795 ((( 796 - **mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v**795 +mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v 797 797 ))) 798 798 799 799 [[image:image-20221012173639-1.png]] ... ... @@ -811,5 +811,7 @@ 811 811 ((( 812 812 Under normal circumstances, users need to change the APPKEY to solve this problem. 813 813 813 + 814 + 814 814 815 815 )))