Control4 Operating System (OS) Release Version 2.0.6 ......Control4® OS Release 2.0.5 (OS 2.0.5) is a maintenance release for OS 2.0 system installs and is the default OS 2.0 version

Copyright © 2010 Control4. All Rights Reserved.

Saved: 1/14/2011 11:34:00 AM TechDoc00046 Page 1 of 38

Control4 Operating System (OS) Release Version 2.0.6 Release Notes




About Control4 Control4, a leading provider of the operating system for the smart home, delivers intelligent control of consumer electronics products, appliances and networking systems through an

easy-to-use and intuitive software interface. Founded in 2003, the company delivers affordable automation and control of lighting, music, video, HVAC, security, and energy management

systems to the broad market through more than 1,600 custom integrators, retail outlets, and distributors in over 65 countries. Control4 is the platform of choice for major consumer electronics companies, hotels, businesses and utilities that require an intelligent, open and affordable control solution. For more information visit www.control4.com.

Disclaimer Control4® makes no representations or warranties with respect to this publication, and specifically disclaims any express or implied warranties of merchantability or fitness for any

particular purpose. Control4 reserves the right to make changes to any and all parts of this publication at any time, without any obligation to notify any person or entity of such changes.

Licenses

GNU GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION (Section 3.b.) You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of

Sections 1 and 2 ab ove provided that you also do one of the following:

Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete

machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange. The complete text for this license is available on the Control4 website.

Gracenote Gracenote®, Gracenote logo and logotype, and the "Powered by Gracenote" logo are either a registered trademark or a trademark of Gracenote, Inc. in the United States and/or other

countries. Music and DVD recognition technology and related data are provided by Gracenote®. Gracenote is the industry standard in Music and DVD recognition technology and related

content delivery. For more information visit www.gracenote.com.

Libertas Libertas Firmware copyright statement for Touch Screens 6/26/09

Copyright (c) 2006, One Laptop per Child and Marvell Corporation. All rights reserved.

Redistribution. Redistribution and use in binary form, without modification, are permitted provided that the following conditions are met:

* Redistributions must reproduce the above copyright notice and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of Marvell Corporation nor the names of its suppliers may be used to endorse or promote products derived from this software without specific prior written permission.

* No reverse engineering, decompilation, or disassembly of this software is permitted.

* You may not use or attempt to use this software in conjunction with any product that is offered by a third party as a replacement, substitute or alternative to a Marvell Product where a

Marvell Product is defined as a proprietary wireless LAN embedded client solution of Marvell or a Marvell Affiliate. DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND

CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND

FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,

INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR

TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE.

Copyright ©2011 Control4. All rights reserved. Control4, the Control4 logo, the 4-ball logo, the Control4 Certified logo, theControl4 iQ logo, and Everyday Easy are registered trademarks or trademarks of Control4 Corporation in the United States and/or other countries.

Contact Information Control4 Corporation

11734 S. Election Road

Salt Lake City, UT 84020 USA http://www.control4.com

Part Number: TechDoc00046, Rev A. (OS 2.0.6) Control4 Operating System (OS) Software Release 2.0.6 Release Notes




Contents 1. Introduction ......................................................................................................................... 5

1.1 OS 2.0.6 ............................................................................................................................ 5

1.2 OS 2.0.5......................................................................................................................... 5

1.3 OS 2.0.4 ........................................................................................................................ 6

1.4 OS 2.0.2......................................................................................................................... 6

1.5 OS 2.0.1 ......................................................................................................................... 7

1.6 OS 2.0............................................................................................................................ 8

1.7 Considerations and Advantages................................................................................. 9

1.7.1 OS 2.0 ........................................................................................................................ 9

2. New Features in OS 2.0—Quick Reference ..................................................................... 10

2.1 Flash-Based Navigator .............................................................................................. 11

2.2 4Store Applications ................................................................................................... 12

2.3 ZigBee Pro Improvements ........................................................................................ 13

2.4 Enhanced Media Database and Other Improvements to the Audio System ........ 14

2.5 Improved Customization ........................................................................................... 15

2.6 Other New Features in OS 2.0 .................................................................................. 16

2.6.1 Other Enhancements or Software Changes in OS 2.0 ........................................ 17

2.7 Changes Inherited from Release 1.8.2 ...................................................................... 20

3. Other Changes in OS 2.0 .................................................................................................. 22

3.1 Defects Resolved ....................................................................................................... 22

4. Known Limitations ............................................................................................................. 23

4.1 OS 2.0.......................................................................................................................... 23

4.1.1 New Limitations ...................................................................................................... 23

4.1.2 Pre-Existing Limitations......................................................................................... 26

5. Questions ........................................................................................................................... 30

5.1 Do I Need to Update My Customers to OS 2.0?...................................................... 30

5.2 Can I Continue to Install Prior Release Systems? ................................................... 30

5.3 What Performance Changes Should I Expect from OS 2.0? .................................. 30

6. Firmware Versions for OS 2.0 Systems ........................................................................... 32

7. Upgrading to OS 2.0 ......................................................................................................... 33

7.1 OS 2.0 Software License ........................................................................................... 33




7.2 Quick Reference to OS 2.0 Upgrade Process ......................................................... 33

7.2.1 Pre-Work Prior to Arrival at the Customer’s Location ....................................... 34

7.2.2 Upon Arrival at the Customer’s Location ......................................................... 34

7.3 Validated Upgrade Paths .......................................................................................... 35

7.3.1 Primary Controller/System Upgrades .................................................................. 35

7.3.2 Secondary Device Upgrades ............................................................................. 36

7.4 Residential Software Product Releases ................................................................... 36

8. Technical Support Contact Information .......................................................................... 38

9. Legal Notice ....................................................................................................................... 38




1. Introduction The Control4® Release 2.0.6 (OS 2.0.6) is the best release yet for new Installations and is strongly recommended for those systems which will be using the 5" In-Wall Touch Screen. Note: For customers already running the OS 2.0.4 or OS 2.0.5 releases, there is no need to upgrade to OS 2.0.6 unless one of the changes cited below is needed for improved system operation.

1.1 OS 2.0.6 OS 2.0.6 is a maintenance release for OS 2.0 system installations and is the default OS 2.0 version for new OS 2.0 installations and upgrades. This release provides support for the 5" In-Wall Touch Screen and includes the following changes:

• 5" and 7" In-Wall Touch Screens—Enhanced the X and Y scaling factors which improves usability.

• Navigator • Resolved problem where the "Loading..." popup could get stuck and would overlay on the

Navigator UI • Modified the IP camera interface to send integer values only when sending pan/tilt

commands to the camera. Corrected a problem where some models of IP cameras could not be controlled through the UI.

1.2 OS 2.0.5 Control4® OS Release 2.0.5 (OS 2.0.5) is a maintenance release for OS 2.0 system installs and is the default OS 2.0 version for new OS 2.0 installations and upgrades. This release provides support for the 5” In-Wall Touch Screen and now enables the Home Controller HC-200B to be used as a dedicated Primary Controller in a multi-controller system. This release includes the following changes:

• 5” In-Wall Touch Screen—UI and Intercom support for this new product. • HC-200B—The HC-200B can now be used as a dedicated Primary Controller in a multiple-

Controller system. Note: Control4 recommends that the Navigator process be disabled on the HC-200B when used in this configuration.

• Navigator • Updated the Flash-based Navigator UI on all devices with the new Control4 logo. • Corrected a problem where the main page icons weren't properly displayed after

reconnecting to Director. • Corrected a problem where the main page icons weren't properly displayed when

accessed from the Custom Home page. • Corrected a problem where the Flash Navigator could stop responding when working with

very large playlists. • Corrected a problem where an unexpected bar may appear when using the Custom

Home page. • Corrected a problem where some IP camera models would not show on the Flash UI but

did on prior OS 2.0 versions.




• Updates—Resolved certain problems with deleting files, downloading packages, and installing packages that could cause the update process to stall on the HC-200 and HC-300 Controllers.

• Composer—Removed the WAV file extension from the default list of extensions for audio file scanning.

• Carrier Infinity—Updated the Carrier Infinity driver to correct problems with the UI not properly controlling the Carrier Infinity system.

1.3 OS 2.0.4 Control4 OS Release 2.0 (OS 2.0.4) is a maintenance release for OS 2.0 system installs. This release includes the following changes:

• Resolved a problem with snmpd/crond system processes which could cause Controllers to become inoperable after a few weeks of operation until they are rebooted.

• Updated the WiFi driver for the 7” In-Wall Touch Screen. • Updated the system firmware for the HC-1000 to ensure that the file system check procedure

runs properly when needed. • Corrected the problem where the HC-200 Primary Controller was disabling the IO Extender. • Added the ability for Composer HE to back up a project.

1.4 OS 2.0.2 Control4 OS Release 2.0 (OS 2.0.2) is a maintenance release for OS 2.0 system installs. This release provides support for the 7" Infinity Edge Touch Screen and Intercom, and resolves a small number of other issues. The changes to resolve other issues include:

• Controllers • Resolved a problem where the Controller would report "too many open files" and would

not allow Composer to connect. • Resolved a problem with the Home Theater Controller not correctly showing the state of a

device connected to the Contact Sensor. • Navigator. Updated the Flash Navigator to correct a problem with certain models of

Panasonic IP cameras which couldn't be viewed via the Navigator interface. • Network. Added support for resetting DNS from static to dynamic when a network reset is

performed. • Thermostat

• Updated the firmware for the Control4 Wireless Thermostat that resolves the problem when the heat or cool setpoint is changed by the Navigator; it would change correctly but the Hold mode wasn't correctly reflected on the Navigator interface.

• Updated the Control4 Wireless Thermostat driver to correct a problem with the scheduled event setpoints being sent for the wrong day.




1.5 OS 2.0.1 Control4 OS Release 2.0 (OS 2.0.1) is a maintenance release for OS 2.0 system installs. This release provides support for new hardware products and corrects problems encountered with the initial OS 2.0 release.

• 7” Portable Touch Screen • Added support for putting the Touch Screen into suspend mode via the Suspend button.

• Composer HE • Modified Composer HE so that it does not depend on the digital certificate installed by

