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

v3.28.1

Added

• The http.client.transport.compression experimental flag. It controls whether the HTTP clients used by the stack support gzip and zstd decompression of server responses. It is enabled by default.
• The http.server.transport.compression experimental flag. It controls whether the HTTP servers used by the stack support gzip compression of the server response. It is enabled by default.

Changed

• The Things Stack is now built with Go 1.21.
• Statistics for gateways are now fetched in a single request.

Fixed

• Resolve scroll jumps when selecting different tabs of a table in the Console.
• BatchGetGatewayConnectionStats RPC rights check in certain cases.

v3.28.0

Added

• Locations retrieved from gateway status messages are now be displayed in the gateway map in the Console, even when they are not received through a secure connection.
• The Network Server ID (NSID, EUI-64) used in LoRaWAN Backend Interfaces is now included in the application uplink message network metadata as well as in the Backend Interfaces HomeNSAns message that Identity Server returns to clients. The NSID is configurable via is.network.ns-id.
• It is now possible to trigger a resending of the email validation email from within the Console. The new action is part of the error screen that users see when they log into the Console without having their contact info validated yet (and the network requires validation before usage).
• Updated Japanese translations for the Console and backend.
• --grpc.correlation-ids-ignore-methods configuration option, which allows certain gRPC methods to be skipped from the correlation ID middleware which adds a correlation ID with the name of the gRPC method. Methods bear the format used by --grpc.log-ignore-methods, such as /ttn.lorawan.v3.GsNs/HandleUplink.
• Support for setting multiple frequency plans for gateways from the Console.
• The ns-db purge command to purge unused data from the Network Server database.

Changed

• Users can now request a new email for the account validation from time to time instead of once per validation, the interval between email requests is determined by is.user-registration.contact-info-validation.retry-interval and by default it is an hour.
• Traffic related correlation IDs have been simplified. Previously one correlation ID per component was added as traffic passed through different stack components. Now a singular correlation ID relating to the entry point of the message will be added (such as gs:uplink:xxx for uplinks, or as:downlink:xxx for downlinks), and subsequent components will no longer add any extra correlation IDs (such as ns:uplink:xxx or as:up:xxx). The uplink entry points are pba and gs, while the downlink entry points are pba, ns and as.
• Packet Broker Agent uplink tokens are now serialized in a more efficient manner.
• The Network Server now stores only the most recent uplinks tokens.
• The Application Server webhook health system now records failures only every retry interval while in monitor mode, as opposed to recording every failure.
  • Monitor mode in this context refers to situations in which either --as.webhooks.unhealthy-attempts-threshold or --as.webhooks.unhealthy-retry-interval are less or equal to zero. In such situations, the Application Server will record failures but will not stop the execution of the webhooks.
  • Using a retry interval of zero and a non zero attempts threshold restores the previous behavior.

Fixed

• Providing fixed downlink paths to the ttn-lw-cli devices downlink {push|replace} commands using the -class-b-c.gateways parameter. The gateways IDs are comma separated, and the antenna index i can be provided by suffixing the ID with :i (i.e. my-gateway:0 for antenna index 0). The group index j can be provided by suffixing the ID with :j (i.e. my-gateway:0:1 for antenna index 0 and group index 1). The antenna index is mandatory if a group index is to be provided, but optional otherwise.
• Gateway registration without gateway EUI not working.
• Listing deleted entities is now fixed for both admin and standard users, which previously returned an account_not_found error.
• Update to an user's PrimaryEmailAddress via a non admin now invalidates the PrimaryEmailAddressValidatedAt as it was intended.
• Negative number support in Cayenne LPP.
• Fix panic in snapcraft CLI deployment, commands will no longer generate a panic error message when telemetry is enabled.

v3.27.2

Added

• Locations retrieved from gateway status messages are now be displayed in the gateway map in the Console, even when they are not received through a secure connection.

Fixed

• Fix gateway connection stats being stuck at Connecting until the first uplink is processed in the Console.

v3.27.1

Added

• Add support for administrative_contact and technical_contact in the Console.
• Reimplement move away prompt in payload formatter views in the Console.
• Add telemetry collection for the CLI. A background process was added to the CLI in order to send the following information: Operating System, Architecture, Binary version and Golang version. The message is sent every 24 hours and it contains an unique random number as an identifier. It is enabled by default and in order to disable it, set telemetry.enable to false in the CLI configuration. For more information, consult the documentation here.
• Add telemetry collection for the IdentityServer. A background task was added in the Identity Server which is responsible for collecting information regarding the amount of each entity in the database, this has the purpose of allowing us to better understand how users are interacting with the system, an example being if tenants are using Organizations or just Users. All information is sent every 24 hours and it contains an identifier composed of the URLs present in the following configuration fields console.ui.[is|gs|ns|as|js].base-url. It is enabled by default and in order to disable it, set telemetry.enable to false in the Stack configuration. For more information, consult the documentation here.

Fixed

• OAuth clients created by an admin no longer trigger an email requesting approval from one of the tenant's admins.
• Broken network routing policy links in the Packet Broker panel of the admin panel in the Console.
• Application Server downlink related events now contain the complete set of end device identifiers, and the received at timestamp is now provided at all times.
• Wrong order of breadcrumbs in the device views of the Console.

v3.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 adminstrative 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.

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 LoRa 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

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