Transfer Data using a Deploy Code (Recommended)

Use a deploy code to transfer system data from a cloud backup to a new Crestron Home processor. The deploy code is the most versatile method of transferring data and is recommended for most situations. The Crestron Home processor system data must be backed up using the myCrestron Residential Monitoring Service. When a deploy code is used, system data is downloaded from the myCrestron Residential Monitoring Service and then loaded onto the Crestron Home processor.

Transfer data using a deploy code between the control processors listed below:

		To
		CP4-R	MC4-R	PC4-R	DIN-AP4-R	CP3-R	PYNG‑HUB
From	CP4-R
	MC4-R
	PC4-R
	DIN-AP4-R
	CP3‑R
	PYNG‑HUB

When migrating system data that contains Crestron wireless devices, the wireless gateway data is either transferred to the control processors internal wireless gateway or stored in a Virtual Gateway.

• Stored in a Virtual Gateway: Wireless gateway data is stored in a Virtual Gateway if the old system had an internal wireless gateway and the new system does not or if the old system use external wireless gateway (CP4-R with CEN-GWEXER). For example, during an MC4-R to CP4-R or CP4-R with CEN-GWEXER to MC4-R data migration. To transfer the data to a gateway, refer to Add a Wireless Gateway and Migrate Wireless Devices.

• Transfer to internal gateway: Wireless gateway data is transferred to the internal wireless gateway automatically if the old and new system have internal wireless gateways. For example, during a PYNG-HUB to MC4-R or MC4-R to MC4-R data migration.

  IMPORTANT: When transferring to an internal gateway:

  • The internal wireless gateway can only accept an automatic a wireless gateway data migration one time. Wireless gateway data migration will fail if attempting subsequent migrations to the same internal wireless gateway.
  • To make sure that the wireless gateway data can be transferred to the wireless gateway, the wireless gateway should be factory fresh.

Requirements

• If adding an Ethernet-to-Cresnet bridge during the data transfer, the Ethernet-to-Cresnet bridge must be installed and configured prior to the transfer. For details, refer to Migrate Cresnet® Wired Devices to an Ethernet-to-Cresnet Bridge.
• Cresnet connection The Crestron Home processor must be connected to the myCrestron Residential Monitoring Service prior to using a deployment code. Refer to myCrestron Residential Monitoring Service for details.
• The new control processor must be connected to the same network and have the same subnet mask as the old control processor. Using a private switch and connecting all devices to it is best.
• Write down the Hostname of the old control processor. The hostname will be needed when setting up the new Crestron Home processor.

• Migrating from PYNG-HUB to a CP4-R or MC4-R control processor:

  • Audio components, such as audio sources, endpoints, and routing, are not transferred to the new control processor. The audio components must be manually added to the system.

  • Camera tiles do not display in the user interface after migrating to the new control processor. To view the camera tiles, remove the camera and then add it again. For details, refer to Cameras.
• Add a Crestron wireless gateway to the system if the old control processor had an internal wireless gateway and the new processor does not have a gateway.

• Disconnect the Amazon® Alexa® voice control account or the Google Assistant™ voice control account prior to transferring data. To remove voice control service, refer to Remove Voice Control Services.

  Note: The homeowner may need to enter their Amazon or Google credentials to unregister the old processor.

• Lutron RadioRA3, Homeworks QSX, and RA2 Select processors and their configurations cannot migrate to a different Crestron Home processor. During the pairing process, a unique certificate is created that allows communications between the two processors. After migration, the Lutron system must be paired and reconfigured.

Transfer Data

Generate a Deploy Code

1. Go to portal.my.crestron.com.
2. Select  Devices and then select a processor.

3. The Deploy Code is displayed in the system information. If the deploy code is not shown or to create a new Deploy Code, select Generate Deploy Code.

   NOTE: The deploy code expires after 14 days.

   

Set Up the Crestron Home System using a Deployment Code

