Carrier Cloud Crestron Home™ Driver

It is recommended that you save a configuration or golden configuration before installing any driver.

The option “delete configuration file” should should remain unchecked. The driver saves the communication configuration into a file. When any user attribute value is changed, the driver is deleted (including the configuration file) and re-added again. If the driver is going to be removed permanently and not re-installed, the option “delete configuration file“ should be checked.

This thermostat model uses a cloud service to send and receive information. Carrier (and most cloud based services) have a limit on the number of queries and requests that can be made. For Carrier, this is 10 minutes.

Carrier provides a limited number of queries each month, so we have to be respectful of that limit for all our users. Should Carrier provide a solution that doesn’t require polling, we will update our driver accordingly.

This has to do with Carrier wanting to charge access to their API based on usage. Should Carrier decide to backtrack on this decision, we will update so the license accordingly.

The driver receives the system name from Carrier, which is assigned during the initial thermostat pairing process on the web page. Even if you update the name on the web page, the system name returned by Carrier’s server will still reflect the old name. To update the system name that is returned to the driver, you will need to unpair the device and then pair it again. This will ensure that Carrier sends the updated system name.

If the driver doesn't create the directory with the zone list, there are a few steps you can take to troubleshoot the issue:

• Verify the system name: Ensure that you are using the correct system name that was used when the thermostat was initially paired with the user's Carrier account. Using the wrong system name can prevent the driver from creating the directory. The system name is case-sensitive. If you are unsure about the system name, it's recommended to refer to the documentation or user manual provided by Carrier or contact their support team for assistance.

• Unpair and pair the thermostat: If you don't remember the system name or suspect that it might be incorrect, you can try un-pairing and re-pairing the thermostat again on the user's Carrier account. This process typically involves accessing the settings menu on the thermostat and selecting the unpair or disconnect option. Once unpaired, follow the instructions provided to pair the thermostat again with the correct system name.
• Allow time for communication: After adding the thermostat to a room, it's important to wait for a sufficient amount of time for the driver to establish communication with Carrier’s service. In some cases (especially systems with a large number of thermostats), it may take at least 1 to 2 minutes for the driver to properly communicate and create the directory with the zone list.
• The authorization code has a very short expiration time (approximately ~30 seconds). Many people obtain the authorization code first and then slowly go through the process to install the driver. Instead, go through the process of installing the driver and enter in all other information (ie. api key, api secret, license key). Then go through the process to obtain the authorization code and system name. Once you obtain that info, put it in the driver and proceed.

• If after all these steps the folder is still not showing up, then you may contact us via email. We may ask you to send us the user’s account credentials in order to properly troubleshoot the issue. If sending the account credentials is not possible for whatever reason, then your only other option is to use an alternate control method, such as our other Carrier driver, that uses RS-232 and SAM module.

This driver supports controlling all zones, including damper zones, that are associated with the configured location. Please verify your driver settings and ensure you have entered the correct authorization code and the location name.

No, you do not need a license for each driver instance. The license is per processor, which means you can have as many instances as you need on the same processor using the same license.

If your processor is using OS4 the new path is “Drivers → Managed Platforms”.

Unfortunately you need to uninstall the driver, taking care to make sure you check the option to the Delete the Configuration in the “Installer Settings” in the main platform driver. Than install the driver again using a new authorization code. The reason for this is a security feature on the manufacturer’s side. The existing authorization is paired with a specific set of devices and can not be updated dynamically. The only option is to generate a new authorization code that is paired with an updated list of devices. A word of warning, this will also delete all the quick actions associated with this driver.