Upgrade to The Things Network v3.18.2 (completed)

Completed: Upgrade to The Things Network v3.18.2

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

Scheduled: Mon, 28 Mar 2022 09:30:00 +0200 until 11:30:00 +0200

Resolved: Mon, 28 Mar 2022 11: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, 25 Mar 2022 11:31:11 +0100

During this maintenance window we will upgrade The Things Network to 3.18.2

We do not expect noticeable downtime during this deployment.

Here is the changelog since the current version 3.18.1:

Added

  • Support for using Go templates to construct the Packet Broker Cluster ID from The Things Stack's Cluster ID using the pba.cluster-id-template setting.
  • Support for importing end devices using a CSV file. See documentation for the data format.
  • Support claiming end devices in an external Join Server (ex: The Things Join Server).

Changed

  • Replace as.down.data.forward to as.down.data.receive in default event filter, so that decrypted and decoded dowlink payload can be examined in the Console.

Fixed

  • Join-accept scheduling if it took more than ~1.2 seconds to process the device activation with default configuration. These slow device activations can be observed when using external Join Servers.
  • Fix issues in the webhook forms causing webhooks to be created with all message types enabled and no way of deactivating message types.
  • Fix validation issue in the webhook form not detecting message type paths with more than 64 characters.
  • Fix "reactivate"-webhook button in the Console.
  • Port returned by the LBS LNS discovery message if standard 80/443 ports are used.

In Progress

Posted: Mon, 28 Mar 2022 09:31:19 +0200

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

Completed

Posted: Mon, 28 Mar 2022 11:30:23 +0200

The scheduled maintenance has been completed.

1 Like

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

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