Upgrade thingsHub

Terminologies:

• Upgrade Path: A defined order for upgrading to the desired version. This path may involve multiple intermediate steps.

• Mandatory Versions: Specific versions within the upgrade path that are required for successful installation of the target version. These versions will be clearly identified as "(mandatory)" for your reference.

Introduction

We recommend that you upgrade thingsHub often to stay current with the latest fixes and enhancements. You can upgrade to any of the supported releases from any supported release.

Because thingsHub upgrades are backward compatible, the upgrade process is mostly straightforward, and existing devices, data tables, integration or dashboard will not change.

There are, however some versions that are must in the upgrade path. You should not upgrade to any later versions before upgrading to these compulsory versions. These must-upgrade versions are marked as (mandatory) in the Page title.

Following the Upgrade Path:

Upgrade path is the mandatory steps that your thingsHub system must go through before upgrading to the desired version.
It is critical to adhere to the designated upgrade path, particularly regarding mandatory versions. Skipping these intermediate steps can lead to:

• Compatibility Issues: Newer versions may not function correctly with older, unsupported versions.

• Software Bugs: Bugs or unintended behavior may arise due to missing functionalities from skipped versions.

• System Instability: In the worst-case scenario, skipping mandatory versions could render your system unstable or inoperable.

Computing the Upgrade Path

Upgrade path from version A to version B will include all the mandatory versions between versions A and B, followed by the version B at the end.

For example: To upgrade from 5.1 to 5.4, the upgrade path will look like:
5.1 → 5.3 → 5.4

To learn what’s available in a thingsHub release, refer to What’s New page.

Upgrading to specific thingsHub Version

Refer to any of the following upgrade guides: