My ecobee device – things that are smart wiki electricity quotes by benjamin franklin


• You can then rely on ecobee’s schedules and only use ST to let ecobee know when your family is present or away from home, so that there is no overlap between the 2 systems. Most of the ST thermostats (even the Nest) connected to the home automation platform lose their scheduling capabilities. With MyEcobee device you can make SmartThings and ecobee work together for more comfort and energy savings at your home!

• Rich APIs that allow you to virtually control all aspects of your ecobee thermostat: you can create a temporary ‘hold’, resume the scheduled program, control any device connected to ecobee (hrv/erv, humidifier, etc.), create a program/vacation, modify the program/vacation, etc. Nest APIs don’t allow most of these features as they are very limited.

• Contrary to ecobee, z-wave and zigbee thermostats are totally dumb when connected to a home automation hub. These thermostats then lose their scheduling capabilities… So, you need to re-program your schedules using different HA scripts which can be a pain if you have very precise scheduling requirements (in a large home for example).

Most of my Ecobee smartapps have been developed with this principle in mind: ecobee is responsible for the basic scheduling (as it’s more reliable and also accessible from the physical thermostat anytime) and ST is responsible for managing exceptions to the schedules that you define (i.e., ‘Away’ or ‘Home’ mode switch as an example).

With ecobee, you can not only set up your heating/cooling setpoints, but also your fan settings in your climates (fan set to ‘On’, ‘Auto’, and ‘Circulate’ with the fanMinOnTime settings which allows you to set a minimum fan time in minutes per hour).

As your preferences may be very different from mine, I won’t recommend here any specific cooling/heating settings. It really depends if you put more emphasis on your comfort or your savings…It’s a delicate balance between the 2 dimensions that your may need to fine tune for you and your other family members (if any).

So, you can configure two instances of the same smartapp: one for the ‘home’ ST Hello mode that will set your ecobee thermostat to ‘Home’ when you’re back from work for example, and another one for ‘Away’ for the ‘Away’ ST hello mode when you leave your home.

On the opposite side, ecobeeResumeProg resumes the ecobee’s climate (or program) when one of the predefined presence sensors is back home, or when there is a ST Hello Mode change, or when one of the motion sensors specified in the smartapp detects movement in your home.

The smartapp allows you to set up some ‘more or less heat’ and ‘more or less cool’ thresholds for increasing/decreasing the heating/cooling setpoints based on an outdoor temp sensor (could also be a virtual weather station).and a user-provided adjustment setting (ex. +/- 5°F) during the day.

In fact, with this smartapp, you can also use any types of ecobee thermostats (not only ecobee3 or the ecobee lite) such as the ecobee Smart-Si, EMS, or stat-02 (which are the older models) to have basically the same behavior as the ecobee3 and its remote sensors.

In brief, this smartapp combines all the previous smartapps in one single package because it monitors your home based on outdoor/indoor sensors and can set your ecobee thermostat to ‘Away’ or ‘Home’ according to a time threshold (in minutes) that you define.

(++++) If you plan to have smart vents later or want to average out your inside temp sensors with finer room control (logic similar to the ecobee3’s follow me with its proprietary remote sensors), look at the ScheduleTstatZones or ecobeeSetZoneWithSchedule smartapps

The ScheduleTstatZones smartapp can control any smart thermostats (not only ecobee but also Nest and any z-wave thermostats) and ST-connected vents (such as Keen Home vents or ecovents) to reach the ultimate comfort in the preconfigured ‘zones’ of your home. The smartapp’s logic is also based on indoor temp/motion sensors, an outdoor temp sensor, and smart vents (optional).

You’ll then be able to configure your own schedules (ex. weekends, evenings, mornings, weekdays). The smartapp will then set/adjust your main thermostat & your smart vents (and some optional room thermostats for baseboards or fireplaces) every 5 minutes based on the average temp algorithm calculated from the rooms’ temp sensors that are part of the zone that you’ve configured.

If you have many ecobee thermostats and/or many ecobee3’s remote sensors, create many MyEcobeeInit (for 2 or 3 thermostats max) instances and/or many ecobee3RemoteSensorInit (for 2-3 remote sensors max) instances and split your ecobee devices between the instances that you created. You can assign a different name for each instance on the last page.

If you get a blank screen after pressing ‘Next or you get the following error: java.lang.RuntimeException: Unexpected status code 500 from global or "Error – bad state. Unable to complete page configuration" or java.lang.NullPointerException: Cannot get property "authorities" on null object

So, the algorithm will work all the same after 1 hour or several days. So, if the smartapp works for more than 1 hour, it should work for days even months without issues provided that there are no other external factors (ex. connection issues between ST and ecobee with your physical thermostat).

You can use either a temp Sensor (such as Aeon MultiSensor, SmartSense or Keen Vents), a motion sensor (such as the SmartSense), a power meter (such as Aeon HEM) or a powerSwitch to reschedule the smartapp if needed (as long as this device is polled on a regular basis -ex. every 5 minutes ) so that it can create a ‘heartbeat’ for the smartapp.

For cloud-to-cloud integration, these rate limiting constraints are sometimes too low (due to network latency, servers involved, etc.), and this exception can be raised from time to time. There are some threads about it in the ST community forum: