[release] LoRa Gateway Bridge v2.5.x



Upgrade notes

When using the v2_json marshaler (default), this version is fully compatible
with previous versions of LoRa Server. When changing the marshaler to protobuf
or json, you first need to upgrade to LoRa Server v2.1.0. When
LoRa Server v2.1.0 is installed, it is recommended to use either the protobuf
or json marshaler as it provides better compatibility (e.g. with the iBTS gateway).


Protocol Buffer data serialization

To save on bandwith between the gateway and the MQTT broker (e.g. when the
gateway uses a cellular connection), this update makes it possible to
configure the marshaler for encoding / decoding the data (in
lora-gateway-bridge.toml) using Protocol Buffers.

This will become the default option in LoRa Gateway Bridge v3.

New JSON format

The new JSON structure re-uses the messages defined for
Protocol Buffers
based serialization. For backwards compatibility, the default marshaler for
LoRa Gateway Bridge v2.x will be v2_json.

Kerlink iBTS fine-timestamp

When using the protobuf or json marshaler, LoRa Gateway Bridge will
expose the fine-timestamp fields when using Kerlink iBTS gateways.

Prometheus metrics

For monitoring the health and throughput of each LoRa Gateway Bridge instance,
LoRa Gateway Bridge is able to expose various metrics that can be scraped by


Configuration structure of MQTT backend

The structure of the [backend.mqtt] configuration section has been updated.
These changes are fully backwards compatible.


All vendored dependencies have been updated.

1 Like

Version v2.5.0 introduced an issue in the configuration parsing by setting configuration aliases. Potentially this is a bug in the library used to parse configuration files and has been reported. For technical details, see: https://github.com/spf13/viper/issues/560.




Fix configuration parse error (some keys were not loaded because of configuration alias).