[release] ChirpStack v4.1

Announcements
1

v4.1.0

Features

API request logging

This feature logs API requests to Redis Streams. This enables external services to monitor for example device create, update and deletes by reading from the Redis Streams. A code-example can be found here.

Uplink logging for unknown devices

While the feature to log frames was already present, it was not possible to only read uplink frames of devices that are unknown. This extends the frame logging feature to also log uplinks for unknown devices, in which case DevEUI 0000000000000000 is used. A code-example for reading the frame log can be found here.

Event logging

A code-example to read event logs from the Redis Streams was added. It can be found here.

Improvements

  • Make metadata fields in gateway messages consistent.
  • Emit all fields for JSON integration messages, even if they are their default values. (#63)

Bugfixes

  • Fix Redis pipelined commands in case Redis Cluster is configured.
  • Fix UI notifications z-index.

Other changes

  • The import-ttn-lorawan-devices sub-command has been renamed to import-legacy-lorawan-devices-repository.
5 Likes
2

Thanks for your great work.

3

v4.1.1

Improvements

  • Update JS API dependencies to latest versions.
  • Replace relative paths in Rust API build to absolute. (#69)

Bugfixes

  • Fix setting the full frame-counter to the uplink frame after resolving the device-session (this can affect payload decryption).
2 Likes
4

v4.1.2

Improvement / bugfix

  • Do not wait for integrations to finish before sending downlink.
2 Likes
5

v4.1.3

Bugfixes

  • Fix Redis key_prefix configuration. While this value could be configured, it was not applied to the generated keys.
  • Fix header z-index issue in UI. This was causing the dropdowns to render partly behind the header.
4 Likes