Specifications

Control4 Operating System Release Notes

Saved: 9/12/2013 8:58:00 AM

DOC-00100

OS 2.5.2 Release Notes

Page 12 of 16

9. Back up the project. After completing the update, make a backup file of the Composer

Pro project. Give it a name that distinguishes it from the pre-upgrade backup. If you

ever need to restore this system, having a current backup will save you a lot of time

and effort.

3.3 Validated Upgrade Paths for OS 2.5.2

3.3.1 Primary Controller/System Upgrades

 Controllers running system versions earlier than Release 1.2.x may not be able to retain their

project through an update.

 Any Release 1.2.x or prior version system (primary controller and devices) must be updated to

Release 1.3.2. The update server automatically updates them to Release 1.3.2.234, after which

they can be updated further, but it's a multiple-step process.

 Any Release 1.3.x system can be updated to Release 1.6 or to any Release 1.7.x. The system

can be updated further afterward, but it's a multiple-step process. Home Controller HC-300s

being updated will have their internal memory repartitioned. The installer must save the project

and restore the controller after the update is completed, because the project will be lost when

the device is repartitioned.

 Only systems running Release 1.7.4 or later can be directly updated to OS 2.5.2 or later.

3.3.2 Secondary Device Upgrades

 A Home Controller HC-300 functioning as a secondary controller needs to be updated to

Release 1.6 or Release 1.7.x. This allows the system to repartition the internal memory.

 All other secondary controllers (Release 1.3.x or later) can be updated directly to any upstream

version as long as they're added to a project with a primary controller that is running the correct

version.