AU915 gateway receives Join Requests but no Join Accept is sent

Simão Fernandes 3
Viewed 33

Hello ChirpStack Support,

I am contacting you because I am facing an issue with an AU915 setup in which the gateway is receiving OTAA Join Requests, but no Join Accept is being sent back by the network.

Current setup:

  • Gateway: Dragino DLOS8N-EC25 AU915
  • End node: configured to AU915
  • Region / frequency plan: AU915
  • Gateway sub-band: FSB2
  • Network environment: gateway connected to ChirpStack
  • These tests are being performed in Europe, outside the usual deployment region for AU915

Observed behavior:

  • The gateway is online and receiving uplink traffic
  • In the gateway traffic/logs, I can see repeated OTAA Join Requests from the end node
  • However, no Join Accept appears to be generated or transmitted back
  • On the ChirpStack side, there are no events appearing in the device event tabs during these join attempts

What has already been checked:

  • The gateway frequency plan and sub-band were reviewed and corrected to match the end-node traffic
  • The end node is also configured to AU915
  • The issue persists even after correcting the sub-band
  • The main symptom remains the same: gateway receives Join Requests, but the join process does not continue on the ChirpStack side

I would appreciate your help verifying:

  1. Whether the gateway uplinks are correctly reaching ChirpStack
  2. Whether ChirpStack is processing the Join Requests
  3. Whether there is any issue with the gateway-to-ChirpStack forwarding path
  4. Whether there is any gateway region / backend / MQTT topic configuration issue that could prevent the Join Request from being handled properly

Best regards,
Simão

gateways chirpstack
1 Answers

In the gateway traffic/logs, I can see repeated OTAA Join Requests from the end node

If this is the case, but you do not see any uplink data on the device page, then it could be that the configured key is incorrect and ChirpStack was not able to authenticate the device (because of failing MIC check).

Orne Brocaar931

We confirmed the device keys are correct, and we can see OTAA Join Requests at the gateway, so we can rule out an issue between the end-node and gateway. We believe the issue is somewhere in the path gateway → Helium Network → ChirpStack, as this gateway is connected to Helium. The same setup works fine for us on EU868. Could you suggest the best troubleshooting steps for this AU915 case?

Thank you in advance for your support.

Simão Fernandes•

Did you check the ChirpStack server logs for any errors or warnings?

Orne Brocaar•
Related
Gateway Mesh / Rx delay configuration
How to make your custom gateway compatible with Chirpstack
1 answers
Channel Frequency List | LNS & Gateway
2 answers
Join-request received by gateway and seen in ChirpStack troug/ no join-accept (AU915)
1 answers
Basic Station Certs Generator
1 answers
no internal frame cache for token 0
1 answers