In the case of out bindings for EMS or Utility accounts, the `` criteria can be a path to a management set (for example, `/Toronto/Campus/BuildingA`). You can use either a comma-separated list of thermostat identifiers (no spaces), or, for non-EMS thermostats only, a wildcard (the `*` character). The thermostat identifier can be found in the report.įor out (`>`) bindings only, `` can instead be selection criteria that specify which thermostats to change. > For non-ecobee3 users who are using the older web portal, you can go to the Home IQ™ tab and choose Download Data from the Report chart. > The final component of the URL is your thermostat identifier. You can set up multiple, distinct API connections by repeating the appkey and scope settings with a prepended "user ID" that indicates a separate account will be used to complete authorization. # the temperature scale to use when sending or receiving temperatures # Time in ms to allow an API request to complete (as of 1.8, optional, defaults to 20000) # Time in ms to wait after successful update, command or action before refresh (as of 1.8, optional, defaults to 6000) # Data refresh interval in ms (optional, defaults to 180000) # Rate at which to check if poll is to run, in ms (as of 1.8, optional, defaults to 5000) # choices are smartWrite,smartRead, or ems, or multiple (required, comma-separated, no spaces) # the application scope used when authorizing the binding #ecobee:appkey=9T4huoUXlT5b5qNpEJvM5sqTMgaNCFoV # the private API key issued be Ecobee to use the API (required, replace with your own) In OpenHAB 1.7, ecobee:refresh defaulted to 60000ms (one minute). The refresh interval can also be specified, and defaults to 180000 milliseconds (three minutes). Under openHAB 1.x, these values must be set in the configurations/openhab.cfg file, or in the conf/services/ecobee.cfg file under openHAB 2.x (minus the ecobee: prefixes). Typically, scope will be set to smartWrite, but if you have an EMS thermostat, set scope to ems. You must generate your own appkey on the Ecobee developer dashboard. In order to use the Ecobee API, you must specify the appkey and scope that will be used. In order to use this binding, you must have already registered your thermostat(s) with Ecobee, registered a new app as a developer, and then login to your web portal.įor installation of the binding, please see the Wiki page Bindings. Monitoring ambient temperature and humidity, changing HVAC mode, changing heat or cool setpoints, changing the backlight intensity, and even sending textual messages to one or a group of thermostats, can be accomplished through this binding (and its accompanying action bundle available in 1.8, or before then via CI builds or here). The EMS, EMS Si, Smart, Smart Si and ecobee3 models are supported by this binding, which communicates with the Ecobee API over a secure, RESTful API to Ecobee's servers. of Toronto, Canada, sells a range of Wi-Fi enabled thermostats, principally in the Americas. Note: This Binding is available in 1.7 and later releases. Items, Rules and more Examples of a SmartHome.Item definition examples Sitemap definition examples Please update the wiki if you do come across any out of date information. Be aware that things may have changed since they were written and some examples might not work correctly. Feature overview Installation Setup intro Linux and OS XĪ good source of inspiration and tips from users gathered over the years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |