Quick Summary (TL;DR)
The best thermostat for Home Assistant depends first on your heating equipment, then on how its data reaches Home Assistant. For a UK/EU boiler or hydronic heating system, Plugwise Anna/Adam is a particularly clear local-network option with an official Home Assistant integration. tado° X offers local Matter-over-Thread thermostat functions, although advanced vendor-app services and boiler compatibility must be checked separately. Bosch Smart Home Controller is another officially supported local hub for compatible Bosch room thermostats. Drayton Wiser offers substantial local integration through a community-maintained Home Assistant project, not an official core integration.
- Local-first shortlist: Plugwise Anna/Adam; Bosch Smart Home Controller plus compatible thermostats; tado° X through Matter; and, with greater maintenance responsibility, Drayton Wiser through its custom integration.
- Established cloud choices: tado° V3+ and earlier, Netatmo, Google Nest and Honeywell evohome. Their Home Assistant integrations are not equivalent to a locally controlled thermostat.
- Most important compatibility check: a UK 230 V switched-live boiler circuit, a volt-free relay, an OpenTherm bus, a proprietary heat-pump controller and a North American 24 V HVAC system are not interchangeable.
- Best reliability rule: keep the manufacturer-approved heating safety functions and an independent heating schedule or local thermostat fallback wherever possible. Home Assistant should provide supervision rather than being the sole frost-protection system.
For a new installation, choose your thermostat only after identifying the heating appliance model, its permitted control interface, whether you need domestic hot-water or room-by-room control, and what happens when broadband or Home Assistant fails. Do not buy solely because the box says “Zigbee”, “Matter”, “Wi-Fi” or “works with Alexa”.
The real question: which device is actually controlling the heat?
A smart thermostat can be a stand-alone controller connected to a boiler, a battery-powered wireless temperature sensor speaking to a receiver, one zone in a multi-room hydronic system, or merely an interface that asks a cloud service to change a setpoint. Those architectures may produce an identical Home Assistant climate card. Their failure modes are completely different.
A proper buyer comparison therefore separates three links: (1) room thermostat to boiler or wiring centre; (2) thermostat to its local hub or radio mesh; and (3) hub to Home Assistant, directly or through a vendor cloud. Cloud-free Home Assistant communication does not establish that every heating function is local or that the boiler will keep running if the hub stops.
| Control path | Example | Internet required for Home Assistant control? | Main caveat |
|---|---|---|---|
| Thermostat → local LAN hub → HA | Plugwise Anna / Adam | No, for supported local entities | Controller and heat-source compatibility still matter |
| Matter thermostat → Thread network → HA | tado° X | No, for exposed Matter controls | Advanced app features and firmware may still need vendor connectivity |
| Heating hub → community local API → HA | Drayton Wiser via HACS | No, for compatible hub and custom integration | Not an official core integration; maintain it after upgrades |
| Vendor cloud → HA | tado° V3+, Netatmo, Nest | Yes, for their referenced HA integrations | API quotas, authentication and vendor availability |
| Zigbee / Z-Wave thermostat → coordinator → HA | Specific verified direct-pair models | No, after local pairing | Radio protocol does not guarantee boiler-receiver or entity support |
Our comparison: smart thermostat systems worth considering in 2026
| System / family | Best application | Home Assistant path | Integration status | Check before buying |
|---|---|---|---|---|
| Plugwise Anna or Adam | Boiler/OpenTherm heating, Adam multi-zone | Direct local gateway integration | Official HA integration | Country availability, supported boiler interface, zoning hardware |
| tado° Smart Thermostat X | Modern UK/EU relay or supported OpenTherm | Matter over Thread | Official Matter, limited exposed feature set | Thread border router, exact receiver, X generation only |
| Bosch Smart Home Controller | Bosch smart heating zones and wider ecosystem | Local controller push | Official HA integration | Compatible controller revision, room thermostat and heating actuator |
| Drayton Wiser | UK boiler/radiator and hot-water zoning | Local Wiser Hub API | Community HACS project | Hub/kit revision, supported devices, HACS maintenance |
| Heatmiser Neo | Wired and underfloor multi-zone heating | NeoHub local API on supported hubs | Community integration, model-dependent | NeoHub firmware, legacy API, Wi-Fi NeoStat exclusions |
| tado° V3+ and older | Existing tado homes retaining hardware | Vendor cloud API | Official HA integration | 2026 API daily quota; different ecosystem from X |
| Netatmo | Simple boiler and room controls | Netatmo cloud | Official HA integration | Internet/account dependence, relay compatibility |
| Google Nest | Supported pre-existing Nest installations | Google SDM cloud | Official HA integration | Region/model, SDM setup and fee, wiring |
| Honeywell evohome | UK/EU multi-zone installations | Total Connect Comfort cloud | Official HA integration | Zones/receiver selection, limited schedules through HA |
1. Plugwise Anna and Adam: a strong local-first heating choice
Why it ranks highly: Home Assistant includes a documented Plugwise integration that discovers supported local gateways and reads or changes climate entities without relying on the Plugwise cloud for those LAN interactions. Anna is an individual smart thermostat; Adam is a gateway for a larger zoned installation with compatible Lisa, Tom and other devices. The official integration explicitly covers on/off and OpenTherm configurations, depending on the hardware.
This is attractive if you want a thermostat with its own legitimate heating-control capability while Home Assistant handles higher-level occupancy and monitoring. With Adam, each configured zone can appear separately, including useful states such as room temperature, setpoint and, where available, heating-related information. It is an especially good architecture for an installation where you are willing to specify one supported hub and all its room devices as a system.
Limitations: availability and installer familiarity differ by country. Not every Plugwise sensor or sensor attribute exists on every installation, and Home Assistant does not create or edit all thermostat schedules. Plugwise documents creating schedules through its app or local web interface and selecting them via Home Assistant. Confirm the precise boiler connection, hot-water arrangement and gateway support before committing to a purchase.
2. tado° X: local Matter control with an important feature distinction
The tado° X range uses Matter over Thread. Home Assistant’s official Matter integration can control device functions exposed through the Matter specification over the local network, provided the Thread network and Matter controller are configured correctly. This means a local target-temperature change need not make a round-trip through tado’s cloud. For a home already using Matter/Thread, the appeal is a modern, standardised integration rather than a proprietary cloud thermostat API.
However, local thermostat control is not the same as feature parity with the vendor app. Some schedules, commissioning features, firmware updates, energy insights, geofencing and optional paid functionality may depend on tado services or be absent from Home Assistant’s Matter entities. The vendor says X supports relay and OpenTherm heating interfaces in supported combinations, while warning that X is not compatible with its older V3+ ecosystem. In October 2026 the UK product catalogue also includes second-generation X options; check the specific bundle and receiver rather than assuming all kits have identical capabilities.
For wireless installations, the control of a boiler may reside in a matching wireless receiver, not the wall-mounted wireless room sensor. If you have stored hot water, multiple central-heating zones or a boiler using eBUS or another proprietary modulation bus, use the vendor compatibility checker and an installer review. Being Matter-compatible does not prove that the thermostat can modulate your specific boiler.
- Choose it if: you want local setpoint control via Matter and have a verified tado X compatible heating configuration.
- Think twice if: you already own V3+ devices, demand every app feature in Home Assistant or rely on a non-OpenTherm proprietary boiler bus.
- Budget for: the right wired/wireless kit, Thread border router if needed, room sensors/TRVs, and professional commissioning where appropriate.
3. Bosch Smart Home Controller: official local hub integration
The official Bosch SHC integration uses a local connection to a supported Bosch Smart Home Controller and exposes compatible room thermostats and other Bosch smart-home devices. The integration uses a controller pairing process and pushes most state changes promptly to Home Assistant. Bosch is therefore an option for buyers who prefer a mainstream manufacturer hub but do not want cloud availability to determine whether Home Assistant can change a supported local room setpoint.
Do not assume the Bosch room thermostat directly switches your boiler or that the controller alone replaces a properly installed heat-demand relay. Heating depends on the specific actuator, radiator valve, underfloor circuit or boiler interface that you install alongside the room sensor. This ecosystem is more compelling when you plan Bosch door contacts, radiator controls and room-temperature zoning together. Check the exact controller generation and thermostat compatibility for the local market.
4. Drayton Wiser: capable UK heating with community-maintained local access
Drayton Wiser is a practical UK option because the manufacturer’s system can handle heating schedules, wireless room thermostats, smart radiator controls and suitable hot-water arrangements without requiring Home Assistant to be present for every decision. A widely used community Home Assistant integration communicates locally with compatible Wiser hubs and is distributed through HACS; the project is not an official Home Assistant core integration. Current development covers multiple revisions and devices, but you must consult its actual compatibility list and release notes.
A local HACS integration is a meaningful advantage over a cloud-only bridge, yet it brings an owner-maintenance responsibility. Major Home Assistant updates, replacement hubs, or firmware changes can require integration updates. Configure sensible hub-side schedules first, monitor the system for a few weeks, and make Home Assistant automations modest supervisory overlays. If the project stopped tomorrow, would the household still be able to set a temperature from the wall thermostat and heat the rooms? That is the relevant reliability test.
5. Heatmiser Neo: useful for zoned and underfloor systems, but verify the NeoHub
Heatmiser NeoStat plus a compatible NeoHub is a serious candidate for wired hydronic zones or underfloor heating manifolds. Some NeoHub versions expose a local LAN API, and a maintained community project, Heatmiser-for-home-assistant, supports specified NeoHub/Neo products. The project is explicitly community-maintained and notes that NeoStat WiFi devices cannot use the NeoHub-based integration. Older examples of the NeoHub API require enabling an optional legacy interface; firmware capabilities must be confirmed rather than assumed.
Crucially, Home Assistant’s separate legacy “Heatmiser” integration documents wired DT/PRT hardware through a serial interface; it must not be taken as evidence that every NeoHub and NeoStat works through an official core integration. If you are specifying a complete new manifold wiring centre with NeoStats, choose the hardware and approved installer design first, then test the exact hub and custom integration version before relying on additional Home Assistant automation.
6. Cloud choices: tado° V3+, Netatmo, Nest and evohome
Cloud heating systems are not automatically bad products. They may offer polished apps, accessible installers, mature zoning, geofencing and robust native schedules. The issue is whether you want Home Assistant to be able to read and control the system when your internet connection, an account login or a vendor API fails. Distinguish that from whether the thermostat and its own local receiver continue operating in that situation.
tado° V3+ and earlier
Home Assistant’s tado integration connects to the vendor’s internet service, not a local thermostat API. The official documentation warns that from 1 January 2026 the API became heavily rate-limited, with daily quotas dependent on subscription type; exceeding a quota can prevent new data and authentication until the reset. That materially weakens the case for buying old-generation tado solely for dense Home Assistant logging or minute-by-minute automation. Existing V3+ owners may sensibly keep the vendor schedules while using Home Assistant sparingly, but buying V3+ with the expectation that it will upgrade seamlessly to X would be a mistake.
Netatmo
The Netatmo integration explicitly requires an active internet connection and Netatmo account to communicate with the cloud service. It can offer climate entities and thermostat setpoint control with supported equipment. Consider it for conventional boiler setups if you value the official app and integration convenience, but not if a purely local Home Assistant connection is a firm requirement.
Google Nest
Home Assistant’s Google Nest integration uses the Smart Device Management API and Google Cloud Pub/Sub. It has supported thermostat climate entities, but the SDM setup involves Google authorisation and a one-time device-access fee described in the documentation. Nest variants differ substantially by region and generations; a US 24 V thermostat must not be purchased as a presumed replacement for a UK switched-live controller or boiler bus.
Honeywell evohome
The European Honeywell Total Connect Comfort integration is cloud polling and can expose up to twelve zones and some domestic hot-water capabilities for supported systems. Home Assistant can change zone setpoints and overrides, but cannot manage the complete native schedule. Existing evohome installations may be best retained as designed; their Home Assistant integration is useful for display and supplementary automations, not as a promise of local control.
7. Zigbee, Z-Wave and HomeKit thermostat options: local does not mean universal
You can obtain local climate entities using Zigbee Home Automation (ZHA), Z-Wave JS, a compatible Matter controller or Home Assistant’s HomeKit Device integration. But the radio protocol describes communication, not whether a device has the correct certified receiver, heating interface and Home Assistant feature mapping. A Zigbee temperature puck is not an autonomous boiler thermostat. A Zigbee TRV can close a radiator while the boiler continues to run unless heat demand is coordinated by an appropriate controller.
| Local protocol | What Home Assistant needs | Strength | Common problem |
|---|---|---|---|
| Matter over Thread | Matter server and functional Thread border-router network | Standards-based local control of exposed attributes | Vendor-only controls unavailable or incomplete |
| Zigbee | Compatible coordinator with ZHA or Zigbee2MQTT | Low-power room sensors and many supported TRVs | Heating demand and receiver compatibility differ by model |
| Z-Wave | Regional-frequency radio and Z-Wave JS | Direct local thermostat climate/control on supported devices | US 24 V product assumptions do not transfer to UK/EU mains wiring |
| HomeKit Device | Compatible unpaired HomeKit accessory | Local pairing without needing Apple hardware for some IP accessories | Models may expose fewer controls than the vendor app |
| Proprietary LAN hub | Vendor gateway plus supported local integration | Hub can maintain its own native schedule | Need correct hardware generation and supported API |
If you find a supposedly “universal Zigbee room thermostat”, look up the exact model number in the relevant Home Assistant/ZHA or Zigbee2MQTT compatibility information. Confirm whether it exposes a real climate entity, controls a supported relay or zone controller and can keep heating safely if the Home Assistant host is unavailable. For heat pumps, manufacturer-approved weather compensation often matters more than aggressive room-by-room setpoint automation.
Heating-system compatibility: what you must check before ordering
| Installed system | What the controller may need | Why a generic thermostat may fail | Recommended verification |
|---|---|---|---|
| UK gas combi boiler | Correct relay, switched-live or compatible digital thermostat | Wrong voltage or loss of modulation | Exact boiler model, manual and installed receiver |
| System boiler plus hot-water cylinder | One/two heating channels and independent hot-water programming | Room thermostat does not necessarily control cylinder | S-plan/Y-plan/other control layout confirmed by engineer |
| OpenTherm boiler | Supported OpenTherm controller and documented wiring | Relay controller may downgrade to on/off | Boiler and thermostat support OpenTherm in your country |
| eBUS/proprietary digital boiler | Approved proprietary controller or vendor gateway | OpenTherm support cannot be inferred | Boiler bus protocol and official compatible accessory |
| Air-to-water heat pump | Manufacturer-approved room influence, sensor or demand interface | Hard on/off cycling can compromise efficiency | Installer-approved control hierarchy and weather compensation |
| Hydronic underfloor heating | Compatible wiring centre, manifold zone actuators, floor sensor if required | Wrong voltage/actuator type or unsafe floor temperature | Manifold controller/actuator specification, floor limits |
| North American 24 V HVAC | Compatible 24 V HVAC thermostat and wiring | Regional control voltages and terminals differ | Specific country/HVAC model, C-wire and staging checks |
Do not remove an existing boiler or heat-pump safety thermostat, over-temperature limit, flow interlock or frost safeguard to make a smart-home integration work. Where a manufacturer requires a specific thermostat, the correct answer may be to retain it and integrate through an approved data interface instead of replacing it. For context, our OpenTherm Gateway with ESP32 and Home Assistant tutorial explores a different, specialised integration route; it is not a general endorsement of replacing every boiler controller.
Local control versus offline heating: five separate failure scenarios
| Failure | Local Matter/Plugwise/Bosch | Cloud API integration | What you should verify physically |
|---|---|---|---|
| Internet disconnected | HA may continue if LAN/Thread is healthy | HA read/control may stop | Thermostat still holds an appropriate schedule |
| Home Assistant restarted | HA unavailable during restart | HA unavailable during restart | Wall control and manufacturer hub still operate |
| Wi-Fi or LAN switch failed | Gateway-to-HA control may stop | Cloud connection may stop too | Receiver-to-heating appliance has local fallback |
| Vendor cloud outage | Core local commands may continue | API commands may fail | Native thermostat and relay are autonomous |
| Receiver / thermostat battery failure | Local integration alone cannot fix missing device | Cloud integration alone cannot fix missing device | Fault indication and safe heating strategy |
For a house that must avoid frozen pipes, do not interpret a climate card showing “heat” as proof the burner, circulation pump or heat-pump compressor is working. Verify room temperatures, demand states, source operating state and actual energy use where available. Protecting the home requires the installer’s approved heating and frost-protection design; Home Assistant alerts are a useful addition, not a sole safety layer.
What a Home Assistant climate entity can and cannot tell you
The Home Assistant climate model typically offers target temperature, current temperature, HVAC mode, preset and perhaps an operating-state attribute. Those values depend on the integration. “Heating” could mean that a room thermostat is requesting heat; it does not necessarily mean the boiler is burning gas or that a heat pump is delivering thermal energy. A displayed setpoint can be stale if the cloud API no longer updates or a hub loses contact with its sensor.
- Useful readings: room temperature, target temperature, heating demand, thermostat mode, battery status, window/door sensors, last update and individual zone state.
- More useful when available: boiler modulation, compressor status, heating supply/return temperature, circulating pump state, hot-water demand and an independently measured heating electricity meter.
- Not guaranteed: scheduling API, weather compensation, exact boiler output, flow temperature setpoint, automatic fault reset or full native app equivalence.
- Verification: at commissioning, change one setpoint through the supported path and confirm the room controller/receiver and heating system respond as designed, then return to the intended schedule.
Buying by installation type: which thermostat would we choose?
| Household scenario | Practical shortlist | Main purchase check |
|---|---|---|
| Single UK/EU boiler, willing to use local gateway | Plugwise Anna; tado X if Matter setup already planned | Confirm relay versus OpenTherm and installer support |
| Existing Drayton Wiser home, expanding to Home Assistant | Keep Wiser, evaluate community local integration | Test compatible hub and fallback schedules |
| New hydronic underfloor heating manifold | Installer-specified Heatmiser Neo or supported zone controller | Actuator voltage, floor probes, relay/heat-demand design |
| Whole-home Bosch smart sensors and room controls | Bosch Smart Home Controller with compatible thermostats | Check complete actuator/boiler control chain |
| Existing tado V3+ system | Keep native schedules, throttle HA polling or evaluate X migration as a full replacement | V3+ cannot join an X system; cloud API quota |
| Existing Netatmo or evohome system | Retain installed controls, add official cloud integration for supervisory viewing | Accept loss of HA control on cloud outage |
| Heat pump with approved proprietary weather compensation | Keep the heat-pump controller; use documented monitoring interface | Do not replace digital control with generic on/off demand |
| US-style 24 V furnace / HVAC | Region-correct Z-Wave or HomeKit-compatible thermostat | Compatibility with HVAC stages, terminals and safety logic |
If the manufacturer’s heating controller already supplies good weather-compensation, hot-water and frost logic, retaining it is often a better engineering decision than installing a prettier wall thermostat that reduces the plant to an on/off relay. The right Home Assistant integration may therefore be the heat pump’s own monitoring gateway, not a replacement thermostat.
Budget and total-cost comparison: count the entire control chain
Quoted thermostat prices are often misleading because a “smart thermostat” product listing may be just the room device. The installed heating system may also require a receiver, hub, Thread border router, wiring-centre changes, TRVs, manifold actuators, temperature sensors and professional labour. Currency, taxes, bundles and installation prices change, so the following is a transparent planning model rather than a scraped retail price list.
| Cost item | Typical scope | When the cost applies |
|---|---|---|
| Central thermostat or starter kit | Single compatible room controller and possibly receiver | All installations |
| Vendor hub / gateway | Hub that translates local heating/radio traffic | Plugwise Adam, Bosch SHC, Wiser/Neo, depending on kit |
| Thread border router / Zigbee coordinator | Matter Thread or Zigbee network hardware | Only when not already provided |
| Smart TRVs / extra room units | One or more per zone as supported | Multi-room radiator control |
| Zone controller / manifold work | Hydronic actuators, certified wiring centre, sensors | Underfloor or multi-zone central heating |
| Installer labour | Survey, wiring, commissioning, safety checks | Varies substantially with retrofit complexity |
| Cloud subscription / API access | Optional automation, analytics or vendor features | Vendor- and subscription-specific; check terms |
| Owner maintenance | Firmware, HACS, battery replacement, backup testing | All systems; more hands-on with community integrations |
Illustrative five-year cost model
Compare a hypothetical £230 single-zone local starter kit plus £170 installation with a hypothetical £180 cloud starter kit plus the same £170 installation and a £35/year optional feature subscription. These are deliberately illustrative assumptions, not verified quotes or claims that a particular brand charges these amounts. Five-year nominal costs are £400 for the first example and £525 for the second. But it would be wrong to declare local hardware £125 cheaper without also comparing the included receiver, zones, spare parts, integration support and whether the optional cloud feature is truly needed.
If the only reason for upgrading is to save energy, establish a realistic baseline first. A thermostatic system cannot guarantee a universal percentage saving. Insulation, occupancy, boiler efficiency, how the household currently heats and whether unnecessary heating hours are reduced all influence the outcome. A new thermostat can improve comfort or observability even when its fuel savings are limited. Our guide to verifying Home Assistant energy data against your utility bill is a useful method for checking claimed reductions using comparable time windows.
Heating schedules, occupancy and Home Assistant automations
An unreliable heating setup usually has two controllers trying to set the same schedule: the thermostat’s native schedule returns to 20°C just after Home Assistant sets 17°C, or a separate phone app starts a preheat routine in conflict with a manually requested override. Decide which layer owns the authoritative weekly schedule and which is allowed only temporary changes.
One sensible hierarchy is: the certified appliance and manufacturer receiver maintain frost protection and mandatory operating limits; the local thermostat or heating hub owns the baseline day/night schedule; Home Assistant issues occasional occupancy-based setpoint overrides with a limited duration. That architecture remains intelligible after a network fault. It also means household members can use the thermostat even if Home Assistant has been rebooted for an update.
- Presence: avoid lowering occupied-zone temperatures based on a single unreliable phone tracker. Combine signals and use a grace period.
- Open windows: if compatible with the heating controller, a confirmed open-window state can temporarily reduce that zone’s demand. Do not disable central frost protection.
- Humidity: temperature setbacks must not make damp or condensation problems worse; check the actual building.
- Heat pumps: favour small, deliberate setpoint adjustments rather than repeated deep setbacks and rapid on/off changes.
- Holidays: ensure someone can restore heating locally and that an autonomous frost strategy remains active.
- Automation timing: respect vendor limits, local hysteresis and minimum compressor runtime; do not poll vendor cloud services more often than documented.
A safe automation pattern without custom boiler wiring
Use Home Assistant’s Schedule helper to choose an intended comfort target and an automation to call climate.set_temperature on an existing, supported thermostat entity. Keep the native thermostat program available as the fallback and test how a temporary setpoint interacts with its schedule. The example below is conceptual; it does not control a relay or override appliance safety protections.
alias: Evening comfort request (example)
triggers:
- trigger: time
at: "17:30:00"
conditions:
- condition: state
entity_id: binary_sensor.house_occupied
state: "on"
actions:
- action: climate.set_temperature
target:
entity_id: climate.living_room
data:
temperature: 20
mode: singleReplace the entity IDs only with actual supported entities after checking which setpoint changes persist, how manual overrides expire and whether native scheduling resumes. This example is intentionally limited to a normal climate-entity request. A reliable implementation also needs a normal fallback state, sensible occupancy logic and a way for occupants to override the automation.
What to do when Home Assistant goes offline
Test failures deliberately during commissioning—not during freezing weather or without a qualified person responsible for plant operation. A system that continues heating with appropriate local control after Home Assistant and WAN have been disconnected is much easier to recommend than one that needs a cloud login to resume heating.
- Identify which wall controller, receiver and heating programme continue working without Home Assistant.
- Disable internet access temporarily during an appropriate test and verify whether Home Assistant can still change a local thermostat setpoint. Restore connectivity afterwards.
- Check whether the thermostat retains its last schedule after the vendor cloud becomes unavailable, rather than assuming all cloud-backed equipment stops heating.
- Check hub power-loss behaviour, low-battery warnings, default setpoint, freeze protection and manual override procedure with the installer.
- Back up the Home Assistant configuration and write down the method for restoring normal, manufacturer-native heating without relying on dashboards.
Integration setup checklist before purchasing
- System details: manufacturer/model of boiler or heat pump; present thermostat, receiver and wiring-centre models; hot-water storage, zone count and actuator types.
- Electrical/control interface: documented dry-contact or switched-live requirements, voltage, boiler modulation protocol, approved gateway and terminal limitations.
- Regional variant: UK/EU 230 V controls versus North American 24 V HVAC, plug and radio-frequency differences, installer regulations.
- Network: local LAN IP, Wi-Fi coverage, Thread border router, Zigbee coordinator, multicast/IPv6 requirements for Matter and availability of Ethernet.
- Integration: Home Assistant official versus HACS, native versus cloud API, actual climate attributes, schedules and known rate limits.
- Fallback: physical thermostat controls, autonomous schedule, frost and fault protection, cloud outage and HA outage behaviour.
- Lifecycle: firmware update mechanism, spares, replacement battery cost, subscriptions and the available installer warranty.
Troubleshooting: what common symptoms really mean
| Symptom | Likely explanation | Useful diagnostic action |
|---|---|---|
| HA shows setpoint but room stays cold | Boiler receiver or heat-source call missing; cloud state stale | Check local wall controller, receiver demand and appliance faults |
| Room warms after schedule should end | Native schedule and HA automation are competing | Choose one schedule owner and inspect override expiry |
| Matter thermostat intermittently unavailable | Thread border router, IPv6 or mesh coverage issue | Use official Matter diagnostics and network checks |
| tado V3+ suddenly stops updating | Cloud API limit or authentication issue | Inspect HA integration logs and vendor quota guidance |
| Wiser HACS entity breaks after update | Custom integration version mismatch or API change | Check maintainer release notes and restore native hub schedules |
| Heatmiser Neo WiFi cannot pair through NeoHub integration | Wi-Fi model not supported by NeoHub integration | Verify exact model and supported integration, do not force pairing |
| One zone heats all rooms | Hydronic zoning/wiring-centre and source demand not coordinated | Installer checks zone valve/actuator/control architecture |
| Heat pump cycles too frequently | Thermostat strategy unsuitable for the heat-pump controls | Return to installer-approved weather-compensated strategy |
Frequently asked questions
What is the best fully local thermostat for Home Assistant in the UK?
There is no universal winner because boiler and hot-water arrangements differ. For supported equipment, Plugwise Anna/Adam has an official local Home Assistant integration. tado X gives local Matter control of exposed thermostat attributes; Drayton Wiser can use a community local integration. Buy only after confirming the physical heating interface.
Does a Matter thermostat work without internet?
Supported Matter commands can travel locally, including over Thread when the controller and border router are healthy. Vendor schedules, app functionality, account operations, updates or extra features may still need internet and are not necessarily visible in Home Assistant.
Is tado X the same as tado V3+ in Home Assistant?
No. Home Assistant documents legacy tado devices through its cloud integration, while tado X devices belong to the Matter integration. The X and V3+ product lines are not compatible with one another as a shared heating system.
Can Home Assistant replace my boiler thermostat with a smart relay?
The Generic Thermostat helper can operate an appropriate switch, but that is not equivalent to a manufacturer-approved boiler or heat-pump thermostat. Certified switching arrangements, voltage isolation, safety interlocks, minimum run times and frost protection must be assessed by the heating/electrical professional.
Will heating stop when my broadband goes down?
Not necessarily. Many thermostats, receivers and hubs continue their internal schedules without internet even when Home Assistant cloud integration stops updating. Verify the behaviour of the exact installed system; do not assume either continued heat or total shutdown.
Do smart thermostats automatically reduce gas bills by a fixed percentage?
No. Savings depend on existing schedules, building heat loss, occupancy, setpoints, outdoor conditions and the heating source. Treat manufacturer percentage claims as context-specific and check bills or calibrated measurements over comparable periods.
Should I replace a heat-pump controller with a room thermostat?
Usually not without an approved design. Many heat pumps depend on weather compensation, flow temperatures, compressor run-time protections and manufacturer control logic. Consider an official integration or external meter before replacing their native controller.
Can I mix Zigbee TRVs with any Zigbee boiler receiver?
No. Device pairing and command compatibility do not guarantee coordinated heat demand or proper boiler control. Verify the specific hub, radiator valves and certified heat-demand receiver as a complete system.
What is the difference between a local integration and local scheduling?
A local integration means Home Assistant talks directly to the device or gateway on your network. Local scheduling means the thermostat/receiver executes its programme without Home Assistant or internet. A robust heating system benefits from both.
Is Heatmiser Neo supported by the official Heatmiser Home Assistant integration?
Do not assume so. Home Assistant’s legacy Heatmiser integration documents DT/PRT hardware over a serial-style interface. NeoHub/NeoStat uses separate community projects and device/version-dependent APIs. NeoStat WiFi is not supported by at least one NeoHub-based integration.
Do I need a Zigbee dongle for tado X?
No; tado X uses Matter over Thread, not Zigbee. You need an appropriate Matter controller and Thread border router; check whether your chosen tado kit or existing infrastructure provides it.
Can I control my thermostat with Home Assistant but keep the vendor app?
Often yes, but the answer and available controls depend on the product. Check dual-controller behaviour, schedules and overrides before commissioning, and avoid competing temperature automations.
Recommended buying decision
If local Home Assistant reliability is your priority, start with Plugwise Anna/Adam for supported on/off or OpenTherm heating; consider tado X for Matter/Thread users who accept that exposed Matter attributes may not equal the full tado app; and consider Bosch for a complete compatible smart-home heating ecosystem. Drayton Wiser is a strong retrofit option if you are happy maintaining its community integration. Existing Heatmiser Neo installations can be worth integrating after checking the specific hub firmware and API.
If you prioritise an installed, supported vendor heating system above local HA integration, Netatmo, Nest, evohome and older tado hardware remain relevant choices in supported regions. Just budget for their cloud dependencies and avoid making Home Assistant the only path to comfortable or safe heating. The installer-approved heating architecture matters more than a long list of app features.
For deeper context, read our whole-home energy monitoring without the cloud, OpenTherm Gateway with ESP32 and Home Assistant and Home Assistant Energy Dashboard entity guide. These cover related connectivity and monitoring concepts without duplicating this thermostat buying comparison.
Official documentation and technical references
- Home Assistant: Plugwise local gateway integration — supported Adam/Anna hardware, local controls, schedule and polling limitations.
- Home Assistant: Matter integration — local Matter/Thread connectivity and controller requirements.
- Home Assistant: Bosch Smart Home Controller — local integration and supported device types.
- Home Assistant: tado — V3+/older cloud integration, X exclusion and January 2026 API limits.
- tado: UK Smart Thermostat X product guidance — relay/OpenTherm configurations and Matter/Thread.
- tado: product compatibility — generation limits and boiler checks.
- Wiser community Home Assistant integration — local hub API, HACS and supported device information.
- Heatmiser Neo community project — supported NeoHub approach and exclusions.
- Home Assistant: legacy Heatmiser integration — separate RS232/RS485 Heatmiser device family.
- Home Assistant: Netatmo cloud integration — internet and account requirements.
- Home Assistant: Google Nest SDM — supported thermostats, cloud and setup fee.
- Home Assistant: Honeywell evohome Europe — cloud integration and schedule limits.
- Home Assistant: Zigbee Home Automation — device support varies.
- Home Assistant: HomeKit Device integration — local thermostat accessory support.
- Home Assistant: Generic Thermostat — software thermostat based on a sensor and switch.
Editorial and safety note (October 2026): Product generations, vendor APIs, cloud rate limits, Matter features, firmware, subscriptions and market availability can change. This guide distinguishes documented integration capabilities from model-dependent features and estimates. Never alter boiler, gas, mains-voltage, heat-pump, over-temperature or frost-protection wiring on the basis of a smart-home tutorial. Have appropriately qualified heating and electrical professionals verify compatibility and commission the system according to local rules and current manufacturer instructions. Illustrative prices are not retail quotations.