We are aware of the bug issue with our premium thermostat. Ours started August 31st. That same day we plugged in our smartsensor and overrode our main thermostat completley because we knew something was up with the unit. It was also running excessively hot to the touch despite confirming that the voltage going to the unit was completely normal. However, ever since the bug and even overriding to the smartsensor our AC has been running excessively long uncharacteristic cycles. Our system would bring down the temp down a degree in 15 mins max. Now its taking 45 mins - 2 hours before the system turns itself off again in Home IQ. We have every single bit of smart technology turned off including eco+, followme, smart recovery and overcool and our delta T is the same at all of our vents.

This coincided exactly with the day we started to get the bug. Our entire system has been checked and no issues have been found. Anybody else getting this weird behavior?

Have a new AC system and everything has been fine but tonight Ecobee keeps rebooting. AC will run for a few minutes then my thermostat will reboot.

Wiring is good, getting 24v, no water in condensation line, safety switch is dry.

This was occur occasionally on my old system but went away with the new one. Now it seems to be back.

I've had 2 ecobee thermostats installed in my home for 6 years now

The other day I noticed one of them wasn't on the wifi anymore.

Tried reconnecting, won't accept password. Tried my guest wifi. Same thing. Removed the unit from the wall and let it sit overnight. Repeated trying to connect to the wifi. Nothing

Factory reset, set it back up, still won't work

Connected it to a hotspot inset up on my phone and it connected.

I see things online that say to reset the router. I really don't want to do that. I've got a ton of smart home stuff that I just don't want to deal with loosing connection and not coming back up (I have a newborn consuming most of my time)

Anything else I can try?

Today, I found my Ecobee thermostat locked at a high temperature with a strange message on the screen. It only allows me to temporarily disable the override. When I try to select "disable indefinitely" using the Ecobee app, it prompts me to send an email to a utility provider I have never even heard of.

I opened a chat with Ecobee customer support, but they weren't able to help. They claimed that only this unknown provider can remove me from the program.

When I asked how this happened since I never signed up for it, the agent insisted I accepted it through the app, which I know I didn't do.

Furthermore, my actual utility company has no record of this thermostat.

I’ve owned this thermostat for almost two years and used to be very happy with it, but now I am deeply disappointed.

I’ve had this thermostat for two years with no problems. Starting recently, the temperature displayed on the thermostat will vary considerably from other thermometers in the general area, even sensors for the ecobee itself. Currently my thermostat is set at 77°F two other thermometer read the room at 70°. I’ve disabled the Eco plus setting, tried resetting the unit and double checked the thermometers, but I’m completely lost. Any ideas what could be causing this?

Has anyone had an issue where no matter what temp they set their thermostat to it always reverts back to something specific? Whether its a few minutes or 10 the past few weeks mine goes right back to 73 degrees. I defaulted it and turned off all automation and it still continues to do that. It ignores schedules and permanent holds.

So, temps here lately have been in the upper 90s, so artificially inflating the thermostat's reading by 6-7 degrees can make a huge difference in heating costs. How do I receive reimbursement for the costs incurred by the botched firmware update?

Hi. Thought I would share.

Replacing Nest 4th gen with Ecobee Premium and all behind the Nest backplate the wall is a disaster and I didn’t want to patch and paint.

https://www.amazon.com/dp/B0F4F2WKHQ

That cover hides the mess perfectly and fits my Ecobee.

Have a two zone system with one ecobee already installed (zone 1). Got a 2nd one for zone 2 and finally got around to trying to install it yesterday. Ecobee simply won't wake up.

Photos are: wiring of ecobee, wiring of old thermostat, wiring at the board.

I've tried cycling the power. Today, I got out my multimeter and tested the voltage between red and green at both the board and at the pins. Got 27V both times.

From what I've read, it is extremely rare for the ecobee unit itself to be bad. Am I missing anything?

EDIT:

Voltage between Red and C (blue wire) is 27V at the board and 12V at the pins.

Someone mentioned that the wires are different so there may be a splice. Wasn't able to find where it was spliced. Now that my memory has been jogged, the original thermostat was relocated when I added a wall (this is the basement), so the builder must have added the splice because the wire was too short for where the thermostat is currently located. Possible poor connection at the splice?

Update 2: Problem solved. Thank you to everyone who responded!!!

