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

Added

  • tti-lw-stack dcs-db purge command to remove authorized entities from the DCS registry.
  • Support for scanning a QR code that only contains the hexadecimal encoded DevEUI.
  • Experimental flag ns.adr.auto_narrow_steer. When enabled, end devices which do not have an explicit channel steering mode will be steered towards the LoRa narrow channels.
  • Add a NOC button in the application and end-device views in the Console.
  • The storage integration now supports iterating pages of uplinks, instead of retrieving all of the uplinks at once.
    • The Application Server will now return a continuation token via the X-Continuation-Token header. The continuation token can be provided to a subsequent request in order to continue the iteration from the last retrieved uplink, using the continuation_token parameter.
    • The continuation token replaces any other filtering options such as the type, limit, after, before, f_port, order or field_mask. These have to be provided only in the initial request - subsequent iterations no longer need to provide them, as they are saved as part of the token.
    • This requires a storage integration database migration (ttn-lw-stack storage-db migrate).

Changed

  • The Network Operations Center applications and end devices insights are no longer experimental.

Removed

  • Device claiming that transfers devices between applications is now removed.
    • Related fields in the ClaimEndDeviceRequest message are reserved.
    • RPCs AuthorizeApplication and UnauthorizeApplication of the Device Claiming Server will now return an Unimplemented error code.
    • ttn-lw-cli end-devices claim, ttn-lw-cli applications claim, ttn-lw-cli applications claim authorize and ttn-lw-cli applications claim unauthorize commands are no longer supported and will return an error.
    • --with-claim-authentication-code option for ttn-lw-cli end-devices create is no longer supported.
    • If the DCS does not support claiming for the provided JoinEUI, ttn-lw-cli end-devices create will no longer fallback to create devices in the Cluster Join Server and instead error.
    • tti-lw-stack dcs-db migrate and tti-lw-stack dcs-db clean commands are removed.
    • The deprecated Claim App (by default available via /claim) has been removed and now redirects to the Console.

Fixed

  • Console not applying webhook field masks when creating a webhook from a template that has field masks set.
  • LoRa Basics Station PONG messages will now contain the application payload of the associated PING, as required by the WebSockets specification.
    • This fix enables PING/PONG behavior for non reference implementations of the LNS protocol.
  • Fix crash of “Edit webhook” view due to invalid Authorization header encoding in the Console.
← 3.26.1 3.25.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