Composer Pro for proper operation. Composer HE will now work properly when installed on a computer which doesn’t have Composer Pro installed.

• Composer Pro • Added support for password challenge when connecting to a Primary Controller with a

non-default system password. • Controllers

• Updated Home Controllers HC-200, HC-300, HC-200B, and HC-300C. • DriverWorks

• Corrected a problem with bitwise operations returning an incorrect value. • Internationalization

• Added an informational message to inform the Installer that Director restarts when the language is changed.

• If the locale is not set, English will show as the default. • Added the correct font files for Chinese (People’s Republic). • Additional language support provided for Hebrew, Croatian, and Italian.

• Media • Improved the project conversion ability of OS 2.0 so that the cover art and playlists are

properly converted if a backup project created in an earlier version is loaded. • Corrected the problem where the apostrophe character (‘) in a playlist was converted to

“'.” • Added an option to change the Song Artist metadata automatically for all songs in an

album when Album Artist field is changed. • Added support to write tags to FLAC files to the Media Database conversion wizard. • Added driver for Media Player V2.

• Navigator • On Screen. Added support for Pan/Tilt control for an IP camera using the up, down, left,

right arrows on the System Remote Control device. • Corrected the problem where the IP Camera image remained on the Navigator interface

when it shouldn’t be displayed. • Corrected a problem where the main page Thermostat’s temperature icon was not

showing the correct mode. • Improved the ability to use Favorites to access pages within the My Music and Rhapsody

interfaces. • Improved the On-Screen navigation on various interface screens.




• Improved the Alpha jump navigation (On-Screen Navigator) for movies. • Corrected a problem when using Page Down on the On-Screen Navigator movies screen.

Movies were being skipped. • Corrected a problem where the Now Playing information of the Tuner interface was not

showing the current RDS data. • Corrected problems which could cause the Now Playing bar to present inaccurate track

numbers. • Corrected the problem where the Now Playing interface had the wrong navigation menu

structure when the iPod Dock was the selected device. • Corrected a problem where the Navigator would not properly select or navigate artists

and albums with an “&” in their name. • Corrected a problem with focus disappearing while navigating an iPort. • Improved the ability to recover after a dropped network connection (reconnect to

Director). • Corrected a problem where the Custom Buttons were not made visible to the Flash

Navigators after using Refresh Navigators. • Corrected a problem with invert relay devices not showing the proper state on the Flash

Navigator. • Corrected a problem with the Security interface not showing the correct arm/disarm state

on initial entry. • Corrected a problem where Navigator on the Touch Screen was restarting after going to

the Network Settings page of the UI. • Added a confirmation popup to the Room Off and Zone Off commands on the Touch

Screens to protect against inadvertent "Room Off" when the user is adjusting the volume. • Ensured that Refresh Navigator will update the project information for all Navigators after

the project is reloaded. • Added support for a password challenge when connecting to a Primary Controller with a

non-default system password. Flash-based Navigators will prompt for the password when they make the initial connection to Director after the password has been changed (or after the upgrade if the system is already configured for a non-default password). If you don't want the Navigator devices to prompt for a password, you must set the password on the Primary Controller to the Control4 default (t0talc0ntr0l4!).

• Other • Add the Reset System password functionality to Network Reset. • Improved the ability for network file storage devices to remain connected or be

reconnected by the system. • Added support to the System Manager UI for including spaces in the ASCII WPA key. • Corrected a Disc Changer proxy problem which prevented the Sony CX777ES and Sony

CX7000ES drivers from correctly selecting a new movie if a movie was already being played.

1.6 OS 2.0 Control4 OS Release 2.0 (OS 2.0.0.80198) is a comprehensive software release featuring changes to the Control4 Navigator interfaces, new functionality, new SDKs, support for new hardware products, and various other changes.




OS 2.0 provides the following benefits for customers:

• An updated look and a streamlined user experience • Faster access to audio and video content and more seamless integration with iTunes,

Windows Media Player and other media management tools • Improved customization of UI and system services • Support for non-English languages within Navigator

OS 2.0 provides the following benefits for Control4 Dealers and Installers:

• The ability to provide compelling new custom solutions for customers without adding significant programming

• Improvements in third-party solution offerings arising from the certification program and Control4 SDKs

• New software-enabled functionality and new hardware products OS 2.0 provides the following benefits for third-party partners:

• A significantly more capable platform 4Store applications—local and server interfaces for developing custom applications Flash-based Navigator SDK—allows the development of control applications and

custom interfaces DriverWorks SDK—contains continued improvements to features and documentation

based on experience gained working with active partners • Preferential display of Control4-certified drivers in Composer driver searches

These Release Notes contain information you need to understand before deciding whether this product should be installed on your new customers’ systems or as an update for existing customers’ systems.

1.7 Considerations and Advantages

1.7.1 OS 2.0 Control4® OS 2.0 is recommended for new customer installations and as an upgrade path for existing customers. OS 2.0 is required in order to utilize some new Control4 hardware products within a Control4 system install.

WARNING: The OS 2.0 release utilizes ZigBee® Pro for ZigBee RF communications. Controllers and ZigBee firmware devices upgraded to OS 2.0 cannot be downgraded to Release 1.7.4 or prior versions. Make sure you read these Release Notes and the Composer Pro Software Release Update Instructions – 1.7.4 to 2.0 before you decide whether upgrading to OS 2.0 is a good option for your customers. WARNING: A few legacy products are not supported in OS 2.0. Other products are supported but may have limited functionality or may not provide access to new OS 2.0 capabilities. See Section 4, “Known Limitations.”




1. Control4 recommends that customer systems running Release 1.8.2 (or 1.8.0) be upgraded to OS

2.0. • Both OS 2.0 and Release 1.8.2 utilize ZigBee Pro for RF communication within the system.

Control4 has made improvements to the ZigBee Pro infrastructure (firmware and server processes) in the OS 2.0 release. These will improve the performance of ZigBee Pro over the Release 1.8.2.

• Please use Composer 2.0 to update projects running on Release 1.8.2 to OS 2.0. However, if you need to make project changes to a Release 1.8.2 system prior to updating it to OS 2.0, please use Composer 1.8.2.

2. Control4 will continue to support Release 1.7.4 for existing customers. • Please use Composer 1.7.4 to manage projects running on Release 1.7.4. Other versions of

Composer may introduce incompatible drivers or project settings. • Most new products ordered (both new hardware products and existing product) from Control4

will ship from Control4’s warehouse with Release 1.8.2 or OS 2.0 or compatible firmware installed. If you need to order products capable of running in an existing Release 1.7.4 system, please let your Inside Sales Associate know of this requirement when the order is placed.

3. Control4 no longer provides support for prior versions of software. We recommend that these systems either be left “as is” or be upgraded to Release 1.7.4 or to OS 2.0. • Control4 will not provide new or replacement hardware products for prior versions. • Customers may continue to run prior versions for as long as they want to. However, Control4

Technical Support will have limited ability to answer questions and provide assistance for older product releases.

• Release 1.3.2.442 was the final release of the Release 1.3.x product line. While Control4 doesn’t actively support this release, it is the best/final release of this line and may be considered as an option for customers who are using a Home Theater Controller or a Media Controller as the Primary Controller within the system.

• Customers systems running Release 1.6.0 or any 1.7.x release should be upgraded to Release 1.7.4 or to OS 2.0.

IMPORTANT: OS 2.0 is a complete system software release. All Control4 devices have new software or firmware. The update process will require that all devices in the entire Control4 system be updated.

2. New Features in OS 2.0—Quick Reference This section lists the new features and software changes for Control4® OS 2.0. Subsequent sections will provide additional information about many of these new features. For additional information, please see the Composer Pro Getting Started online Help in Composer Pro or the online Composer Pro User Guide. Both of these documents are available in PDF format also in the Control4 Dealer web site (Support > Product Information). Basic System Capabilities in OS 2.0:

• Flash-based Navigator with new functionality and improved user experience • 4Store applications • ZigBee Pro improvements




• New media database, media scanning functionality • AAC codec support • Zones page improvements • Custom Home pages • Favorites • Macros • Page Flips – programmatic • Whole-home access in Flash Navigator • Composer Pro software activation • Electronic licensing—all Control4 software licenses • Software License—Pay for Update • Secure Connections Only (SSL) • Locale (Internationalization) • Hide/Show/Order Lights and Lighting Scenes • Off state for Lighting Scenes • Certified device drivers visibility • Programming Detective • WPA Support

2.1 Flash-Based Navigator One of the most noticeable changes in OS 2.0 is the new Control4® user interface (Navigator). The Flash-based Navigator runs on most of the Control4 Navigator UI devices. It features an improved look, informational navigation elements, and will enable you to provide an improved user experience for your customers. The Navigator interfaces available used within an OS 2.0 system include:

• Flash-based Navigator—provides new functionality and most prior version functionality (with some limitations)

• Legacy GUI Navigator—provides all functionality provided in prior versions but doesn’t provide all new functionality

• Flash-based Web Navigator—essentially the same as the Flash-based Navigator but doesn’t support Rhapsody or 4Store applications

• Legacy HTML Web Navigator—provides all functionality provided in prior versions and doesn’t require Flash support in the Web browser

• List Navigator—provides all functionality provided in prior versions • iPhone/itouch and iPad Navigator—OS 2.0 versions feature a new UI but there’s no

support for 4Store applications




Navigator Device Supports Update to OS 2.0

User Interface

Remote V1/V2 No N/A

SR-250 Yes List Navigator

LCD Keypad (POE and ZigBee) Yes List Navigator

Mini Touch Screen V1/V2 Yes Legacy Navigator

10.5” Portable Touch Screen V1 Yes Legacy Navigator

10” Wall Mount Touch Screen Yes Legacy Navigator

Home Theater Controller and Media Controller (On-Screen)

Yes (Secondary Controller only)

Legacy Navigator

Web Browser (not Flash capable) Yes Legacy HTML Navigator

10.5” Portable Touch Screen V2 Yes Flash Navigator

Home Controllers HC-200, HC-300, HC-500 (On-Screen)

Yes Flash Navigator

7” Wall Mount, Portable, Tabletop Touch Screens

Yes Flash Navigator

Web Browser (Flash capable) Yes Flash Navigator

iPod touch, iPad, iPhone Yes Custom Navigator

2.2 4Store Applications Control4® has created the 4Store application platform and included it with each Flash-based Navigator (except Web Navigator). Two (2) default applications are provided with the OS 2.0 release: Weather and News applications are automatically installed on the Flash-based Navigators. Other applications can be purchased and downloaded from 4Store.com. Applications purchased from 4Store.com are licensed for use anywhere on the Control4 system associated with the consumer account and can run on all Navigator devices within the system. If a customer has multiple Control4 systems, they will need multiple 4Store consumer accounts in order to purchase and install applications—one (1) for each system. Some applications may require a Control4 driver to provide full functionality. The application developer can (but doesn’t have to) indicate a required driver in the 4Store application which they create. If a driver is required, a Control4 Dealer will need to be involved in the installation of the driver prior to the application being downloaded. 4Store application developers can also (but aren’t required to) provide a demo mode for consumers to try out their application before getting the needed drivers installed. Control4 reviews all 4Store applications prior to their availability on 4Store.com. Review considerations include: Truth in Advertising, Stability, Security, Resource Requirements, Content (no “Adult” content), and first-pass Legal considerations. We do not review applications based on usefulness, user interface, or redundancy.




Application developers are responsible for all support associated with their applications. For more information about 4Store, including the 4Store application developer program, please see www.4store.com.

2.3 ZigBee Pro Improvements Control4® began using ZigBee Pro for RF communications with Release 1.8.0 in August 2009. OS 2.0 provides continued improvements in ZigBee Pro operation within the system, including the following:

• LCD Keypad. The ZigBee LCD Keypad now has ZigBee Pro firmware and is a supported device. If you have a project with an LCD Keypad, you will use the standard EmberNet to ZigBee Pro upgrade procedures to get it updated and operational (see Composer Pro Software Release Update Instructions – 1.7.4 to 2.0 for more information).

• Specify which mesh to join on multiple ZigBee Server configurations. When identifying a ZigBee Pro device or joining ZigBee Pro devices to the mesh, only one (1) ZigBee mesh will be placed into “Allow Join” mode. This enables sites with multiple ZigBee Servers to have complete control over which mesh devices will join.

• Improved Performance. We have improved the performance of the ZigBee Pro subsystem. In most environments, this results in approximately 30% improvement in performance. This is most noticeable in the responsiveness of List Navigator on the System Remote Control SR-250.

• Improvements to avoid “Waiting for Network” on SR-250. We have corrected certain conditions which caused the System Remote Control SR-250 to display “Waiting for Network”.

• Implicit Off Scenes. Each Lighting Scene now has an implicit Off state. This Off state is defined as ‘all lights’ in the scene ramping to 0 at the rate specified in the scene definition. The implicit Off state for scenes can be used in programming. Implicit Off scenes do not show up in the Navigators. So you will still probably have some explicitly defined Off scenes that the customer can access through the Navigators.

• Updated Firmware. Changes made to ZigBee Pro require that updated firmware be installed on most ZigBee Pro devices. As with prior releases, firmware updates occur automatically as part of the upgrade process. Be advised that ZigBee Pro performance will be sluggish while the update is underway. You can monitor the state of the ZigBee Pro firmware updates using Network Tools > ZigBee Network.

• Updating from EmberNet. For Release 1.7.4 or prior version systems not previously updated to Release 1.8.x and ZigBee Pro, a full update to ZigBee Pro is required when the system is updated to OS 2.0. Please refer to the update instructions Composer Pro Software Release Update Instructions – 1.7.4 to 2.0.

http://www.4store.com/�




2.4 Enhanced Media Database and Other Improvements to the Audio System The Media Database has been completely revamped for the OS 2.0 release. It is better optimized, more scalable, and faster. The Media Database and other media enhancements in OS 2.0 include:

• New Media Database. The new Media Database has been completely redesigned and is now faster, more scalable, and smaller. Existing Media Databases will be converted automatically during the upgrade process to OS 2.0. You must use Composer 2.0 to update prior version systems to ensure that the conversion process takes place.

• Director-based media scanning. Composer Pro no longer performs media scanning operations; these are handled by Director. This enables media scanning to be executed programmatically. It also frees up your Installer so that they don’t have to remain in Composer waiting for media scanning to be completed at the end of the Installation.

• Write tags back to files. With OS 2.0, any changes made to the Control4 Media Database can also cause the id3 tags in the MP3 files to be updated. This allows Control4 and other Media Managers to synchronize with each other. During the update to OS 2.0 you can choose to write metadata from the prior Control4 Media Database to id3 tags. You should do this if the Control4 Media Database is the most current/correct. You should choose to skip this action if you believe your id3 tags are already current or are more correct than the Control4 Media Database.

• Support for third-party Media Manager. Control4 can now synchronize the Media Database with the id3 tags in MP3 files. This allows the customer to use other Media Manager software for ripping their CDs or managing the metadata of their stored audio files. Control4 will automatically update the Media Database to reflect changes made by the other Media Manager to the id3 tags.

• Scheduled/programmatic scanning. When configuring media scanning, you can choose to schedule scans periodically or even kick off media scans using programming.

• Add extensions, select devices to scan. When configuring media scanning manually or programmatically, you can add audio or video file extensions to look for in the scan and also select which media storage devices to scan.

• Optional metadata lookup. If the customer’s Control4 system is registered on my.control4.com, the system can access Control4’s metadata lookup service arrangement with Gracenote®. If you don’t want to look up metadata when scanning, that option can be turned off in the media scanning configuration.

• Song Artists. Control4 now supports Song Artist metadata in addition to Album Artist. When browsing local music by artist, both Song and Album artists are displayed and selectable to generate the list of available titles.

• Zones Interface now supports analog sources. Improvements made to the Zones interface now provide improved support for audio sources that are distributed through an AV switch or Multi-Channel Amplifier. This change benefits both Flash-based Navigator interfaces and List Navigator.

• AAC codec (.m4a) support. Control4 now supports AAC codec decoding on Home Controller HC-200, HC-300, and HC-500. AAC is not supported on the Speaker Point, the Mini Touch Screen, the Home Theater Controller, the Media Controller, or the 7” Touch Screen devices. If any of those devices are used as audio end points within the system you are installing or updating, you should not use the AAC format audio. AAC content also must not be DRM protected.




Audio End Point MP3 FLAC AAC

Mini Touch Screen V1/V2 Yes Yes No

Home Theater Controller and Media Controller

Yes Yes No

7” Wall Mount, Tabletop Touch Screen

Yes Yes No

Speaker Point Yes Yes No

Home Controller HC-200, HC-300, HC-500

Yes Yes Yes

• Streaming MP3 (Internet Radio) source support. Control4 has implemented partial support

for Internet Radio sources by enabling HTTP-streamed MP3 sources to be played within the system. There is no direct user interface for accessing this functionality, but Control4 Dealers can configure specific Internet Radio stations for their customers. Please see the configuring Internet radio Technical Note on the Control4 Knowledgebase for additional information.

• Other audio enhancements in Flash Navigators. • Now Playing bar with basic controls and a Quick Link to Now Playing and Device Control

interfaces • Alphabetic scrolling • Genre filters • Source filters • “The” titles co-mingled alphabetically in both audio and video lookups • Play All by Genre, Artist, and Genre/Artist

2.5 Improved Customization Several of the new features provided in OS 2.0 allow you to customize the user experience further for your customers. Some of these capabilities are even accessible to the customer directly through the Flash-based Navigators.

• Favorites. The user can now make any page in the UI a “Favorite” page and directly access it from the Favorites menu. Favorites can also be organized in folder and accessed via programming (see Page Flips) or placed directly on the user’s Custom Home Page.

• Custom Home pages. The user can now create their own default Home page and include (or exclude) both default Control4 pages and their own favorites.

• Programmatic page flips. Any of the Favorite pages defined on a Navigator can be programmatically accessed using Composer Pro or Composer HE programming. The classic example for this is programming to flip to the IP Camera page for the front door on Navigator when the doorbell is pressed.

• Macros. A Macros agent has been added to the system and can be used to host pre-programmed routines. Macros can be activated through Composer Pro or Composer HE programming. They can also be tied to the UI when a Favorite is configured on Navigator.




• Change Backgrounds. Users can choose from a selection of backgrounds for their Touch Screen and On Screen Navigators.

2.6 Other New Features in OS 2.0 • Whole-home interface. The new Flash-based Navigator provides support for access to

devices throughout the home without changing rooms. You’ll find whole-home interface on Lights, Comfort (for your Thermostats), Motors and Sensors, and Blinds.

• Composer Pro software activation. Control4 Dealers can now grant and revoke Composer Pro privileges for their installation teams. A my.control4.com account with Composer Pro privileges is required in order for Composer Pro to be activated after installation. Every 30 days, the user is required to reactivate their Composer Pro software. An Internet connection is required in order to complete the activation.

• Electronic licensing for all Control4 software licenses. Control4 now handles all electronic licenses in a paperless manner. Licenses can be purchased via credit card by Control4 Dealer accounts with the proper privileges, or they can continue to be purchased via a Purchase Order. All licenses are electronically assigned to the Dealer’s my.control4.com account, and can then be directly assigned by the Dealer to their customer. Control4 doesn’t support retraction of licenses; once a license has been assigned to a customer, it is considered used.

• Pay for Update. OS 2.0 is a significant new release for Control4, Control4 Dealers, and Control4 customers. A system-wide software upgrade charge is required to upgrade from prior version systems. The price is the same regardless of system size or configuration. Dealers may want to consider charging for the time spent performing the upgrade also.

• Secure Connections Only (SSL). If installing a Control4 system with no Legacy GUI Navigators, you can choose to configure it to allow SSL connections only. This will ensure that no unencrypted communications pass between the Navigators and Director. If you need to continue to support a Legacy GUI Navigator, you should not enable SSL only. The new Flash-based Navigators will always connect via SSL, if possible, and the Legacy Navigators will be able to connect without SSL.

• Locale (internationalization). Control4 has enabled support for other languages in the Flash-based Navigators. Available languages are listed in Composer Pro. When a language selection is made using Composer, the Flash-based Navigators are reconfigured to use the selected language. Only one (1) language selection is allowed per system.

