A four-check handoff when W200 changes temperature source

When a W200 automation switches its temperature data source, I treat the change as a handoff that needs separate verification. A correct setpoint does not prove that the new room sensor is actually driving control.

For one low-risk test window, I choose two rooms with a stable temperature difference, keep the thermostat setpoint unchanged, and disable overlapping climate rules. At the scheduled handoff I record four things:

  1. the time the automation triggers;
  2. the data source shown in Aqara Home;
  3. the selected sensor reading versus the thermostat’s displayed control temperature;
  4. the first heating or cooling call after the switch.

If the source name changes but the control temperature does not, the selection may be only a UI or binding change. If both change but the HVAC action does not, I would check mode, deadband, and safety limits. If the source reverts after saving, the automation may not be persisting a virtual or soft-sensor target.

That separates source selection, temperature display, and HVAC control instead of treating them as one result.

4 Likes

That separation between source selection, displayed control temperature, and HVAC action is useful. In my Home Assistant setup I keep Aqara temperature and humidity sensors as room references and compare them with separate room sensors, because a handoff can look correct while one room still dominates the decision. Presence also determines which room readings should influence the climate logic, so checking the active source at the exact trigger time is important.

For a W200 change, I would log the trigger time, selected sensor, source reading, displayed control temperature, and first heating or cooling call. I would also record the previous source and whether the room was occupied. That helps distinguish a real handoff from a stale value or an overlapping rule. This kind of small controlled test is much more useful than checking only the final setpoint.

1 Like