"Last Uplink Received At" field is empty

It seems the wireless device has successfully joined the Kerlink gateway, as you can see the uplink message received in the gateway logs. However, for the device to communicate directly with AWS IoT Core, it needs to complete the activation or join procedure with AWS IoT Core as well.

• Make sure the device credentials (DevEUI, AppEUI, AppKey) configured in AWS IoT Core match what is configured on the device.
• Check for any errors in the gateway logs around the time the device is trying to join AWS IoT Core. Errors like invalid region or MIC failure indicate incorrect credentials.
• If no errors are seen, wait a few minutes and check the "Last Uplink Received" field again. It may take some time for the device to complete the join procedure with AWS IoT Core.
• As a test, try sending an uplink message from the device again to see if it triggers any new log entries for the join process with AWS IoT Core.

Thanks for answering, Giovanni.

• The device credentials are correct, since the OTAA join request is successful. I tried making it wrong intentionally, and the OTAA request failed.
• I don't see any errors on the gateway logs. And I also don't see any request that the device is trying to connect to AWS IoT Core.
• "Last Uplink Received" is still empty, and I already sent a more than a message per 30 seconds, and a total of more than 20 uplink messages.

I don't know if this will help, but I'm using RAK4630 as the wireless device. And here's the code: https://github.com/RAKWireless/WisBlock/blob/master/examples/RAK4630/communications/LoRa/LoRaWAN/LoRaWAN_OTAA_ABP/LoRaWAN_OTAA_ABP.ino

Hi. Have you enabled IoT wireless logging and checked CloudWatch? https://docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-logging-monitoring.html

Have you tried using Network Analyzer to confirm that uplinks reach AWS IoT Core for LoRaWAN? https://docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-network-analyzer-overview.html

Can you enable XDEBUG logging on the gateway, if not already? This will allow you to see the join in detail:

2024-03-05 06:36:00.015 [S2E:VERB] RX 917.4MHz DR0 SF12/BW125 snr=7.0 rssi=-63 xtime=0x64000142D6FEF4 - jreq MHdr=00 JoinEUI=70b3:d57e:d002:6b90 DevEUI=70b3:d549:99b6:a683 DevNonce=2084 MIC=1936168195

2024-03-05 06:36:00.015 [AIO:XDEB] [4|WS] > {"msgtype":"jreq","MHdr":0,"JoinEUI":"70-B3-D5-7E-D0-02-6B-90","DevEUI":"70-B3-D5-49-99-B6-A6-83","DevNonce":2084,"MIC":1936168195,"RefTime":1709620559.871467,"DR":0,"Freq":917400000,"upinfo":{"rctx":0,"xtime":28147503087419124,"gpstime":1393655777968900,"fts":-1,"rssi":-63,"snr":7,"rxtime":1709620560.015467}}

2024-03-05 06:36:00.642 [AIO:XDEB] [4|WS] < {"msgtype":"dnmsg","DevEui":"00-00-00-00-00-00-00-00","regionid":4,"dnmode":"updn","dC":0,"diid":34690,"pdu":"20921397266e86a35e4e5dbcf8a7434c73","priority":1,"RxDelay":5,"RX1DR":8,"RX1Freq":925100000,"xtime":28147503087419124,"rctx":0,"MuxTime":1709620560.498498}

And the uplinks:

2024-03-05 06:36:15.864 [RAL:XDEB] [CRC OK] 918.000MHz 10.75/-65.0 SF7/BW125 (mod=16/dr=2/bw=3) xtick=43c96a6c (1137273452) 29 bytes: 4095C84201000000037A9DEA7910D3DE0E92CC3A5FDE6DEB3A6170F61E

2024-03-05 06:36:15.865 [AIO:XDEB] [4|WS] > {"msgtype":"updf","MHdr":64,"DevAddr":21153941,"FCtrl":0,"FCnt":0,"FOpts":"","FPort":3,"FRMPayload":"7A9DEA7910D3DE0E92CC3A5FDE6DEB3A","MIC":519467105,"RefTime":1709620575.721342,"DR":5,"Freq":918000000,"upinfo":{"rctx":0,"xtime":28147503103306348,"gpstime":1393655793856120,"fts":-1,"rssi":-65,"snr":10.75,"rxtime":1709620575.865576}}

The gateway has to send the updf message type on the web socket, for AWS IoT Core for LoRaWAN to be able to receive it.