• Hide/Show/Order Lights and Lighting Scenes. The Control4 Installer (or Composer HE customer) can now specify which lights and Lighting Scenes should be visible in any room as well as their order. This is accomplished using the Device Visibility and Display Order configuration on the Navigator tab in System Design.

• Certified drivers visibility. Many Control4 partners have worked with Control4 to obtain certification for their device drivers. These drivers will have a ‘Certified’ label attached to them which is visible when searching for drivers on the Local Database and Online Database.

• Programming Detective. In order to improve the ability for installers to find programming within projects, Control4 has published the Programming Detective at: http://downloads.control4.com/updates/PD/SelfExtract/ProgrammingDetective.exe, a free utility.

• WPA Support. Control4 has added support for WPA wireless security on 10.5” V2 Touch Screen and on Home Controllers HC-200, HC-300, and HC-500. The 7” Touch Screens already supported WPA.

http://downloads.control4.com/updates/PD/SelfExtract/ProgrammingDetective.exe�




• Texting keyboard for character entry. When using the On-Screen keyboard or in any list (such as My Albums) that provides alphabetic sorting and searching, you can use the number keys on the System Remote Control SR-150 and SR-250 as a texting keyboard for letter entry.

• Alphanumeric sorting and searching. When you view a list that is sorted alphabetically, you can use the alphanumeric search to quickly access content. This can be activated using the texting keyboard, or by pressing and holding the Up or Down arrow keys.

2.6.1 Other Enhancements or Software Changes in OS 2.0 • Control4 Wireless Thermostat. Control4 has made additional driver and firmware changes

to the Control4 Wireless Thermostat to enable additional functionality and flexibility with various HVAC configurations and an improved ability to change the temperature scale. • Added differentiation between Fahrenheit and Celsius in programming. • NOTE: Existing programming which evaluates temperature values will not work correctly

and must be manually changed. Please use the Programming Detective to find programming in your customer projects. Existing programming which sets temperature set points should continue to work, but you may want to find and replace that programming as well. Examples of programming that will need to be replaced:

o If Temperature > 70 then ... o If Heat Set point < 70 then ...

• Added Vacation mode, which can be enabled/disabled through programming. Vacation mode consists of one set point for heat and one set point for cool. When disabled, the thermostat will resume its current/default schedule. Vacation mode settings are configured using Composer (no Navigator interface).

• Improved schedule interface in Composer and Flash Navigator • Added Advanced Device Configuration to Composer with additional support for multi-

stage HVAC system configuration o Customize and set the engage and cutoff temperature deltas as well as all of the

minimum and maximum run times for all heating and cooling stages. A minimum off time per stage is also available for configuration. The engage deltas per stage are the temperature offsets to engage this stage. For heat and cool stages 2, the deltas are additive: Temperature to enter Heat/Cool stage 2 = set point + H/C stage one delta + H/C stage two delta.

o Heat Pump. The ability to disable the Auxiliary stage is available by setting the Auxiliary Stage Delay value to 255. Also, forcing the Auxiliary stage to run simultaneously with Heat stage (1 or 2) indefinitely is available by setting the Auxiliary Stage Cutoff Delay value to 255.

o The engage and cutoff points for heating and cooling, as opposed to just overshoot (heating cutoff point) and undershoot (cooling cutoff point) points, was introduced in Release 1.8.2. Also introduced in Release 1.8.2 was the new Heat Pump Auxiliary Stage functionality described above. The temperature delta enforced to separate the engaging of heat and cool, dependent upon set, engage, and cutoff points in auto mode has been changed from two (2) degrees to one (1) degree.

• Added “offline” and “no pan” text to LCD display of Control4 Wireless Thermostat to indicate when it’s not connected to a ZigBee Pro mesh.




• Composer Pro Installation. Control4 has changed the installation program for Composer Pro 2.0 resulting in a significantly smaller download and faster installation.

• Internationalization. Control4 systems can now be configured to use languages other than English in the user interface (Flash-based Navigators only). Please note that all system interfaces, including Composer and other utilities, are still English only. • Improved support for non-English characters in audio and video filenames and metadata.

We use UTF-8 for character encoding. • Localization levels are dependent on the language and the local Control4 Distributor. At

this time, full localization support is available or planned for the following languages: o English, Spanish, German, Danish, Finnish, Dutch, French, Italian, Norwegian,

Portuguese, Russian, Swedish, Turkish (actual language availability subject to change)

o Fully-localized language versions have support for Flash Navigator and List Navigator (SR-250)

• Languages that support 8859-15 encoding (e.g., Swahili) may utilize local language translations for the List Navigator. However, the SR-250 firmware will use one of the embedded languages for some strings.

• Other languages, including all of the double byte languages not supportable by the SR-250, will be able to use a localized Flash-based GUI Navigators. They will use English or another of the full localization languages for the SR-250 List Navigator.

• Language selection is made using Composer and applies to all devices within the system. • LCD Keypad now supports ZigBee Pro. The LCD Keypad now supports ZigBee Pro

firmware. If the customer system was previously upgraded to Release 1.8.x and ZigBee Pro, you’ll need to enable an EmberNet Upgrade Controller to update its firmware. If updating from Release 1.7.4 or a prior version, the LCD Keypad will upgrade automatically with all the other devices as you perform the upgrade to ZigBee Pro. • The LCD Keypad is an English-only device. It

may work fairly well in languages which share a lot of characters with English, but if you configure a system to use another language, you should not expect the LCD Keypad to correctly handle foreign characters.

• If you need to cause the LCD Keypad to leave the ZigBee Pro mesh, use the following instructions:

o If connected to a Controller, press: Info, select About, and press Config. o If not connected to a Controller, press: Info. o At the Setup menu, press the buttons in the following order: 2, 6, 4, 8, 10. o Press the LEAVE button.




• Media scanning architecture. The Media Database and media scanning architecture have been completely updated for OS 2.0 resulting in improved performance, scalability, and functionality. Here are a few of the changes: • Scanning is performed by the Controller rather

than Composer. • Scanning can be executed programmatically and

by schedule. • Scanning configuration allows the addition of

different file extensions. Control4 will look for files with the specified extension(s) and add them to the Media Database. Note: Just because a file extension is recognized by the scanning process doesn’t mean that the file is playable within the Control4 system.

• Enable/disable online Media Database lookups for metadata.

• Synchronize options allow the Control4 system to recognize changes made by third-party Media Managers.

• When scanning, metadata is populated based on the following priority scheme: o Metadata stored in the id3 tags is presumed to be the most correct information. o If information is not available in the id3 tags, OS 2.0 uses the online media lookup

service (optional configuration). o Artist, Album, Song names are derived from the directory structure if no other

information is available: \artist

\artist\album1 \artist\album1\song1 \artist\album1\song2 \artist\album1\song3

\artist\album2

• Listen menu on SR-250. If your customers use the Listen menu on the SR-250, they can now view and select channels and Rhapsody using List Navigator.

• Touch Screen—Now Playing shortcuts. On the Touch Screen, you have a full Now Playing bar with basic Device Controls, volume controls, quick access to the Now Playing page (or device control page for analog devices), and quick access to the Zones page. To access the Now Playing (or Device Control) page from the Touch Screen simply press the Cover Art icon or Device icon in the leftmost corner of the Now Playing bar.

• On Screen—Now Playing and SR-250 shortcuts. Since the On Screen Navigator is controlled using the System Remote Control, all basic transports and volume controls are already at your fingertips—no need to navigate to them. For that reason, the Now Playing bar is informational and can't be navigated. In addition to the volume and Device Controls on the SR-250, there are other shortcuts: • MENU—Quickly access the Favorites popup. • INFO—Quickly access the Now Playing or Device Controls menu based on the selected

audio source in the room.




• CNCL—Back out one menu level when navigating using the On Screen Navigator. • PG Up/Down—Activate the dimming control for dimmers when using the On Screen

Navigator. • GUIDE—Toggle between the List and Grid views in various interfaces. • Texting Keyboard for character entry—When using the On-Screen keyboard or in any

list (such as My Albums) that provides alphabetic sorting and searching, you can use the number keys on the SR-150 and SR-250 as a texting keyboard for letter entry.

• Alphanumeric sorting and searching—If you view a list that is sorted alphabetically, you can use the alphanumeric search to access content quickly. You can activate this using the texting keyboard or by pressing and holding the Up or Down arrow.

• On Screen—Screen Saver programming. Added support in Composer programming to configure the screen saver on Controllers (for On Screen Navigator).

• Volume ramp rate on Multi-Channel Amplifier. Changed the volume ranging rate on the Multi-Channel Amplifiers to match the rate used on the Speaker Point; this provides faster ramping of volume.

• Support for audio devices with On Screen Navigators. Improved support for audio devices which provide their own On-Screen interfaces. Control4 will automatically select the video path when audio is selected (may require a new .c4i file implementing the "always_select_video_with_audio" capability).

• Custom Screen Saver. When the Custom Screen Saver is used, we now restrict it to the bottom of the screen (so as not to be on the faces of family members in your customers’ photos).

2.7 Changes Inherited from Release 1.8.2 Because some Control4 Dealers will be bypassing Release 1.8.2 and upgrading customers directly from Release 1.7.x or prior version systems directly to OS 2.0, this section highlights some of the changes made in Release 1.8.x which they will need to be aware of.

• ZigBee Pro. Dealers who are not familiar with the upgrade procedures from EmberNet to ZigBee Pro must become aware of and follow the proper upgrade procedures or the ZigBee devices on the system will not be upgraded. Please see Composer Pro Software Release Update Instructions – 1.7.4 to 1.8.2 on the Knowledgebase for more information. • ZigBee Server and ZigBee Access Point (ZAP) processes are now separate processes.

This allows the ZigBee Server process to run on a Home Controller HC-1000 or on a separate Controller from the ZAP(s).

• Multiple ZAPs can be configured to bridge ZigBee RF traffic to the Ethernet network for internal system communications.

• All ZigBee devices in a Control4 system now use the same channel with additional flexibility of configuration provided through multiple ZAPs.

