Wiki source code of Notes for ChirpStack

Version 131.1 by Kilight Cao on 2022/12/22 14: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
	41
108.4	42	= 2. Semtech UDP =
1.1	43
108.4	44	== 2.1 Step 1. Add the Network-servers ==
1.1	45
108.4	46
1.2	47	The network-Servers address varies depending on the ChirpStack server setup environment
1.1	48
1.3	49	(% class="box" %)
	50	(((
108.5	51	Windows ~-~-> Network-server server * : localhost:8000
	52	Linux ~-~-> Network-server server * : chirpstack-network-server:8000
1.3	53	)))
1.1	54
108.4	55
108.6	56	(% style="color:red" %)If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.
1.1	57
108.4	58
87.2	59	[[image:image-20220531171609-1.png]]
1.2	60
	61	Add the Network-servers
	62
84.2	63
108.4	64
108.6	65	== 2.2 Step 2. Create Gateway-profiles ==
1.2	66
108.6	67
88.2	68	[[image:image-20220531171651-2.png]]
1.2	69
	70	Create Gateway-profiles
	71
84.2	72
1.2	73
108.6	74	== 2.3 Step 3. Create Service-profiles ==
	75
	76
89.2	77	[[image:image-20220531171809-3.png]]
1.2	78
	79	Create Service-profiles
	80
89.3	81
1.2	82	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.
	83
1.4	84	(% style="color:red" %)Note : Before add the gateway, the user needs to complete the preceding three steps.
1.2	85
84.2	86	If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %)
1.2	87
84.2	88
108.6	89
108.7	90	== 2.4 Step 4. Add the gateway ==
1.2	91
108.7	92
1.2	93	The example gateway id is: a840411e96744150
	94
1.5	95	(((
1.4	96	(% style="color:red" %)Note : The Gateway EUI and server addresses must match the ChirpStack configuration.
108.7	97
	98
1.5	99	)))
1.2	100
90.2	101	[[image:image-20220531171923-4.png]](% style="display:none" %)
1.2	102
	103	Add the gateway
	104
108.7	105
	106
91.2	107	[[image:image-20220531172031-5.png]]
1.2	108
	109	Configure the gateway
	110
84.2	111
1.2	112
108.8	113	== 2.5 Step 5. Checking gateway Status ==
	114
	115
92.2	116	[[image:image-20220531172158-6.png]](% style="display:none" %)
1.2	117
84.2	118
108.8	119
1.2	120	gateway Status
	121
93.2	122	[[image:image-20220531172304-7.png]]
1.2	123
	124	gateway Status
	125
86.6	126
108.8	127
108.9	128	= 3. Gateway Registration for Basics Station =
1.2	129
108.9	130	== 3.1 Introduction ==
9.1	131
108.8	132
9.1	133	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.
	134
	135	ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
	136
	137
108.8	138	(% style="color:blue" %)Below list the support products and Requirements:
	139
9.1	140	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]]
	141	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/]]
	142
108.8	143	(% style="color:blue" %)How to set up chirpStack Basic Station
	144
9.1	145	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]]
	146
	147
108.8	148	(% style="color:blue" %)What do you need to prepare
	149
9.1	150	A gateway that can access the internet normally
	151
86.7	152
108.9	153	== 3.2 Add Gateway ==
9.1	154
108.9	155
20.2	156	[[image:image-20220524164205-10.png]]
9.1	157
86.8	158
108.9	159	== 3.3 Access the gateway GUI ==
9.1	160
108.9	161
9.1	162	Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
	163
20.2	164	[[image:image-20220524164319-11.png]]
9.1	165
108.9	166
9.1	167	User need to Choose the ChirpStack/Senet ~-~- Basic Station , input Server URI and Upload the TLS Certificate
	168
	169	(% class="box" %)
	170	(((
	171	Service Provider ~-~-> Choose the ChirpStack/Senet ~-~- Basic Station
	172
	173	LNS URI ~-~-> Enter the LNS URI address, For example : wss:~/~/xxxx.chirpstack.com:433 or ws:~/~/xxxx.chirpstack.com:3001
	174
	175	LNS TLS trust ~-~-> Upload the TLS Certificate
	176	)))
	177
	178	(% class="wikigeneratedid" %)
20.2	179	[[image:image-20220524164341-12.png]]
9.1	180
86.9	181
108.9	182	== 3.4 Start Station ==
9.1	183
108.9	184
108.14	185	When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack.
9.1	186
86.10	187
108.9	188	== 3.5 Successful Connection ==
9.1	189
108.9	190
9.1	191	If user completes the above steps, which will see live date in the ChirpStack.
	192
23.2	193	[[image:image-20220524164448-13.png]]
9.1	194
86.11	195
108.9	196	== 3.6 Trouble Shooting ==
	197
	198
