LoRa Gateway Bridge is able to integrate with Cloud IoT Core. This makes it easier to scale up, but also makes it possible to manage gateway authentication using the web-based Cloud IoT console (or APIs).
The gateway IP address is exposed through the gateway stats.
Fix configuration parse error (some keys were not loaded because of configuration alias).
When using the
v2_json marshaler (default), this version is fully compatible
with previous versions of LoRa Server. When changing the marshaler to
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
json marshaler as it provides better compatibility (e.g. with the iBTS gateway).
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
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.
The new JSON structure re-uses the messages defined for
based serialization. For backwards compatibility, the default
LoRa Gateway Bridge v2.x will be
When using the
marshaler, LoRa Gateway Bridge will
expose the fine-timestamp fields when using Kerlink iBTS gateways.
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.
The structure of the
[backend.mqtt] configuration section has been updated.
These changes are fully backwards compatible.
All vendored dependencies have been updated.
LoRa Gateway Bridge uses a new configuration file format. See configuration for more information.
Support MQTT client certificate authentication (#74).
When upgrading using the
.deb package / using
configuration will be automatically migrated for you. In any other case,
please see configuration.
LoRa Gateway Bridge now publishes TX acknowledgement messages over MQTT. See MQTT topics.
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).
timeSinceGPSEpoch field is now exposed, containing the time
since GPS epoch (1980-01-06, only available when the gateway has a GPS
timefield is now omitted when unavailable.
MQTT_CA_CERTconfiguration flag was added to specify an optional CA certificate (thanks @minggi).
SKIP_CRC_CHECKconfig flag to disable CRC checks by LoRa Gateway Bridge.
txInfostruct in JSON to override the default behaviour (which is
iPol=truewhen using LoRa modulation)
lorawanvendor to fix a mac command related marshaling issue.
packet_forwarder3.0.0 (which implements just-in-time scheduling).