MIC mismatch

TTN V2 to V3 Upgrade Migrating Devices to V3
1

Hello,

I receive “MIC mismatch” when I migrate device vom V2 to V3. (OTAA join)
Device is a Dragino LDDS75. (EU868)
MAC is configured to V1.0.3. but also V1.0.2 ist not working.


{
  "name": "ns.up.join.drop",
  "time": "2021-02-18T10:51:29.295032328Z",
  "identifiers": [
    {
      "device_ids": {
        "device_id": "dragino-ultrasonic-w1",
        "application_ids": {
          "application_id": "dragino-ultrasonic-w1"
        },
        "dev_eui": "",
        "join_eui": ""
      }
    }
  ],
  "data": {
    "@type": "type.googleapis.com/ttn.lorawan.v3.ErrorDetails",
    "namespace": "pkg/joinserver",
    "name": "mic_mismatch",
    "message_format": "MIC mismatch",
    "correlation_id": "94e3a7ee41ec47828b1702abd7cea503",
    "code": 3
  },
  "correlation_ids": [
    "gs:conn:01EYT2WGFG0RKDK0WPF9VKYVB6",
    "gs:up:host:01EYT2WGFP7E4HA834NJGRY8S2",
    "gs:uplink:01EYTC8941PS0SSS68DEH6EAEF",
    "ns:uplink:01EYTC8945V42YEP8E4K965C32",
    "rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01EYTC89439A9WXZXGPRJ3CSAW"
  ],
  "origin": "ip-10-100-6-153.eu-west-1.compute.internal",
  "context": {
    "tenant-id": "CgN0dG4="
  },
  "visibility": {
    "rights": [
      "RIGHT_APPLICATION_TRAFFIC_READ"
    ]
  },
  "unique_id": "01EYTC894F0B0M4P0WYNQMS94E"
}

regards,
Thomas

2

Please take a few minutes and learn how to format your posts.

Have you checked your AppKey is correct?

1 Like
3

Yes, AppKey was copied from the V2. I also did double check. Where I’m not sure is the MAC Version.
Datasheet at Dragino says Lora 1.0.3 but this setting did not exist in V2, so I’m not sure.

4

I have deleted and re-created a new device. Now the MIC mismatch is gone, but it endless loops the join process:
join

5

I am quite sure that the mac version is not your problem.

Are you really sure that the device isn’t also being handled in parallel by the v2 stack?
AFAIK you should have only one set of valid APP EUI/keys in one of the stacks.
So, invalidate the APP EUI/key in the v2 stack and make sure it is valid in the v3 stack, for example.
And, once it works on the v3 stack, you can delete the device from the v2 stack.

Perhaps there is something wrong with your device, not receiving the join settings or not remembering them.

I’ve migrated a couple of devices and it all went pretty much exactly as expected.

6

I have connected my gateway to V3 and disconnected from V2, so there should not be a conflict with V2, right? AppKey was also modified in V2.
I V2 the device worked fine for one year.

7

From gateway view it looks ok, but device is not working. downlink

8

Still endless join loop. Try go get in contact with dragino. join

9

Is there now a solution for this? The error also occurs when setting up a new device.

10

Hello, I have the same issue with the code LoraWAN_End_Node V.1.2.0 (Cube WL) and the LSM100A

11

Where you able to solve it?