9.1	199	User can check the station log in the logread/system log page.
	200
95.2	201	[[image:image-20220531172837-8.png]]
9.1	202
86.13	203
9.1	204	and recode the station log in the system/Recode log page.
	205
95.2	206	[[image:image-20220531172857-9.png]]
9.1	207
86.12	208
124.1	209	= 4. How the gateway connects to Chirpstack v4 via gateway-bridge =
108.9	210
1.2	211
128.1	212	(% style="color:blue" %)Below list the support products and Requirements:
	213
	214	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]]
	215	1. Firmware version since: [[Chirpstack-gateway-bridge>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/]]
	216
	217	(% style="color:blue" %)How to set up chirpStack Gateway-bridge
	218
	219	Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]]
	220
	221
	222	(% style="color:blue" %)What do you need to prepare
	223
	224	A gateway that can access the internet normally
	225
127.1	226	== 4.1 Configure Packet Forwarder ==
1.2	227
124.1	228	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	229
124.1	230	* In the LoRaWAN menu, click on LoRaWAN ~-~- Semtech UDP
	231	* Make sure the following settings are set:
	232	Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
	233	LoRaWAN Server Address:** //localhost or 127.0.0.1//
	234	Server port for upstream:** //1700//
	235	Server port for downstream:** //1700//
	236
	237	Click Save & Apply.
	238
	239	[[image:image-20221222114220-2.png\|\|height="748" width="931"]]
	240
	241
127.1	242	== 4.2 Configuring gateway frequency ==
124.1	243
127.1	244	Note: Gateway frequencies must match
	245
	246	[[image:image-20221222134830-3.png\|\|height="408" width="923"]]
	247
	248
	249	== 4.3 Modify the gateway-bridge configuration file ==
	250
	251
	252	Run the gateway command line command to modify the gateway-bridge configuration file:
	253
	254	(% class="box infomessage" %)
	255	(((
	256	root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
	257	)))
	258
124.1	259	[[image:image-20221222113302-1.png]]
	260
127.1	261	[[image:image-20221222140203-4.png\|\|height="875" width="806"]]
	262
	263
	264	(% class="wikigeneratedid" id="H" %)
	265	After the modification, run the following command: /etc/init.d/chirpstack-gateway-bridge restart
	266
	267	== 4.3 (Re)start and stop gateway-bridge ==
	268
	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
	287	(% class="wikigeneratedid" %)
	288	== 4.4 Successful Connection ==
	289
	290	[[image:image-20221222141754-5.png\|\|height="488" width="1150"]]
	291
	292	[[image:image-20221222141830-6.png\|\|height="582" width="1153"]]
	293
124.1	294	= 5. Downlink =
	295
	296	== 5.1 Convert HEX to Base64 ==
	297
	298
