MIC mismatch with OTAA

meenakshymadhu
Thu, 03 Jul 2025 11:10:49 +0000
The Things Stack v3

Hello,
I am working as an intern and exploring 1WL EVK.
I have managed to successfully passthrough data to the network server through our RAKwireless (RAK747268) gateway. I am currently using Things network (Third party) as our network server and intend to integrate TTN with Abeeway Device manager through Abeeway location engine.
I am facing MIC mismatch error at the network server side. All the preliminary investigations points to appKey mismatch between the network server and the device.
Note:I have used OTAA. I have overwritten factory default JoinEui with all zeros (0000000000000000) and using custom appKey, matching to the values inputted in the network server. The appKey is set by flashing the manufacturing firmware and using command “provis lora set appkey XXX”.

1. Is there a way to verify(read and confirm) the appKey?

2. If I want to use the factory settings, can I go back to the factory configurations ? (We have factory devEui & joinEui but no appEui)

Appreciate any other suggestions, on overcoming this MIC mismatch error. Kindly request your help and support.

This is the event details.
{
“name”: “ns.up.join.cluster.fail”,
“time”: “2025-07-03T11:02:24.131697028Z”,
“identifiers”: [
{
“device_ids”: {
“device_id”: “1wl-evk”,
“application_ids”: {
“application_id”: “1wl-new”
},
“dev_eui”: “20635F01F0019AEA”,
“join_eui”: “20635F0000000001”
}
}
],
“data”: {
“@type”: “type.googleapis.com/ttn.lorawan.v3.ErrorDetails”,
“namespace”: “pkg/joinserver”,
“name”: “mic_mismatch”,
“message_format”: “MIC mismatch”,
“correlation_id”: “42b645719e4947f79ef65e1220f872a8”,
“code”: 3
},
“correlation_ids”: [
“gs:uplink:01JZ7Z7CKTX325B0PJ652XAAX5”
],
“origin”: “ip-10-100-7-207.eu-west-1.compute.internal”,
“context”: {
“tenant-id”: “CgN0dG4=”
},
“visibility”: {
“rights”: [
“RIGHT_APPLICATION_TRAFFIC_READ”
]
},
“unique_id”: “01JZ7Z7CM31SZPN6YB3W4PG2BQ”
}

9 posts - 4 participants