Has anyone figured out a way to change the data source of the thermostat using soft sensors in automation if not, do we know if this is on the roadmap for Aqara?
4 Likes
@bspooner I don’t see anything in the current Aqara automation/thermostat info that supports switching a thermostat’s temperature data source to a “soft sensor” (virtual sensor) via Automation, and there’s also nothing here that confirms whether it’s on Aqara’s public roadmap.
What is supported today is using the Thermostat S3 as an automation trigger/target (e.g., temperature/humidity thresholds as IF conditions, and “set temperature / mode / wind speed” as THEN actions). This information comes from community discussions and user experience summaries and may vary by environment. Please verify carefully. https://www.aqara.com/en/product/temperature-humidity-sensor/installation-video/
If your goal is to “use another sensor’s readings,” one practical workaround is to build automation rules based on that other sensor (or a device that can surface those readings) and then drive the thermostat setpoint accordingly (instead of changing the thermostat’s internal data source). This won’t truly re-bind the thermostat sensor source, but it can approximate the behavior.
For roadmap/feature requests (like selecting a virtual/soft sensor as the thermostat’s reference), the best path is to submit it directly: Contact the Aqara Home App Customer Service Team (Profile> Help & Feedback > Customer Service) or scan the QR code:
This will be more efficient. If you do not have an Aqara Home account, “Please click here” to create a ticket. Sorry for the inconvenience.
2 Likes
I’ve been wondering about exactly this too.
The Soft Sensor update is already a big improvement, especially being able to average several temperature sensors and use that as the W200’s data source.
What would make it much more powerful, though, is being able to change the active data source through an automation.
For example:
- Daytime → use/average the living room sensors
- Evening → switch to the bedroom sensors
- Nobody home → use a central sensor or a different temperature strategy
That would let the W200 follow where people actually are instead of using the same temperature reference all day.
As far as I can tell, I don’t think Aqara currently exposes “change data source” as an automation action. If that’s correct, +1 from me for adding it to the roadmap — it would make Soft Sensors considerably more useful.
4 Likes
Sure, you can do this today. Create an automation based on time, for the THEN choose the W200 and select the Set Temperature Data Source parameter to choose the sensor you want to use.
3 Likes
Cool! Thanks for the headsup! I will try
The issue is you only see physical sensors the soft sensors don’t show up under data source under automations
1 Like
I handle a very similar problem in Home Assistant rather than inside the W200. My Aqara temperature and humidity sensors act as room references, while presence decides which readings should influence the climate logic at that moment. I also compare the values with separate room sensors so one warm or cold spot does not make the system overreact.
That is why exposing soft sensors in Set Temperature Data Source would be genuinely useful. It could let the thermostat follow the room or zone that is actually occupied instead of always using one physical sensor. Until Aqara exposes that option, Home Assistant can handle the selection and setpoint adjustments externally while the native controls remain available.
2 Likes
W200 Feature Request: Expose Fan Mode State + Allow Soft Sensors as Automation Data Sources
I recently installed an Aqara Thermostat Hub W200 and am using it with Aqara Home, Matter, and Home Assistant. Overall I really like the W200, but I’ve encountered two limitations that make advanced thermostat automation difficult.
- Fan mode needs to be exposed as a readable state
The W200 supports Fan Auto and Fan On/Normally Open, and these modes can be changed on the W200 itself or through Aqara.
However, the current fan mode does not appear to be exposed through Matter/Home Assistant as a readable state.
It would be very helpful if the W200 reported its current fan mode through Matter (Auto / On / Timer / Cycle, as applicable). This would allow Home Assistant and other Matter controllers to remain synchronized when someone changes the fan mode directly on the W200.
Ideally, fan mode would be both readable and writable through Matter.
- Allow Soft/Virtual Temperature Sensors as W200 automation data sources
The W200’s ability to create a Soft Sensor that averages multiple room temperature sensors is excellent.
For example, I have a Main House Average Soft Sensor that averages multiple rooms. At night, I want the W200 to use only my physical Bedroom Temperature Sensor.
The desired automation is:
- At Home / daytime → Main House Average Soft Sensor
- Sleep → Bedroom Temperature Sensor
Aqara automations provide a Set Temperature Data Source action, but the usable automation targets appear to be limited to physical temperature sensors.
Interestingly, when configuring the action I can navigate to Associated Sensor Data Source and see/select my Main House Average Virtual Sensor. However, after returning to the scene, the action reverts to the physical Bedroom Temperature Sensor. The Soft Sensor therefore cannot actually be saved as the automation’s temperature data source.
Please allow Soft Sensors / Virtual Sensors to be selected as Set Temperature Data Source targets in scenes and automations, just like physical Aqara temperature sensors.
This would make the W200 considerably more powerful for multi-room HVAC control and would allow users to automatically switch between whole-house averaging during the day and room-specific control while sleeping.
If these capabilities are already planned for a future W200/Aqara Home firmware release, I’d love to know.
Device: Aqara Thermostat Hub W200
Firmware: 4.5.49
Integration: Aqara Home + Matter + Home Assistant
1 Like