• All ZigBee RF communications are now AES encrypted. • Only devices that have been joined to the secure ZigBee Pro mesh network will

communicate within the Control4 system. Devices not belonging to the mesh will not communicate. This change allows physically-adjacent systems to coexist without the ZigBee networks interfering with each other.




• Multiple ZigBee Servers. In order to ensure that installations which do not have a strong ZigBee mesh throughout the home can properly control local devices using the Remote Control, the installer can create Multiple ZigBee Servers.

• Security • Set Password. Control4 provides an interface in Composer (System Design) to allow the

Installer to change the password on the Primary Controller. If not set, the password of the Primary Controller remains set to the default, and no password is required to access the project using Composer.

• Forgotten Password. If a password is set in Composer and then forgotten, the password can be reset only through a physical connection to the Controller.

• SSL. Composer will now connect via SSL to Director. • Reset Password. The process for resetting the password on a project requires physical

access to the Controller on which the project is running. Use the network reset feature of the Primary Controller. After the network reset completes, the project and system password reset to the default.

• Trusted Controllers. The first time Composer connects to a Director, it will ask you if you trust that Controller (similar to SSH). If you respond yes, Composer will make an SSL connection to the Controller.

• SSH for system console access. In order to improve overall system security, Control4 has disabled the telnet server on all devices except those which don’t support SSH (the exceptions are: Home Theater Controller, Speaker Point, and Mini Touch Screens which still use telnet). You will need an SSH client to log in to the device. Control4 recommends putty (see http://www.chiark.greenend.org.uk/~sgtatham/putty/ for information and free download).

• SSH from the command line. If you need to use the command line SSH client on the Controller to log in to another device, you will use the following syntax, ssh user@ip_address.

Example: ssh [email protected]

• Lighting • We implemented multicast Lighting Scenes in conjunction with the ZigBee Pro firmware.

Each device stores information about its defined behavior in up to 32 different Lighting Scenes. When you execute a scene, a multicast is sent to all devices on the mesh. Devices immediately respond based on their defined behavior, eliminating “popcorn” lighting.

• We added an option to the Properties page of the 2-Button, 3-Button, and 6-Button Keypads to ‘Follow Bound Color.’ This is the default configuration, and has been the only option in previous releases. In this configuration, the Keypad LED colors are set based on the device to which they are bound using Button-Link bindings. New with Release 1.8.0, Installers can uncheck this option. This lets the Installer specify the on/off colors for the Keypad LEDs independently of the device to which they are linked.

• We added double- and triple-tap events to the Control4 Dimmers, Switches, and Keypads. When you tap a button consecutively two (2) or three (3) times for about one-half of a second, these events fire. Now you can use these events for programming without requiring the more complex programming logic tied to timers and button Press/Release events.

Note: When programming using double- and triple-tap events, be aware that Press and Release events also occur when double- and triple-tap events occur.

http://www.chiark.greenend.org.uk/~sgtatham/putty/�




Plan your programming using these events so that they don't conflict with the intended outcome. In most cases, when using double- and triple-tap programming events, don't program on the Press and Release events.

• Audio • We added support for Free Lossless Audio Codec (FLAC) encoded audio files. Any .flac

files loaded on a storage device accessible through the Control4 system (USB, NAS, or Controller HDD) can be scanned and played back just like .mp3 files.

• Agents • The Composer Timer agent interface has been updated to allow for specification of timer

duration in a more flexible way. Timer selection is now in the format hh:mm:ss. • Control4 now includes Control4 system and user-defined variables in the templates

created using the Email Notification agent. To use this new capability, the Installer can create or modify email templates using Composer, Agents, Email Notification, and then use the ‘Add Variable’ option.

• System Remote Control • Control4 added programming events to the System Remote Control SR-150 and SR-250

‘Watch’ and ‘Listen’ button presses. This lets the Installer use Control4 programming to define room-specific behavior when the Watch/Listen buttons are pressed. The Watch/Listen button options now include: ‘No Action’ (new, used for programming your own behavior), ‘Select Most Recently Used Device,’ and ‘Show Device List.’ You can select the desired behavior using the Composer Pro System Design view. Programming triggered by the Watch and Listen buttons is performed using the room events.

• Control4 added the menus for My Library, Rhapsody, Zones and Now Playing to the Listen button when ‘Show Device List’ is the configured behavior on the System Remote Control SR-250.

3. Other Changes in OS 2.0

3.1 Defects Resolved • Audio

• Fixed an audio re-sampling problem that could cause noise on a digitized input. • Improved the randomness of the shuffle algorithm used in shuffling the music in a queue. • Corrected the problem where, if a playlist was queued in shuffle mode, the same song

always played first. • Changed the volume ranging rate on the Multi-Channel Amplifiers to match the rate used

on the Speaker Point—this provides faster ramping of volume. • Resolved a problem with 4 Zone Amplifier that could cause it to occasionally stop

responding to Mute commands—requiring a power cycle to resolve. • Composer/Director/Controller

• Resolved a problem when Composer connected to Virtual Director it could not clear the project.

• Resolved various reported problems where Composer could crash during use.




• Corrected a problem where the Controller could become unregistered from my.control4.com after a power outage. Obviously it needs Internet connection and power to work correctly, but when restored, it will automatically reconnect.

• Corrected a problem where programming that was changed via Find/Replace displayed incorrectly in Composer (it worked but didn’t display correctly).

• Implemented a new Samba package to correct a problem where SMBD would continue to consume memory until all memory was consumed, requiring a power cycle to reset.

• DriverWorks SDK/Proxy Drivers • Corrected the bitwise functions (DriverWorks) so that they work correctly on Home

Controllers HC-200, HC-300, and HC-500. • Improved support for multi-proxy devices using the iPod proxy.

• ZigBee Pro devices • Resolved a problem with System Remote Control not on ZigBee Pro mesh continually

trying to reconnect to the parent (consuming batteries). • ZigBee Pro mesh and System Remote Control SR-250 performance improvements—

providing a faster List Navigator experience for the customer. • Added support on Dimmers and Switches to allow programmatic control of the load even

when device is configured with buttons not attached. • Removing System Remote Control SR-250 from a mesh no longer resets the wake-on-

motion and backlight settings • Corrected a problem where System Remote Control SR-250 wasn’t beeping (in response

to a programming command) until the second check-in (approximately one (1) minute of extra delay).

• Control4 partner CardAccess has added support for ZigBee Pro firmware to the Mini Remote.

4. Known Limitations

4.1 OS 2.0

4.1.1 New Limitations • If you receive an error message of the form:

2010-05-19 09:42:28,119 [5732] WARN Control4.Client.ConfigDataManager - The file 'driver file name' has an improperly formatted version tag. The driver will still be loaded but there may be problems with updating this driver until the problem is fixed.

This means you have a DriverWorks driver in your project using a non-integer in the version field. The driver will continue to function, but it will not be updated when using the “Update Driver” function. It needs to be replaced manually.

• The Flash player we are using for Navigator doesn’t support HTML tables (used in popups created by the WeatherBug and Temperature Consolidator drivers) or .gif images. Flash-based Navigator users can use the built-in Weather app and Comfort display and do not




need to use the drivers. Other drivers which format information for popup display using HTML tables or .gif images need to be modified.

• Because there is no .gif image support in Flash Navigator, IP camera drivers which were configured to pull Internet images in .gif format will not work correctly. They need to be removed from the project or modified to access a supported format (.jpg or .png).

• Control4 has removed the ability to change a Controller’s network configuration from the On-Screen Navigator as there are too many architectural points of failure (ZigBee, Director, Navigator, Sysman). When a device loses its network configuration, it can’t be recovered easily via an On-Screen Navigator. From henceforth, Controller network configuration will be supported only via the System Manager interface.

• If using Page Flips via Programming on an On Screen device – you need to take into account the power state (on/off) of the display device (TV or Projector) and whether it is being used for something else (TV, movies). You will need to turn it on (if off) and select the controller as the source device (enabling the path to the On Screen Navigator) via programming. When you are done with the Page Flip, you will need to account for turning off the device as needed so that you don’t leave TVs or projectors turned on unnecessarily.

• While viewing an IP Camera with On-Screen Navigator, you cannot select the image/stream to control it. The Legacy Navigator provides the ability to use either the remote arrows or the On Screen interface to control the pan, tilt, and zoom functions. Support for this has not been provided on the OS 2.0 Flash Navigator at this time.

• The Control4 Wireless 10.5” Touch Screen V2 doesn’t currently support language changes. This support is planned for a future release.

• The Control4 interface and Media Database ignore “The” in the sorting and presentation of Albums and Movies; however, we have chosen to include “The” when sorting and presenting Artists.

• Control4 has chosen to remove the ability to monitor Update Manager using the Navigator interface in the new OS 2.0 Flash-based Navigator. This functionality is still available in the Legacy Navigators.

• The Control4 10.5” Wireless Touch Screen V1 ships with 64 MB of RAM. This is not enough memory to update reliably to OS 2.0. If you are updating a customer with one of these Touch Screens, a CF replacement (512 MB) is available for order; the part number is: RPK-TSM10.5V1-CFC. The Control4 10.5” Wireless Touch Screen V2 ships with 128 MB of RAM and has enough capacity, but if you want to order a replacement CF card (512 MB), the part number is: RPK-TSM10-CFC.

• Control4 has chosen not to implement an On Screen Navigator interface for 4x3 (SD) resolution display devices. We simply scale the 16x9 interface for display on the SD device. This comes with the following limitations:

o The font size and image size of many interface elements may not be optimal. o The IP camera display buffer is not scaled and will not “fit” correctly if used on an

SD display device. • Control4 has modified the Receiver and Tuner proxies and removed “functionality” which has

probably never worked correctly and was deemed unnecessary. This includes events and conditionals in the following areas: • AM/FM Tuner

o Band Changes o Channel Changes

• Sirius/XM Tuner o Song_Info Changes




o Channel Changes • Receiver

o Input Changes o Bass Changes o Treble Changes o Balance Changes o Loudness Changes o Any Audio Setting Changes o Current Volume is o Current Treble is o Current Bass is o Current Balance is o Current Loudness is

• Because media scanning has been moved into the background, scanning status is available only through Director status messages.

• Control4’s future support for the 10.5" In-Wall Touch Screen will be limited to backwards compatibility; no future software upgrades are planned for this device.

• Control4’s future support for the 10.5" Wireless V1 will be limited to backwards compatibility; no future software upgrades are planned for this device.

• The Home Theater Controller and Media Controller can be used only as Secondary Controllers within an OS 2.0 system.

• Control4’s future support for the Mini Touch Screen V1 will be limited to backwards compatibility; no future software upgrades are planned for this device.

• There is no USB Restore capability tied directly to OS 2.0. If a USB Restore is needed for OS 2.0, use a Release 1.7.4 (Mini Touch Screens, Speaker Point, Media Controller, and Home Theater Controller) or Release 1.8.2 (all other products) Restore stick, and then update to OS 2.0 again.

• Control4 has not implemented a Flash-based UI for browsing CDs stored in a Disc Changer. • Custom Buttons are supported via the Favorites interface in the new OS 2.0 UI. • Control4 has not implemented a UI for creating Lighting Scenes in the new Flash Navigator. • In the Legacy Navigator, when on the Now Playing page, the user could link to the Album or

Artist page. These links are not active on the Flash-based Navigator. • Control4 has not implemented a method for locking specific screens in the Navigator

interface. • The UI for Pool Control is not yet completed for Flash Navigators. The pool control drivers

and proxies remain in the project and are fully functional. • The UI for Video Wall is not yet completed for Flash Navigators. • In the Legacy Navigator, there was a volume slider control for devices (audio end points) with

discrete volume control. In Flash Navigator 2.0, the volume control uses Up/Down controls. • In the Legacy Navigator, certain motor and sensor devices, the Fireplace Switch, and

Wakeups were made available via the Comfort menu. In the Flash Navigator 2.0 UI, these are under “More.”

• Control4 WiFi devices that support both WEP and WAP allow for the entry of ASCII keys in the network configuration interface. However, Control4's implementation of WEP is restricted




to hexadecimal keys. You can use ASCII keys for WPA networks, but you must use HEX keys for WEP network configurations.

• The password reset functionality for Control4 devices, which is expected to occur with the network reset procedure, is not currently active in the OS 2.0 software. This functionality will be re-enabled in a future release. If you forget the password for a device, use the USB Recovery procedure to restore the device to a configuration with a known password.

• The password challenge that Composer is expected to issue when connecting to a Primary Controller with a non-default password is not currently active in the OS 2.0 software. This functionality will be re-enabled in a future release.

• When connecting to a Release 1.7.4 or a Release 1.8.2 system with a Control4 Wireless Thermostat with Composer 2.0 you will receive a message that the Wireless Thermostat driver failed to initialize. You can ignore this message. After the system updates to OS 2.0, the drivers needed by Composer will match those used by the system.

4.1.2 Pre-Existing Limitations • Miscellaneous

• The audio driver on Control4 devices only supports sample rates of 7200 – 48000 bits/second. Control4 will not attempt to play any stored digital audio files with a higher sample rate. The files will scan and show up in the Media Database, but they will not play. If this situation occurs, an error in the audio log (if enabled) will indicate that the sample rate is too high.

• Control4 has improved the performance of FLAC audio streaming in Release 1.8.2. However, it is still possible to require more CPU when streaming multiple FLAC files than what the Home Controllers HC-200, HC-300, or HC-500 can deliver. On these Controllers, Control4 only can stream up to two (2) FLAC files concurrently. If you are expecting to need more, use an HC-1000 as the Primary Controller.

• The ZAP Coordinator cannot be replaced without recreating the mesh. The security parameters of the ZigBee Pro mesh are maintained by the ZAP Coordinator. Control4 does not currently have a solution for replacing the coordinator without requiring the mesh to be re-created and the devices to be rejoined. Because the ZAP Coordinator can’t be changed, it won’t show up in the list of ZAPs to avoid inadvertent changes.

• ZigBee mesh is down when the coordinator is not running. The ZigBee Pro mesh requires that the Controller defined as the coordinator is available and running ZAP. If not, the mesh network will be down until the coordinator is available.

• EmberNet upgrades using the same Controller as the coordinator. Control4 has designed the upgrade procedure to allow any Controller with a ZigBee radio to function as an EmberNet Upgrade Controller. If the coordinator is functioning in that capacity, it will not be running ZAP during the time that the EmberNet upgrade is underway, and the ZigBee Pro mesh will be down. As soon as you disable the Controller as an EmberNet Upgrade Controller, the system re-flashes the ZigBee radio to run the ZigBee Pro stack, and then restarts ZAP. At that point, your mesh will come back up.

• Some devices are not supported. OS 2.0 does not have ZigBee Pro firmware for all of the devices which may have been used in prior version systems: • System Remote Control V1/V2—no longer supported. • Audio products (Amps, Switches, Tuners)—must be configured using Ethernet. • Contact Relay Extender—must be configured using Ethernet.




• Button tap counts are more precise in the new firmware. This isn’t necessarily a problem, but it is a change that some Beta testers noticed. With the ZigBee Pro firmware, the tap counts are handled more precisely than in previous versions. Four (4) button taps are used for identifying. If you are used to just pressing the button a bunch of times, you will find that it doesn’t work if you press the button five (5) times.

• Clearing a project doesn’t force Leave Network. From time to time, a Control4 Dealer or Installer will clear and reload projects. To minimize this effort, Control4 doesn’t force ZigBee devices to leave the mesh when a project is cleared. The down side to this implementation is that if you are moving ZigBee devices to another mesh, you need to use the button sequence to cause them to leave the mesh manually before they will attempt to join another mesh network.

• Home Theater Controller and Media Controller can only be used as Secondary Controllers. Beginning with Release 1.8.0, the Home Theater Controller and Media Controller can be used as Secondary Controllers only. They cannot function as Primary Controllers.

• Lighting Scenes limitations. Each device can be included in up to 32 total scenes. The project can have up to 1,000 total scenes. If a device is added to more than 32 scenes, you will get an error in Composer.

• A maximum of six (6) non-routing devices can be added to the ZigBee Pro mesh without routing nodes. This limitation is unlikely to affect most deployments; however, the maximum number of non-routing devices (System Remote Controls or other “sleepy” devices) that can be joined to the front panel of a Controller is six (6). To add more sleepy devices, add other routing nodes (Dimmers, Switches, or Keypads) to the mesh.

• System Remote Control SR-250 with 00.00.18 firmware needs to be physically awakened in order to update. New System Remote Control SR-250s may have version 00.00.18 firmware on them. If so, they will need to be awakened in order to begin the update to ZigBee Pro. System Remote Control SR-250s with later versions of firmware will wake up and check for updates without being manually awakened.

• Windows PC running Composer must be rebooted after updating the system. After updating to OS 2.0, the PC running Composer must be rebooted to remount the Samba file shares properly. Because the Samba server on the Controller has been updated, the PC no longer recognizes the previously-loaded shares as valid. After the PC reboots, the shares will mount properly. This is important to understand if you are trying to load media or perform a full backup containing media after the update. These operations will not complete correctly until Windows is rebooted.

• Devices operating with MiniApp firmware do not have the ability to be controlled by or provide status feedback to the Control4 system. The MiniApp firmware image is used only during the ZigBee update process. Devices being updated from EmberNet to ZigBee Pro and from one (1) ZigBee Pro firmware version to another will run the MiniApp firmware version during the update process. After the device is updated to the full firmware image, it will resume normal operation.

• If a Control4 Wireless Thermostat is installed in a battery-only configuration, the Thermostat does not conserve the battery by putting the Thermostat to sleep. Control4 has always recommended that the Control4 Wireless Thermostats be installed with a dedicated power source (common wire) whenever possible, and if that isn't possible to utilize the Power Stealing configuration. Control4 has never recommended that the Control4 Wireless Thermostat be installed in a battery-only configuration. However, if you have installed the Control4 Wireless Thermostat in a battery-only configuration, be aware that the current ZigBee Pro firmware for the Thermostat does not conserve the battery by putting the Thermostat to sleep. This is not an issue for devices that have common power. It should work




just fine with supported power stealing configurations. However, if a Thermostat is configured for power stealing on a heat-only or cool-only system, it will use too much battery power and require frequent battery replacement.

• During the startup phase, ZigBee Server has to assume that all nodes on the mesh are battery powered. This results in the address table on the ZigBee Access Point front panel getting filled up very quickly since it is limited to eight (8) slots. After each node reports that they are routing nodes, the entry times out and then we have a free slot we can use. This affects the ability of devices (such as the Black and Decker ZigBee DoorLock and battery-powered devices from CardAccess) which actually need to use a slot in the address table on the front panel. After the mesh comes up and stabilizes, these devices can participate in the mesh. It can take up to 20 minutes for a 70-node mesh network to stabilize. During this period of mesh stabilization, these battery-powered devices may not work correctly.

• Synchronization of scenes. Synchronization of scenes happens in the background after the scene has been created. To force synchronization of one particular scene, use the "Sync this Scene" button. To force synchronization of all scenes, use the "Sync All Scenes" button. Note: "Sync All Scenes" will thrash your ZigBee network for a while until every device in every scene has been contacted and brought fully up to date. As a rule of thumb, you should wait five (5) minutes or so after using "Sync All Scenes" before attempting to test or expecting ZigBee performance to return to normal.

If you try to add a device that has reached its maximum amount of scenes, it will allow you to add the device to the scene. However, when the system gets the error back from the device that it isn't able to add any more scenes, it will remove the device from that scene and pop up a nodal dialog in Composer that will alert the Installer to the problem (similar to the dialog that you get if you try to identify a device that's already identified within the project).

