v3.32.0

Added

• Newly redesigned The Things Stack Console. The most notable changes are as follows:
  • New look and feel
  • New sidebar-based navigation and structure
  • Top entities are automatically stored and displayed for faster access
  • More useful panels in the overviews of gateways, applications and end devices
  • Quick search feature to search globally for any entity
  • New event overlay for better in-context event examination
  • Notifications can now be viewed from within the Console
• Support for managed gateways and claiming through The Things Gateway Controller.
• Support for The Things Industries gateway protocol. This is adds a new pair of ports to Gateway Server: 1889 for Envoy or Traefik terminated TLS mutual authentication, and 8889 for The Things Stack terminated TLS mutual authentication.
• Option to filter the output of the List RPCs for end devices and gateways based on when they were updated.
  • ListGatewaysRequest and ListEndDevicesRequest RPCs have a new Filter field that supports an updated_since timestamp.
• Preparation for universal rights assigned to users.
  • This requires a database schema migration (ttn-lw-stack is-db migrate).

Deprecated

• Experimental RPCs AuthorizeGateway and UnauthorizeGateway of the Gateway Claiming Server (GCLS).
• CUPSRedirection field of ClaimGatewayRequest.

Removed

• authorize and unauthorize sub-commands of the gateway claim command.

Fixed

• Fix unhandled video stream in QR code scanner

v3.31.1

Changed

• Gateway ID and device ID are not autogenerated and prefilled anymore.

v3.31.0

Added

• Europe 868.1 MHz single channel frequency plan.
  • This is experimental and may be removed or hidden in the future.

Changed

• The rate limit key for LoRa Basics Station has changed from gs:accept:ws to gs:accept:semtechws/lbslns.

Fixed

• Fix potential issue with application event stream stopping after showing initial events.
• Fix storybook compiling issue.

v3.30.2

Fixed

• Increased the timeout for Basic Station gateways sending HTTP headers. There should now be enough time for embedded devices with little to no hardware acceleration to perform a TLS handshake. In particular, The Things Indoor Gateway can now connect to The Things Stack presenting a ECDSA certificate.
• Reconnect a gateway when the antenna gain is adjusted.
• Fixed length bytes fields, such as EUIs, device addresses or device keys, are no longer considered as being all zero when provided as null values in JSON requests.

v3.30.1

Added

• Support fine-grained NbTrans controls while using Dynamic ADR mode in the Console.
• User bookmark listing now supports filtering bookmarks by entity type.
  • This can be specified by setting entity_types field in ListUserBookmarksRequest.

Fixed

• Show both AFcntDown and NFcntDown in the Device overview in the Console.
• Fixes the keys displayed in the session information section of overview tab of an End Device in the Console - for LW 1.1.x, replaces NwkSKey with FNwkSIntKey. For LX 1.0.x display only the NwkSKey and AppSKey.

v3.30.0

Added

• Fine grained NbTrans overrides for the dynamic ADR mode. See the --mac-settings.adr.mode.dynamic.overrides.data-rate-[index].min-nb-trans and --mac-settings.adr.mode.dynamic.overrides.data-rate-[index].max-nb-trans family of parameters.
• Support for storing user's bookmarks in the database.
  • This requires a database schema migration (ttn-lw-stack is-db migrate) because of the new user_bookmarks table.
• Support for storing user's Console Preferences in the database.
  • This requires a database schema migration (ttn-lw-stack is-db migrate) because of the new console_preferences column in the users table.

Changed

• Searching for collaborators displays only accounts that are not already attached to the entity's collaborator list.

v3.29.2

Fixed

• Memory leak in components which heavily use HTTP clients, such as the Application Server.

v3.29.1

Added

• Option to store rate limits in Redis. When used, the rate limits are applied over the entire cluster instead of per-instance.
• Field complement_collaborators was added to SearchAccounts. Allows an user to request the accounts that are not already attached to the entity's collaborator list.

v3.29.0

Added

• relays command to ttn-lw-cli, which enables the management of LoRaWAN relays, including their configuration and uplink forwarding rules.

Changed

• User's primary email address validation is now decoupled from deprecated ContactInfo field.
  • This requires a database schema migration (ttn-lw-stack is-db migrate) because of the new email_validations table.
• Entities' ContactInfo field now returns information regarding the administrative and technical contacts instead of the deprecated ContactInfo information.
  • This requires a database schema migration (ttn-lw-stack is-db migrate) due to the removal of old information in the contact_infos table.
  • The emails of the administrative and technical contacts are only returned in the ContactInfo field if the caller has the appropriate rights.
• Organizations can now opt out from sending administrative and technical notifications to all collaborators.
  • New organizations do not send administrative and technical notifications to all collaborators by default.
  • To alter the behavior update the organization's fanout_notifications field.

Removed

• The http.client.transport.compression and http.server.transport.compression experimental flags.

Fixed

• Fix Add collaborator form not validating collaborator on submit in the Console.

v3.28.2

Added

• Rate limiting classes for individual HTTP paths.
• Rate limiting keys for HTTP endpoints now contain the caller API key ID when available. The caller IP is still available as a fallback.
• Allow users to set multiple frequency plans only in the same band in the Console.

Changed

• Server side events replaced with single socket connection using the native WebSocket API.
• Gateways now disconnect if the Gateway Server address has changed.
  • This enables CUPS-enabled gateways to change their LNS before the periodic CUPS lookup occurs.
• The LoRa Basics Station discovery endpoint now verifies the authorization credentials of the caller.
  • This enables the gateways to migrate to another instance gracefully while using CUPS.

Fixed

• Batch gateway rights assertions when multiple membership chains are available (for example, both via a user and an organization).