Releases: chirpstack/chirpstack-gateway-bridge
v3.4.0
v3.3.0
v3.3.0
Features
Message IDs
This release implements unique message IDs (both for events and commands) that can be used for correlation or logging purposes.
BasicStation channel-plan configuration
To make it easier to work with the BasicStation Packet Forwarder, this release makes it possible to configure the channel-plan inside the LoRa Gateway Bridge configuration file. It is no longer needed to configure a Gateway Profile within LoRa App Server. This means that it is also possible to use the LoRa Gateway Bridge with BasicStation gateways, without the need of installing LoRa Server and LoRa App Server.
Pre-compiled binaries are available at: https://www.loraserver.io/lora-gateway-bridge/overview/downloads/
v3.2.1
v3.2.1
Bugfixes
- Fix NetID 3 & 4 filter according to the errata published by the LoRa Alliance.
- Fix Basic Station bandwidth for LoRa Std channel (from kHz to Hz). (#130)
Pre-compiled binaries are available at: https://www.loraserver.io/lora-gateway-bridge/overview/downloads/
v3.2.0
v3.2.0
Features
NetID and JoinEUI filters
Configuration options have been implemented to filter uplink messages on netID
and JoinEUI. This makes it possible to ignore messages from neighboring
to save on bandwidth usage (e.g. when the gateway is using a cellular backhaul).
Execute commands
This feature makes it possible to execute commands on the gateway (when the
LoRa Gateway Bridge is running on the gateway). Note: commands must be
pre-configured in the LoRa Gateway Bridge configuration file.
Improvements
Basic Station backend
- Verify Common Name when using client certificates. (#129)
Pre-compiled binaries are available at: https://www.loraserver.io/lora-gateway-bridge/overview/downloads/
v3.2.0-test.1
v3.2.0-test.1
Features
NetID and JoinEUI filters
Configuration options have been implemented to filter uplink messages on netID and JoinEUI. This makes it possible to ignore messages from neighboring to save on bandwidth usage (e.g. when the gateway is using a cellular backhaul).
Execute commands
This feature makes it possible to execute commands on the gateway (when the LoRa Gateway Bridge is running on the gateway). Note: commands must be pre-configured in the LoRa Gateway Bridge configuration file.
v3.1.0
v3.1.0
Features
Azure IoT Hub X.509
X.509 certificate authentication is added to the azure_iot_hub MQTT authentication option.
Improvements
Prometheus metrics
The Prometheus metrics have been improved for consistency. Documentation has been updated to document the metrics that are available.
Max reconnect interval
The MQTT max. reconnect interval is now a global MQTT configuration and can be used regardless of the MQTT authentication type.
Lat / lon / alt = 0
When the latitude, longitude and altitude are all three 0, then LoRa Gateway Bridge assumes there is no GPS module / location available and it will not expose a location in the stats message.
Bugfixes
- The CRC check has been fixed for the Semtech UDP backend.
- Fix message buffering for QoS > 0 (on manual reconnect, the Paho library discards messages when offline).
Deprecated
Managed gateway configuration
Documentation (and configuration) references to the managed packet-forwarder configuration have been removed. The feature itself is still available and will stay available until the next major release. Please refer to this forum discussion for more background.
v3.0.1
v3.0.0
v3.0.0
Features
Basic Station packet-forwarder support
The LoRa Gateway Bridge has been refactored to support multiple packet-forwarder backends. Next to the Semtech UDP packet-forwarder, support has been added to support the Basic Station packet-forwarder. This backend implements the Basic Station LNS protocol.
Updated payload formats
The uplink payload contains a context field, used to store gateway specific context data (like the internal counter).
The downlink frame contains a timing field which can be either IMMEDIATELY, DELAY or GPS_EPOCH. Based on the timing value, an additional object must be given with the additional timing information. Refer to Commands for more details.
Azure IoT Hub integration
LoRa Gateway Bridge now has support to connect the Azure IoT Hub MQTT interface. Like with the Google Cloud Platform IoT Core integration this makes it easier to scale up and manage gateway credentials using the IoT Hub console (or API).
Fake RX time
In case the gateway does not have a GPS module, the RX time would would be left blank. This feature makes it possible to use the system time as a fallback. (#109)
Custom gateway meta-data
This feature makes it possible to expose additional meta-data in the gateway stats. Meta-data can either be static or dynamic (executing external commands). The latter option allows to for example read and expose the gateway temperature, humidity, ...
Upgrading
LoRa Gateway Bridge v3.0.0 include a couple of changes that are not backwards compatible. You need to re-generate the configuration file and update it where needed. LoRa Gateway Bridge v3 is compatible with LoRa Server v2.7+. Below a summary:
MQTT topics
The MQTT topic configuration has been updated from:
uplink_topic_template="gateway/{{ .MAC }}/rx"
downlink_topic_template="gateway/{{ .MAC }}/tx"
stats_topic_template="gateway/{{ .MAC }}/stats"
ack_topic_template="gateway/{{ .MAC }}/ack"
config_topic_template="gateway/{{ .MAC }}/config"To:
event_topic_template="gateway/{{ .GatewayID }}/event/{{ .EventType }}"
command_topic_template="gateway/{{ .GatewayID }}/command/#"Event types are: up, stats and ack.
Commands are: down and config.
Please note that LoRa Gateway Bridge v3 is compatible with LoRa Server v2.7+, but you will need to update the MQTT topics in your loraserver.toml file. Example snippet:
uplink_topic_template="gateway/+/event/up"
stats_topic_template="gateway/+/event/stats"
ack_topic_template="gateway/+/event/ack"
downlink_topic_template="gateway/{{ .MAC }}/command/down"
config_topic_template="gateway/{{ .MAC }}/command/config"Backends
With LoRa Gateway Bridge v2 you would configure the MQTT backend under the [backend...] section. This has changed and the [backend...] section is now used for selecting and configuring the packet-forwarder backends.
Integrations
The MQTT integration configuration has moved to the new [integration...] section. This allows for adding new integrations in the future besides MQTT.
Prometheus metrics
The Prometheus metrics have been updated / cleaned up.
Pre-compiled binaries are available at: https://www.loraserver.io/lora-gateway-bridge/overview/downloads/
v3.0.0-test.4
v3.0.0-test.4
v3.0.0-test.3
v3.0.0-test.3