• Automatic channel changing. Control4 has not implemented automatic channel changing the ZigBee Pro implementation. The only scan Control4 does is on the first deployment. If you want to change the channel, you're welcome to, but Control4 recommends that you wait until the system is stabilized—with no updates underway—and all devices are online. The channel-changing process entails the Network Manager (ZigBee Server) telling all nodes that the network is changing to a new channel. The devices acknowledge this and change to the new channel. If you do this with devices offline or updating, they can become lost. Eventually, they should find their way to the correct channel, but it can take a while.

• Recovery. USB Recovery of Media Controller, Home Theater Controller, Speaker Point, and Mini Touch Screens is not provided directly to Release 1.8.x or OS 2.0. If you need to recover any of these devices, use the Release 1.7.4 USB Recovery image, and then use Update Manager to update to OS 2.0.

• Images used in the Announcement agent and in the Web images from the camera driver should be no larger than 300 KB. The display of images in the Announcement agent and the display of Web images through the Web images camera driver are designed to work with small images commonly used on Web sites or in graphical user interfaces. The recommended size for these images is 300 KB or less. Larger images will be scaled to the required size for the Navigator, but this scaling process for very large images can cause, for example, a Mini Touch Screen to restart.

• Programming conditional “If time is daytime” or “nighttime” may not execute correctly within one (1) minute after sunset. If programming exists that is triggered at sunset or sunrise, and other programming exists that is triggered immediately upon this change that executes the conditional on daytime or nighttime, the change may not be immediately




