Wiki source code of Notes for ChirpStack

Version 131.2 by Xiaoling on 2022/12/26 10:18

version	line-number	content
108.4	1	~ Table of Contents:
1.2	2
1.1	3	{{toc/}}
	4
86.4	5
	6
	7
108.4	8	= 1. Introduction =
1.1	9
108.4	10
53.1	11	(% style="color:black" %)The ChirpStack open-source LoRaWAN Network Server stack provides open-source components for LoRaWAN networks And the Chirpstack supports the users in building a private LoRaWAN Server. For more info please refer to this [[link>>url:https://www.chirpstack.io/]]
1.1	12
1.5	13	(((
51.1	14	(% style="color:black" %)The dragino gateway can connect the ChirpStack server via Semtech UDP or Semtech Basic Station.
108.4	15
	16
1.5	17	)))
1.1	18
108.4	19	(% style="color:blue" %)Prerequisite:
1.1	20
108.4	21	1) Have a Chirstack Server.
1.1	22
54.2	23	[[image:image-20220525100058-1.png]]
1.1	24
1.2	25	ChirpStack home page
1.1	26
54.2	27
1.1	28
108.4	29	2) Gateway model support
	30
1.2	31	(% class="box" %)
	32	(((
1.5	33	(((
1.2	34	Semtech UDP : All Model
108.4	35	Basic Station : [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
	36	(% style="color:red" %)Note (%%): the firmware needs >[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] if use the Bais station
1.2	37	)))
1.5	38	)))
1.1	39
86.5	40
108.4	41	= 2. Semtech UDP =
1.1	42
108.4	43	== 2.1 Step 1. Add the Network-servers ==
1.1	44
108.4	45
1.2	46	The network-Servers address varies depending on the ChirpStack server setup environment
1.1	47
1.3	48	(% class="box" %)
	49	(((
108.5	50	Windows ~-~-> Network-server server * : localhost:8000
	51	Linux ~-~-> Network-server server * : chirpstack-network-server:8000
1.3	52	)))
1.1	53
108.4	54
108.6	55	(% style="color:red" %)If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.
1.1	56
108.4	57
87.2	58	[[image:image-20220531171609-1.png]]
1.2	59
	60	Add the Network-servers
	61
84.2	62
108.6	63	== 2.2 Step 2. Create Gateway-profiles ==
1.2	64
108.6	65
88.2	66	[[image:image-20220531171651-2.png]]
1.2	67
	68	Create Gateway-profiles
	69
84.2	70
108.6	71	== 2.3 Step 3. Create Service-profiles ==
	72
	73
89.2	74	[[image:image-20220531171809-3.png]]
1.2	75
	76	Create Service-profiles
	77
89.3	78
1.2	79	In Step 3. Create Service-profiles, the above parameters can be set. If necessary, you can set them by yourself. This is only an example.
	80
1.4	81	(% style="color:red" %)Note : Before add the gateway, the user needs to complete the preceding three steps.
1.2	82
84.2	83	If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %)
1.2	84
84.2	85
108.7	86	== 2.4 Step 4. Add the gateway ==
1.2	87
108.7	88
1.2	89	The example gateway id is: a840411e96744150
	90
1.5	91	(((
1.4	92	(% style="color:red" %)Note : The Gateway EUI and server addresses must match the ChirpStack configuration.
108.7	93
	94
1.5	95	)))
1.2	96
90.2	97	[[image:image-20220531171923-4.png]](% style="display:none" %)
1.2	98
	99	Add the gateway
	100
108.7	101
	102
91.2	103	[[image:image-20220531172031-5.png]]
1.2	104
	105	Configure the gateway
	106
84.2	107
108.8	108	== 2.5 Step 5. Checking gateway Status ==
	109
	110
92.2	111	[[image:image-20220531172158-6.png]](% style="display:none" %)
1.2	112
84.2	113
108.8	114
1.2	115	gateway Status
	116