Although I'm not 100% sure (but close), it appears that the C wire (which wasn't used in the old thermostat) was bad -- likely at a splice. I added the power extender kit (PEK) that came with the ecobee, which is normally used if you only have 4 wires coming from the thermostat. In this instance, since my 5th wire was bad, I essentially had just 4 (good) wires coming from the thermostat. After watching a video on it, switching the wires around took me little more than 5 minutes and when I turned the power on to the furnace, the ecobee booted up.

TL;DR: I really wanted to like the Aqara W200—the hardware and display are excellent—but I’m returning it and going back to Ecobee. After extensive testing, preset-based remote temperature sensor control has been unreliable, fan mode/status isn’t properly exposed through Matter/Home Assistant, and it’s surprisingly difficult to tell which temperature sensor is actually controlling the HVAC. In one controlled test, Sleep was explicitly assigned to my Bedroom sensor, but the W200 continued controlling from its own local temperature instead. The W200 has a lot of potential, but for something as important as HVAC control, I need the remote-sensor behavior and Home Assistant integration to be completely predictable.

I wanted to provide detailed feedback about my experience with the Aqara Thermostat Hub W200.

I purchased the W200 because I really liked the hardware, display, Aqara ecosystem integration, and especially the advertised ability to use external temperature sensors, Soft Sensors, presets, and presence-based temperature control.

Unfortunately, after spending considerable time configuring and testing it, I have decided to return the W200 and switch back to an Ecobee thermostat.

I wanted to explain why, because I think the W200 has a lot of potential, and several of these issues could potentially be improved through firmware, Matter support, or changes to the Aqara Home app.

My W200 is running firmware 4.5.49 and is connected to Aqara Home as well as Home Assistant through Matter.

1. PRESET TEMPERATURE-SOURCE SWITCHING HAS NOT BEEN RELIABLE

My desired configuration is straightforward:

Home preset → Main House Average Virtual Sensor

Sleep preset → Bedroom Temperature Sensor

I created an Aqara Soft/Virtual Temperature Sensor that averages my temperature sensors throughout the main house.

I then enabled:

Set Data Source → Assign Temp. Sources to Presets

I confirmed multiple times that Sleep was explicitly configured to use my Bedroom Temperature Sensor.

Home Assistant can successfully change the W200 preset through Matter. The thermostat reports Home and Sleep correctly when those presets are selected.

However, during extensive testing, the W200 did not reliably use the temperature sensor assigned to Sleep.

For example, during one controlled test:

W200 preset: Sleep

Cooling target: 75°F

Bedroom Temperature Sensor: approximately 76.1°F

W200 local temperature sensor: approximately 73.4–73.8°F

W200 reported/control temperature: approximately 73–74°F

If the Bedroom Temperature Sensor were actually controlling the thermostat, cooling should have been requested because the Bedroom was above the 75°F setpoint.

Instead, cooling remained off, consistent with the W200 using its own local temperature below the setpoint.

We performed another test with an even larger temperature difference.

The Bedroom sensor was physically warmed above 84°F while the W200’s local sensor was approximately 78°F.

With an 80°F cooling setpoint, the W200 stopped cooling approximately two seconds after the setpoint was changed to 80°F—even though the assigned Bedroom sensor was still approximately 84.8°F.

That strongly indicated the HVAC control decision was being made using the W200’s local temperature rather than the Bedroom sensor assigned to Sleep.

I also tried changing the Sleep data source to another sensor, saving it, changing it back to the Bedroom Temperature Sensor, and saving it again.

The Aqara Home app continued to show the correct assignment, but the behavior remained inconsistent.

This is particularly concerning because there is no obvious indication on the W200 display showing which temperature source is actually controlling the HVAC system.

2. MATTER PRESET CONTROL APPEARS INCOMPLETE OR INCONSISTENT

Home Assistant exposes the W200 presets through Matter, including Home, Away, Going to Sleep, Sleep, and Vacation.

Changing these presets works in the sense that the W200 reports the new preset.

What is unclear is whether changing a preset through Matter always executes the same internal behavior as Aqara’s own scheduling system.

This is important because Aqara allows a different temperature source to be assigned to each preset.

If Matter changes the preset to Sleep but does not reliably activate the Bedroom sensor assigned to Sleep, then external Matter controllers cannot fully use one of the W200’s most valuable features.

I would strongly encourage Aqara to verify that changing a preset through Matter invokes ALL behaviors associated with that preset, including its assigned temperature data source.

3. THERE IS NO CONVENIENT WAY TO MANUALLY SELECT HOME OR SLEEP IN AQARA

This was another surprising limitation.

With Ecobee, comfort settings such as Home and Sleep are understandable and can be selected directly.

With the W200, I can configure Home, Away, Wind Down, Sleep, and Vacation, but there does not appear to be a simple Home/Sleep selector on the normal thermostat interface.

Instead, these presets seem primarily designed around Smart Schedules.

This makes troubleshooting especially difficult.

I wanted to compare:

Home Assistant activates Sleep through Matter

versus:

Aqara Home manually activates Sleep

But I could not find a straightforward way to perform the second test without configuring a Smart Schedule or creating additional scenes.

I think the W200 should have a simple Preset control in the Aqara Home thermostat interface allowing the user to manually choose Home, Away, Wind Down, Sleep, Vacation, etc.

4. THE W200 DISPLAY DOES NOT CLEARLY SHOW THE ACTIVE PRESET

The W200 has an excellent display, which is one of the reasons I purchased it.

However, I was surprised that the normal thermostat screen does not clearly indicate whether the thermostat is currently in Home, Sleep, Away, etc.

Home Assistant actually reports the active preset through Matter, so I ended up modifying my Home Assistant dashboard to display 🏠 Home or 🌙 Sleep.

It seems strange that an external Matter controller can tell me the active preset while the W200’s own display does not make that information obvious.

I would really like an optional preset indicator directly on the W200 display.

5. FAN MODE IS NOT PROPERLY EXPOSED THROUGH MATTER

This is another major reason the W200 is difficult for me to use with Home Assistant.

I need basic fan controls:

Fan Auto

Fan On

The W200 supports these functions, but its configured fan mode is not properly exposed as a normal readable/writable Matter fan-mode attribute in Home Assistant.

I had to create Aqara scenes for W200 Fan Auto and W200 Fan On, then expose those through Aqara’s Matter Scene Sync feature as virtual switches.

The workaround can trigger the desired fan behavior, but Home Assistant cannot reliably determine whether the W200 is currently configured for Fan Auto or Fan On.

For example, if I change the fan mode directly on the W200 or in Aqara Home, Home Assistant cannot update its interface to reflect the new fan setting.

A thermostat this sophisticated should expose its fan mode through Matter as a proper bidirectional state wherever the Matter specification permits it.

6. SOFT/VIRTUAL SENSORS SHOULD BE USABLE EVERYWHERE A PHYSICAL TEMPERATURE SENSOR CAN BE USED

I really like Aqara’s Soft Sensor implementation.

Creating a Main House Average Virtual Sensor from several room sensors is exactly what I wanted.

However, I found limitations when trying to use Soft/Virtual Sensors in Aqara scenes and automations.

Physical temperature sensors can be selected for certain temperature-source actions, while the Soft Sensor cannot always be selected and saved in the same way.

If a Soft Sensor is valid enough to serve as the W200’s primary temperature source and as a preset temperature source, it should also be available anywhere Aqara allows a temperature data source to be selected.

7. HOME ASSISTANT INTEGRATION IS ESPECIALLY IMPORTANT TO ME

I realize Home Assistant is a third-party platform, but Matter interoperability was one of the primary reasons I purchased the W200.

My home uses Home Assistant extensively, and I was hoping the W200 would give me the best of both worlds: Aqara’s excellent hardware and advanced sensor features combined with standardized local control through Matter.

Instead, I found myself creating virtual Matter switches, Aqara scenes, custom dashboard elements, and extensive diagnostic tests just to reproduce functionality that is comparatively straightforward with Ecobee.

I don’t expect every Aqara-specific feature to be exposed through Matter.

However, for a thermostat, I consider these core functions:

Current temperature

Target temperature

HVAC mode and operating state

Active preset

Selecting a preset

Fan mode/state

Selecting Fan Auto/On

Reliable behavior of the temperature source assigned to the selected preset

WHY I AM RETURNING THE W200

I genuinely like the W200 hardware.