recognized. It may take up to one (1) minute for this programming to execute correctly on the change from night to day or from day to night.

• Upclassing or upscaling per input or output is not handled. Some new AV equipment will upclass or upscale per input or per output. Currently, the Control4 system only is able to handle upclassing or upscaling per device.

• Handling audio announcements through an Audio Switch or Amplifier when all digital audio inputs into the Switch or Amplifier are already in use. If all analog outputs into the Audio Switch or Amplifier are already in use and an audio announcement must be played; the audio announcement is given priority for playback and is piggy-backed on an existing audio session. If the room configured to receive the audio announcement is not part of an existing audio stream, the room joins the oldest digital audio session temporarily, the announcement is played, and then the room is removed from the session. The result is that the announcement plays correctly, but it may play in rooms not configured to receive the audio announcement.

• Deleting an agent configuration may not delete all associated programming. When deleting an agent, confirm that all associated programming is also deleted. You may need to delete some elements of associated programming manually.

• Using multiple audio outputs simultaneously on the Home Theater Controller or Media Controller when Navigator is running simultaneously may cause audio playback to skip. In systems with multiple audio zones with the Home Theater Controller or Media Controller used as audio end points, Control4 recommends that these Controllers do not run Navigator simultaneously.

• Streaming an analog source from audio input on a Controller to a WiFi audio end point is limited to one (1) stream. Audio signals that are processed through the analog input on a Controller are processed as a PCM stream and require much more bandwidth than streaming an MP3 to a WiFi audio end point. In this configuration, Control4 recommends that only one (1) stream be used at any one time.

• Static on audio output? As a reminder, occasionally when using the Home Theater Controller, Media Controller, Mini Touch Screen or Speaker Point as an audio end point, the devices will output static from one (1) or both of the audio outputs when music plays. This can be resolved by power cycling the device. The Mini Touch Screen’s click sound also may play very loudly, and sound very harsh. This is caused by the same root problem; power cycling the device will resolve it. Note: The devices need to be completely unplugged and not just rebooted for the audio device to reset properly.

• USB-mounted hard drives must be FAT32. USB drives that are formatted using NTFS are still mounted as Read-Only and cannot be written to. For best results, please format USB drives as FAT32 before using them with a Control4 system.

• Container variables and lights. As with previous releases, Control4 recommends that you do not utilize container variables for lighting. The two-way feedback from the individual lights can cause undesired light-level oscillation when a light level is adjusted and multiple light loads are included in a container variable.

• Cannot register a Controller with a “.” in the name. Due to network device naming conventions, it is not possible to register a Controller that has been configured with a ‘.’ in the Controller’s name successfully. Control4 advises Dealers to avoid this naming convention.

• Some devices may report online status after being offline. Due to the networking architecture and services used by the Control4 system, some services will not report themselves as offline in Network Tools immediately after the device is offline. If the status is in question, ping the device or attempt to connect in System Manager and look at the status of the services for immediate feedback.




• Dock for iPod locks up on retrieval of cover art on classics and Nano. Control4 recommend that you disable the cover art.

5. Questions Here are a few common questions that you may have related to OS 2.0. A more comprehensive FAQ is available on the Control4 web site.

5.1 Do I Need to Update My Customers to OS 2.0? It is not necessary for you to update your customers' systems to Release 1.8.2. Control4 recommends that Dealers first familiarize themselves with OS 2.0 in their own home system and test systems. After gaining an understanding of the full product, including ZigBee Pro and the update procedures, you can make an informed decision about which of your customers might benefit from an update to OS 2.0. If your customer wants to use the new features and capabilities provided in OS 2.0 or if your customer purchases new products which require OS 2.0, then you will need to update their system. Composer OS 2.0 is not backwards compatible with prior versions of Control4 system software. Using Composer OS 2.0, you can connect to a system running a previous version of software, but you should not modify the system. You can have multiple versions of Composer installed on the same computer at the same time. If you have customers running prior versions of software on their systems, the corresponding versions of Composer must be used for maintenance and configuration work for those systems. Customers who have purchased Composer Home Edition (Composer HE) must update their software to obtain the new capabilities of OS 2.0.

5.2 Can I Continue to Install Prior Release Systems? Control4 is in the process of transitioning all product manufacturing to OS 2.0. Until this is complete, unless otherwise specified all hardware shipped from Control4 has been updated to Release 1.8.2 and ZigBee Pro. For a limited time, small amounts of hardware capable of running Release 1.7.4 will be made available to Dealers for use in existing customer installations. Control4 recommends that you use OS 2.0 for all new installations. Please contact your Control4 Sales Representative if you need to order hardware for a Release1.7.4 system.

5.3 What Performance Changes Should I Expect from OS 2.0? With each software release, as we've added new functionality, the CPU places more demands on the Controller. With OS 2.0, we are replacing the Legacy Navigator with a Flash-based Navigator. Control4 is also using ZigBee Pro which will perform slower than EmberNet in many configurations




(Composer Pro Software Release Update Instructions – 1.7.4 to 2.0). On single Controller systems, increased CPU requirements from any system component (including Navigator) compete with the demands of ZigBee Server, Director, and other system processes. Anytime more CPU is required by any system component, it will affect the overall system's performance. The OS 2.0 release is no exception. While each system will be different based on system configuration and usage patterns, here are the general changes you should expect regarding performance:

• Control4 has made modest improvements in ZigBee Pro performance (when compared to Release 1.8.2). These are most noticeable when using the List Navigator on the System Remote Control SR-250. If a customer is upgrading from Release1.7.4 or a prior version, List Navigator will be slower due to the encryption added with ZigBee Pro.

• On-Screen Navigator will perform at about the same level of responsiveness as the legacy On Screen Navigator with Release 1.8.2. Some operations will be faster; others may be slower. CPU requirements for this usage will be slightly higher which can impact other system processes.

• Single Controller systems should be evaluated based on the known or expected system load to ensure that there is adequate capacity prior to being updated to OS 2.0. For additional information, please see the Control4 Support Knowledgebase article, “Balancing System Size and Usage Requirements in 1.8.0.”

• Added support for the AAC codec does consume a little bit more CPU. However, since we are using the DSP on the Home Controller HC-200, HC-300, and HC-500 Controller to perform the decoding, it won’t impact system performance on most systems.

• Other system processes should perform at about the same level as with prior releases.




6. Firmware Versions for OS 2.0 Systems The following table lists the devices and their firmware versions for OS 2.0 and later.

Control4 Devices Firmware Version

Control4 Dock for iPod 00.03.20

Audio Matrix Switch 03.03.70

Multi Channel Amplifier 03.03.70

Multi Channel Amplifier V3 03.03.70

4-Zone Amplifier 03.03.70

Multi Tuner V1 00.03.70

Multi Tuner V2 03.03.70

Media Player 01.00.17.34

Media Player V2 02.00.22.39 (OS 2.0.1)

Contact/Relay Extender – Ethernet 03.03.80

Ethernet LCD Keypad 03.03.70

Front panel for Matrix Switch, Multi Channel Amplifier, and Multi Tuner

No support for ZigBee Pro firmware – use Ethernet to connect to and control the audio products.

Contact/Relay Extender – ZigBee No support for ZigBee Pro firmware – use Ethernet.

System Remote Control V1 and V2 No support for OS 2.0.

System Remote Control SR-150 03.03.63 (03.04.20 for OS 2.0.1)

System Remote Control SR-250 03.03.63 (03.04.20 for OS 2.0.1)

Wireless Dimmer and Switch (EM250, AVR, Reverse Phase/ELV)

03.03.38

Wireless Inline Dimmer 03.03.32

Wireless Outlet Dimmer and Switch 03.03.32

Wireless LCD Keypad 03.03.59




Wireless 2-, 3-, 6-Button Keypads (EM250, AVR)

03.03.27

Wireless Thermostat 03.04.21 (OS 2.0.2)

7. Upgrading to OS 2.0

7.1 OS 2.0 Software License In conjunction with the OS 2.0 release, Control4 is introducing a Software License. All new hardware products will ship with the license to run OS 2.0. Customers who have purchased hardware prior to OS 2.0 can purchase a software license for OS 2.0.

• The OS 2.0 Software License is an electronic license purchased by the Control4 Dealer using their my.control4.com Dealer account credentials or through the standard purchase order process.

• A Dealer must purchase and assign a license to the customer’s my.control4.com account (to which the system is registered) in order to upgrade their system to OS 2.0.

• Control4 is providing a no-charge upgrade to OS 2.0 for Controllers shipped on/after after December 23, 2009. No paperwork or manual approval is required to receive the no-charge upgrade. To receive the no-charge upgrade, the eligible Controller must be the Primary Controller for the Control4 system. During the upgrade process, Update Manager will check the MAC address of the Primary Controller. If it is in Control4’s list of Controllers shipped on/after December 23, 2009, the upgrade will proceed without requiring a Software License.

7.2 Quick Reference to OS 2.0 Upgrade Process The Upgrade to OS 2.0 follows the same essential process that prior upgrades have followed, with a few basic exceptions which are called out here. The following description is a quick reference and doesn’t go into detail in many areas. Please refer to the referenced documentation for additional information.

