I’ve recently stood up Chirpstack via Docker. For a test I’ve moved a gateway I had on the TTN network over to my new Chirpstack instance. However, the gateway is not coming up on the Chirpstack site. When I do as tcpdump of port 1700 I see data from my gateway.
It looks like the stats messages are being sent so the gateway should show online. Are you receiving the packets from the device in the events tab?
If you subscribe to the MQTT topic:
mosquitto_sub -v -t “#”
You should be able to see the MQTT messages under “application/” which are the messages after they have been processed by Chirpstack, and use that to determine whether Chirpstack has acknowledged the gateway/uplinks yet.
us915_1 is the correct prefix. It also looks like the stats and uplinks are coming through fine, can you share photos of the events tab of the device and the events of the gateway through the UI?
One thing I messed up when configuring us915_1 for the first time is that Chirpstack uses 0-indexing for its subbands though typically for gateways / devices they use 1 as the first subband, if that is the case for you do you have your devices / gateway on us915 subband 2?
Looking back now, it seems that your gateway bridge was sending us915 topic prefixes, maybe changing that to us915_1 would be enough to solve the issue?
From when you did this command, the gateway is posting the MQTT messages, but Chirpstack is not posting the typical “application/” messages back into the broker after it processes the messages. So probably chirpstack is not seeing these messages, most likely here that is because the topic prefix was us915. It would be worth doing the command again with the proper topic prefix us915_1
Like I said though, I don’t have any actual applications with devices attached yet. I was working on getting the gateway up and working before I run out with a device to try and connect.
# Network related configuration.
[network]
# Network identifier (NetID, 3 bytes) encoded as HEX (e.g. 010203).
net_id="000000"
# Enabled regions.
#
# Multiple regions can be enabled simultaneously. Each region must match
# the 'name' parameter of the region configuration in '[[regions]]'.
enabled_regions=[
"us915_0",
"us915_1",
]
