Wrong region for My Gateway UG63

[nida]

Hello,
I work for a small company and we want to setup a ChirpStack LoraWAN Network Server.
Our Gateway: Milesight UG63

I use a Docker Desktop and Semtech UDP,

The gateway is stated as Online but somehow the region is eu868. I want the region to become as923 but the error in the log keep giving this
ERROR chirpstack::uplink: Deduplication error error=No channel found for frequency: 922600000, dr: 5

When I look in the WebGUI on the gateway - LoRaWAN frames tab it is indefinetly loading and I can see nothing. Same happens for the device tab - Events/LoRaWAN frames. It is just loading, but displays nothing.

this is my chirpstack-gateway-bridge.toml:

this is my chirpstack.toml:

Can someone please help me how I can fix those things? How can I change the frequency region of my gateway to as923? Thanks in advance!

[Liam_Philipp]

Have you changed the topic-prefix in your docker-compose.yml?

This section:

  chirpstack-gateway-bridge:
    image: chirpstack/chirpstack-gateway-bridge:4
    restart: unless-stopped
    ports:
      - 1700:1700/udp
    volumes:
      - ./configuration/chirpstack-gateway-bridge:/etc/chirpstack-gateway-bridge
    environment:
      - INTEGRATION__MQTT__EVENT_TOPIC_TEMPLATE=eu868/gateway/{{ .GatewayID }}/event/{{ .EventType }}
      - INTEGRATION__MQTT__STATE_TOPIC_TEMPLATE=eu868/gateway/{{ .GatewayID }}/state/{{ .StateType }}
      - INTEGRATION__MQTT__COMMAND_TOPIC_TEMPLATE=eu868/gateway/{{ .GatewayID }}/command/#
    depends_on:
      - mosquitto

eu868 should be replaced with as923.

[nida]

yes i did

this is my docker-compose.yml:

services:
  chirpstack:
    image: chirpstack/chirpstack:4
    command: -c /etc/chirpstack
    restart: unless-stopped
    volumes:
      - ./configuration/chirpstack:/etc/chirpstack
      - ./lorawan-devices:/opt/lorawan-devices
    depends_on:
      - postgres
      - mosquitto
      - redis
    environment:
      - MQTT_BROKER_HOST=mosquitto
      - REDIS_HOST=redis
      - POSTGRESQL_HOST=postgres
    ports:
      - 8080:8080

  chirpstack-gateway-bridge:
    image: chirpstack/chirpstack-gateway-bridge:4
    restart: unless-stopped
    ports:
      - 1700:1700/udp
    volumes:
      - ./configuration/chirpstack-gateway-bridge:/etc/chirpstack-gateway-bridge
    environment:
      - INTEGRATION__MQTT__EVENT_TOPIC_TEMPLATE=as923/gateway/{{ .GatewayID }}/event/{{ .EventType }}
      - INTEGRATION__MQTT__STATE_TOPIC_TEMPLATE=as923/gateway/{{ .GatewayID }}/state/{{ .StateType }}
      - INTEGRATION__MQTT__COMMAND_TOPIC_TEMPLATE=as923/gateway/{{ .GatewayID }}/command/#
    depends_on:
      - mosquitto
  
  chirpstack-gateway-bridge-basicstation:
    image: chirpstack/chirpstack-gateway-bridge:4
    restart: unless-stopped
    command: -c /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge-basicstation-as923.toml
    ports:
      - 3001:3001
    volumes:
      - ./configuration/chirpstack-gateway-bridge:/etc/chirpstack-gateway-bridge
    depends_on:
      - mosquitto

  chirpstack-rest-api:
    image: chirpstack/chirpstack-rest-api:4
    restart: unless-stopped
    command: --server chirpstack:8080 --bind 0.0.0.0:8090 --insecure
    ports:
      - 8090:8090
    depends_on:
      - chirpstack

  postgres:
    image: postgres:14-alpine
    restart: unless-stopped
    volumes:
      - ./configuration/postgresql/initdb:/docker-entrypoint-initdb.d
      - postgresqldata:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=root

  redis:
    image: redis:7-alpine
    restart: unless-stopped
    command: redis-server --save 300 1 --save 60 100 --appendonly no
    volumes:
      - redisdata:/data

  mosquitto:
    image: eclipse-mosquitto:2
    restart: unless-stopped
    ports:
      - 1883:1883
    volumes: 
      - ./configuration/mosquitto/config/:/mosquitto/config/

volumes:
  postgresqldata:
  redisdata:

[Liam_Philipp]

Everything looks to be configured correctly, strange.

If you enter your mosquitto container and mosquitto_sub to the broker can you confirm the events being posted under the correct topic-prefix?

The MQTT connection is the only connection Chirpstack has to the gateways so if the topics are being posted correctly there Chirpstack should recognize that.

[nida]

Im sorry but i am not quite sure how to enter to my mosquitto container and mosquitto_sub to the broker so that i can confirm the events being posted under the correct topic-prefix.

[Liam_Philipp]

The answers are always just a google away

1. cd chirpstack-docker
2. sudo docker ps (then look for the name of your MQTT container, it is likely chirpstack-docker-mosquitto-1)
3. sudo docker exec -it chirpstack-docker-mosquitto-1 sh
4. mosquitto_sub -t "#" -v 

Then look at the output and see what topic-prefix the events are being posted as.