Upgrade to The Things Network v3.19.0 (completed)

TTN Announcements
1

Completed: Upgrade to The Things Network v3.19.0

This is a cross-post of an incident on our The Things Network status page.
It will be updated automatically.

Scheduled: Mon, 18 Apr 2022 12:00:00 +0200 until 13:30:00 +0200

Resolved: Mon, 18 Apr 2022 13:30:23 +0200

Affected Components

  • Europe 1 (eu1.cloud.thethings.network): Operational
  • North America 1 (nam1.cloud.thethings.network): Operational
  • Australia 1 (au1.cloud.thethings.network): Operational

Scheduled

Posted: Fri, 15 Apr 2022 17:29:46 +0200

During this maintenance window we will upgrade The Things Network v3.19.0

We do not expect noticeable downtime during this deployment.

Here is the changelog since the current version 3.18.2:

Added

  • Session management page in Account App.
  • Status page references in the Console.
  • Notification Service API that will allow users to receive notifications about their registered entities.
    • This requires a database schema migration (ttn-lw-stack is-db migrate) because of the added tables.
  • Cluster setting cluster.cluster-id-address-template that can be used as a Go template to construct the cluster address from a cluster ID. Example value is {{.}}.thethings.example.com where {{.}} gets replaced by the configured cluster ID.
  • Packet Broker setting pba.cluster-id-from-address can be used to construct the Cluster ID from the configured cluster address. This requires cluster.cluster-id-address-template to be set.
  • Add network_server_address, application_server_address and join_server_address to applications.
    • This requires a database schema migration (ttn-lw-stack is-db migrate) because of the added columns.
  • New ADR settings API, which allows stronger control over the ADR algorithm.
    • The new settings fields can be found under mac-settings.adr, and are mutually exclusive with use-adr and adr-margin. The legacy settings need to be unset before the new API options may be used.
    • mac-settings.adr.mode.disabled completely disables the ADR algorithm.
    • mac-settings.adr.mode.static.data-rate-index, mac-settings.adr.mode.static.nb-trans, mac-settings.adr.mode.static.tx-power-index allow the user to provide static ADR parameters to be negotiated with the end device. These options persist over multiple sessions and do not require a session reset in order to be propagated to the current session.
    • mac-settings.adr.mode.dynamic.min-data-rate-index and mac-settings.adr.mode.dynamic.max-data-rate-index control the data rate index range which the Network Server will attempt to negotiate with the end device. Note that if the provided interval is disjoint with the available data rate indices, no negotiation will take place.
    • mac-settings.adr.mode.dynamic.min-tx-power-index and mac-settings.adr.mode.dynamic.max-tx-power-index have similar behavior, but for transmission power indices.
    • mac-settings.adr.mode.dynamic.min-nb-trans and mac-settings.adr.mode.dynamic.max-nb-trans have similar behavior, but for NbTrans.
    • mac-settings.adr.mode.dynamic.margin may be used to provide the margin of the ADR algorithm. It replaces the old adr-margin setting.
    • use-adr and adr-margin are still supported, but deprecated. Any future API usage should instead use the mac-settings.adr settings.

Changed

  • Sortable tables are now sorted by default in the Console

Fixed

  • Console determining gateways as "Other cluster" even though using the same host if server addresses not matching exactly (e.g. due to using different host or scheme).
  • Inconsistency in setting gateway's LNS Auth key in the Console.
  • CLI no longer informs the user that is using the default JoinEUI when passing its value via flags.
  • Generating device ID from a DevEUI when importing a CSV file.
  • The is-db migrate command that failed when running on databases created by v3.18.
  • Some error messages being displayed as error:undefined:undefined in the Console, e.g. in the live data view.
  • Missing query flag on CLI search commands.

In Progress

Posted: Mon, 18 Apr 2022 12:00:39 +0200

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Completed

Posted: Mon, 18 Apr 2022 13:30:23 +0200

The scheduled maintenance has been completed.

2

The incident on our status page was just updated with new information. The first post in this topic has been updated accordingly.