Join-request received by gateway and seen in ChirpStack troug/ no join-accept (AU915)

Viewed 8

Hello ChirpStack support team,

I'm contacting you because I'm experiencing an issue with an AU915 configuration where the gateway is receiving OTAA join requests, but no frames are being seen on the ChirpStack server.

Current configuration:
Gateway: Milesight UG65
Gateway Region/Frequency Plan: AU915
End Device: Configured for AU915
Network Server: ChirpStack
Activation Mode: OTAA

Observed behavior:
The gateway is online and operating normally.

I can see join-request traffic in the gateway's network logs/traffic.

However, no corresponding frames appear on the ChirpStack server.

As a consequence, the join process does not proceed on the ChirpStack side.

No relevant join activity appears in the device events within ChirpStack.

Additional test performed:
To isolate the problem, I changed the device configuration from AU915 to US915.
With US915, the device was able to join correctly to the ChirpStack server.
This suggests that connectivity between the gateway and ChirpStack is generally working, but there may be some configuration or compatibility issue specifically related to the AU915.

Points I would like help verifying:
If the uplinks from the gateway to AU915 are actually reaching ChirpStack correctly.
If ChirpStack is receiving, but not processing, join requests on AU915.
If there is any configuration issue in the gateway region, backend, or MQTT topic that might be preventing the join request from being processed correctly?

Best regards,
Tiago

1 Answers

In general, this documentation page could help you troubleshoot this issue further: https://www.chirpstack.io/docs/guides/connect-gateway.html#adding-the-gateway-to-chirpstack.

If you see the LoRaWAN frames on the gateway page in ChirpStack, then in general it means the communication between the GW <> ChirpStack is fine. It could be that there is a misconfiguration in the device-profile, or that the keys are incorrect causing ChirpStack to reject the join-request.