That’s one part of the infrastructure telling the other that a join-accept message has been created and will be sent down to the node (end device). No server side log can actually “see” if the node received the join accept.
Before you can get to the point of moving any application data, a gateway has to actually transmit that join accept, and the node has to receive it, decode it, and start using the result. Often the latter fails due to timing issues in the node or mixups about the radio settings applicable to TTN in a given region.
If the next thing the node does is transmit another join request rather than transmit an application data packet, then you know that the join request / join accept process has failed. Until it succeeds, you won’t get any application data.
Also worth noting that some node stacks (for example LMiC) may try to join when the application part of the firmware asks them to send data - if they are not joined, they cannot send data, so they send a join request instead, without any application data as that’s not yet possible until they receive and process a join accept.
I think I face exactly this problem join request after join request without sending any data…
Using mcci-catena/MCCI LoRaWAN LMIC library@^3.3.0
and the second problem is as I don’t know if I have a SX127x or a SX1262 LoRa module on my T-Beam module … don’t know how to find out. There is nothing written on the chip.
Is seems as there is no way “at the moment” to make a SX1262 work …
… does someone have a working example for the ESP32 and SX12xx ? to learn how to communicate with ttn.