Is there a possibility to set the hysteresis with this thermostat ? If not, what is the default ?
Probably best to ask tado’s helpdesk (use the chat function or ask the question on their community forum).
I have installed it via tado app and then integrated it into Alexa and using my new Echo dot to control the temperature. Works fine.
Is there any way to integrate the thermostats into HA via Alexa? Or do I need a Skyconnect matter dongle for that?
I am new to HA, I have HA green.
Thanks for your help 
Since you’ve been able to add it to Alexa already, the device is connected to Thread border router (presumably Amazon’s) and is already on the network. You don’t need a SkyConnect dongle in that case, you can simply share the device on Alexa side and add it to Home Assistant as a Matter device (add the Matter integration, then you’ll have “Add Matter device” as an option).
This is what I tried via the Tado app. But sharing the code to HA is not working for me. It just gives the error that it was not added. How can I save the logging information when trying to add the device? Maybe an error that is more clear pops up then.
The commissioning is handled by the Matter Server, so best is to just share the Matter Server add-on logs. You can increase the verbosity if needed, but even standard setting might give an indication already.
What do you use as Thread border router? What type of Home Assistant installation do you use? I guess the most likely case is that your system can’t communicate with the device for some reason.
In my case I didn’t even need a code. In Tado app, go to settings, device and click device linking. From there my Android phone already knew that I have Home Assistant. Just clicked home assistant in the pop-up and that’s it
1 Like
Thanks for the replies! Fortunately I could find a somewhat better error message in the logs:
2024-11-11 22:39:49.547 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 19.
2024-11-11 22:39:49.632 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/controller/SetUpCodePairer.cpp:280
2024-11-11 22:40:19.562 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2024-11-11 22:40:19.563 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2024-11-11 22:40:19.565 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:89: CHIP Error 0x00000003: Incorrect state
2024-11-11 22:40:19.568 (MainThread) ERROR [matter_server.server.client_handler] [547950574864] Error while handling: commission_with_code: Commission with code failed for node 19.
On the forums I could find that people warn about vLAN or mDNS. My network is as simple as it can be with a single router provided by my ISP and all devices in that same network connected by wifi. IPv6 is enabled but I could not find any setting about mDNS. Only dynamic DNS which is disabled but apparently that is something completely different.
I am using an ESP thread border router with the latest firmware. It runs on its own so it is directly connected to the wifi.
The HA is running in a docker container on the raspberry pi together with the matter server which runs in another container.
I will dive further into it but any suggestions are very welcome!
You are most likely lacking proper IPv6 Neighbor Discovery Protocol Route Information Options (NDP RIO) support on your host OS. You can find some information about it in the Matter Server readme: GitHub - home-assistant-libs/python-matter-server: Python server to interact with Matter.
If that doesn’t help, I recommend using a Home Assistant OS installation at least for a quick test. HAOS has all the right knobs and features set to work well with third party Thread border routers.
I confirm that Tado Wireless Thermostat X now is working with HomeAssistant via Matter and also with Tado APP as well.
Modifying temperature from tado app/thermostat, you see HA refreshing correctly and also modifying temperature from HA is applying configuration an acting as expected.
Firmware version thermostat (from tado app): 243.1
1 Like
So that means with just HA and sky connect it’s possible to connect directly without the need for tados own hub?
Did they expose OTA updates or do you still need the hub for that?
Am I reading it right that you can now use third party sensors to sort out temp management? I know the TRV temp sensor is normally not ideal due to its location so have alternatives in each room that I would use as a temperature monitor.
Been looking for decent smart TRVs but everything’s been with big cons and didn’t discover the X model till today as that seemingly fixes the main issue with it being cloud based beforehand!
Are you guys happy with the TRVS?
Thanks for the advice!
It works great now in HA. Google Home still shows offline but that is a known issue and Tado is working on it I think. It had something to do with a too low interval of advertisement if I am not mistaken.
So what I found out is that my system uses networkd and the NetworkManager is not installed. To make it work I added a config file in /etc/systemd/network/ for example 99-wlan0.network.
sudo nano /etc/systemd/network/99-wlan0.network
And added the following in the file:
[Network]
DHCP=no
IPv6AcceptRA=yes
I flushed the NDP table:
sudo ip -6 neigh flush dev wlan0
After adding the config and flush I restarted the service:
sudo systemctl restart systemd-networkd
Now by executing the following command multiple times I could slowly see neighbouring devices showing up:
ip -6 neigh
And could ping them with:
ping6 <ipv6-address>
It took some time before the neighbouring devices were found so have some patience.
Further than that I did not change the default parameters. The kernel parameters for all interfaces are:
net.ipv6.conf.all.disable_ipv6=0
net.ipv6.conf.all.forwarding=0
net.ipv6.conf.all.accept_ra=1
net.ipv6.conf.all.accept_ra_rt_info_max_plen=64
But I found that the max payload length did not matter in my case. To make sure what the kernel parameters are:
sudo sysctl -a | grep ipv6.conf.all
Thanks a lot for helping out! If someone has the same issue as me I hope this post helps them.
Thanks everyone for all the insights! You got me sold for this, and the X has been ordered to replace the V3+ and leverage matter over thread. I noticed that the “Programmer with Hot Water Control and OpenTherm” here Wireless Smart Thermostat X - Starter Kit incl. Programmer with Hot Wa – tado° Shop is listed as a Thread Border Router - similar to Bridge X Bridge X – tado° Shop . Has anyone experienced if Tado’s thread network can be joint with an existing one in HA (here HA SkyConnect is in a unique thread network with a Google Nest Max)?
To expand, I’ve got an echo that is already keeping keys and joining functions hidden and that so sits inaccessible, I’d rather not proceed if this Tado functionality, in reality, means that there’ll be a third thread network in the house…it would defy the biggest part of the point upgrading, because even if we’d have local access over matter, it won’t benefit an already over-crowded RF environment and the TRVs won’t benefit from the thread router bulbs in each room, right? 
Hi all, sorry in advance as it is not strictly a home assistant-related question, even though my ultimate goal is to integrate this thermostat in HA. So I am considering buying a wired Tado X thermostat but I have no thread router at the moment. Instead of buying the Tado X bridge that will not do much beside linking the thermostat to Wifi and eventually Home Assistant, I am considering buying an Echo device. Older posts in this thread say it does not work, but more recent ones suggest it now does. Can anyone confirm it would do the job or are there other alternatives to consider?
Cannot say anything about Echo but can confirm, that Tado is conpatible with SkyConnect. Have it myself and it’s working without any issue. If you’re satisfied with very basic functionality, and yor’re capable to set everything via automation, it can works flawlesly even without tado app (tado cloud).
1 Like
@Hicks12 In my case I have Wireless Thermostat X connected with tado (first configuration) and then connected to HA via matter ( as second controller ) and thermostat is using the X Receiver connected to boiler as Thread Border Router.
You can configure directly with HA at matter level using they own TBR, but not sure if using a Thread Border Router via HA will work.
In my case updates are managed by Tado and I can’t confirm if you can update without tado ecosystem.
I really only need to toggle HVAC Mode between ‘off’ and ‘auto’ for opened windows - is that still the same mechanism as with the old ones?
To answer my own question, I contacted Tado support and they told me that at the moment, the only alternative to their bridge are Apple devices (Apple TV and Homepod). Good to hear though that Skyconnect works too. The only issue is that there has been a recall on Skyconnect devices and it might get difficult to get one.
Fantastic, thank you!
Are you aware of other attributes that could be templated? I’m interested to see the state (“heat” or “off”), and ideally also how much open they are?