W200 with W100’s

I’ve seen videos stating that a firmware update allows the W200 to work with multiple temperature sensors. If that’s correct, can each individual temperature sensor be used for its own separate automation?

Also, can one of the sensors be used specifically to control the HVAC fan only, rather than triggering heating or cooling based on the temperature?

For example, I have a small office where I use my gaming PC and racing simulator. After about 10 minutes of gaming, the room can climb from around 72°F to 75–80°F depending on the season. I have an HVAC register directly above my setup.

What I’d like to do is create an automation along the lines of:

If presence is detected AND the office temperature is above 72°F → turn on the HVAC fan.

The goal would be to circulate the cool air already in the house and pull it through the office without lowering the thermostat for the entire house and potentially making everyone else too cold.

Is this something the W200 can accomplish with multiple temperature sensors and the HVAC fan control?

3 Likes

@ronster1082 Great use case for targeted comfort without freezing out the rest of the house! Let me break this down based on what’s available.

Multiple sensors with the W200: Yes, the Thermostat Hub W200 can link with up to 10 sensors, including the Climate Sensor W100, Temperature and Humidity Sensor T1, and Presence Multi-Sensor FP300. You can switch which sensor’s data drives the thermostat’s temperature and humidity readings according to your needs.

Your specific automation idea: Here’s where it gets tricky. The W200’s sensor linkage is designed to let you switch the primary control source — not run parallel, independent automations per sensor. The thermostat still operates as a unified HVAC controller, meaning fan activation is tied to its overall mode and setpoint logic.

For your “fan-only circulation” scenario, the W200 does support a dedicated Fan mode with speed control (High/Medium/Low/Auto) and a timer option. However, triggering this automatically via a specific room’s temperature + presence isn’t directly supported as a native thermostat behavior. The W100’s own automations get disabled when linked to a thermostat, so you’d lose its independent button-triggered scenes too.

Workaround path: You might approximate this through broader Aqara automations (Hub M3 + sensors + smart switches) to trigger the fan mode, but the W200 itself doesn’t expose granular “sensor X controls fan only” logic in the reference materials.

Worth testing whether a post-linkage automation via Aqara Home can target the W200’s fan state specifically — or if the ecosystem treats it as a monolithic climate entity. This information comes from community discussions and user experience summaries and may vary by environment. Please verify carefully.

If native support for room-aware fan circulation is critical for your setup, that sounds like solid feedback for the product team. 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.