Docker Compose upgrade instructions

Upgrading ThingsBoard to 4.4.0.1 (latest 4.4.0 patch)

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=4.4.0.1

Execute the following commands:

./docker-stop-services.sh

./docker-upgrade-tb.sh

./docker-start-services.sh

Upgrading ThingsBoard PE to 4.3.1.7 (latest 4.3.1 patch)

Starting with 4.3.1.4, ThingsBoard migrates all existing alarms to a new storage format. Alarm data is not lost. Migration time depends on the number of alarms.

From 4.2.x: the migration runs inside the upgrade script. Don't interrupt it. Plan a longer maintenance window, and do a trial run on a copy of your production database first.
From 4.3.0 – 4.3.1.3: the migration runs in the background after startup, and older alarms may not appear in the UI or API until it finishes. The Applied LTS migration 4.3.1.4 log message marks completion. With multiple tb-nodes, don't run old and new versions side by side: old tb-nodes keep creating alarms in the old format, and some of them may never appear.
Already on 4.3.1.4 or later: no action needed.

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=4.3.1.7PE

Execute the following commands:

./docker-stop-services.sh

./docker-upgrade-tb.sh

./docker-start-services.sh

Upgrading ThingsBoard PE to 4.3.0.1 (latest 4.3.0 patch)

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=4.3.0.1PE

Execute the following commands:

./docker-stop-services.sh

./docker-upgrade-tb.sh

./docker-start-services.sh

Upgrading ThingsBoard PE to 4.2.2.7 (latest 4.2.2 patch)

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=4.2.2.7PE

Execute the following commands:

./docker-stop-services.sh

./docker-upgrade-tb.sh

./docker-start-services.sh

Upgrading ThingsBoard PE to 4.2.1.2 (latest 4.2.1 patch)

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=4.2.1.2PE

Execute the following commands:

./docker-stop-services.sh

./docker-upgrade-tb.sh

./docker-start-services.sh

Upgrading ThingsBoard PE to 4.2

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=4.2.0PE

Execute the following commands:

./docker-stop-services.sh

./docker-upgrade-tb.sh

./docker-start-services.sh

Upgrading ThingsBoard PE to 4.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=4.1.0PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 4.0.2

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=4.0.2PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 4.0.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=4.0.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 4.0

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=4.0.0PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.9.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.9.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.9

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.9.0PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.8.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.8.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.8

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.8.0PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.7

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.7.0PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.6.4

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.6.4PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.6.3

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.6.3PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.6.2

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.6.2PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.6.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.6.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.6

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.6.0PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.5.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.5.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.5

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.5.0PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.4.4

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.4.4PE

Execute the following commands:

./docker-stop-services.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.4.3

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.4.3PE

Execute the following commands:

./docker-stop-services.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.4.2

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.4.2PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.4.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.4.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.4

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.4PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.3.4.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.3.4.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.3.4

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.3.4PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.3.3

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.3.3PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.3.2

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.3.2PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.3.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.3.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.3

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.3PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.2.2

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.2.2PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.2.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.2.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.2

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.2PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.1.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.1.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.0.1

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.0.1PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh

Upgrading ThingsBoard PE to 3.0

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every ThingsBoard upgrade. This ensures your ThingsBoard service runs with the latest best-practice parameters and configurations, while also guaranteeing that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of ThingsBoard — be aware that the manifests in the master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target ThingsBoard version while merging deployment files.

ThingsBoard PE service upgrade

Change the parameter TB_VERSION in the .env file:

TB_VERSION=3.0PE

Execute the following commands:

./docker-stop-services.sh
./docker-upgrade-tb.sh
./docker-start-services.sh