93.2	117	[[image:image-20220531172304-7.png]]
1.2	118
	119	gateway Status
	120
86.6	121
108.9	122	= 3. Gateway Registration for Basics Station =
1.2	123
108.9	124	== 3.1 Introduction ==
9.1	125
108.8	126
9.1	127	The [[Semtech Basic Station>>url:https://doc.sm.tc/station/]] backend implements the [[LNS protocol>>url:https://doc.sm.tc/station/tcproto.html]]. It exposes a WebSocket handler to which Basic Station powered gateways can connect.
	128
	129	ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
	130
	131
108.8	132	(% style="color:blue" %)Below list the support products and Requirements:
	133
9.1	134	1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
	135	1. Firmware version since :[[lgw~~-~~-build-v5.4.1651822913>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Test_Firmware/lgw--build-v5.4.1651822913-20220506-1543/]]
	136
108.8	137	(% style="color:blue" %)How to set up chirpStack Basic Station
	138
9.1	139	Users can check out the ChirpStack Basic Station [[link>>https://www.chirpstack.io/gateway-bridge/backends/basic-station/]] and [[forum>>https://forum.chirpstack.io/search?q=basic%20station]]
	140
	141
108.8	142	(% style="color:blue" %)What do you need to prepare
	143
9.1	144	A gateway that can access the internet normally
	145
86.7	146
108.9	147	== 3.2 Add Gateway ==
9.1	148
108.9	149
20.2	150	[[image:image-20220524164205-10.png]]
9.1	151
86.8	152
108.9	153	== 3.3 Access the gateway GUI ==
9.1	154
108.9	155
9.1	156	Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
	157
20.2	158	[[image:image-20220524164319-11.png]]
9.1	159
108.9	160
9.1	161	User need to Choose the ChirpStack/Senet ~-~- Basic Station , input Server URI and Upload the TLS Certificate
	162
	163	(% class="box" %)
	164	(((
	165	Service Provider ~-~-> Choose the ChirpStack/Senet ~-~- Basic Station
	166
	167	LNS URI ~-~-> Enter the LNS URI address, For example : wss:~/~/xxxx.chirpstack.com:433 or ws:~/~/xxxx.chirpstack.com:3001
	168
	169	LNS TLS trust ~-~-> Upload the TLS Certificate
	170	)))
	171
	172	(% class="wikigeneratedid" %)
20.2	173	[[image:image-20220524164341-12.png]]
9.1	174
86.9	175
108.9	176	== 3.4 Start Station ==
9.1	177
108.9	178
108.14	179	When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack.
9.1	180
86.10	181
108.9	182	== 3.5 Successful Connection ==
9.1	183
108.9	184
9.1	185	If user completes the above steps, which will see live date in the ChirpStack.
	186
23.2	187	[[image:image-20220524164448-13.png]]
9.1	188
86.11	189
108.9	190	== 3.6 Trouble Shooting ==
	191
	192
9.1	193	User can check the station log in the logread/system log page.
	194
95.2	195	[[image:image-20220531172837-8.png]]
9.1	196
86.13	197
9.1	198	and recode the station log in the system/Recode log page.
	199
95.2	200	[[image:image-20220531172857-9.png]]
9.1	201
86.12	202
131.2	203	= 4. How the gateway connects to Chirpstack v4 via gateway-bridge =
108.9	204
1.2	205
128.1	206	(% style="color:blue" %)Below list the support products and Requirements:
	207
	208	1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]],[[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]],[[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]],[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]]
	209	1. Firmware version since: [[Chirpstack-gateway-bridge>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/]]
	210
	211	(% style="color:blue" %)How to set up chirpStack Gateway-bridge
	212
	213	Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]]
	214
	215
	216	(% style="color:blue" %)What do you need to prepare
	217
	218	A gateway that can access the internet normally
	219
1.2	220
131.2	221	== 4.1 Configure Packet Forwarder ==
	222
	223
124.1	224	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
121.2	225
124.1	226	* In the LoRaWAN menu, click on LoRaWAN ~-~- Semtech UDP
	227	* Make sure the following settings are set:
	228	Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
	229	LoRaWAN Server Address:** //localhost or 127.0.0.1//
	230	Server port for upstream:** //1700//
	231	Server port for downstream:** //1700//
	232
	233	Click Save & Apply.
	234
	235	[[image:image-20221222114220-2.png\|\|height="748" width="931"]]
	236
	237
131.2	238	== 4.2 Configuring gateway frequency ==
124.1	239
127.1	240
131.2	241	(% style="color:red" %)Note: Gateway frequencies must match
	242
127.1	243	[[image:image-20221222134830-3.png\|\|height="408" width="923"]]
	244
	245
131.2	246	== 4.3 Modify the gateway-bridge configuration file ==
127.1	247
	248
	249	Run the gateway command line command to modify the gateway-bridge configuration file:
	250
	251	(% class="box infomessage" %)
	252	(((
	253	root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
	254	)))
	255
124.1	256	[[image:image-20221222113302-1.png]]
	257
131.2	258
127.1	259	[[image:image-20221222140203-4.png\|\|height="875" width="806"]]
	260
	261
	262	(% class="wikigeneratedid" id="H" %)
	263	After the modification, run the following command: /etc/init.d/chirpstack-gateway-bridge restart
	264
	265
131.2	266	== 4.4 (Re)start and stop gateway-bridge ==
	267
	268
127.1	269	Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
	270
	271	(% class="box infomessage" %)
	272	(((
	273	# start
	274
	275	/etc/init.d/chirpstack-gateway-bridge start
	276
	277	# stop
	278
	279	/etc/init.d/chirpstack-gateway-bridge stop
	280
	281	# restart
	282
	283	/etc/init.d/chirpstack-gateway-bridge restart
	284	)))
	285
131.1	286
131.2	287	== 4.5 Successful Connection ==
131.1	288
131.2	289
131.1	290	[[image:image-20221222141754-5.png\|\|height="488" width="1150"]]
	291
131.2	292
131.1	293	[[image:image-20221222141830-6.png\|\|height="582" width="1153"]]
	294
131.2	295
124.1	296	= 5. Downlink =
	297
131.2	298	== 5.1 Convert HEX to Base64 ==
124.1	299
	300
111.1	301	(% 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.
108.9	302
121.2	303	[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:
111.1	304
	305	[[image:image-20221010193350-1.png]]
	306
	307
	308
121.2	309	[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]
	310
111.1	311	[[image:image-20221010193621-2.png]]
	312
	313
124.1	314	== 5.2 Chirpstack Downlink Note ==
111.1	315
	316
108.2	317	[[image:image-20220601102543-2.png]]
1.2	318
121.2	319	Convert the data to Base64
1.2	320
121.2	321	(% style="display:none" %) (%%)
86.14	322
1.2	323
121.2	324	[[image:image-20220531173236-10.png\|\|height="597" width="1215"]]
1.2	325
121.2	326	Check ChripStack downlink DataRate
86.15	327
121.2	328
	329
65.2	330	[[image:image-20220525101326-11.png]]
1.2	331
121.2	332	Make sure the RX2DR is the same in the end node
1.2	333
86.16	334
124.1	335	== 5.3 Loraserver Downlink Note ==
108.9	336
	337
1.2	338	User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
	339
1.5	340	(((
108.9	341	Below is examples:
1.5	342	)))
1.2	343
1.4	344	(% class="box" %)
	345	(((
	346	Connect to your server via MQTT：
	347	MQTT Client ID: Any
	348	Protocol：mqtt/tcp Server IP：loraserver_ip:1883
1.2	349	User name: User name Password: password
1.4	350	)))
1.2	351
97.2	352	[[image:image-20220531173419-11.png]]
1.2	353
1.5	354	(((
121.2	355	MQTT Connect to ChirpStack
86.17	356
108.9	357
86.17	358
1.5	359	)))
1.2	360
1.5	361	(((
108.9	362	After connect
1.5	363	)))
1.2	364
1.4	365	(% class="box" %)
	366	(((
	367	Subscribe : Format：application/ID/device/ Device EUI/rx
1.2	368	Example: application/7/device/00aedb3da649cb23/rx
1.4	369	)))
1.2	370
1.4	371	(% class="box" %)
	372	(((
	373	Publish:
1.2	374	Format: Top: application/ID/device/ Device EUI/tx
	375	Payload: {"confirmed":true or false,"fPort":XX,"data":"xxxx"}
	376	Example: Top: application/7/device/00aedb3da649cb23/tx
	377	Payload: {"confirmed":true,"fPort":2,"data":"AwEB"}
1.4	378	)))
1.2	379
98.2	380	[[image:image-20220531173519-12.png]]
1.2	381
121.2	382	MQTT Connect to ChirpStack
1.2	383
86.18	384
121.2	385	If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB
1.2	386
100.2	387	[[image:image-20220531173658-14.png]]
1.2	388
108.9	389
1.5	390	(((
1.2	391	Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码：
1.5	392	)))
1.2	393
1.4	394	(% class="box" %)
	395	(((
	396	function sha1_to_base64(sha1)
1.2	397	{
	398	var digits="ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
	399	var base64_rep = "";
	400	var cnt = 0;
	401	var bit_arr = 0;
	402	var bit_num = 0;
1.5	403	\\ for(var n = 0; n < sha1.length; ++n)
1.2	404	{
	405	if(sha1[n] >= 'A' && sha1[n] <= 'Z')
	406	{
121.1	407	ascv = sha1.charCodeAt( n ) - 55;
1.2	408	}
	409	else if(sha1[n] >= 'a' && sha1[n] <= 'z')
	410	{
121.1	411	ascv = sha1.charCodeAt( n ) - 87;
1.2	412	}
	413	else
	414	{
121.1	415	ascv = sha1.charCodeAt( n ) - 48;
1.2	416	}
1.5	417	\\ bit_arr = (bit_arr << 4) \| ascv;
1.2	418	bit_num += 4;
	419	if(bit_num >= 6)
	420	{
1.4	421	bit_num -= 6;
1.2	422	base64_rep += digits[bit_arr >>> bit_num];
1.4	423	bit_arr &= ~~(-1 << bit_num);
1.2	424	}
	425	}
1.5	426	\\ if(bit_num > 0)
1.2	427	{
	428	bit_arr <<= 6 - bit_num;
	429	base64_rep += digits[bit_arr];
	430	}
1.5	431	\\ var padding = base64_rep.length % 4;
	432	\\ if(padding > 0)
1.2	433	{
	434	for(var n = 0; n < 4 - padding; ++n)
	435	{
	436	base64_rep += "=";
	437	}
	438	}
	439	return base64_rep;
	440	}
1.5	441	\\console.log(sha1_to_base64("data"));
	442	\\data is downlink payload required by end node.
1.4	443	e.g console.log(sha1_to_base64("030101"));
	444	result: AwEB
1.2	445	AwEB is the 0x030101's base 64 Encode.
1.5	446	\\e.g console.log(sha1_to_base64("030000"));
1.4	447	result: AwAA
	448	AwAA is 0x030000's base 64 Encode.
	449	)))
1.2	450
86.21	451
108.9	452	== 4.3 Add the decode function in Chirpstack for the payload ==
	453
	454
1.2	455	User enters the payload code according to the steps.
	456
121.2	457	[[image:image-20220531173754-15.png\|\|height="474" width="1334"]]
1.2	458
	459
102.2	460	[[image:image-20220531173856-16.png]]
1.2	461
102.2	462
106.2	463	[[image:image-20220531174120-20.png]]
84.2	464
105.2	465	[[image:image-20220531174046-19.png]]
1.2	466
86.22	467
124.1	468	= 6. Multiply Uplink in ChirpStack =
108.9	469
	470
1.4	471	(((
1.2	472	nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
1.4	473	)))
1.2	474
1.4	475	(((
1.2	476	ChirpStack will auto adjust nbtrans according to uplink rssi. [[link to source>>url:https://github.com/brocaar/chirpstack-network-server/blob/master/internal/adr/adr.go]]
108.9	477
	478
1.4	479	)))
1.2	480
121.2	481	[[image:image-20220526091912-7.png\|\|height="241" width="1336"]]
1.2	482
108.9	483
1.5	484	(((
1.2	485	nbtrans is a field of ADR message, in unconfirm mode, it tells end node how many time it needs to transmit for every frame.
108.9	486
	487
1.5	488	)))
1.2	489
76.2	490	[[image:image-20220525104359-21.png]]
1.2	491
1.4	492	(((
1.2	493	Above behaviour will cause the platform shows below two cases of error:
108.9	494
	495
1.4	496	)))
1.2	497
1.4	498	(((
1.2	499	Error of duplicate Frame Counter
1.4	500	)))
1.2	501
76.2	502	[[image:image-20220525104437-22.png]]
1.2	503
86.23	504
108.9	505
121.2	506	Duplicate transmission in short time
1.2	507
121.2	508	[[image:image-20220601102430-1.png\|\|height="598" width="1319"]]
1.2	509
86.24	510
124.1	511	== 6.1 Solution ==
108.9	512
	513
1.2	514	This example uses the Windows version as a template, other versions can refer to this. Similiar reference: [[https:~~/~~/confluence.alitecs.de/plugins/servlet/mobile?contentId=79790102#content/view/79790102>>url:https://confluence.alitecs.de/plugins/servlet/mobile?contentId=79790102#content/view/79790102]]
	515
108.9	516
1.5	517	(((
108.11	518	(% style="color:blue" %)1. Install the GO compilation environment: Download the corresponding version of the Go compiler at [[https:~~/~~/go.dev/dl/>>url:https://go.dev/dl/]] and install it.
108.9	519
	520
1.5	521	)))
1.2	522
79.2	523	[[image:image-20220525104532-24.png]]
1.2	524
86.25	525
108.9	526	installation path:
1.2	527
79.2	528	[[image:image-20220525104554-25.png]]
1.2	529
86.25	530
108.9	531
1.5	532	(((
108.11	533	(% style="color:blue" %)2. Environment variable settings:
1.5	534	)))
1.2	535
1.5	536	(((
1.2	537	1) Open Computer -> Properties -> Advanced System Settings -> Environment Variables and add a "new" system variable:
1.5	538	)))
1.2	539
1.5	540	(((
108.9	541	2) Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
1.5	542	)))
1.2	543
43.2	544	[[image:image-20220524165433-33.png]]
1.2	545
86.26	546
108.9	547	3) Modify the system variable Path and add C:\Go\bin\:
1.2	548
43.2	549	[[image:image-20220524165452-34.png]]
1.2	550
106.3	551
1.2	552	User variable setting file generation directory: D:\go:
	553
43.2	554	[[image:image-20220524165517-35.png]]
1.2	555
86.27	556
1.2	557
108.11	558	(% style="color:blue" %)3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.
108.9	559
1.2	560	The name of the plugin: Example ADR plugin:
	561
48.2	562	[[image:image-20220524165540-36.png]]
1.2	563
	564	Set Nbtrans: Nbtrans=1 (Nbtrans is the number of retransmissions, if it is 1, no retransmission, it is recommended to be 1). To enable it, you need to uncomment.
	565
48.2	566	[[image:image-20220524165557-37.png]]
1.2	567
86.28	568
1.2	569
108.11	570	(% style="color:blue" %)4. Compile the ADR configuration file and generate the exe file.
108.9	571
1.2	572	1) Create a folder named adr-setting
	573
	574	2) Open the adr-setting folder
	575
	576	3) Put adr.setting.go in this folder.
	577
	578	4) Open the computer cmd and run the following commands in sequencecd adr-setting
	579
	580	go mod init adr-setting
	581
	582	go get github.com/brocaar/chirpstack-network-server/v3/adr
	583
	584	go get github.com/hashicorp/go-plugin
	585
	586	go get adr-setting
	587
	588	go build
	589
	590	5) Finally generate this file：
	591
48.2	592	[[image:image-20220524165623-38.png]]
1.2	593
86.29	594
1.2	595
108.11	596	(% style="color:blue" %)5. Add the plugin and run the plugin.
108.9	597
1.5	598	(((
1.2	599	The exe file generated in the previous step is placed in the same root directory as chirpstack-network-server.toml, and the ADR plugin is added to the toml file. The location of the addition is as follows:
1.5	600	)))
1.2	601
48.2	602	[[image:image-20220524165641-39.png]]
1.2	603
1.4	604	(((
1.5	605	(((
1.2	606	For example: adr_plugins=[“adr-setting”]
1.4	607	)))
1.5	608	)))
1.2	609
1.4	610	* (((
1.5	611	(((
1.4	612	Adding a single plugin format is adr_plugins=["filename"]
	613	)))
1.5	614	)))
1.2	615
1.4	616	* (((
1.5	617	(((
1.4	618	Adding multiple plugins The format is adr_plugins=["file name 1", "file name 2",...]
	619	)))
1.5	620	)))
1.2	621
1.4	622	(((
1.5	623	(((
1.2	624	Finally, re-run chirpstack-network-server.exe, and then select the plugin you just compiled in Device-profiles,
1.4	625	)))
1.5	626	)))
1.2	627
79.2	628	[[image:image-20220525104647-26.png]]
1.2	629
	630	Finish.
	631
