Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Sensor assignment to climate setting delay

I have climate definitions that I do not use as part of any schedule. Through the API, I set a hold to the specific climate (generally until the next timed event). I have disabled "follow me" and "auto away." It all works great except for one aspect - the sensors involved do not change over to the sensors used in the new climate, sometimes for up to an hour. They always eventually change, but when I change the climate, I want to start cooling or warming right now! (just like when I change the temperature). It seems like when the schedule changes the climate the sensor settings follow rather quickly. Is there a setting I may have missed somewhere?
1 person has
this question
+1
Reply
  • Hi ajlamar,

    Can you please explain in more detail what you mean when you say the sensors involved do not change over to the sensors used in the new climate? Is this on the thermostat that you see this or in the API?

    Does the delay you mention correspond to the end of the hold and start of a new climate?

    Please provide the JSON used for your request and response as there is not enough detail here for us to fully understand what you're describing.

    Thanks,
    Dan
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Hi Dan. Thanks for your reply! Our house can vary greatly from room to room, so I have defined (using the web site) a number of different climates using different sets of sensors. For example, in "Sleep," only the bedroom sensors are used. I created a climate ("comfort setting") using the website called "work at home." This climate uses only one sensor - the bedroom where I work from. Since this climate is not part of any schedule, and I don't want it to be, it is activated via the API.

    What happens is, let's say we are in "Home" comfort setting by schedule. "Home" uses three sensors. Then I use the API to change to "work at home" which uses only one sensor. For some period of time afterward, the original three sensors remain "in use" and are contributing to the average temperature reported. Eventually the two drop off and the one specified sensor becomes the only one active. This process of the sensors being included or excluded often takes 10 min - 1 hour. The sensors in use match on the mobile app and from the API, and are clearly being used based on the average temperature. I rarely touch the actual thermostat, but I will check it next time I do this.

    In this example, it took less than 5 mins. For the record, 5 mins is no problem, though that does not seem to be typical.

    File 1 - Original state "Home" - Note 3 sensors active
    https://www.dropbox.com/s/dzxj1ozntzp...

    File 2 - Override climate to "WorkAtHome75" (which is ref "smart2") - Note 3 sensors still active but see that by climate definition should be only 1.
    https://www.dropbox.com/s/rful2v3j07s...

    File 3 - Sensors have now "caught up" 5 minutes later - Only the one in use.
    https://www.dropbox.com/s/7guzle0vb8f...

    Thanks!
    Andy
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Hi ajlamar,

    This functionality is actually by design. The firmware on your ecobee gradually transitions between sensor readings to prevent your HVAC system from sharply transitioning between extreme/sudden temp settings.

    Another contributing factor has to with our APIs behaviour. Like the GET Runtime Report, the sensors component of the GET Thermostat call populates its response from the latest thermostat state change. Since thermostat state changes are sent to the server every 15 minutes (or whenever a thermostat's equipment state changes), it makes sense to experience some delay.

    Fore more info see the Get Runtime Report page (see https://www.ecobee.com/home/developer...) as well as GET Thermostat Summary (https://www.ecobee.com/home/developer...).

    Hope that helps,
    Dan
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • This slow shift from one sensor to another is really a bad design or at least there should be an option to disable it. This is a case where the thermostat is fighting against your wishes and thinks it is smarter than you but it doesn't take into account legitimate scenarios where you would want the shift from a sensor to another to be immediate. Here is a scenario:

    I have two comfort zones "home" and "sleep" that are 10 degrees apart with "sleep" being 10 degrees lower. The living room sensors which participate in "home" registers a temp of 75. My bedroom sensor which is in a cold side of the house registers 65 so it is already at the correct temperature if I were to shift from climate "home" to sleep" but what happens when I go to climate sleep? The thermostat uses the sensor at 75 to regulate my bedroom which doesn't need regulation so it turns on the AC for about 15-30 minutes until the stupidly slow sensors shift to the bedroom sensors. By that time the bedroom now is way too cold so the heater now has to go on to put the temp back where it was. Had the sensors shifted immediately, no AC or heater would have been engaged and no suffering in a cold bedroom would be necessary. But ecobee thinks they are smarter than the user and gives us no control over this behavior.

    This is what prompted me to look into the API and make my own control software that tricks the thermostat into shifting the the sensors immediately. To do this you have to programmatically and dynamically shift the desired sensor participation into all the comfort zones. So I no longer use comfort zones or leave it always in the same comfort zone but instead I shift the sensor participation around. If you do this the shift will occur immediately.

    You can do this through the interface but it is a pain to do it all the time so I automated this with the API.

    There are other quirks that you can get around with the API like the lame 2 degree limit between cool and hot presets which is actually 4 degrees because the thermostat sometimes does not activate if it's one degree off in either direction.

    You can trick it with a background service that constantly monitors the temperature and engages heat/cool based on a given desired temp instead of using auto. This way I am never off even by one degree in either direction from the temperature I want.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated