I have installed Chirpstack (on docker) on a CentOS 7 machine. On my gateways (currently 3 Lorix One gateways) I use the chirpstack gateway bridge (directly on my gateway) and forward my data to my MQTT server. This means that on my gateway under Bridge configuration > Integration > Server I put my MQTT server the rest are default values (Bridge configuration > Backend [semetech_dupo, 127.0.0.1] and Backend configuration > Server 127.0.01 and port 1700).
My current use case is that I have some devices that send messages every 2 minutes. I know 2 minutes is a lot but I only use it for testing purpose. I am also sure that I do not reach the duty cycle since before moving to Chirpstack I was using The Things Network and their it worked. However, what is weird is that only 1 out of 3 (so every 2 minutes) or 2 out of 3 (so every 4 minutes) packages seem to arrive on my network server. Did anyone face a similar issue already ?
Is it possible that the network server implies some kind of limit ? Cause I have the exact same behavior when using the gateway bridge on a gateway and when I use the UDP packet forwarder. When I use the bridge the data are forwarded to MQTT and then to chirpstack-ns, if I use the UDP packet forwarder the packages are forwarded to chirpstack-gb (on my docker container) and then to the network server. So the common point seem to be the network server.
Are you sure that the channels configured on your gateway do match with the channels configured in the chirpstack-network-server.toml? Else the device might be sending uplinks on channels to which the gateway is not listening.