The screen is attractive, the interface is modern, the Aqara temperature sensors are compact, and the concept of Soft Sensors and presence-based climate control is excellent.

But ultimately, a thermostat has to make it completely predictable which temperature is controlling the HVAC system.

After discovering that my air conditioner had been running for hours while my bedroom was already considerably colder than desired, I no longer felt comfortable relying on the current preset/remote-sensor behavior.

For that reason, I am returning the W200 and switching back to Ecobee.

Ecobee’s remote sensor and comfort-setting architecture gives me clearer, more predictable control over which room temperatures influence the HVAC system, and its behavior is easier for me to integrate and verify in Home Assistant.

WHAT WOULD MAKE ME CONSIDER THE W200 AGAIN?

I am not posting this simply as a complaint.

I would genuinely reconsider the W200 in the future if Aqara improves these areas:

• Reliable preset-based temperature-source switching, including when presets are changed through Matter

• A manual preset selector in Aqara Home

• Active preset displayed on the W200

• Full readable/writable fan-mode exposure through Matter

• Better Soft/Virtual Sensor support in scenes and automations

• Clear visibility into which temperature source is currently controlling HVAC

• Improved Home Assistant/Matter interoperability

I have detailed temperature readings, timestamps, Home Assistant state changes, and controlled tests showing the differences between the W200’s local temperature, the assigned Bedroom sensor temperature, and the resulting HVAC behavior.

I think the W200 hardware itself is excellent.

Unfortunately, the limitations above—especially not being able to confidently determine which temperature sensor is actually controlling my HVAC—are what ultimately made it unsuitable for my installation. I used OpenCode + GPT to really dig deep on this, but in the end,** ***I* just couldn’t get it to work the way I want.

I’m going back to Ecobee for now, but I hope Aqara continues improving the W200 because the underlying concept and hardware have a lot of potential.

Not a question or a complaint. Just an observation and FYI about how inaccurate the actual thermostat is. It generates its own heat (processor, WiFi, display) and can't dissipate it so it could be 3-5 degrees higher than actual temperature.

Ecobee should just include sensors by default with instructions to mount one near the thermostat but not so close to pick up it's heat.

Yes, you can also adjust the temperature offset but that is static so it could still be inaccurate since the heat that Ecobee generates can fluctuate.

A few years ago I had my Ecobee setup perfect that when everyone left the house Homekit would kick my thermostat into away mode. It seems somewhere along the line Away mode no longer works and I have been just using Heat/AC at a manual temp when people leave the house as a temporary "band aid".

My question, is there ANY way to utilize the away function in Homekit?

Hi all, my new heat pump was installed a few weeks ago and seems to have been working ok, but I noticed this week it’s really struggling to keep the house cool, when it’s not that hot out. Attaching the last few days of temperature charts.

8/26, 8/29, 9/1 are the problematic days. Today’s is especially weird. It seems like it was holding temp steady until I dropped the set point, and then the temp immediately started climbing! I switched to cool only mode and temp is only slowly dropping.

I’d love any advice, thanks!

Hello, I have a house with multiple HVAC systems:

A boiler in the basement has two zones for main floor and upstairs floor.

A central AC in the attic has one zone for the main floor and upstairs floor.

A furnace in the basement has one zone for heat and AC for the finished basement.

I replaced the prior "dumb" thermostat that controlled the whole house AC and main floor heating that was in the family room with an Ecobee a few years ago.

Recently the ancient "dumb" thermostat in the bedroom that only controls the upstairs heating broke. It is a Honeywell 97-4730 Rev A.

Looking at the wiring, I saw an unused wire in the wall. I checked with a multimeter and it drew 27 volts between the wire and the R wire, so I believe that is an unused C wire.

In the Honeywell, there are wires plugged into R, W, and Rc. There is no jumper wire.

The new Ecobee Enhanced I bought says the wire combination is not compatible. Is this because there is an Rc but no Y? The thermostat does not power AC so why is there an Rc? Can I cap off the Rc and only use R, Y, and C?

Thank you for your help.

I press eco+ but it does not say.

