Multiple Processors

Use multiple processors in the same Crestron Home OS system.

To use multiple processors in the same system, all processors must use Crestron Home firmware 3.21 or later. All processors should use the same firmware.

Systems with multiple processors have a parent and child processor relationship. An overview of the relationship is described below.

• Parent Processor: The system can have only one parent processor.

  The parent processor claims additional processors as child processors and imports the configuration data required for operation. The parent processor only imports the data required to trigger actions on the child processors.

  The parent processor can claim up to four child processors.

  The parent processor communicates with child processors to control the system.

• Child Processor: A processor can be a child to one parent processor.

  The child processor controls the devices that are connected to it. The parent processor communicates with the child processor to trigger actions.

  The child processor must be online to be claimed by a parent processor and during configuration.

Pair Processors

• Maximum System Size
• Local Connection Settings
• Child Processor Settings

Multiple Processor Configuration Overview

Supported Features

• Rooms
• Keypads

• HR-Series Remotes

  Note: Only programmable buttons are imported.

• Lights and Light Scenes
• Fans and Fan Scenes
• Quick Actions
• Shades

User Interface Devices

If a User Interface Device is paired with a child processor, it will only see the devices attached to the child processor. It will have full control of loads and scenes on the child processor but may not be able to trigger scenes on other child processors or the parent processor. If the User Interface Device that is paired with the child processor triggers a scene that also exists on other child processors or the parent processor, it will also be triggered on those processors.

Quick Actions

Quick Action Merging

When a Quick Action is imported from a child processor, the imported Quick Action will display in the Quick Actions menu. When the Quick Actions are imported, Quick Actions may be created or merged with existing Quick Actions based on their names. When Quick Actions are imported, consider the following:

• Matching name (merge): If the name of a Quick Action on the child processor matches the name of a Quick Action on a parent processor, the Quick Actions will display as a merged Quick Action. A merged Quick Action will display the name of the parent Quick Action and the names of the child processors that contain the Quick Action. The programming for the Quick Action on the parent and child processor is maintained.
• Unique name (create): If the name of a Quick Action on the child processor does not match the name of a Quick Action on a parent processor, the Quick Action will be created on the parent processor and the Quick Action from the child processor will display as a merged Quick Action. The configuration for the Quick Action on the child processor is maintained, the Quick Action on the parent processor can be configured.

Quick Action Configuration

Quick Actions that are created on a child processor must be configured using the same child processor. A parent processor cannot be used to configure a Quick Action that was configured on a child processor.

To add more functions to a child Quick Action, configure the parent Quick Action to perform the additional functions. For example, to create a Quick Action for Watch TV in a system where the parent processor controls Audio and Video and a child processor controls lights:

• Parent processor: Configure the Quick Action on the parent processor to turn on the TV and select the video source.
• Child processor: Configure the Quick Action on the child processor to set the lights to the desired level.

To configure a Quick Action, refer to Quick Actions.

Rename a Quick Action

• Parent processor is offline: the Quick Action name will be changed on the parent processor when it comes online.
• Child processor is offline: A warning is displayed indicating that the child processor is offline. If the Quick Action rename is accepted, the old Quick Action name from the child processor will be reimported to the parent processor with the original name in addition to the renamed Quick Action. To merge the Quick Action with the updated name you will need to create the Quick Action on the child processors.

Changing Icons

Icons for Quick Actions are assigned using the Crestron Home app and can be assigned while connected to the parent or child processor.

If the parent processor has a default icon assigned and the child processor has a non-default icon assigned, the icon assigned to the child processor will import into the parent. If the parent processor and child processor both have non-default icons assigned, the icon assigned on the parent processor will be used. Icons do not update between the parent and the child processor after import.

Reorder Quick Action

The order or the Quick Actions is assigned using the Crestron Home app. The Quick Actions for parent and child processors can be arranged in any order. The sorting order is stored on the parent processor.

When Quick Actions are initially imported, the Quick Actions for the parent processor are displayed before the Quick Actions on the child processor. The Quick Actions for each processor are displayed alphabetically.

Delete a Quick Action

Quick Actions can be deleted using the parent processor or the child processor. When deleting a Quick Action using the parent or child processor, consider the following:

• Parent processor: Deleting a Quick Action using the parent processor will delete the Quick Action from all processors in the system.
• Child processor: Deleting a Quick Action using the child processor will delete it from the child processor. It will also delete the Quick Action from the Parent processor if no programming was added on the Parent processor. If the Quick Action was created on the Parent processor or if programming was added using the Parent processor, the Quick Action will not be deleted on the Parent processor.

Scenes

• Scene Names: Scenes with the same name will be merged on the parent processor.

  Scene Name	Child Processor	Parent Processor	Merged Scene Result
  Entertainment	Light A set to 75% Light B set to 60%	Sconce 1 set to 40% Sconce 2 set to 20%	Light A set to 75% Light B set to 60% Sconce 1 set to 40% Sconce 2 set to 20%

