Hello,
I am using the LilyGo T3 V1.6.1 LoRa module with lmic library. When I use the OTAA procedure, everything works fine.
For battery‑powered operation I tried switching to ABP. Unfortunately, no messages are arriving in the application.
I can see the messages on the gateway, but they never reach the application.
There are no errors, no hints, and the device is never shown as seen.
Disable frame counter validation is active.
I tried most of the examples and hints from the internet, but none of them were helpful.
Is there any possibility to look inside ChirpStack using the terminal and find out why the messages are rejected?
I am using ChirpStack Gateway OS 4.12.0 on a Raspberry Pi 4.
Thank you
ABP device never seen by application although gateway receives frames
Arthur
1
Viewed 27
2 Answers
I found out that if I start the server in the console, I get more information:
2026-08-30T16:08:52.387518Z INFO up{deduplication_id=59388f76-56bb-4a1a-a9ea-69ebf5bd7037}:data_up: chirpstack::uplink::data: None of the device-sessions for dev_addr resulted in valid MIC dev_addr=0153f56e
And now I see the problem is with the MIC. The NWKSKEY and APPSKEY are the same in the source code and the activation. Any other hints on how I can check the MIC calculation?
Related
ABP device never seen by application although gateway receives frames
2 answers
Chirpstack v3 networkserver stops handling most (but not all) traffic when switched over to new MQTT broker
1 answers
Trouble connecting device to gateway & Chirpstack
Class-C downlinks are not transmitted without time synchronization
Connecting SWIOTT GTW721 to Chirpstack
2 answers
Is fport=null the correct behavior?
1 answers