Quick Summary (TL;DR)
For a Home Assistant-first radiator heating system, choose the valve and its integration path together—not merely the cheapest motorised radiator head. The SONOFF TRVZB is a cost-conscious Zigbee choice with detailed Zigbee2MQTT support; SONOFF TRV-ZBT (Gen 2) adds more exposed controls but is currently better suited to Zigbee2MQTT than stock ZHA. Aqara W600 is a flexible Zigbee-or-Thread alternative, while tado° X and Matter-ready Eve Thermo suit homes already investing in a working Thread network. Danfoss Ally offers a Zigbee radiator option; Drayton Wiser makes particular sense when buying a complete boiler-and-room system.
The trap: a smart thermostatic radiator valve (TRV) controls water flow through one radiator. By itself it normally cannot request the boiler or heat pump to produce heat. A room may be demanding 22°C and the valve wide open while the central thermostat has already switched the heat source off. Proper multi-room heating requires compatible heat-source demand coordination, minimum flow, pump protection and a sensible fallback when Wi-Fi, the hub or Home Assistant goes down.
Our buying order: verify the physical valve body and adapters; choose Zigbee/ZHA, Zigbee2MQTT, Matter-over-Thread or the supplier bridge; check actual model-specific entities; establish boiler/heat-pump control; and only then buy six or ten identical TRVs. Test one room first. Matter and Zigbee are local-capable, but not every vendor feature is exposed through Home Assistant, and a Zigbee device advertised as “Matter compatible” often depends on a separate bridge.
- Best budget route: SONOFF TRVZB plus a supported Zigbee coordinator and Zigbee2MQTT, provided its exposed features meet your needs.
- Best newer Zigbee specialist: SONOFF TRV-ZBT (Gen 2), but confirm software version and avoid assuming complete native ZHA support.
- Best dual-protocol flexibility: Aqara Radiator Thermostat W600, selecting either Zigbee or Thread during setup.
- Best Thread/Matter ecosystem: tado° Smart Radiator Thermostat X or a confirmed Matter-ready Eve Thermo revision.
- Best integrated UK heating platform: Drayton Wiser room valves and its compatible heating hub, with the community-maintained local Home Assistant integration.
What a smart radiator valve does—and what it cannot do
A traditional thermostatic radiator valve uses an expanding sensor to throttle a radiator as local temperature approaches its setting. A smart TRV substitutes electronics and a motorised actuator, letting you set a numeric target temperature, timed setback or a room-level boost. That is useful, but it is only one part of the heating control chain: room temperature → radiator valve → circulation → heat-source demand.
Many homes have one wall thermostat controlling the boiler and independent mechanical TRVs on the radiators. Fitting smart heads may improve how individual rooms are heated, but does not automatically make the boiler follow demands from every room. In some installations, a separate boiler relay, OpenTherm-compatible controller, zone controller or original central thermostat still determines whether hot water reaches the radiators. That coordination is a system-design issue, not a feature unlocked by pairing a Zigbee device.
| Element | What it controls | What it does not automatically control |
|---|---|---|
| Smart TRV on a radiator | Local valve opening and room setpoint | Boiler firing, pump operation or system bypass |
| Remote room temperature sensorAliExpress price | A better estimate of occupied-area temperature | Hydraulic flow or burner demand without suitable controls |
| Zigbee/Thread network | Communication between room devices and controller | The boiler safety chain |
| Boiler thermostat / heating hub | Heat demand and sometimes modulation | Every radiator independently unless integrated |
| Home Assistant | Scheduling, dashboards and supervisory automation | Certified boiler protections, minimum water flow and safe electrical isolation |
This is especially important with heat pumps, which often prefer long, stable operation and weather compensation rather than many short calls for heat. A radiator-by-radiator control strategy that makes most valves close at once can reduce minimum flow and increase cycling. Your heating professional should assess bypass provision, buffer or hydraulic separation, pump control and the manufacturer’s minimum-flow requirements before you change central demand logic.
Best smart radiator valves for Home Assistant: 2026 comparison
The table rates integration approach, not heating output or laboratory-measured reliability. “Local” means the basic control path can stay inside the home when correctly installed; it does not imply that every vendor function, firmware update or bridge setup works offline. Model revisions and firmware matter.
| Valve / ecosystem | Radio / Home Assistant route | Best reason to buy | Important limitation |
|---|---|---|---|
| SONOFF TRVZB | Zigbee 3.0; Zigbee2MQTT, with ZHA capabilities to verify | Value-oriented retrofit; rich Z2M entities | ZHA and Z2M do not necessarily expose identical functions |
| SONOFF TRV-ZBT (Gen 2) | Zigbee; Zigbee2MQTT 2.12.1+ specified by SONOFF | Newer valve behaviour and extensive advanced reporting | Manufacturer warned native ZHA functionality was not yet complete at verification |
| Aqara E1 | Zigbee 3.0; Aqara hub or model-tested third-party Zigbee stack | Existing Aqara/Zigbee households | Bridge-based Matter is not native Matter on the valve |
| Aqara W600 | Selectable Zigbee or Thread/Matter | Protocol choice; M30×1.5 with supplied adapters | Protocol switching requires setup; not simultaneous dual-network operation |
| tado° Smart Radiator Thermostat X | Matter over Thread; Home Assistant Matter | Local setpoint via Matter; coherent tado X system | Needs compatible Thread border router; tado X is not tado V3+ |
| Eve Thermo (Matter-capable revision) | Matter over Thread | Local-first Thread ecosystem | Check exact generation and firmware; older HomeKit-only units differ |
| Danfoss Ally Radiator Thermostat | Zigbee 3.0; vendor hub or compatible third-party Zigbee | Established hydronic-valve maker; retrofit ecosystem | Feature exposure varies by gateway and Zigbee integration |
| Drayton Wiser Radiator Thermostat | Wiser hub; community local HA integration | Complete boiler + multi-room system in UK | Vendor hub required for the standard system; third-party integration is not HA core |
Our recommendations by household
1. SONOFF TRVZB: best starting point for a Zigbee2MQTT retrofit
The original SONOFF TRVZB is attractive when you already run a stable Zigbee2MQTT network and want multiple independently scheduled radiators without buying one proprietary bridge per room. The published Zigbee2MQTT device definition exposes a Home Assistant climate function as well as items such as battery state, window detection, child lock and frost-protection settings. It also documents local-versus-remote temperature input behaviour. These are documented software capabilities, not a guarantee of identical controls in every frontend or firmware release.
Its appeal is not merely a low head-unit cost: you can usually reuse an existing Zigbee coordinator for other sensors and reduce the number of proprietary ecosystems. Before ordering a full pack, inspect your chosen coordinator, Zigbee2MQTT release, intended valve adapters, room temperature strategy and return policy. A connected TRV that cannot reach the radiator pin or reports an unsuitable temperature is not a bargain.
2. SONOFF TRV-ZBT Gen 2: strong advanced controls, but verify the stack
SONOFF now lists a separate TRV-ZBT Gen 2, which must not be confused with TRVZB. Its Zigbee2MQTT device page shows advanced controls and diagnostics including valve-position-related values, calibration, temperature-source selection and other model-specific attributes. The manufacturer recommends a sufficiently recent Zigbee2MQTT release for full support. Its own documentation also warns that complete native ZHA support had not yet been merged at the time checked; that could change with later software.
Choose this if those advanced functions are genuinely useful and you are comfortable maintaining Zigbee2MQTT. If you insist on stock ZHA only, confirm the current release’s support before buying. Do not treat a generic “Zigbee 3.0 compatible” logo as a promise that all proprietary valve settings will appear.
3. Aqara W600: best flexibility between Zigbee and Thread
The Aqara W600 supports two radio ecosystems: Zigbee and Thread, with Matter support on the Thread path. Aqara specifies an M30×1.5 connection, supplied valve adapters and two AA batteries. This is appealing for buyers deciding whether to extend an established Zigbee network or move future rooms towards Matter over Thread.
Dual-protocol does not mean both protocols operate at the same time. Aqara documents a protocol-switch process through its app and factory-reset/setup workflow. Decide which stack you intend to use before fitting several valves, and verify which features Home Assistant actually exposes in that mode. An Aqara bridge can also present devices to other platforms; that is not the same architecture as direct pairing to Home Assistant’s Zigbee coordinator or Matter controller.
4. tado° Smart Radiator Thermostat X: best for a coordinated Matter heating ecosystem
tado° X radiator heads communicate over Thread and can be commissioned as Matter devices in Home Assistant. In a compatible installation, their basic climate entities can work locally. A Thread border router and properly configured Matter controller are required, but you do not necessarily need a dedicated tado Bridge X when a compatible border router is already installed. Availability and exact setup options differ by market.
tado X is also a relatively coherent choice if you need the matching room thermostat or boiler controller rather than only isolated valves. However, tado X and earlier V3+ equipment are different product generations that cannot simply be mixed. Home Assistant’s older Tado cloud integration explicitly does not support X devices; use the Matter integration for X. Vendor-app services, advanced schedules and firmware management may not map into generic Matter features.
5. Eve Thermo: best for a verified Matter/Thread installation
Eve Thermo is a local-network-oriented radiator option, but hardware revisions make the precise product listing important. Eve’s current Matter-capable Thermo documentation specifies Thread, a compatible Matter controller and Thread border router, M30×1.5 valve fitment and adapters for common Danfoss patterns. Some older Eve devices originally used HomeKit-only commissioning and require particular hardware or firmware steps to gain Matter support.
Buy by exact product generation and advertised Matter status—not by the Eve Thermo name alone. Check whether you need an Apple device for any upgrade path and whether your preferred Home Assistant controller provides the climate controls you expect. A suitable network and pairing procedure are more important than a stylish product page.
6. Danfoss Ally and Drayton Wiser: choose the heating-system context
Danfoss Ally is a Zigbee 3.0 radiator thermostat from an established hydronic-heating manufacturer. Danfoss says it can operate with its Ally Gateway and third-party systems using Zigbee. Nevertheless, no universal Zigbee promise guarantees identical weekly schedules, valve-opening readings or binding behaviour in ZHA and Zigbee2MQTT. Inspect the exact model support and local installation constraints.
Drayton Wiser is better understood as a complete heating platform: the Wiser hub and compatible room valves coordinate central heating. The local Home Assistant connection is provided by a community-maintained HACS integration, not an official built-in core integration. Drayton’s newer Wiser radiator-head revisions are described as compatible with its platform, but verify the hub generation and regional system before buying. It is sensible for a house where reliability of boiler demand matters more than eliminating a vendor bridge.
Zigbee, Matter over Thread or a proprietary heating bridge?
These choices operate at different layers. Zigbee is a device network typically connected to Home Assistant through ZHA or Zigbee2MQTT. Thread is another IP-based low-power mesh; Matter is an application standard that can run over Thread. A vendor bridge may speak Zigbee or Thread to valves but use Ethernet/Wi-Fi, local APIs or cloud services upstream. The key practical question is who keeps heating the house if Home Assistant is unavailable.
| Architecture | Required equipment | Home Assistant route | Offline considerations |
|---|---|---|---|
| Direct Zigbee + ZHA | Supported coordinator / healthy Zigbee mesh | Built-in ZHA | Locally connected, but model-specific features and independent schedules vary |
| Zigbee + Zigbee2MQTT | Supported coordinator, MQTT broker, Z2M service | MQTT discovery/entities | Local-capable; more components and software maintenance |
| Matter over Thread | Thread border router, Matter controller, matching valve | Built-in Matter | Basic control can stay local; vendor-specific features may be missing |
| Vendor heating bridge | Compatible vendor hub + radiator heads + boiler control | Official or community integration, sometimes cloud | Better integrated heat-source control; openness depends on hub and API |
For a small self-managed home with Zigbee sensors already installed, adding two compatible Zigbee radiator heads is attractive. For a larger existing tado X or Wiser heating setup, ripping out a working heat-source controller to remove the vendor bridge can make reliability worse. For a brand-new Home Assistant system, buy the protocol for which you have tested devices, good radio coverage, a clear battery-maintenance strategy and a predictable fallback.
ZHA versus Zigbee2MQTT: which provides better TRV control?
Home Assistant’s ZHA integration supports many Zigbee device classes, including climate devices, but its climate category is marked beta in the official documentation. ZHA also cautions that there is no single official list of every working device and that non-standard attributes may need device-specific quirks. Zigbee2MQTT offers individual model pages describing exposed properties and firmware-specific support. Neither approach is automatically superior for every valve.
| Check | ZHA | Zigbee2MQTT |
|---|---|---|
| Initial Home Assistant experience | Integrated into HA device setup | Separate service and MQTT broker |
| Device-specific support | Standard clusters plus quirks | Converters documented by exact model |
| Advanced TRV attributes | May require newer quirks or workarounds | Often detailed on each device page |
| Maintenance | Home Assistant and zigpy updates | Z2M, broker and converters need updates |
| Moving a paired valve | Usually factory-reset and re-pair | Usually factory-reset and re-pair |
| What to verify | Does this exact revision expose a climate entity? | Is this exact device model listed with needed properties? |
If a valve pairs but you only get a battery sensor, do not assume the radiator is now controllable. Check the device signature, quirk or converter support, wake-up process and software version. Likewise, a valve that appears as climate may not expose precise opening percentage or external-room-sensor input. Test every important function before replicating across the home.
Thread, Matter, border routers and bridges: what is actually needed?
A Thread border router links the Thread mesh to your home IP network. A Matter controller, such as a properly configured Home Assistant Matter setup, commissions and controls Matter accessories. Some third-party smart-home hubs combine these roles; others do not. A Zigbee USB coordinator is not automatically a Thread border router simply because both radios use 2.4 GHz. Home Assistant’s official Thread and Matter guides explain the separate roles and the importance of IPv6/multicast connectivity.
With tado X or compatible Matter-ready Eve Thermo, first establish that the phone, Home Assistant and border router can commission Matter devices on a correctly configured network. If the valve has already been added to a vendor Matter fabric, use the vendor’s supported share to another Matter controller procedure rather than blindly reusing its original pairing code. That distinction prevents a common “invalid code” failure.
Aqara E1 illustrates a different type of compatibility claim: it is a Zigbee device which may appear via a Matter-capable Aqara bridge. That does not turn the E1 into a native Matter-over-Thread radiator head. The controller can see different features when a device is bridged than when it is joined directly to Zigbee2MQTT or ZHA.
Mechanical fit: check the valve before ordering
The radio protocol will not help if the actuator does not fit the radiator valve body. M30×1.5 is common on modern radiator valves, but Danfoss RA/RAV/RAVL and other manufacturers use different couplings. Supplied plastic adapters vary by model, and the presence of an adapter in a kit is not proof it will suit every valve. Check the valve-body maker and dimensions, whether the pin moves freely and whether the radiator currently has a functioning thermostatic head.
| Pre-purchase check | What to inspect | Why it matters |
|---|---|---|
| Valve body interface | M30×1.5, Danfoss pattern or another recognised profile | Wrong adapter may damage threads or fail to actuate pin |
| Valve pin condition | Does existing thermostatic head regulate reliably? | Sticking wet-side valve is not solved by a new smart motor |
| Actuator clearance | Adjacent wall, shelf, radiator cover, furniture | Oversized head may not physically rotate or fit |
| Room placement | Radiator under window, curtain, enclosure or hot pipe | On-head temperature can be biased above room air |
| Included adapters | Check exact kit and regional packaging | May change the real installed cost |
| Wet-system changes | Any need to replace valve body or drain system | Requires appropriate plumbing/heating expertise |
Replacing only the detachable thermostatic head on a compatible, sound valve is a different job from replacing the water-bearing valve body. Do not loosen plumbing unions or modify a pressurised/heated radiator system on the assumption that smart-head fitting requires it. If the valve is manual-only, seized, leaking or unsuitable, have a qualified heating installer advise on the correct body.
A remote room sensor can matter more than another premium feature
A TRV positioned a few centimetres from a hot radiator, behind a curtain or close to a cold external wall does not necessarily measure the temperature where people sit. If it reads 24°C while the centre of the room is 20°C, the radiator may close too early. Some systems support a dedicated wall sensor, a vendor-reported remote sensor, or device-specific external-temperature updates. Others provide only a local calibration offset or lack a dependable remote-sensor mechanism.
SONOFF’s Zigbee2MQTT pages distinguish local and external temperature selection and document how external values can be supplied; that does not mean every Home Assistant temperature sensorAliExpress price automatically binds to it. You may need a carefully tested supervisory automation to send measurements. Aqara E1 advertises integration with Aqara temperature sensors within its ecosystem; availability through a direct third-party coordinator is a separate question. tado X and Wiser have their own room-control and sensor options, with features dependent on the setup.
Use an independently placed room sensor to diagnose bias first, ideally away from direct sun, radiators, draughts and electronics. Observe several heating cycles and occupant comfort before enabling corrective automation. Large arbitrary offsets can fix one condition while making another worse; a proper remote-measurement path or better placement is preferable.
Heating-demand coordination: valves, boiler, pump and heat pump
This is the decisive difference between a collection of smart radiator heads and a coherent heating system. A room controller can want heat even while the central boiler controller is satisfied. Conversely, many TRVs can close while the boiler or pump still runs. The safe design must account for manufacturer instructions on minimum flow, pump overrun, bypass or hydraulic separation and any radiators intentionally left without throttling heads.
| Heating system | Likely sensible arrangement | What to verify professionally |
|---|---|---|
| Combi boiler with a central wall thermostat | Retain a certified boiler demand controller; integrate selected room demand | Boiler interface, minimum flow and anti-cycling |
| Boiler with zone valves / cylinder | Keep existing zoning and hot-water interlocks | Valve end switches, pump overrun and hot-water priority |
| Air-to-water heat pump | Preserve weather compensation and stable circulating flow; use moderate room adjustments | Minimum flow, emitters, buffer and compressor cycling |
| District heating / communal heat | Local radiator control inside permitted user interface | Building rules, balancing and control-valve restrictions |
| Single radiator in a well-controlled house | Replace compatible mechanical head; retain central controls | No unintended boiler-demand or frost-protection changes |
For a deep dive on boiler interfaces, our existing OpenTherm Gateway with ESP32 and Home Assistant explains the differences between reading/modulating boiler data and merely switching a contact. Neither OpenTherm nor a relay should be retrofitted to a heat source based on a generic TRV automation recipe. Retain certified over-temperature, frost and combustion-safety functions.
Battery life, noise and mesh coverage
Radiator valves are battery-powered motors, so their real battery life depends on motor travel, schedule frequency, radio reception, ambient temperature, firmware and how often the homeowner manually adjusts them. A vendor may quote a one-year battery life under test conditions; do not treat that as a guaranteed service interval in a large older house. Keep the specified batteries available and set low-battery notifications in Home Assistant.
Both Zigbee and Thread use low-power mesh networking. Mains-powered router devices can extend a healthy mesh, but not all mains smart plugs act as reliable routers for every environment. Battery radiator valves are usually sleepy endpoints, not routers. Metal radiators, foil-backed insulation, masonry walls and large floor plans can all make a previously adequate network unreliable. Position gateways carefully and confirm signal health over several days before expanding to the next room.
| Symptom | Possible cause | First low-risk test |
|---|---|---|
| Valve drops offline behind radiator | Poor link budget or unstable routing | Observe reachability and improve coordinator/router placement |
| Batteries drain unusually fast | Frequent motor movement or repeated reconnects | Reduce unnecessary adjustments; inspect network diagnostics |
| Noisy night-time corrections | Aggressive schedule with repeated target changes | Reduce number of setpoint transitions |
| Valve asks for heat but room stays cold | No central heat demand, air lock or balancing issue | Compare boiler status and radiator flow; seek heating service if needed |
| Room overheats despite low target | Wrong fit, pin travel, local reading error | Check mechanical mounting and independent thermometer |
Total cost: a realistic six-radiator example
To compare an open Zigbee setup with a bridged or Matter ecosystem, separate the price per radiator from the system cost. The table below is an illustrative budget scenario, not a current retailer quotation: actual prices, promotions, adapters and currency vary across the UK and Europe. It excludes professional plumbing or boiler control work when required.
| Illustrative six-radiator budget | Open Zigbee example | Matter / vendor-system example |
|---|---|---|
| Six TRV heads | 6 × £35 = £210 | 6 × £80 = £480 |
| Controller / bridge / network allowance | £45 for supported Zigbee adapter (if needed) | £60 for a compatible border router or vendor bridge (if needed) |
| Optional wall sensors | 3 × £20 = £60 | 3 × £30 = £90 |
| Subtotal before boiler-demand changes | £315 | £630 |
| Missing item that may dominate cost | Boiler/hub integration, balancing or valve-body changes | Boiler/hub integration, balancing or valve-body changes |
If you already own a reliable Zigbee coordinator and room sensors, the incremental open-system cost can be much lower. If you already own a working Wiser or tado X boiler controller, using compatible same-family heads may be economically better than replacing the control architecture. Count the hours you will spend maintaining unsupported quirks, bridges or complex heating automations as well as the cash purchase price.
Be sceptical of universal percentage-savings claims. A TRV cannot repeal heat loss through a wall; it may avoid heating unused rooms, but results depend on insulation, occupancy, weather, thermal balancing and the heat source’s efficiency under part load. For a heat pump, over-aggressive room setbacks can even be counterproductive. Compare measured room temperatures and energy consumption over representative periods rather than extrapolating from a single cold day.
Recommended Home Assistant commissioning approach
A cautious rollout avoids turning an affordable device purchase into an unreliable whole-house heating project. The following checklist concerns the smart head and software only; plumbing, boiler wiring, electrical controls and minimum-flow decisions belong with competent installers.
- Survey the radiators. Photograph the existing valve-body markings, identify adapter types and note whether the present mechanical TRVs work. Do not remove water-bearing components.
- Choose the controller path. For Zigbee, establish ZHA or Zigbee2MQTT on a supported coordinator. For Matter/Thread, prove border-router reachability and a working Matter controller. For Wiser or other vendor systems, confirm hub generation.
- Buy one trial valve. Verify exact model number, supplied adapter, installation clearance, motor calibration and manual adjustment on one suitable radiator.
- Test the visible entities. Confirm target temperature changes, reported temperature, battery, manual overrides and any required frost/child-lock behaviour. Observe how long updates take.
- Test failures deliberately, safely. Disconnect Home Assistant from the network temporarily without touching heating safety circuits. Check whether the valve retains an acceptable local setpoint or vendor schedule and what the boiler controller does.
- Confirm central heating behaviour. With the heating professional’s agreed controls in place, ensure a cold room can call for heat, that the circulation path remains protected and that the boiler does not rapidly cycle.
- Expand in small groups. Add remaining valves only after logging stable room temperature, battery and wireless performance. Keep at least one practical manual fallback and document the system for other occupants.
For measuring how the changes affect actual energy consumption rather than relying on thermostat screenshots, see our Home Assistant energy data versus utility bill guide and per-appliance energy baseline guide. The objective is comfort and verifiable energy performance, not an impressive collection of graph entities.
Room schedules, open-window logic and sensible automation
Start with a simple programme: comfort setpoint when occupied, a modest setback for ordinary absences and a different setting for genuinely unused rooms. Avoid repeatedly raising targets in the hope of “heating faster”: a thermostatic radiator head is not a boiler power regulator. If the radiator valve already has a reliable local schedule, decide whether that schedule or Home Assistant owns the room target so they do not overwrite each other.
Good supervisory logic observes a stable remote room-temperature sensorAliExpress price, filters short-lived readings and makes bounded setpoint changes with minimum dwell times. The heating-system controller, rather than an improvised consumer relay, continues to enforce safe central demand. On an internet or Home Assistant outage, the system should settle to documented, safe local behaviour rather than demand unlimited heat or shut every radiator without protection.
| Situation | Reasonable supervisory response | Avoid |
|---|---|---|
| Short window opening | Use manufacturer-supported window function or time-limited setback | Turning off certified frost protection |
| Bedroom unoccupied during day | Modest, documented setback compatible with room use | Repeated large swings and aggressive reheating |
| Remote sensor offline | Fall back to tested head sensor / existing schedule | Writing stale temperature indefinitely |
| Multiple rooms demand heat | Pass demand to approved system controller if designed for this | Assuming valve demand itself fires boiler |
| Home Assistant offline | Retain vendor/physical thermostat controls and manual override | Making Wi-Fi or MQTT the only frost-protection strategy |
Troubleshooting: why a paired smart TRV still fails to heat
The radiator is cold even though Home Assistant shows “heating”
A TRV climate entity can indicate demand without any heat supply. Check whether the central thermostat or zone controller has enabled heating and whether other radiators are warm. If the heat source is active but one radiator remains cold, possible plumbing issues include air, balancing, flow or a sticking wet-side valve; consult a heating professional rather than issuing more Zigbee commands.
The valve opens and closes repeatedly or the room temperature oscillates
Compare the on-head temperature with an independent sensor. Radiator heat can make the local reading climb quickly, then cool when the valve closes. Use a properly supported remote room sensor or modest calibration, fewer setpoint changes and suitable heating-system controls. Large swings may also reflect radiator oversizing, hydraulic imbalance or unstable central thermostat logic.
The valve pairs but advanced settings are missing
Verify the exact hardware identifier and firmware—not merely the retail name. Check the Zigbee2MQTT device page or current ZHA quirks. For tado X, confirm that you selected Home Assistant Matter rather than the older tado cloud integration. For Aqara W600, verify which protocol mode was selected. Some vendor-specific functions remain available only in their own app or bridge.
Matter commissioning fails even with a valid code
Verify Thread border-router availability, local IPv6/multicast networking and whether another controller already owns the device. If the valve has already been commissioned, use the vendor’s multi-admin/share procedure to generate appropriate pairing credentials. Do not treat Thread network discovery and Matter commissioning as interchangeable operations.
The valve closes fully and the pump keeps running
This is a system-level issue, potentially involving water-flow protection and central controls. Stop experimenting with room automations that could recreate it. Have the boiler/heat-pump installer assess the hydraulic arrangement, any required bypass or buffer, pump overrun and manufacturer limits.
Frequently asked questions
What is the best cheap smart radiator valve for Home Assistant?
For a household already running Zigbee2MQTT, the original SONOFF TRVZB is a sensible low-cost candidate with a clearly documented converter. Compare the final price including adapter and delivery, and test a sample first. “Cheap” is less useful if you need to replace the valve body or pay for a separate ecosystem bridge.
Is Zigbee or Thread better for radiator thermostats?
Neither automatically wins. Zigbee has a mature Home Assistant ecosystem through ZHA and Zigbee2MQTT; Thread/Matter offers an increasingly standardised local control route, but some advanced attributes may be absent. Choose the protocol matching the hardware, network and integration support you actually maintain.
Can Aqara W600 work with Zigbee and Thread at the same time?
No: it supports selecting a Zigbee or Thread operating mode. Aqara documents the protocol-switching process. Verify the selected mode and how to change it before purchasing several valves.
Do I need the tado Bridge X with tado Smart Radiator Thermostat X?
A compatible Thread border router is needed, but it does not have to be a dedicated Bridge X in every setup. The supported heating-system configuration, controller, commissioning process and radio coverage determine the rest. Generic Home Assistant Matter control does not necessarily duplicate every function of the tado app.
Will tado V3+ valves work with tado X?
tado states that X products are not compatible with V3+ and earlier generations. Existing customers should choose the matching generation rather than mix them on the assumption that all “tado” devices belong to one system.
Can a smart radiator valve turn on a boiler by itself?
Normally no. The valve regulates the flow through its radiator. Boiler demand requires a compatible central controller or deliberately engineered integration. Any such design must preserve the manufacturer’s safety and hydraulic requirements.
Can I use a Zigbee TRV with Home Assistant without a proprietary bridge?
Often yes, if that exact model is supported by your Zigbee coordinator and ZHA or Zigbee2MQTT. Confirm support and entities by model number; pairing alone does not prove thermostat control. Some manufacturer features may only be exposed through the original gateway.
Why does the radiator head report a higher temperature than the room?
Its sensor may sit near hot radiator surfaces or behind furniture/curtains. Use an independent thermometer at a representative occupied position. A supported external sensor or sensible local calibration can reduce this bias, but device-specific implementation must be checked.
Can smart TRVs improve a heat pump’s efficiency?
They may avoid unwanted heating in some rooms, but closing many radiators can reduce flow and prompt cycling. A heat-pump installer should determine whether zoning and control changes suit the system, its minimum-flow requirement and weather-compensated operation. No generic savings percentage is justified.
Does a smart TRV support frost protection if Home Assistant is offline?
That depends on its firmware, local schedule, operating mode and central heating system. Test the documented fallback rather than assuming Home Assistant automation will always run. Never rely on an unverified room valve to replace the building’s essential frost-protection design.
Can Home Assistant see how far the radiator valve is open?
Some models and integrations expose valve-position or travel values; others report only temperature setpoint or heating state. The SONOFF Zigbee2MQTT pages document model-specific fields. Treat a “heating” status as a control state, not necessarily a calibrated percentage flow measurement.
Are Matter-enabled Zigbee bridges the same as native Matter TRVs?
No. A bridge translates a vendor or Zigbee device into a Matter representation. A native Matter-over-Thread radiator head joins a Thread network and communicates through Matter directly. Exposed attributes, setup, updates and failure points differ.
Final buying verdict
Most Home Assistant tinkerers who already run Zigbee2MQTT: start by testing a SONOFF TRVZB, or evaluate TRV-ZBT Gen 2 if its newer diagnostic controls justify the extra software-version checks. New mixed-protocol homes: look closely at Aqara W600 but commit to either Zigbee or Thread before scaling. Thread/Matter-first homes: tado X and exact Matter-capable Eve Thermo revisions are worth shortlisting. Households that need a dependable boiler-and-room package: assess complete Drayton Wiser or tado heating architectures instead of treating individual valves as the whole solution.
Before spending money on a large set, ask one question: what happens if the coldest room calls for heat after Home Assistant has stopped working? If you cannot answer that confidently, design and commission the heat-source controls first. A reliable 20°C room is more valuable than twenty impressive climate entities.
Official documentation and further reading
- Home Assistant: Zigbee Home Automation (ZHA) — Zigbee coordinator, climate support and model-specific quirks.
- Home Assistant: Matter — Matter setup, commissioning, limitations and local infrastructure.
- Home Assistant: Thread — border routers and Thread network management.
- Home Assistant: tado integration — cloud integration and explicit exclusion of tado X.
- SONOFF: original TRVZB product — original Zigbee model and valve fit.
- SONOFF: TRV-ZBT Gen 2 — Gen 2 model, Zigbee2MQTT requirement and ZHA caveat.
- Zigbee2MQTT: SONOFF TRVZB — original model’s published entities.
- Zigbee2MQTT: SONOFF TRV-ZBT — Gen 2 published entities and settings.
- Aqara: Radiator Thermostat E1 specifications — original E1 radio and mechanical fit.
- Aqara: Radiator Thermostat W600 — radio choice, supported adapters and specification.
- Aqara: switching protocol modes — vendor guidance for dual-protocol devices.
- tado: X compatibility — X versus earlier product generations.
- tado: Smart Radiator Thermostat X Matter pairing — commissioning and multi-admin access.
- Eve: Thermo Matter/Thread product — verify exact generation and adapters.
- Danfoss: Ally support — Zigbee ecosystem and gateway.
- Drayton: Wiser second-generation radiator thermostat — revised head and platform compatibility.
- Community: Wiser Home Assistant integration — locally connected community integration; verify current release requirements.
Editorial note (16 October 2026): This comparison is based on published documentation and integration support rather than a laboratory endurance test of every valve. Hardware generations, firmware, Home Assistant support, subscription policies, regional prices and feature exposure change. Confirm the exact device model, compatibility matrix and supplied adapters before buying. Smart TRVs are not substitutes for certified boiler controls or hydraulic safety provisions; use a qualified heating professional for wet-system, boiler, pump and electrical alterations. Budget figures are illustrative.