Join Error, when using SenseCAP M2 Gateway with OTAA on AWS IoT Core for LoRaWAN

Products & Technology SenseCAP
,
#1

Hello.
I tried to use several LoRaWAN sensor devices via SenseCAP M2 Gateway on AWS IoT Core for LoRaWAN.
but, when OTAA activation settings, it occured join error continuously.

In addition, I checked the followings.

  • when ABP activation settings on AWS IoT Core for LoRaWAN, it operated normaly.
  • when OTAA activation settings on TTN, it operated normaly.
  • when OTAA activation settings using other gateway(dragino LPS8N) on AWS IoT Core for LoRaWAN, it operated normaly.

environment:

  • Frequency Plan: AS923-1
  • Device: seeed Tracker T1000-A, seeed Wio-E5 mini, dragino LT-22222-L, dragino LA66-USB
  • Gateway: seeed SenseCAP M2 gateway, dragino LPS8N

Has anyone encountered the same problem and resolved it?

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

Does anyone have any information?

#3

Access the SenseCAP M2’s log files to see if the OTAA join requests from devices are being received and forwarded to AWS IoT Core. Look for:

Errors indicating dropped packets or rejected requests.
Mismatches in DevEUI, AppEUI, or AppKey.

#4

Hi, I’ve tried to reproduce your issue in our test environment but didn’t find the problem as you described, both devices (seeed Sensor S2103, seeed Tracker T-1000A) are successfully connected to AWS IoT Core with OTAA activation settings.

Below is the environment of M2 Gateway:

  • Build Version: r1-20220615
  • OS Version: 0.9.3-4
  • Firmware Version: 1.2.0-25
  • LoRaWAN Region: AS923
  • LoRaWAN Network Mode: Basics Station
  • Server: LNS Server

I refer to this Wiki for the process of configuring gateways and devices Connecting to AWS IoT.