Getting Started Concepts The Things Stack Cloud The Things Stack Enterprise Integrations API Hardware
Get The Things Stack

Release Notes

    Overview
  • 3.34.1
  • 3.34.0
  • 3.33.2
  • 3.33.1
  • 3.33.0
  • 3.32.3
  • 3.32.2
  • 3.32.1
  • 3.32.0
  • 3.31.1
  • 3.30.2
  • 3.30.1
  • 3.30.0
  • 3.29.2
  • 3.29.1
  • 3.29.0
  • 3.28.2
  • 3.28.1
  • 3.28.0
  • 3.27.2
  • 3.27.1
  • 3.27.0
  • 3.26.2
  • 3.26.1
  • 3.26.0
  • 3.25.2
  • 3.25.1
  • 3.25.0
  • 3.24.2
  • 3.24.1
  • 3.24.0
  • 3.23.2
  • 3.23.1
  • 3.23.0
  • 3.22.2
  • 3.22.1
  • 3.22.0
  • 3.21.2
  • 3.21.1
  • 3.21.0
  • 3.20.2
  • 3.20.1
  • 3.20.0
  • 3.19.2
  • 3.19.1
  • 3.19.0
  • 3.18.2
  • 3.18.1
  • 3.18.0
  • 3.17.2
  • 3.17.1
  • 3.17.0
  • 3.16.3
  • 3.16.2
  • 3.16.1
  • 3.16.0
  • 3.15.2
  • 3.15.1
  • 3.15.0
  • 3.14.2
  • 3.14.1
  • 3.14.0
  • 3.13.3
  • 3.13.2
  • 3.13.1
  • 3.13.0
  • 3.12.3
  • 3.12.2
  • 3.12.1
  • 3.12.0
  • 3.11.3
  • 3.11.2
  • 3.11.1
  • 3.11.0
  • 3.10.8
  • 3.10.7
  • 3.10.6
  • 3.10.5
  • 3.10.4
  • 3.10.3
  • 3.10.2
  • 3.10.1
  • 3.10.0

3.27.0

Added

  • The as-db purge command to purge unused data from the Application Server database.
  • RPCs and CLI command to delete a batch of end devices within an application.
    • Check ttn-lw-cli end-devices batch-delete for more details.
  • Add UserInput component to the Console to handle user id input fields by implementing an autosuggest.
  • The Identity Server configuration has a new optional restriction regarding administrative and technical contacts of entities. This limits the action of an user or organization to set these contacts only to themselves, it is disabled by default but it is possible to enable it by setting is.collaborator-rights.set-others-as-contacts as false.
  • Implement IDStringer for Network Operations Center API to increase granularity of Network Operations Center rate limiting.

Changed

  • Instead of retrying application downlinks indefinitely, the Application Server now retries them for a configured number of times. Each ApplicationDownlink message contains the attempt and max_attempts fields to indicate the current and maximum number of attempts for a specific application downlink.
  • The Application Server configuration has the as.downlinks.confirmation.default-retry-attempts and as.downlinks.confirmation.max-retry-attempts fields that configure the allowed number of retries for application downlinks. The default values are 8 for the as.downlinks.confirmation.default-retry-attempts and 32 for the as.downlinks.confirmation.max-retry-attempts.
  • The as.downlinks.confirmation.default-retry-attempts field is used for all application downlinks that were scheduled before this change and for every application downlink that does not have the max_attempts field set. On the other hand, the as.downlinks.confirmation.max-retry-attempts field ensures that the max_attempts field’s upper bound is contained and does not exceed its value.
  • The number of historical frames considered for the multi-frame query window size in the LoRaCloud Geolocation Services integration. The window size is now limited between 1 and 16 frames with 16 being the default value.
  • Packet Broker Agent now subscribes as Home Network to all DevAddr prefixes. This is to support NetID delegation where DevAddr blocks of other NetIDs should be routed to the cluster of a different NetID.

Deprecated

  • The as.uplink-storage.limit configuration option.

Removed

  • Command-line interface support for listing QR code formats and generating QR codes. This is considered the responsibility of a LoRaWAN Join Server.

Fixed

  • The gateway data rate utilization panel in Network Operations Center now includes all gateway uplink traffic, not just traffic that has been processed for an end device.
    • This requires a Network Operations Center migration (tti-lw-stack noc-db migrate).
    • Existing data is not migrated: only new data will be shown in the panel.
  • End device data stream not being closed when navigating away from end device pages, which could cause event streams stopping to work due to too many open connections.
  • Editing certain fields in the Tenant Settings form, more specifically in the presence of cluster overrides and sending the patch update.
← 3.27.1 3.26.2 →

On this page

Sections

Getting Started

Concepts

The Things Stack Cloud

The Things Stack Enterprise

Integrations

API

Hardware

Sitemap

View our Sitemap

Contributing

GitHub

About Us

The Things Industries