• Scene Fade Times: If the parent processor has a default fade time assigned and the child processor has a non-default fade time assigned, the fade time assigned to the child processor will import into the parent. If the parent processor and child processor both have non-default fade times assigned, the fade time assigned on the parent processor will be used.
• Scene Icons: If the parent processor has a default icon assigned and the child processor has a non-default icon assigned, the icon assigned to the child processor will import into the parent. If the parent processor and child processor both have non-default icons assigned, the icon assigned on the parent processor will be used. Icons do not update between the parent and the child processor after import.

Creating Scenes

When a scene is created on the parent processor or a child processor, the scene is added to all processors in the system that have the room. For example if one of the child processors does not have the same room then it will not get the scene.

Scene Editing

• Parent and Child loads can be added to a scene
• Child processor information is displayed for child loads
• When a load from a child processor is added to a scene, the scene is added to the child processor with that load. When additional child loads are added the scene on the child processor is updated to include those loads
• If the scene is deleted from the parent processor, it is deleted from all child processors

If the child processor is offline, the loads belonging to the child processor will display as offline in the Crestron Home Setup app connected to the parent processor. Changes made on the parent processor while the child is offline will be overwritten when the processor comes online.

• Changes on the child processor will automatically update the scene on the parent processor
• New scenes will be displayed on the parent processor
• If a scene is deleted on a child processor the loads will be removed from the parent processor scene. The scene will not be deleted from the parent processor.
• If the parent processor is offline, the scene will be imported when it comes online.

Scene Visibility

Scene visibility is imported with the child scene. If it is modified after import it does not stay in sync with the child.

Lighting Loads and Fans

If a parent and child have a load with the same name the child device will have a number appended to the end of the name to make them unique.

Delete or Rename a Light or Fan

The lighting load and fan can only be deleted or renamed by the processor that acquired it. To delete or rename a lighting load or fan, connect to the parent processor or child processor and then delete the device.

Ceiling Fan Button Mode

For fan controllers that are programmed on the same button using the Ceiling Fan button mode, fan speeds that are not common between the two devices will not be shown in programming. During operation and other programming, all fan speeds are displayed. For example, if two fan controllers are assigned to a button using the Ceiling Fan button mode and one fan controller supports four speeds and the other fan controller supports three speeds, only three speeds will be shown in programming.

Tunable Lights and Solar Sync Sensors

When using a solar sync sensor (GLS-LCCT) with tunable lights, one sensor is required for each processor in the system with tunable lights. Tunable light settings are synchronized between the parent processor and child processors.

Rooms

If a room exists on both the parent and child processors the rooms will be merged. The merge is case insensitive. The Crestron Home app will display the room with the case that is set in the parent processor.

Delete a Room

To delete a merged room, the room must be deleted on the child processors and the parent processor. If the deletion is only performed on the parent processor, the room on the child processor will be imported to the parent processor when the processors restart and check for updates.

Rename a Room

To change a merged room name, the name change can be made on any child or parent processor. The room name will be changed on all processors in the system.

If a parent processor is offline when the name is changed, the room name will be changed on the parent processor when it comes online.

If a child processor is offline when the name is changed, a warning will display indicating that the child processor is offline. If the room rename is accepted, the old room name from the child processor will be reimported to the parent processor.

Keypads

Keypads can be connected to a parent control processor or a child processor and can trigger actions from any processor in the system. For example, if a parent processor controls AV and the child processor controls lighting, a keypad button connected to the child processor can trigger an AV action on the parent processor.

For best performance and continuous functionality in case a parent processor goes offline, connect keypads to the child processor.

Keypad Programming

Button presses on keypads from a child processor can be used to trigger actions on a parent processor. The parent processor can send feedback to a keypad on a child processor.

Keypad programming can be performed using any processor in the system. When changes are made on one processor, the programming is overwritten on the other processor. For example, if a button is programmed to trigger a Scene on the child processor and changes are made using the parent processor to control a Lighting Load instead, the button programming on the child processor will be lost.

Keypad Settings

The device settings for an imported keypad can be viewed and modified using the parent processor or the child processor. Changes to the settings are synchronized between the processors.

Keypad Operation

When the button is pressed, the action synchronized between the parent and child processor. For example, if a button controls lights on the parent processor and lights on a child processor, all lights will be controlled at the same time.

The parent processor can send feedback to a keypad on a child processor

Shade Groups

When using shade groups, be aware of the following:

• If a shade belongs to a shade group, only the group is imported.

• Shade groups cannot span across processors.

• Shade groups can only be edited from the processor that the group was created on.

Crestron Home Configurator

Multiple processors are treated independently in the Crestron Home Configurator. There is no association assigned when setting up the system. When deploying the system, use a deploy code on each processor separately. After the configurations are loaded onto all processors, the Crestron Home Setup app is used to designate the parent processor and claim child processors.

Backup and Restore

The parent processor and child processors in the system must be backed up and restored individually.

• Parent processor backups contain programming for the parent processor only which includes the ability to recall actions on the child processors. It does not contain the programming on the child processor.
• Child processor backups contain only the programming for the child processor. It does not contain programming for other child processors or the programming for the parent processor. If the child processor is not backed up it cannot be restored using the parent processor backup.