• Customer systems that are on Release1.8.2 can be upgraded to OS 2.0 using Remote Access. However, Control4 recommends that you become comfortable with the OS 2.0 upgrade procedures by performing several upgrades on-site before you decide to use Remote Access.

• Customer systems that are on Release 1.7.4 or prior releases can’t be upgraded remotely due to the Dealer or Installer’s physical presence needed to join ZigBee devices to the mesh during the ZigBee Pro upgrade process.




7.2.1 Pre-Work Prior to Arrival at the Customer’s Location 1. Ensure that Composer Pro for OS 2.0 has been installed and activated on the Installer’s

laptop or PC. Internet connectivity is required for activation. 2. Internet connectivity is required on premise for upgrading from prior versions to OS 2.0.

Ensure that Internet connectivity is available or plan for temporary Internet connectivity during the time the upgrade is performed.

3. Make sure that you understand the upgrade path based on the current version installed on the customer’s system. For prior version upgrade support see Section 7.3, “Validated Upgrade Paths.”

4. If a Software License is needed (see Section 7.1, “OS 2.0 Software License“ ) use your Dealer account on my.control4.com to assign the license to the customer’s account.

5. If updating from Release 1.7.4 or a prior version, make sure that you understand the impact that the new operating system and ZigBee Pro will have on devices in the system. You may need to sell replacement or additional hardware to make the system work correctly. a. There is no support for ZigBee Pro firmware on the System Remote Control V1 or V2. b. Home Theater Controller and Media Controller can only be used as Secondary Controllers. c. Upgrading the Control4 system may cause reduced performance. You should understand the

system configuration and plan accordingly prior to upgrading to OS 2.0. d. If using Home Controllers HC-200, HC-300, or HC-500 to drive On Screen Navigators on

standard definition (SD) televisions or projectors, be aware that the new On Screen interface utilizes a 16x9 aspect ratio and will be scaled to fit the resolution of their display.

e. Understand other limitations that OS 2.0 may impose as they pertain to the customer’s system, and ensure that you have a plan to deal with them (see Section 4, “Known Limitations”).

7.2.2 Upon Arrival at the Customer’s Location 1. Connect to the Control4 system using the appropriate version of Composer for the system that is

currently running. a. Ensure that all IP and ZigBee devices are identified and online. b. Ensure that all system programming is working as it should prior to beginning the update. c. Make a backup of the Control4 system in Composer prior to beginning the update. This

backup should be named so that you can find it later if needed. 2. (Optional) Make sure that the customer’s media collection is backed up. Whether the media is

stored on a Control4 Controller hard drive, a USB drive, or a network-attached storage device, it is subject to loss if the storage device fails. Control4 doesn’t provide backup solutions for data storage but recommends that you ensure that customers have chosen and used a backup solution to protect their data.

3. Connect to the Control4 system using Composer Pro 2.0 to initiate the upgrade to OS 2.0, and then use Update Manager to begin the update process.

4. The Composer Pro 2.0 upgrade wizard will give you the opportunity to convert the Media Database and write metadata to id3 tags in MP3 files. a. The OS 2.0 media scanning process allows Control4 to synchronize the Media Database with

changes made by a third-party Media Manager (such as Media Monkey, Apple iTunes, or Microsoft Media Player). This is done using the id3 tags embedded in the files.




• If you believe the Control4 Media Database has the most correct/current information about song metadata, you can write this information to the mp3 file tags at this time (the storage device has to be online and writeable). If you don’t write the metadata to the tags and then scan, the information in the Media Database will be replaced by the information in the tags when the media is scanned.

• If you believe the media tags are more correct or current than the Control4 Media Database, you should NOT write the metadata from the Media Database to the tags.

b. The OS 2.0 system uses a different Media Database format. You must convert it when you upgrade the system. If you choose not to convert it, the Media Database will be deleted and can be reconstituted by scanning. • The 10.5” V2 Wireless Touch Screen now operates at a different resolution. During the

upgrade process, the wizard will look for the photo screen saver storage location and automatically scale all screen saver images for the new resolution.

5. Monitor the update progress of the IP devices using Update Manager. 6. After the Touch Screen devices have been updated (those that support the new Flash Navigator)

they will prompt for recalibration prior to use. 7. After the Primary Controller has been upgraded to OS 2.0, the ZigBee devices will be updated.

a. For Release 1.7.4 or prior version systems, an update of all ZigBee Devices to ZigBee Pro is required. Please refer to the ZigBee Pro Upgrade Instructions, Composer Pro Software Release Update Instructions – 1.7.4 to 2.0, if you are not familiar with this procedure.

b. For Release 1.8.x systems, the update to the latest ZigBee Pro firmware versions will happen automatically and will not require user intervention. Please be aware that ZigBee performance will be sluggish while firmware updates are in progress. Devices in MiniApp mode will have limited functionality while being updated.

8. At the conclusion of the update, please reboot the PC running Composer to ensure that the Samba mounts to the Controllers are current.

9. Backup the Project. After completing the update, please make a backup file of the project with Composer 2.0. Give it a name that distinguishes it from the pre-upgrade backup. If you ever need to restore this system, having a 2.0 backup will save you a lot of time and effort.

10. Train the user how to use the new Navigator customization capabilities. The new interface is similar to the prior version interface, but does provide some new capabilities. If you have a user who will be interested in the customization offered by OS 2.0 Navigators, you may want to help them configure their Navigators, and train them how to use these features.

7.3 Validated Upgrade Paths

7.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 Release1.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. Then 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, 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 it after the update is completed, as the project will be lost when the device is repartitioned.

• Only systems with Release 1.6 or later can be directly updated to OS 2.0.

7.3.2 Secondary Device Upgrades • Home Controller HC-300s functioning as Secondary Controllers need to be updated to

Release 1.6 or Release 1.7.x. This allows Control4 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.

7.4 Residential Software Product Releases

Control4 Software Releases (From Inception) Release 1.0

Wednesday, July 06, 2005 1.0.203.8 Initial Release

Friday, September 02, 2005 1.1.2.2 Maintenance Release

Friday, October 14, 2005 1.2.0.90 Maintenance Release

Thursday, November 03, 2005 1.2.2.6 Maintenance Release

Sunday, December 28, 2005 1.2.3.43 WiFi Support

Monday, March 06, 2006 1.2.4.48 Maintenance Release

Thursday, March 23, 2006 1.2.4.50 Maintenance Release

Tuesday, May 30, 2006 1.2.5.28 Thermostat and Outlet Modules Support

Release 1.3

Thursday, September 07, 2006 1.3.0 Initial Release

Monday, October 16, 2006 1.3.0.351

Wednesday, December 20, 2006 1.3.1.114 Initial Release

Friday, January 12, 2007 1.3.1.116

Wednesday, March 07, 2007 1.3.1.120 Daylight Savings Time Change

Tuesday, March 20, 2007 1.3.1.122

Monday, July 23, 2007 1.3.2.228 Initial Release

Friday, August 03, 2007 1.3.2.230 Maintenance Release - Updating firmware on Amp, Switch, etc.

Thursday, August 23, 2007 1.3.2.234 Maintenance Release - Various fixes, including NAS on HC-300.




Control4 Software Releases (From Inception)

Wednesday, October 31, 2007 1.3.2.298 Support for Amplifier V3 Release

Thursday, November 15, 2007 1.3.2.318 Support for HC-1000 Release

Tuesday, February 26, 2008 1.3.2.438 Support for HC-500 Release

Wednesday, April 30, 2008 1.3.2.442 Maintenance Release - Disable Onboard Serial Port on HC300/HC500.

Wednesday, June 11, 2008 1.3.2.442 HC300 VBUS Change to Kernel.

Release 1.6

Tuesday, July 29, 2008 1.6.0.486 Initial Release

Wednesday, Sept 17, 2008 1.6.0.512 Maintenance Release, SR-250

Release 1.7

Monday, December 01, 2008 1.7.0.348 Initial Release

Monday, December 29, 2008 1.7.1.290 Dock for iPod Release

Monday, March 30, 2009 1.7.2.160 Remove Polling; HC-1000v2, ELV Dimmer, 7" Portable Touch Screen

Wednesday, April 29, 2009 1.7.3.20 7" Portable Touch Screen Release

Tuesday, September 29, 2009 1.7.3.68 Maintenance Release – Audio priority and 7” Touch Screen

Monday, December 14, 2009 1.7.4.36 Maintenance Release – On Screen focus and Zones improvements

Release 1.8

Monday, August 31, 2009 1.8.0.44415 Initial Release

Monday, November 16, 2009 1.8.2.56194 Initial Release – multiple ZigBee Servers and Security changes

Wednesday, March 17, 2010 1.8.2.66691 Maintenance Release – Thermostat and B&D Lock

Release 2.0

Tuesday, June 29, 2010 2.0.0.80198 Initial Release

Release 2.0.1

Wednesday, August 18, 2010 2.0.1.86265 Maintenance Release

Release 2.0.2

Tuesday, September 7, 2010 2.0.2.88485 Maintenance Release

Release 2.0.4

Tuesday, October 19, 2010 2.0.4.92890 Maintenance Release

Release 2.0.5

Tuesday, December 14, 2010 2.0.5.99233 Maintenance Release

Release 2.0.6

Wednesday, January 19, 2011 2.0.6.102864 Maintenance Release




8. Technical Support Contact Information If you encounter any issues during or following the update, or if you have any questions, please contact Control4 Technical Support for assistance.

Phone: 1-888-400-4072 Email: [email protected]

For additional information about the new features and capabilities of OS 2.0 and later, refer to the new product training on the Web at http://control4.webex.com.

9. Legal Notice This document is confidential and is only made available to authorized Control4 Dealers who have agreed to terms of confidentiality under the Control4 Non-Disclosure Agreement. These terms must be maintained and pertain to information found in this document.

Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Control4 makes no warranties, either express or implied. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Control4.

Control4 may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Control4, the furnishing of this document, does not give you any license to patents, trademarks, copyrights, or other intellectual property.

mailto:[email protected]�

http://control4.webex.com/�

Documents

Control4 Operating System (OS) Release Version 2.0.6 ......Control4® OS Release 2.0.5 (OS 2.0.5) is a maintenance release for OS 2.0 system installs and is the default OS 2.0 version