Releases: brocaar/chirpstack-application-server
v3.16.0-test.2
v3.16.0-test.2
v3.16.0-test.1
v3.16.0-test.1
v3.15.0
ChirpStack Application Server v3.15.0
Features
LoRaWAN 1.0.4
This adds the LoRaWAN 1.0.4 mac-version and RP002-1.0.0 and PR002-1.0.1 regional parameter revisions to the device-profile configuration.
ReEncryptDeviceQueueItems API method (AS)
This implements the ReEncryptDeviceQueueItems
method to the (internal) application-server API. This method is used by ChirpStack Network Server v3.13+ when it needs request the application-server to re-encrypt the device queue-items.
PostgreSQL schema migrations
This implements automatic schema migrations for the PostgreSQL integration. When you have manually created the tables (as documented previously), then these tables will be automatically adopted and updated to the latest version. For newly setup integrations all tables will be created automatically. (#573)
Improvements
- Don't run Docker container as root. (#520)
- Add gateway downlink info in
txack
message. (#576) - Refactor SQL schema migrations from sql-migrate to golang-migrate. (#585)
- Add option to configure Redis key-prefix.
- Add ns precision to the log timestamps.
- Fix Thingsboard rssi and snr telemetry keys + add fport, fcnt and dr telemetry keys.
- PostgreSQL integration improvements
- Store
confirmed_uplink
anddev_addr
for uplink. (#579) - Use
marshaler
configuration when encodingrx_info
to JSON. - Add
tx_info
field for uplinks. - Store
txack
payloads into PostgreSQL database.
- Store
Bugfixes
v3.15.0-test.3
v3.15.0-test.3
v3.15.0-test.2
v3.15.0-test.2
v3.15.0-test.1
v3.15.0-test.1
v3.14.0
v3.14.0
Features
Remove FUOTA
This removes FUOTA from the ChirpStack Application Server as well as handling the handling of application-layer payloads related to FUOTA. The reason for removing FUOTA is to provide more flexibility as it allows for custom FUOTA implementations. One such implementation is the ChirpStack FUOTA Server.
MQTT integration client-certificates
Like with the Gateway client-certificate feature, this feature makes it possible to generate application-specific client-certificates for authentication and authorization with the MQTT broker. In this case the CommonName is set to the application ID.
Private gateways
This feature makes it possible to make gateways private to a specific service-profile. When enabled, received uplinks can only be used by devices under the same service-profile. To enable you must assign a service-profile to the gateway and update the service-profile to enable the private gateways feature.
Note: this requires ChirpStack Network Server v3.12+.
Select ADR algorithm
This adds a ADR algorithm selection option to the device-profile. In combination with the ChirpStack Network Server pluggable ADR feature, this makes it possible to use different ADR algorithms for different types of devices.
Note: this requires ChirpStack Network Server v3.12+.
Improvements
- Add Semtech Device and Application Service integration workaround for assistance position handling.
v3.14.0-test.3
v3.14.0-test.3
v3.14.0-test.2
v3.14.0-test.2
v3.14.0-test.1
v3.14.0-test.1