1. Open the Crestron Home Setup app and then connect to the Crestron Home processor.

   NOTE: If the Crestron Home Setup app does not connect to the Crestron Home processor automatically, enter the Crestron Home processor's hostname and select Connect. The default hostname for a Crestron Home processor is "[Product-Name]‑[MAC Address]" (excluding punctuation). For example, "CP4-R-123A567B91C3." The MAC address label is located on the bottom or rear of the device.

2. The Crestron Home Setup splash screen is displayed. Select Tap Here to Begin.

   

3. Select the language for the Crestron Home Setup app and then NEXT.

   

4. Select Import System Using Deployment Code and then NEXT.

   

5. The Crestron Home software must be up to date to use a deployment code. If necessary, select Update Software to update the software and then NEXT.

   

6. Enter the deployment code that was generated using the myCrestron Residential Monitoring Service and then select NEXT. The deployment code is validated.

   

7. Select a configuration and then NEXT.

   In the Select Configuration to Import menu, select a configuration. The current firmware version of the control processor is displayed below the menu. Each configuration lists the date, time, and firmware version of the backup.

   To restore a backup, the firmware version of the backup must be equal to or lower than the system version. Firmware versions 3.014.0087 or lower are displayed as unknown.

   • Green Check Icon: Backup version is equal to or lower than the system version.
   • Gray ? Icon: Backup version is unknown.
   • Red ! Icon: Backup version is higher than the system version and cannot be restored until the system firmware is upgraded.

   

8. The configuration is downloaded from the myCrestron Residential Monitoring Service and then displays the system information. To load the system onto the Crestron Home processor, select NEXT.

   

   NOTES:

   • The Step 7: Loading System Information screen is displayed while the system information is loaded onto the Crestron Home processor.
   • The system information is typically loaded to the Crestron Home processor very quickly. The Step 7: Loading System Information screen may be visible for a very short period of time.

9. The Crestron Home processor restarts after the system information is fully loaded onto the Crestron Home processor.

10. Update the hostname for the replacement Crestron Home processor.

    The hostname on the replacement control processor must match the hostname of the control processor that was written down during Generate a Deploy Code.

    1. Go to  Settings > System Configuration > Ethernet Settings to view the Ethernet Settings screen.
    2. Enter the hostname in the Host Name box.
    3. Select Done and then OK to confirm. The Crestron Home processor applies the new Ethernet settings and then reboots.

11. Restart these system components:

    • Control processor: To restart, issue the reboot command

    • DNS server: In most cases, this is accomplished by restarting the router.

    • IP Devices: Restart the touch screens, Ethernet devices, and Wi-Fi network devices in the system.

12. If necessary, perform these steps:

    • Add a new wireless gateway (CEN-GWEXERor CEN-GW1) to the system. For details, refer to Add a Wireless Gateway and Migrate Wireless Devices.

    • Register the Crestron Home processor with an Amazon® Alexa® voice control account or a Google Assistant™ voice control account. For details, refer to Voice Control Settings.

Add a Wireless Gateway and Migrate Wireless Devices

1. To view the Pair Devices screen, select Pair Devices on the Setup screen or on the setup menu.

2. In the Device Types menu, select Manage Gateways. The local network is scanned for gateways. Discovered gateways are displayed in the Gateways on Network menu.

   NOTE: The Virtual Gateway is displayed in the Gateways in System menu with a yellow triangle on the device icon and named "Replacement EX Gateway."

   

   NOTE: To scan the network for new gateways, select Recheck Network.

3. In the Gateways on Network menu, select a new wireless gateway and then select  Add.

4. A dialog appears asking if the new wireless gateway is replacing a Virtual Gateway. Select Yes to add the new gateway to the system and to transfer data stored in a Virtual Gateway to the new gateway.

   

   NOTE: To add the new gateway without replacing the Virtual Gateway, select No. If No is selected, all wireless devices will need to be manually added to the system and programmed.

5. Select a Virtual Gateway from the Virtual Gateway List and then select OK.

   

6. The data stored in the Virtual Gateway is transferred to the new gateway and the new gateway is displayed in the Gateways in System menu.
7. Configure the gateway after it is added to the system. Tap the gear button next to the device name to display a Settings dialog box. For details, refer to Device Settings.