EMS Account - Adding the Events2HVAC Application

Before connecting Events2HVAC to your ecobee devices, you’ll need to add the application to your ecobee account.  The user account that is used to add the application needs to have permissions to view all the hierarchy sets and read/write permissions to the thermostats that need to be controlled.

1.  Login to your ecobee account and go to “My Apps”

 



2.  Open the E2H client.

3.  Select Device Interface àEcobee à Ecobee Options.  (Note: If you don’t see this option, either you didn’t load the ecobee interface during setup of Events2HVAC, or you need to rediscover your devices using Device Interface Manager.)

4.  On the Connection tab, enter the connection information specific to your system.  Select the “EMS” account type.  See the next section on interface options for details about each field.

 

 

5.  Click on the “Enter App Key” button and enter the Application API key that was sent with your license.  You can optionally create your own application key if you have a developer account with ecobee.  Select the appropriate account type before starting the authorization process below.

 

Important: Your API key will be unique to your site.  Treat this key as a password secret and don’t share it with others.

6.  Click on the “Authorize Application” to start the authorization process using OAUTH2 pin code authorization.





7.  Enter the PIN code that is generated in Events2HVAC during the authorization step and click “Validate.”

Note: The generated PIN code from Events2HVAC is valid only for about 9 minutes.


8.  Review the application and permissions request and click on “Authorize” to accept the application.

9.  Wait for the PIN code authorization step to complete with a “Success” message and status that the connection is authenticated.  It can take a few seconds for the exchange to take place.

10. Save the settings by clicking on OK button.  Make sure you restart the Events2HVAC_Service so that it is using the same authentication token, otherwise, the service will cause the new token to be invalidated.