Gateway sending stats, but not connecting.

ChirpStack Gateway Bridge
1

Have a single VM in Azure running mosquitto, chirpstack and chirpstack-gateway-bridge.

Using mosquitto dynamic security, so 1883 is not exposed publicly. chirpstack passes to mosquitto on 1883-localhost.

image
image736Ă—47 1.81 KB

Confirmed that 1700 UDP is exposed and operational.

image
image816Ă—52 1.82 KB

Confirmed that the gateway is sending to the bridge, which is responding.

image
image1193Ă—241 13.5 KB

Set up our gateway, (packet forwarder) using Semtech UDP GWMP protocol, which is sending stats every thirty seconds.

image
image1832Ă—68 5.79 KB

Problem is that the gateway is still reporting as “never seen”, so have been unable to connect a device.

At first glance, is there something that I’ve missed? I’m feeling that 1883 might need to be available as well, but that counteracts what I’m trying to do with dynamic security on mqtt.

2

You likely need to configure your gateway bridge / MQTT forwarder with your MQTT broker security info to have it connect. Unless it is using localhost as well and confirmed working.

If so share your Chirpstack logs.

3

We’ve tried connecting as Liam suggests, but still can’t seem to get the gateway to connect to Chripstack using the MQTT connection. While it’s blurred, the Broker Address is that of our VM running both MQTT and Chirpstack.

I tested those credentials using MQTTX using the same settings without issue.

image
image1168Ă—815 33.2 KB

4

What gateway is this? I would be surprised if it’s MQTT forwarder was compatible, although it does state it is specifically for v4.

I meant the chirpstack-gateway-bridge (the newer version is called the MQTT forwarder), set your gateway to send UDP packets to the chirpstack gateway bridge, then ensure the gateway bridge is properly connecting to your MQTT Broker.

If the gateway bridge already has the right credentials, or is using localhost and should have no security issues. Then share your chirpstack logs so we can properly diagnose the issue. Or atleast any errors you can see in the logs (ideally restart your Chirpstack then view the logs for errors).

5

This is a RAK7268CV2 running WisGateOS_2.2.10_RAK.

I set the RAK back to use UDP 1700.

I restarted the chirpstack-gateway-bridge, and it appears to be connecting to the mqtt broker. Also notice that the second highlighted portion is the gateway ID of the RAK that we registered in Chripstack UI.

image
image1893Ă—407 76.7 KB

I restarted the chirpstack service, but don’t see errors, only the warnings toward the bottom.

image
image1900Ă—1009 145 KB

6

I believe your issue is that you must specify the subband in your region_prefix for the gateway bridge. I.E us915_0 not just us915. You can see in the stats messages, the gateway is posting to us915, but in the MQTT subscription loop parts of the Chirpstack logs, Chirpstack only subscribes to us915_0, not us915. Try changing the region prefix in your gateway bridge and I think that will solve the issue.

7

@Liam_Philipp - Thank you so much for taking the time to assist. You caught the golden goose, and I’m appreciative of your efforts.

Best to you for the upcoming Holidays.

1 Like