Gateway Defualts to EU868 after configuring it for US915

I just finished configuring my gateway and connecting it to chirpstack but when I look at the region ID it says EU868. This should be US915. I even specified it in the concentord configurations in the gateway web interface here:


This is what my chirpstack server is displaying:

My gateway is a raspberry pi 3b with a RAK2287 running on the Base Gateway OS
Please help thanks (:slight_smile:

You still need to change your MQTT topic prefix. It’s under the MQTT forwarder configuration and should be set to “us915_0” instead of “eu868”.

It looks like I’ve already done that.

Very strange, Chirpstack only pulls that info from the MQTT topic prefix. Just tested myself and adjusting the topic prefix in the MQTT forwarder changed the region ID as soon as the next stats message was uploaded (30 seconds).

I have a few suggestions:

  • Ensure us915_0 is listed under your “regions” tab in the Chirpstack application.
  • Delete the gateway and re-add it
  • Try us915_1
  • The classic turn it off and back on again

If none of those help I’d dig a bit deeper. SSH into the Pi and mosquitto_sub to your MQTT broker, you should see stats messages coming in regularly, look at the topic and whether it is us915_0 or eu868.

I completely started from scratched with a new micro sd card but it still shows up as EU868.

How do you mosquitto_sub to your MQTT broker? The mosquitto_sub command doesn’t seem to exist and I’ve tried to install a few packages but none of them seem to work. What package do you recommend I install.

Also what OS are you using to run your gateway?

Never mind I figured it out. I had to edit my docker-compose.yml. Within the docker-compose.yml file, you must replace the eu868 prefix in the
INTEGRATION__..._TOPIC_TEMPLATE configuration with the MQTT topic_prefix of the region you would like to use (e.g. us915_0, au915_0, in865, …).

After that just restart the services to apply the changes using this command:

2 Likes