Shelly Climate Driver Configuration

Installation Process

IMPORTANT NOTE:

The driver is installed as two separate drivers, one under is Climate and one under is Input / Output.  Each must be installed separately.

• ShellyTRVClimate is used to install multiple thermostats for climate control and temperature measurements. 
• ShellyTRVPro is a communication device used to install multiple instances of ShellyTRVInputOutput  to report valve position and battery level and to trigger events based on their values.

Install TRVClimate Driver

It is recommended that you follow the below installation process in order to ensure you are running the latest version of the [driver].

• Unzip and Extract all EDRVC Files from downloaded file into the Driver Installation folder.
• Open Climate, Communication Devices, Add New Communication Device

• Navigate to the folder where the driver is located and Choose the ShellyClimate Driver.   

Note:  If the driver doesn’t appear under the Communication Type then make sure that the TRV driver is extracted to the same folder where all the other drivers are installed from.  It’s good practice to create one folder on the computer where all the third party EDRVC files live.

Note:  If the driver still does not appear, do the following:

1. Extract the downloaded zip file to you EDRVC folder (the folder where all custom EDRVC drivers live)
2. Go to Thermostat, then add a ShellyClimate driver.  Then Delete it.
3. Now go back to Communications device, Add, Check the box the says show unsupported devices, the Driver should show up on the bottom. 

• You’ll receive a warning that this is not a Native Elan driver, click OK
• The Driver will automatically go into trial mode for 7 days.  Wait for about 10 seconds and the Status will turn Green. 
• Enter your activation code and user credentials then Apply

Auto Discovery Process

• The Driver will Hold a default discovery window for 5 minutes.  You can increase that time in the drop down menu.  The driver will install all tstats discovered during this period
• To speed up discovery, trigger each TRV manually and make sure that each TRV is connected to a power source during discovery and install.  This will make it report to the network and the driver will discover it and install it.

• The driver will then Automatically Install
  • All thermostats discovered
  • A default Heating/Cooling Unit.
• The driver will also auto provision the unit and reboot it to save the settings
  • Make sure the TRV is fully functional and is online before installing the driver.

• It is recommended that you create a separate Generic HVAC unit and attach all TRV units to it.  Set the new Generic HVAC unit to Heating only.
• After the drivers are installed, change settings as needed to fit the Heating Unit.

Manual Installation of Thermostat

You can also add a thermostat manually if Auto Discover doesn’t find it.

Click Climate —-> Thermostats —-> Add New Thermostat —-> Shelly TRV.

Fill in the IP address of the thermostat and click Apply.

Make sure the device is online and setup.

Install ShellyTRVPro Input / Output driver for valve position and battery feedback

Under Input / Output —-> Communication Device —-> Add New Communication Device —-> ShellyTRVPro

Click on Auto Discover / Install

• The Driver will Hold a default discovery window for 5 minutes.  You can increase that time in the drop down menu.  The driver will install all tstats discovered during this period
• To speed up discovery, trigger each TRV manually and make sure that each TRV is connected to a power source during discovery and install.  This will make it report to the network and the driver will discover it and install it.

Change Input Names to match devices

You can now create a custom interface and easily connect the elements

Numeric Triggers

The Driver will also add the battery levels and valve position as numeric variables so you can use them as numeric triggers.   For example, if the battery position < value, then execute an event.

However, the issue remains that be default, the controller names all the Input / Output variables using the same name. To change the names for easy identification, match the Driver ID under each numeric input and match that to the System # in the Input Controller and change the name to match.  Use the new names in Event Maps and triggers