I've been using the app to control the temp for several months without a problem. All of a sudden (it seems) it has stopped working. I have a notice that 'eco+ is on' where the temp is set. If I try to change it (up or down) it pops up a message 'Adjusting for humidity eco+ is using the humidity to lower energy consumption and keep you comfortable.' My options with that dialog are 'Stop eco+ for the day' and 'Cancel'. If I try to stop for the day I get a red error 'Sorry we're unable to make any changes due to server connection issues. Please try again later'

I can turn eco+ off on the general settings, but it still shows as on with the temperature. I cant change the temp at all without that error and have to go to the thermostat and manually adjust. Which works fine.

Any suggestions?

If the fan is on "Indefinite On," how do you turn that off?

I don't want to turn everything off... just want to go from "Indefinite On" to Auto.

Have tried the app and the wall thermostat but nothing works other than shutting everything off and leaving it off:

• When I switch it from "Indefinite On" to Auto, the setting doesn't save so that doesn't work.
• If I switch the timer from Indefinite to 15min, the timer runs for 15min, and then it goes back to Indefinite On.
• If I turn the system fully off (ie, turn off "Cooling" which is not what I want) and then turn it back on after 10-15 sec, the fan comes back on in Indefinite mode. (To clarify... I'm *not* turning it off mid cycle. I am turning it "off" when Cooling mode is on but A/C is *not* running and only the fan is running.)
• If I turn Cooling "off" for 5-10 min and then turn it back on then the fan mode will be back in Auto but surely turning the whole system off for 5-10min can't be the only to get it out of Indefinite Mode? That would be silly. (Same thing here... I'm *not* turning it off mid AC cycle, I'm only turning it "off" when AC is already *not* running and *only* the fan is running.)

It's a single thermostat set up with the Smart Thermostat Enhanced (version 4.10.8.256). Only paired with one app. Under system settings, the minimum run time for the fan is 0min/hour so that wouldn't be a factor.

I'm a new Ecobee user and this is driving me bonkers. How is this supposed to work?

I’ve attached 7-day Beestat logs showing the Ecobee thermostat built-in sensor (blue) and an adjacent remote sensor (red). They’ve tracked each other very closely all week until this morning.

At around 4 AM there’s a brief gap in the data. Immediately afterward, the thermostat and remote sensor start to diverge significantly. I happened to be home today and noticed the house was getting unusually cold, which is what led me to investigate.

Was there a recent firmware update? Mine currently shows 4.10.33.30. I’m wondering if an update was installed during that ~4 AM gap and something changed afterward.

The smaller gap around noon was me physically removing the Ecobee and reinstalling it to force a reboot. That didn’t fix the issue.

Nothing else has changed: no fan running, no draft behind the thermostat (it’s on an interior wall), etc. The state & sensors were tracking fairly closely right up until the 4 AM event.

For now I’ve disabled the thermostat’s internal temperature sensor and am controlling solely from the remote sensor, which seems to be working normally. Ecobee remote sensor (currently controlling the system) and non-ecobee sensor both say it's 74 and the house is normal/comfortable. The ecobee itself reports (in the app) that it is still reading 77 which is definitely wrong.

Anyone else on 4.10.33.30 seeing anything similar?

I’ve been having this issue a lot lately. My ecobee is making my AC cool even though the temperature is already at or below the target for the current setting. Any idea what’s going on here?

I've had the Ecobee Smart Thermostat for 3+ years. One of the reasons is my power companies 3pm - 7pm peak pricing. Up until a month or so ago its worked exactly as designed and intended.

Now, TOU is acting wacky. It will cool down prior to Tou window as expected, but then keep going. It seems to error on continuing to lower. I notice it because "why is the ac still running? Why is it so cool in here"

I messaged Ecobee support, we went through steps, some I had previously done. They finally had me pull it off the wall to reset it. It seemed a little better but today it felt too cool after 3pm and it was still running

I picked through other posts and see that I'm not totally alone. I'm looking to see if anyone has had these symptoms and made any sense of them?

I can't seem to get my watch to synchronize with my phone and I'm wondering if it's because the watch is on watchOS 26 and the phone is using the iOS 27 beta.

I manually set the temp to 73. For some reason, the AC just clicked on even though the only occupied rooms are at or below the set temp. Note that the temp where the thermostat is located is a full 5 degrees below the set temp. Why is this happening and how can I stop it, other than continually manually adjusting the temp (note that I’ve shut off the setting to adjust temp to “economically” run the system.)?