chirpstack-application-server

v3.17.7

Improvements

• Update to Go 1.18.
• Update mqtt client dependency.
• Misc UI dependency updates.

v3.17.6

Features

• Add dev-nonce clear functionality. (#660)

Improvements

• Update LoRa Cloud integration with Modem & Geolocation Services.

ChirpStack Application Server v3.17.5-test.1

Features

• Add dev-nonce clear functionality. (#660)

Improvements

• Update LoRa Cloud integration with Modem & Geolocation Services.

v3.17.4

Improvements

• Handle email_verified as string response when using Azure as OIDC backend. (#641)
• Extends uplink event with device-profile name, id and its tags. (#621)

v3.17.3

Bugfixes

• Do not lookup from errToCode map when error is of type slice. (#631)

v3.17.2

Bugfixes

• Fix parsing of multiple TLV records in LoRa Cloud integration. (#628)
• Fix some events not showing up in device data tab.

v3.17.1

Improvements

• Increase Azure Service-Bus API timeout to 5 seconds.

Bugfixes

• Update PostgreSQL client library (fixes re-connect). (see #547)
• Fix doughnut chart styling regression after chartjs update.

v3.17.0

Features

Device metrics

This adds the following metrics to the device overview:

• RSSI
• SNR
• Uplinks per frequency
• Uplinks per data-rate

Improvements

• Add support for new tracker payload in the Semtech LoRa Cloud integration.
• Get timestamp from rxInfo if available for join event in PostgreSQL integration.
• Set http timeout on http integration. (#615)
• Docker images added for ARM v6, v7 and ARM64. (#618)

Gateway metrics

This adds the following metrics to the gateway overview:

• Uplinks and downlinks per frequency
• Uplinks adn downlinks per data-rate
• Downlinks per ack status

v3.16.0

Features

Live frame and event logs

By using a Redis Stream instead of Pub/Sub, the last frames and events (per gateway and device) can be retained, providing a configurable amount of history when opening the related pages (default is 10). This also improves the live frame and event logs interface to provide a better overview and faster rendering.

Note: Redis Streams requires Redis 5.0.0+.

Multicast refactor

This moves the multicast feature under applications, to enforce that all devices within the multicast group belong to the same application as the multicast group.

Before you upgrade, please validate that if you have any existing multicast-groups that:

1. These are not empty (they contain one or multiple devices)
2. All devices within the multicast group belong to the same application

If these conditions are met, ChirpStack Application Server will automatically migrate your multicast group(s) to the same application as your devices. In any other case, the migration will throw an error asking you to either remove the empty multicast group(s) or to re-assign the devices so that the above criteria are met.

InfluxDB v2

This adds InfluxDB v2 support by making the InfluxDB API protocol version configurable when adding the InfluxDB integration.

Improvements

• Add device-address to search functionality. (#603)
• Fetch OpenID Connect claims with UserInfo call. (#613)

Bugfixes

• Fix gatewayId hex converter in live lorawan frames. (#606)
• Fix PostgreSQL integration "unknown message type: gw.UplinkRXInfo" error when json_v3 marshaler is configured.
• Fix use GetRedisKey for key generation in MQTT integration. (#610)

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 and dev_addr for uplink. (#579)
  • Use marshaler configuration when encoding rx_info to JSON.
  • Add tx_info field for uplinks.
  • Store txack payloads into PostgreSQL database.

Bugfixes

• Fix getting network-server name in service-profile list. (#570)
• Base MQTT downlink lock key on payload content. (#577)
• Fix AppendCertsFromPEM error return. (#578)
• Fix copy key to clipboard (UI). (#593)

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.