111.1	299	(% 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	300
121.2	301	[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:
111.1	302
	303	[[image:image-20221010193350-1.png]]
	304
	305
	306
121.2	307	[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]
	308
111.1	309	[[image:image-20221010193621-2.png]]
	310
	311
124.1	312	== 5.2 Chirpstack Downlink Note ==
111.1	313
	314
108.2	315	[[image:image-20220601102543-2.png]]
1.2	316
121.2	317	Convert the data to Base64
1.2	318
121.2	319	(% style="display:none" %) (%%)
86.14	320
1.2	321
121.2	322	[[image:image-20220531173236-10.png\|\|height="597" width="1215"]]
1.2	323
121.2	324	Check ChripStack downlink DataRate
86.15	325
121.2	326
	327
65.2	328	[[image:image-20220525101326-11.png]]
1.2	329
121.2	330	Make sure the RX2DR is the same in the end node
1.2	331
86.16	332
124.1	333	== 5.3 Loraserver Downlink Note ==
108.9	334
	335
1.2	336	User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
	337
1.5	338	(((
108.9	339	Below is examples:
1.5	340	)))
1.2	341
1.4	342	(% class="box" %)
	343	(((
	344	Connect to your server via MQTT：
	345	MQTT Client ID: Any
	346	Protocol：mqtt/tcp Server IP：loraserver_ip:1883
1.2	347	User name: User name Password: password
1.4	348	)))
1.2	349
97.2	350	[[image:image-20220531173419-11.png]]
1.2	351
1.5	352	(((
121.2	353	MQTT Connect to ChirpStack
86.17	354
108.9	355
86.17	356
1.5	357	)))
1.2	358
1.5	359	(((
108.9	360	After connect
1.5	361	)))
1.2	362
1.4	363	(% class="box" %)
	364	(((
	365	Subscribe : Format：application/ID/device/ Device EUI/rx
1.2	366	Example: application/7/device/00aedb3da649cb23/rx
1.4	367	)))
1.2	368
1.4	369	(% class="box" %)
	370	(((
	371	Publish:
1.2	372	Format: Top: application/ID/device/ Device EUI/tx
	373	Payload: {"confirmed":true or false,"fPort":XX,"data":"xxxx"}
	374	Example: Top: application/7/device/00aedb3da649cb23/tx
	375	Payload: {"confirmed":true,"fPort":2,"data":"AwEB"}
1.4	376	)))
1.2	377
98.2	378	[[image:image-20220531173519-12.png]]
1.2	379
121.2	380	MQTT Connect to ChirpStack
1.2	381
86.18	382
121.2	383	If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB
1.2	384
100.2	385	[[image:image-20220531173658-14.png]]
1.2	386
108.9	387
1.5	388	(((
1.2	389	Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码：
1.5	390	)))
1.2	391
1.4	392	(% class="box" %)
	393	(((
	394	function sha1_to_base64(sha1)
1.2	395	{
	396	var digits="ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
	397	var base64_rep = "";
	398	var cnt = 0;
	399	var bit_arr = 0;
	400	var bit_num = 0;
1.5	401	\\ for(var n = 0; n < sha1.length; ++n)
1.2	402	{
	403	if(sha1[n] >= 'A' && sha1[n] <= 'Z')
	404	{
121.1	405	ascv = sha1.charCodeAt( n ) - 55;
1.2	406	}
	407	else if(sha1[n] >= 'a' && sha1[n] <= 'z')
	408	{
121.1	409	ascv = sha1.charCodeAt( n ) - 87;
1.2	410	}
	411	else
	412	{
121.1	413	ascv = sha1.charCodeAt( n ) - 48;
1.2	414	}
1.5	415	\\ bit_arr = (bit_arr << 4) \| ascv;
1.2	416	bit_num += 4;
	417	if(bit_num >= 6)
	418	{
1.4	419	bit_num -= 6;
1.2	420	base64_rep += digits[bit_arr >>> bit_num];
1.4	421	bit_arr &= ~~(-1 << bit_num);
1.2	422	}
	423	}
1.5	424	\\ if(bit_num > 0)
1.2	425	{
	426	bit_arr <<= 6 - bit_num;
	427	base64_rep += digits[bit_arr];
	428	}
1.5	429	\\ var padding = base64_rep.length % 4;
	430	\\ if(padding > 0)
1.2	431	{
	432	for(var n = 0; n < 4 - padding; ++n)
	433	{
	434	base64_rep += "=";
	435	}
	436	}
	437	return base64_rep;
	438	}
1.5	439	\\console.log(sha1_to_base64("data"));
	440	\\data is downlink payload required by end node.
1.4	441	e.g console.log(sha1_to_base64("030101"));
	442	result: AwEB
1.2	443	AwEB is the 0x030101's base 64 Encode.
1.5	444	\\e.g console.log(sha1_to_base64("030000"));
1.4	445	result: AwAA
	446	AwAA is 0x030000's base 64 Encode.
	447	)))
1.2	448
86.21	449
1.2	450
108.9	451	== 4.3 Add the decode function in Chirpstack for the payload ==
	452
	453
1.2	454	User enters the payload code according to the steps.
	455
121.2	456	[[image:image-20220531173754-15.png\|\|height="474" width="1334"]]
1.2	457
	458
102.2	459	[[image:image-20220531173856-16.png]]
1.2	460
102.2	461
106.2	462	[[image:image-20220531174120-20.png]]
84.2	463
105.2	464	[[image:image-20220531174046-19.png]]
1.2	465
86.22	466
124.1	467	= 6. Multiply Uplink in ChirpStack =
108.9	468
	469
1.4	470	(((
1.2	471	nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
1.4	472	)))
1.2	473
1.4	474	(((
1.2	475	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	476
	477
1.4	478	)))
1.2	479
121.2	480	[[image:image-20220526091912-7.png\|\|height="241" width="1336"]]
1.2	481
108.9	482
1.5	483	(((
1.2	484	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	485
	486
1.5	487	)))
1.2	488
76.2	489	[[image:image-20220525104359-21.png]]
1.2	490
1.4	491	(((
1.2	492	Above behaviour will cause the platform shows below two cases of error:
108.9	493
	494
1.4	495	)))
1.2	496
1.4	497	(((
1.2	498	Error of duplicate Frame Counter
1.4	499	)))
1.2	500
76.2	501	[[image:image-20220525104437-22.png]]
1.2	502
86.23	503
108.9	504
121.2	505	Duplicate transmission in short time
1.2	506
121.2	507	[[image:image-20220601102430-1.png\|\|height="598" width="1319"]]
1.2	508
86.24	509
1.2	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.
1.4	693	)))

Wiki source code of Notes for ChirpStack

Applications

Navigation