86.30	632
124.1	633	= 7. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
108.9	634
1.2	635
115.1	636	All data is published to the MQTT topics. if you want to store/get the data, you would have to create an MQTT handler and store the data yourself.
1.2	637
115.1	638	This example will be shown how to store/get all the data in two ways:
108.9	639
115.1	640	//1). Chirpstack ~-~-> Node-red//
	641
	642
117.1	643	[[image:image-20221012184501-1.png]]
115.1	644
121.2	645
120.1	646	Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
115.1	647
	648	[[image:image-20221012174220-2.png]]
	649
	650
120.1	651	[[image:image-20221012184655-3.png\|\|height="395" width="1049"]]
	652
	653
121.2	654	Each message is continuously logged to a specified file
115.1	655
	656	[[image:image-20221012174352-3.png]]
	657
	658
	659	//2). MQTT Sub//
	660
	661	If you don't want to store the information via node-red, you can get the output via the subscribe command.
	662
	663
	664	If connecting from the same machine, you can use the following command to receive data:
	665
	666	(% class="box infomessage" %)
1.4	667	(((
115.1	668	mosquitto_sub -h localhost -t "application/#" -v
	669	)))
	670
	671
	672	Different host
	673
	674	(% class="box infomessage" %)
	675	(((
	676	mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
	677	)))
	678
	679	[[image:image-20221012173639-1.png]]
	680
	681
124.1	682	= 8. Trouble Shooting =
115.1	683
124.1	684	== 8.1 MIC Mismatch or MIC Failed ==
115.1	685
	686
	687	(((
1.2	688	When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
1.4	689	)))
1.2	690
1.4	691	(((
1.2	692	Under normal circumstances, users need to change the APPKEY to solve this problem.
131.2	693
	694
	695
	696
1.4	697	)))

Wiki source code of Notes for ChirpStack

Applications

Navigation