Skip to content

Releases: brocaar/chirpstack-network-server

v3.10.0-test.2

20 Jul 08:55
Compare
Choose a tag to compare
v3.10.0-test.2 Pre-release
Pre-release
v3.10.0-test.2

v3.10.0-test.1

25 May 09:22
Compare
Choose a tag to compare
v3.10.0-test.1 Pre-release
Pre-release
v3.10.0-test.1

v3.9.0

08 Apr 10:52
Compare
Choose a tag to compare

v3.9.0

Features

Redis Cluster and Sentinel

This release introduces the support for Redis Cluster and Redis Sentinel.

Rejected uplink callback to Network Controller

A new API method has been added to the (optional) Network Controller called HandleRejectedUplinkFrameSet. When ChirpStack Network Server rejects an uplink (e.g. when the device is not known to the network, or the activation is missing), it will call this method (when the Network Controller is configured).

Improvements

  • Change ISM band names to their common name. (#477)

v3.9.0-test.1

01 Apr 08:57
Compare
Choose a tag to compare
v3.9.0-test.1 Pre-release
Pre-release
v3.9.0-test.1

v3.8.1

24 Mar 09:52
Compare
Choose a tag to compare

v3.8.1

Bugfixes

  • Fix AMQP re-connect issue.

v3.8.0

28 Feb 15:02
Compare
Choose a tag to compare

v3.8.0

Features

Downlink gateway randomization

When sending a downlink response, ChirpStack Network Server will select from the list of gateways with a given (configurable) margin, a random gateway for the downlink. This should result in a better downlink distribution across gateways. In case non of the gateways are within the configured margin, the best gateway is selected (old behavior).

Monitoring

The monitoring configuration has been updated so that it is possible to configure both a Prometheus endpoint at /metrics and healthcheck endpoint at /health. This change is backwards compatible, but to use the /health endpoint you must update your configuration.

Forward gateway metadata to AS

By forwarding gateway metadata to the (ChirpStack) Application Server, information like serial number, temperature, ... could be stored by the Application Server for various use-cases. The configuration of metadata is covered by the ChirpStack Gateway Bridge.

Improvements

Downlink LoRaWAN frame logging

Previously the first downlink scheduling attempt was logged (visible in the ChirpStack Application Server under the Gateway / Device LoRaWAN frames). This has been changed so that the scheduling attempt acknowledged by the gateway is logged. E.g. when RX1 fails, but RX2 succeeds this will log the RX2 attempt.

Bugfixes

  • Update gRPC dependency to fix 'DNS name does not exist' error. (#426)

v3.7.0

06 Feb 11:44
Compare
Choose a tag to compare

v3.7.0

Features

Improve frame-counter validation

The refactored frame-counter validation makes it possible to report different types of errors to the Application Server which will make it easier to debug frame-counter related issues.

OTAA error event

OTAA related errors will now be pushed to the Application Server to make it easier to debug OTAA related issues.

Downlink tx acknowledgements

Downlink TX acknowledgements (by the gateway) are now forwarded to the Application Server. Please note that this is the TX acknowledgement by the gateway, indicating that it was enqueued for transmission.

Syslog output

When log_to_syslog is enabled in the configuration file, the log output will be written to syslog.

Improvements

  • Implement setting max reconnect interval for MQTT gateway backend.
  • Implement getting the device queue size only (instead of fetching the complete queue).
  • Implement DNS round-robin load-balancing for gRPC.
  • Cleanup old api package (the API definitions have been moved to chirpstack-api).
  • Add uplink IDs to geolocation events for correlation.
  • Remove legacy (and broken) device-session migration code.
  • Cleanup (unused) gateway statistics code.
  • Include 500KHz channels in US915 config examples. (#462)

v3.7.0-test.1

06 Feb 11:43
Compare
Choose a tag to compare
v3.7.0-test.1 Pre-release
Pre-release
v3.7.0-test.1

v3.6.0

17 Dec 08:54
Compare
Choose a tag to compare

v3.6.0

Features

RabbitMQ / AMQP backend

This backend uses RabbitMQ for gateway communication. See the AMQP / RabbitMQ gateway backend documentation for more information. Please note that this backend does not replace the default MQTT backend.

v3.5.0

06 Dec 08:11
Compare
Choose a tag to compare

v3.5.0

Features

RX1 / RX2 selection logic

New configuration options have been added for RX1 / RX2 selection for downlink. (#429)

  • Using rx2_prefer_on_rx1_dr_lt it is possible to prefer RX2 for downlink, when the RX1 data-rate is less than the configured value.
  • Using rx2_prefer_on_link_budget it is possible to prefer RX2 for downlink when RX2 provides a better link budget than RX1.

Mac-command error handling

A new configuration option has been added to limit the number of mac-command errors (per device). This resolves the issue where the Network Server keeps trying to send a downlink mac-command to a malfunctioning device.

RPM packaging

This is the first release providing .rpm packages for CentOS and RedHat. (#454)

Improvements

Update lorawan package

The updated version contains logic for the EU868 band to either use 14 dBm or 27 dBm based on used frequency.

gRPC / Protobuf cleanup

All definitions are now imported from github.com/brocaar/chirpstack-api/go. When using the gRPC API, you must update your imports.

Environment variable configuration

Deprecate use of dots (.) in environment variable names, use double understore (__) instead. (#451)

Antenna diversity

Update lock key of MQTT gateway backend for handling of antenna diversity.

Internal improvements

The (re)usage of Redis connections has been improved.