SenseCAP M2 - The device doesn't join AWS IoT through the gateway

SenceCAP M2 is configured successfully according to the Wiki, and its availability from the AWS IoT console is 100%.

A LoRaWAN device that has already confirmed its connectivity to AWS IoT with another LoRaWAN gateway sends a join request, and AWS IoT accepts it, but the device doesn’t receive any messages from the gateway.

How can I configure the gateway correctly?

I also encountered like same issue.
Please see the followings.
https://forum.seeedstudio.com/t/join-error-when-using-sensecap-m2-gateway-with-otaa-on-aws-iot-core-for-lorawan/283394

In addition, I checked to operate successfly with ABP.
However, it not operated successfly with OTAA.

What`s your activation settings?

1 Like

Hi, akira.

I would like to know the LoRa Log of the M2 gateway when your LoRaWAN device connects to AWS IoT through the M2 gateway(You can refer to the following image to check the LoRa Log)

Normally, the LoRa Log after the gateway receives a join request from a device will look like this.

Tue Dec  3 01:37:50 2024 daemon.info lora_pkt_fwd[4426]: INFO: [up] Join-Request from 2CF7F1C0543001D1
Tue Dec  3 01:37:50 2024 daemon.info lora_pkt_fwd[4426]:
Tue Dec  3 01:37:50 2024 daemon.info lora_pkt_fwd[4426]: JSON up: {"rxpk":[{"jver":1,"tmst":1402283206,"chan":0,"rfch":0,"freq":923.200000,"mid": 8,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","rssis":-40,"lsnr":14.0,"foff":211,"rssi":-39,"size":23,"data":"ACVigYp21vZ20QEwVMDx9yz5kcsQzcE="}]}

The gateway then receives a downlink message with the same spreading factor and bandwidth as the Join request message.

Tue Dec  3 01:37:51 2024 daemon.info lora_pkt_fwd[4426]: JSON down: {"txpk":{"imme":false,"rfch":0,"powe":14,"ant":0,"brd":0,"tmst":1407283206,"tmms":null,"freq":923.2,"modu":"LORA","datr":"SF10BW125","codr":"4/5","fdev":null,"ncrc":null,"ipol":true,"prea":null,"size":33,"data":"II4tz3Wi2sJ7+oH29YQoz/bfEGNQdRvNqLfq9GHkdcae"}}

What is known is that the initial configuration of the M2 gateway to the AWS IoT platform may have a delay of a few hours, during which time the device cannot connect and upload data properly.