v2.5.0

v2.5.0

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).

Features

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 Prometheus.

Changes

Configuration structure of MQTT backend

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

Improvements

All vendored dependencies have been updated.

Pre-compiled binaries are available at: https://www.loraserver.io/lora-gateway-bridge/overview/downloads/

2.4.1

Bugfixes:

• Only log in case of UDP read / write errors (instead of breaking out of loop).

Pre-compiled binaries are available at: https://www.loraserver.io/lora-gateway-bridge/overview/downloads/

2.4.0

Features:

• LoRa Gateway Bridge can now manage the packet-forwarder configuration (channels).
  See Send / receive data for more information.

Pre-compiled binaries are available at: https://www.loraserver.io/lora-gateway-bridge/overview/downloads/

2.3.2

Improvements:

• Expose the following MQTT options for the MQTT gateway backend:
  • QoS (quality of service)
  • Client ID
  • Clean session on connect

Bugfixes:

• Use topic from configuration file on re-connect (this was still hardcoded).

2.3.1

Improvements:

• MQTT topics are now configurable through the configuration file.
  See Configuration.

2.3.0

Features:

• LoRa Gateway Bridge uses a new configuration file format.
  See configuration for more information.

• Support MQTT client certificate authentication (#74).

Upgrade notes:

When upgrading using the .deb package / using apt or apt-get, your
configuration will be automatically migrated for you. In any other case,
please see configuration.

2.2.0

Features:

• LoRa Gateway Bridge now publishes TX acknowledgement messages over MQTT.
  See MQTT topics.

• TX (GPS) timeSinceGPSEpoch field is now exposed to transmit at given
  time since GPS epoch (1980-01-06, only possible when the gateway
  has a GPS time source).

• RX (GPS) timeSinceGPSEpoch field is now exposed, containing the time
  since GPS epoch (1980-01-06, only available when the gateway has a GPS
  time source).

Bugfixes:

• Without GPS time source, the gateway would use 0001-01-01T00:00:00Z
  as RX time. The time field is now omitted when unavailable.

2.1.6

Features:

• Add Kerlink iBTS compatibility (multi antenna and multi board).

2.1.5

Improvements:

• --mqtt-ca-cert / MQTT_CA_CERT configuration flag was added to
  specify an optional CA certificate
  (thanks @minggi).

Bugfixes:

• MQTT client library update which fixes an issue where during a failed
  re-connect the protocol version would be downgraded
  (paho.mqtt.golang#116).

2.1.4

• Retry connecting to MQTT broker on startup (thanks @jcampanell-cablelabs).
• Make latitude, longitude and altitude optional as this data is not always
  provided by the packet_forwarder and would else incorrectly be set to 0.