[release] ChirpStack Gateway Bridge v3.9 (test releases)

ChirpStack Gateway Bridge v3.9.0-test.1


Multi-downlink commands and ACKs

This multi-downlink feature allows a Network Server to send multiple downlink opportunities at once, e.g. one item for RX1 and one for RX2. The gateway will send at most one downlink item from the list. The ChirpStack Gateway Bridge will respond with a list of ACK items, indicating which item item was emitted, which item(s) failed and which item(s) were ignored (because the previous item was

Channel re-configuration

This implements channel re-configuration for the ChirpStack Concentratord backend over MQTT. This also removes the channel re-configuration for the Semtech UDP Packet Forwarder. While this feature had been removed from the documentation code references were still present. As there are different implementations of the Semtech UDP Packet Forwarder, there are also different flavors of configuration files.

The ChirpStack Concentratord provides a unified API to different types of gateways which makes it possible to implement channel re-configuration for this backend.

Kerlink iStation

This release provides IPK packages that can be installed on a Kerlink iStation gateway.


  • Split multi-line meta-data returned by a command only once on delimiter.
  • Forward meta-data provided by a Packet Forwarder backend.



Use the testing channel instead of stable:

sudo echo "deb https://artifacts.chirpstack.io/packages/3.x/deb testing main" | sudo tee /etc/apt/sources.list.d/chirpstack.list


Use the chirpstack/chirpstack-gateway-bridge:3.9.0-test.1 image and tag (will be available shortly).


Could you clarify which packet forwarders support having their meta-data forwarded in this fashion?

Yes :slight_smile: This makes it possible to forward data provided / collected by Concentratord. E.g. in case of the SX1302 it is possible to read the temperature of the chip, but it also allows to forward the configuration version, board model, … In the end, this is merged with the meta-data from the ChirpStack Gateway Bridge, so that the NS receives a single meta-data field with all the key / values.

Gotcha. We have a situation where it would be nice to tack some metadata onto a Semtech UDP uplink or stats payload, but had not thought it was possible (at least without hacking both ends of the conversation).

Example from my local test environment, the Concentratord part is still to be released: