You should combine your Thread networks (but I believe that’s not possible with the Tado X Bridges, AFAIK those work only with the Tado app).
With just the wireless sensor and wireless receiver, I think those function using Wifi? I have an OpenThread Border Router setup using a smlight slzb-06 USB adapter but it doesn’t seem to be used. I have a single version of what is shown in the right image.
To setup mine, I bridged a wifi AP onto my wired LAN and then it’s just IPv6 unrouted traffic between the device and HA. I couldn’t get Matter routing over subnets however, so I gave up on that. Matter assumes that everything is in 1 broadcast domain which is rather annoying but it’s designed to be “simple” I guess. Would rather it had a local API endpoint using a routeable address.
To get it working:
- Tado wireless thermostat linked to Tado wireless receiver and visible in Tado App
- put HA, your phone and Tado X devices on the same L2 broadcast domain
- ensure nothing is blocking broadcast IPv6 traffic on this network
- disable any VPN or services that might affect routing in the phone
- start the Matter pairing from the Tado App
- pick the HomeAssistant Android app on your phone as the Matter target
- ensure your connection to HA in the HA App is using an IP in the same broadcast domain if you have multi-homed HA
- after starting the pairing in the Tado Android app a Matter device will appear in HA like this:
I have an OpenThread border router, but HAOS kept losing the USB device on restart so I’ve disabled OpenThread and it hasn’t affected this Matter connection at all.
After this rigmarole next boiler upgrade I will go OpenTherm and just use an ESP32 to drive the heating. Matter is just getting in the way. If anyone from Tado is reading - give us a local API endpoint, Matter integration is so much worse than just having a local REST API via HTTPS on a standard routable IP address.
Hey, I’m using the Tado X Smart Radiator Thermostat only through Home Assistant via Matter/Thread (using HA’s own Thread Border Router). I don’t have the Tado X Hub, and I’m not using the Tado app except for checking the device info.
My thermostat is currently on firmware 216.1, and I’m wondering if there is any way to update the firmware:
- via the Home Assistant Matter Server,
- via Matter OTA,
- or through any other method that doesn’t require buying the Tado X Hub.
Does anyone know if OTA updates are possible in this setup, or if the Tado X Hub is strictly required for firmware updates on the X-series devices?
I don’t think you need the Tado X bridge, but you likely do need to use the Tado app.
Does anyone know what is the name of the parameter On/Off? E.g. I read the current temperature using a template {{ state_attr(‘climate.kitchen_head’, ‘current_temperature’)|float }} where “current_temperature” is the name of the parameter being transmitted. What’s the name for the “heat” and “off” parameter?
Would just be {{states('climate.DEVICEIDHERE')}} for template purposes. Thermostats seem to typically report “heat” and “off” (and whatever else they do if they do cool too) as their state.
If you enable developer tools you can get a list of states and state attributes for all entities. I think, although I’ve had it enabled for eons now so can’t remember how I did it, it’s under your username; Change the order and hide items from the side bar; click the eye next to Developer Tools.
Under states it lists everything and their attributes. State is just {{states('CLASS.ID')}}, state attributes are {{state_attr('CLASS.ID','ATTRIBUTE')}}. You can do more with them than that within the double curly brackets of course, but that’s basically how you pull the info.
I have the same configuration, but it seems that a matter network without a “real” border router is draining the batteries of the thermostat in like 2 weeks. which is far from ideal.
Did you guys also experienced this?
I’ve been using the thermostat X and 4 radiator valves for about a year now, and other than some issues at the beginning they’ve been pretty solid for the most part. A few days ago though, all 5 devices started showing as unavailable in Home Assistant. They all still show up in my router admin panel and say connected in the Tado app. IIRC, I set them up by first adding them to the Tado app then sharing them with HA using the transfer codes. Is this a known issue? I’ve tried restarting the main unit connected to my boiler (which acts as the border router) and restarting my HA host but that hasn’t solved the issue.
Had mine a month and haven’t noticed it yet? Maybe I got lucky. Seems to use wifi to the boiler control unit then the keypad/display connects to that boiler control unit over whatever it uses.
I have Tado X smart thermostat (no Tado Bridge X) connected to home Thread network. I have 3 border routers (Home Assistant ZBT-1, Google Nest2 and Aqara M3). My battery drained from full to empty within about a month of usage (vendor declares 1 year of use).
I’m not sure why the smart thermostat is battery powered, seems like the device is better suited to USB power. Probably it can be modified to take 5V directly instead of the 3xAAA batteries (voltage of 3xAAA would be ~4.5V so likely 5V tolerant), with a small hole but in the side, USB-C socket installed and leads connected to each end of the battery bay. Just make sure to get a USB-C socket that commands 5V instead of 9V/15V/20V and it should work fine. Could also replace the 3xAAA with a small lipo cell, say 500Mah 1S and use simple USB-powered BMS with 5V output.
Personally I’m really enjoying not touching the device and using a Nest-style ESP32 instead: GitHub - kancelott/neo-nesp: Nest Thermostat clone on a rotary display running @esphome
I have the same/similar issue with my Tado-X & HA. Of my 11 devices (2x Wireless Thermostats and 9x Smart Radiator Thermostats), 5 devices (1x Wireless Thermostat and 4x TRVs) are showing as unavailable. They all work perfectly fine with Tado app and Apple Home, just not with HA as Matter devices. I’ve checked and recharged all batteries, restarted my Tado X-bridge, Wireless Receiver X and Home Assistant, but still remain unavailable. 
1 Like
@Spatchy - I have UniFi access points throughout the house. I restarted all my APs and all the Tado-X TRVs and devices appeared back in HA. Seems that they disconnected again (only 2x of them) after some hours this morning. Have restarted AP and they are both back online. Not sure why they are dropping after some time, yet remain online and available in both Tado app and Apple Home 
The TRVs don’t implement the OtaSoftwareUpdateRequestor Matter cluster, so no updates using Matter.
1 Like
You can increase the log level of the Matter Addon in HA and inspect the logs.
Maybe you can find a clue there.
I’ve been trying to link all of my Tado X devices to Home Assistant through Matter. Among other problems, here is the weirdest one.
I have two identical Wireless Temperature Sensor X units placed in different rooms. After adding both to Home Assistant (via Matter shared from the Tado App), I am getting different entities for each:
- Sensor 1: Shows climate controls AND temp/humidity sensors.
- Matter Firmware: 1.1 | Tado Firmware: 276.2
- Sensor 2: Missing climate controls, showing ONLY sensors.
- Matter Firmware: 1.0 | Tado Firmware: 280.1
It’s strange because the sensor with the newer Tado firmware (280.1) seems to have an older Matter version (1.0) and is missing features.
Has anyone else seen this inconsistency? Is there a way to force the Matter firmware to update, or is this a known issue with the 280.1 rollout?
There are two variants of the Wireless Temperature Sensor X. CSA lists them with Product ID 0x0003 and 0x0006. 0x0003 is certified with firmware 1.0 as a Temperature Sensor (Device Type ID 0x0302) and with firmware 1.1 as a Thermostat (Device Type ID 0x0301). 0x0006 has only one certification with firmware 1.1 as a Thermostat.
My Wireless Temperature Sensors have a Product ID of 0x0003 and also only show temp and humidity. I’m on Tado firmware 276.2 and Matter firmware 1.0. I’ve bought them on release date. Interestingly they also had climate control with one of the early Tado firmware.
If you look at the DCL the only available Matter firmware for Product ID 0x0003 is version 1.0. I think we have to wait until Tado releases a new matter firmware. Both variants are capable of acting as a Thermostat.
1 Like
After months of struggling with Matter integration issues (devices going unavailable, battery drain, limited features, complex network setup…), I decided to take a different approach: I built a native Home Assistant integration using Tado’s official API.
Why skip Matter entirely?
As many of you experienced, Matter with Tado X is frustrating:
- Devices randomly showing as “unavailable”
-
- Limited to basic thermostat control + humidity
-
- Complex Thread/border router setup
-
- Battery drain issues
The solution: Tado X Integration (HACS)
I created a custom integration that connects directly to Tado’s cloud API - the same one their app uses. No Matter, no Thread, no border router headaches.
Features:
| Entity | What you get |
|---|---|
| Climate | Temperature control, HVAC modes (Heat/Off/Auto), Presets (Schedule/Boost) |
| Sensors | Temperature, Humidity, Heating power, Battery status |
| Binary Sensors | Window open detection, Heating active, Manual control, Connectivity, Low battery |
Supported devices:
- Radiator Valve X (VA04)
-
- Temperature Sensor X (SU04)
-
- Thermostat X (TR04)
-
- Bridge X (IB02)
Easy install via HACS:
Or manually add https://github.com/exabird/ha-tado-x as a custom repository in HACS.
GitHub: GitHub - exabird/ha-tado-x: Home Assistant custom integration for Tado X devices
Hope this helps those of you who, like me, gave up on Matter! Feedback and contributions welcome.
5 Likes
Normally one radiator is uncontrolled, to act as a bypass for the boiler, in my case its a bathroom towel rail.
You could get a plumber to fit an auto bypass valve in the pipework.