This is an example application based on Mbed-OS LoRaWAN protocol APIs. The Mbed-OS LoRaWAN stack implementation is compliant with LoRaWAN v1.0.2 specification.

Dependents:   Projet_de_bachelor_code Projet_de_bachelor_code

Issue: "OTAA Failed - Check Keys"

Following this example using a Multitech mDot to connect to a Conduit, I am confused about the “Add Network Credentials” section. In particular, I am not clear as to which keys go where. In mbed_app.json, I changed the “target overrides” as follows:

- for "lora.device-eui" I used the mDot’s devEUI (came through as “MBED_CONF_LORA_DEVICE_EUI” in resultant mbed_config.h) - for "lora.application-eui" I used “network EUI” (came through as “MBED_CONF_LORA_APPLICATION_EUI” in resultant mbed_config.h) - for "lora.application-key" I used “network Key” (came through as “MBED_CONF_LORA_APPLICATION_KEY” in resultant mbed_config.h) - set lora.phy = 8

I also set lora-radio.value to SX1272.

Loading the resultant binary produced the following:

Mbed LoRaWANStack initialized CONFIRMED message retries : 3 Adaptive data rate (ADR) - Enabled Connection - In Progress ... OTAA Failed - Check Keys

Any ideas what might be going wrong?

3 comments:

28 Jun 2018

I am having the same issue. Any idea of what could be the error?

23 Jul 2018

I have the same problem. It's strange. The end device (In my case a B-072Z-LRWAN1) shows "OTAA Failed - Check Keys", but in TTN I can see the traffic between this device and the gateway. The gateway receives a "Join request" packet and sends a "Join Accept". But, anyway there is not connection at the end. Have you found any solution?

30 Jul 2018

Hi, In this comment an user gives a solution to this issue: https://github.com/ARMmbed/mbed-os-example-lorawan/issues/21#issuecomment-366937981 I modified that file and it worked.