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

Added

  • ttn_lw_as_subscription_sets_publish_success_total and ttn_lw_as_subscription_sets_publish_failed_total metrics to track the number of subscription set publish attempts.
  • Application Server advanced distribution settings:
    • as.distribution.global.individual.subscription-blocks controls if the Application Server should block while publishing traffic to individual global subscribers (such as MQTT clients).
    • as.distribution.global.individual.subscription-queue-size controls how many uplinks the Application Server should buffer for an individual global subscriber. Note that when the buffer is full, the Application Server will drop the uplinks if --as.distribution.global.individual.subscription-blocks is not enabled. Use a negative value in order to disable the queue.
    • as.distribution.local.broadcast.subscription-blocks controls if the Application Server should block while publishing traffic to broadcast local subscribers (such as webhooks and application packages matching).
    • as.distribution.local.broadcast.subscription-queue-size controls how many uplinks the Application Server should buffer for an broadcast local subscriber. Has the same semantics as --as.distribution.global.individual.subscription-queue-size.
    • as.distribution.local.individual.subscription-blocks controls if the Application Server should block while publishing traffic to individual local subscribers (such as PubSub integrations).
    • as.distribution.local.individual.subscription-queue-size controls how many uplinks the Application Server should buffer for an individual local subscriber. Has the same semantics as --as.distribution.global.individual.subscription-queue-size.
  • ttn_lw_gs_txack_received_total, ttn_lw_gs_txack_forwarded_total and ttn_lw_gs_txack_dropped_total metrics, which track the transmission acknowledgements from gateways.
  • gs.txack.receive, gs.txack.drop and gs.txack.forward events, which track the transmission acknowledgements from gateways.
  • Remote federated authentication providers and external user management.
    • Authentication providers can be managed via the AuthenticationProviderRegistry service. See the tti-lw-cli authentication-providers commands for CLI support.
    • External users can be managed via the ExternalUserRegistry service. See the tti-lw-cli external-users commands for CLI support.
  • External users (users associated with a federated authentication provider) may no longer update their passwords, or request temporary passwords.
  • External users will have their information (name and email) updated on login, based on the data provided by the authentication provider.
  • Users may be associated to multiple authentication providers at the same time.
    • This requires a database schema migration (ttn-lw-stack is-db migrate) due to the relaxed unique constraint.
  • ttn-lw-stack as-db migrate command to migrate the Application Server database. This command records the schema version and only performs migrations if on a newer version.
    • Use the --force flag to force perform migrations.
  • Server-side event filtering with the names field.

Changed

  • Gateway Server default UDP worker count has been increased to 1024, from 16.
  • Application Server webhooks and application packages default worker count has been increased to 1024, from 16.
  • Application Server no longer sets the end device’s session.started_at and pending_session.started_at. The session start time should be retrieved from the Network Server, per API specification.
    • This requires an Application Server database migration (ttn-lw-stack as-db migrate) to clear the started_at field in existing (pending) sessions.
  • Console changing to server-side event filtering (used to be client-side).

Removed

  • The ttn_lw_gs_status_failed_total, ttn_lw_gs_uplink_failed_total metrics. ttn_lw_gs_status_dropped_total and ttn_lw_gs_uplink_dropped_total should be used instead, as they contain the failure cause.
  • The gs.status.fail and gs.up.fail events. gs.status.drop and gs.up.drop should be used instead, as they contain the failure cause.
  • The data_rate_index field in uplink message metadata. Observe the fully described data rate in the data_rate field instead.
  • LoRaWAN data rate index reported to LoRa Cloud DMS.
  • Dockerfile doesn’t define environmental variables TTN_LW_BLOB_LOCAL_DIRECTORY, TTN_LW_IS_DATABASE_URI and TTN_LW_REDIS_ADDRESS anymore. They need to be set when running the container: please refer to docker-compose.yml for example values.
  • CockroachDB from development tooling as well as config option within docker-compose.yml.
    • This also changes the default value of the --is.database-uri option, so it can connect to the development Postgres database by default.

Fixed

  • LoRaWAN Backend Interfaces AppSKeyReq and HomeNSReq interop calls in multi-tenant deployments.
  • Handling of NaN values in our JSON API.
  • Receiver metadata from more than one antenna is now available in messages received from Packet Broker.
  • Unhelpful error message when aborting the OIDC Login in the Console.
  • Parsing of multi-word description search queries.
← 3.16.1 3.15.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