Releases: brocaar/chirpstack-network-server
Releases · brocaar/chirpstack-network-server
0.18.0
0.17.2
0.17.1
Features:
- TTL of node-sessions in Redis is now configurable through
--node-session-ttl
/NODE_SESSION_TTL
config flag.
This makes it possible to configure the time after which a node-session
expires after no activity (#100). - Relax frame-counter mode has been changed to disable frame-counter check mode
to deal with different devices (#133).
0.17.0
Features:
- Add
--extra-frequencies
/EXTRA_FREQUENCIES
config option to configure
additional channels (in case supported by the selected ISM band). - Add
--enable-uplink-channels
/ENABLE_UPLINK_CHANNELS
config option to
configure the uplink channels active on the network. - Make adaptive data-rate (ADR) available to every ISM band.
0.16.1
0.16.0
Note: LoRa Server now requires a PostgreSQL (9.5+) database to persist the
gateway data. See getting started for more information.
Features:
- Gateway management and gateway stats:
- API methods have been added to manage gateways (including GPS location).
- GPS location of receiving gateways is added to uplink frames published
to the application-server. - Gateway stats (rx / tx) are aggregated on intervals specified in
--gw-stats-aggregation-intervals
(make sure to set the correct
--timezone
!). - When
--gw-create-on-stats
is set, then gateways will be automatically
created when receiving gateway stats.
- LoRa Server will retry to connect to the MQTT broker when it isn't available
(yet) on startup, instead of failing.
0.15.1
0.15.0
Features:
- Node-sessions are now stored by
DevEUI
. Before the node-sessions were stored
byDevAddr
. In case a singleDevAddr
is used by multiple nodes, the
NwkSKey
is used for retrieving the corresponding node-session.
Note: Data will be automatically migrated into the new format. As this process
is not reversible it is recommended to make a backup of the Redis database before
upgrading.