LoPy OTAA query in documentation -Change in Auth params in OTAA

[shivankgarg98]

I was just revisiting the official pycom documentation on OTAA ( https://docs.pycom.io/chapter/tutorials/lora/lorawan-otaa.html )and I noticed that the parameter of the OTAA function-

# create an OTAA authentication parameters
app_eui = binascii.unhexlify('ADA4DAE3AC12676B')
app_key = binascii.unhexlify('11B0282A189B75B0B4D2D8C7FA38548B')

# join a network using OTAA (Over the Air Activation)
lora.join(activation=LoRa.OTAA, auth=(app_eui, app_key), timeout=0)

A few days back, we have to specify dev_eui too. But now it is not the case?
I am using loraserver.io for my application-server and they don't ask app_eui but dev_eui.
P.S.- My device is not responding to OTAA from 3 days, Maybe this is the issue, Please help me, what is the case?

[robert-hh]

@prawnhead It' less a bug in the firmware, than the way the device is handled by the user and some interference with the background database at Pycom, which keeps the assigned dev_uid. The dev_uid is stored in the device's flash and can be written to that using the updater tool. So you have three elements (flash, user, background system), which have to interact correctly, and there are few way to succeed and many ways to fail.

[Prawnhead]

@robert-hh said in LoPy OTAA query in documentation -Change in Auth params in OTAA:

...That however fails sometimes...

Ok, I'll use explicit dev_eui from now on. Is there a bug report for this?

• Thanks, Chris.

[robert-hh]

@shivankgarg98 The dev_eui parameter is optional (see https://docs.pycom.io/chapter/firmwareapi/pycom/network/lora.html). If you do not specify it, it is taken from the configuration established when loading the firmware. That however fails sometimes. If you want to be sure that it matches the network setting, you can specify it.