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.11.0

Added

  • Reset functionality in Network Server, which resets session context and MAC state (see ttn-lw-cli end-devices reset command). For OTAA all data is wiped and device must rejoin, for ABP session keys, device address and downlink queue are preserved, while MAC state is reset.
  • Store and retrieve Gateway Claim Authentication Code from database.
    • This requires a database schema migration (ttn-lw-stack is-db migrate) because of the added column.
    • This uses the same encryption key set using the is.gateways.encryption-key-id configuration option.
  • Improved handling of connection issues in the Console, as well as automatic reconnects.
  • Helpful details for synthetic meta events in the data view of the Console.
  • Support field mask paths in Storage Integration API requests.
  • CUPS redirection.
    • This requires a database schema migration (ttn-lw-stack is-db migrate) because of the added columns.
  • Configuration option (is.user-registration.enabled) to enable or disable user registrations.
  • Missing CLI commands for getting single API keys or collaborators for entities.
  • New Account App for authentication, authorization and account related functionality.
    • This introduces various UX improvements and new designs around e.g. user login, registration and the “forgot password” flow.
  • Integrate Device Repository.
  • Device Repository component to integrate Device Repository with The Things Stack. See the dr configuration section.
    • The Device Repository database is bundled automatically into Docker release images. See the ttn-lw-stack dr-db init command to manually fetch the latest changes.
  • Device repository service to the JavaScript SDK.
  • Choosing array representation for end device session keys as well as gateway EUI.
  • Storage integration panel in the Console.

Changed

  • Network Server does not store recent_uplinks, recent_adr_uplinks and recent_downlinks anymore.
  • Improved Network Server downlink task performance.
  • Authorized Application Registry is changed to Authorized Entity Registry.
    • This requires a database schema migration (ttn-lw-stack dcs-db migrate) to migrate existing claims to the new registry.
  • Improved Network Server matching performance.
  • Network Server matching mapping in the database.
    • This requires a database migration (ttn-lw-stack ns-db migrate).
  • Sending a non-empty implicitly specified field disallowed field will now cause RPCs to fail. E.g. if RPC supports paths A and A.B, sending value with A.C non-empty and field mask A would result in an error.
  • Improved content of emails sent by the Identity Server.
  • Stricter validation of the maximum length of string fields, binary fields, lists and maps.
  • Frequency plans and webhook templates are now included in Docker images, and used by default, instead of fetching directly from GitHub.
  • JavaScript entrypoints changed from oauth.css and oauth.js to account.css and account.css. Note: For deployments using custom frontend bundles (e.g. via --is.oauth.ui.js-file), the filenames have to be updated accordingly as well.
  • Authentication Providers and External Users are now hard deleted by default.
    • This requires a database migration (ttn-lw-stack is-db migrate).

Removed

  • Application Server linking. The Network Server now pushes data to the cluster Application Server instead.
    • Applications which desire to handle payload decryption within their own domains should disable payload decryption at application or device level and decrypt the payload on their own end.
    • While not backwards compatible, the decision to remove linking was heavily motivated by scalability concerns - the previous linking model scales poorly when taking high availability and load balancing concerns into account.
  • The option to disable CUPS per gateway gcs.basic-station.require-explicit-enable.

Fixed

  • Network Server DevStatusReq scheduling conditions in relation to frame counter value.
  • Missing authentication, remote_ip and user_agent fields in events when using event backends other than internal.
  • Handling of DLChannelReq if dependent NewChannelReq was previously rejected.
  • Login after user registration leading to dead-end when originally coming from the Console.
  • Frame counter display of end devices on initial page load in the Console.
  • AU915-928 data rate indexes in Regional Parameter specification versions below 1.0.2b.
← 3.11.1 3.10.8 →

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