ESP32 LoRa V2 not connecting to LoRaWAN anymore

Hello guys, first topic here, may I need some help.

Until yesterday I was able to connect to a LoRaWAN here in Brazil (KORE) and successfully send packets to the network server of them.

But today, my device is not connecting to the the servers, I am using the example OTAA_OLED from standard lib from heltec to Wifi LoRa V2.

See the messages in serial monitor:

11:02:02.284 -> ESP32 MCU inited OK!
11:02:02.694 ->
11:02:02.728 -> LoRaWAN AU915 Class A start!
11:02:02.728 ->
11:02:03.133 -> joining…
11:02:18.217 -> join failed, rejoin at 30000 ms later
11:02:48.759 ->
11:02:48.759 -> LoRaWAN AU915 Class A start!
11:02:48.759 ->
11:02:49.196 -> joining…
11:03:04.251 -> join failed, rejoin at 30000 ms later

I already left the device for a long time trying to connect, but is not connecting.

In my web server, I can see the requests message to connect to LoRaWAN (KORE forward messages to my server throug POST requests):

Obs: The values in ‘xxxxx’ I put manually here due security reasons.

{
type: ‘info’,
meta: {
network: ‘xxxxxxxxxxxxxx’,
packet_hash: ‘xxxxxxxxxxxxxx’,
application: ‘xxxxxxxxxxxxxx’,
time: 1602770576.795474,
device: ‘xxxxxxxxxxxxxx’,
packet_id: ‘xxxxxxxxxxxxxx’,
gateway: ‘xxxxxxxxxxxxxx’
},
params: { message: ‘Join request accepted’, code: ‘join_accepted’ }
}

{
type: ‘info’,
meta: {
network: ‘xxxxxxxxxxxxxx’,
packet_hash: ‘xxxxxxxxxxxxxx’,
application: ‘xxxxxxxxxxxxxx’,
time: 1602770576.811103,
device: ‘xxxxxxxxxxxxxx’,
packet_id: ‘xxxxxxxxxxxxxx’,
gateway: ‘xxxxxxxxxxxxxx’
},
params: {
message: ‘Join accept message has been successfully sent to device.’,
code: ‘join_accept_sent’
}
}

Have you guys know what can be?

hi,

Could you try another node?

Sadly I just have one.

My friend have one node same of my and he could connect.

I changed to ABP mode and I could connect sucssfully. Today I will do new tests with OTAA mode, but this behavior is very strange. It seens the network server is receving “join request” and sending to my node the “join accepted”, but it looks like the node cannot receive or process the packet sent by NS.