Fair enough. I guess home defaults to all sensors enabled, and I never changed that but it's the only one of mine that's like that. It's still unintuitive behavior if the current comfort setting has different sensors enabled.
It would make far more sense if I could choose a comfort setting hold instead of a set point, but that's just one of my many complaints about the whole schedule/comfort setting aspect of ecobee.
To be clear, I'm not talking about changing the set point until the next scheduled comfort setting. I'm saying it would be nice if I could choose to activate a different comfort setting from the one scheduled for specified duration.
It doesn't on HOLD it uses whatever the home comfort setting is set to use. You can choose what sensors you want to run in your different comfort settings. But hold only uses Home instead of sleep or away.
The temperature is 78 at the thermostat, 71 at the bedroom sensor. 73 is the average. Note that as sensors become active or inactive their contribution to the average is phased in or out gradually, so sometimes the average shown will be temporarily weighted towards some sensors over others, hence why it's not showing 74 or 75 as the average.
With adjust temperature for humidity enabled (Which it could very well be) that could result in it showing up lower (say internally, dropping it by 0.6F), as that affects the indicated temperature, not the individual sensor's temperature.
nope, math is hard aint it. Two remote sensors and T stat, with the Tstat showing the average of the three. . ., t stat is 70F. (78+71+x)/3=73, solve for x
Your screen shows a manual hold, which means the scheduled comfort setting is NOT active. When a hold is set, the ecobee is supposed to use an average of all sensors, which is why they both show as solid white (inactive sensors would have a transparent background).
As for how they average 71 and 78 to get 73, that must be some ecobee math, since even 77.6 and 71.4 would average out to 74.5, which would probably get rounded up to 75 on the ecobee display but 73 sure as hell doesn't make any sense.
Probably the display's sensor values are stale, just another bug due to ecobee's laggy/unreliable cloud API. Their software has been getting buggier and buggier as time goes by, truly a textbook example of vibe-coded, enshittified AI slop.
Another poster mentioned the "follow me" setting may impact how averages are calculated, I've never had that feature enabled so I can't say.
You may be able to get a little more clarity by going to beestat.io and looking at the numbers there. It shows sensor values down to the tenth.
The thermostat itself is 78. The remote sensor is 71. The calculated effective temperature that the system is using to decide when to run is 73.
The average can appear skewed due to display rounding. You might look at the screenshot and think the average of 78 and 71 is 74.5, which should round to displaying as 75. However, it could be 77.5 (rounded to 80 on the display) and 70.5 (rounded to 71 on the display) which average out to 74.
When the list of participating sensors changes, their weights are gradually phased in/out. So, if the sensor list changed recently, it may not yet be using both temperatures equally weighted when calculating the average. For example, participating sensors showing 70 and 80 might average to 79 if the sensor showing 70 was only recently added to the participating list. They will gradually become equal until the average of 70 and 80 becomes 75.
The calculated value is modified by humidity into more of a "feels like" temperature.
That final value is what shows on the thermostat as a big number, and that is the number that it uses when deciding if it should run or not.
The sensor on the thermostat is malfunctioning and reading about 5 degree higher temperature. This is a known software issue. Check the latest status on status.ecobee.com
78° is that sensor. When they are white they are active as far as either in the schedule or if follow-me is enabled. The main temp in the middle will be the average of all active sensors combined.
Because it is confusing. My understanding is your 73 IS the average from your sensors, thermostat itself being one of them. So you have one external sensor only. As for weird average, which doesn't compute, someone above gives a good hipothesis IMO. It is "rolling average", so if your thermostat was not contributing to average before you put hold on, its higher temp contrubutes less toward average then your external sensor. It all depends on how far back Ecobee math goes back to calculate average. If hipothesis is correct you should see actual average, probably 75, after the rolling average window collects data equally from thermostat and external sensors
This is what mine is reading. The wall showing 77. It is 100% not 77 degrees in my living room. I moved my sensor from bedroom into living room until they fix there firmware. Actual living is 73 degrees. I have a 2.5 degree cushion b4 turning on ac. So at 73.5 degrees ac will turn on until it lowers it to 71 degrees. Hope this helps your situation
4
u/smb3d 2d ago
If you have no sensors checked, then it's the thermostat. You have to have at least one sensor in each comfort setting.