aha aha aha, not relevant post
I made the thingy work! The hitch was the border router. It doesn’t “like” to be in a different room than the WIFI router. So, when the connection is uber good, it does its thing but, it takes about 20 minutes? Maybe more? And during this time you don’t have access onto the router, that’s what was confusing for me. I thought the bloody thing froze and each time I rebooted it but, it didn’t freeze, it was doing something and I just interrupted the process, that’s why I had such trouble. Once the border router was up and running, installing the rest of the paraphernalia, the smart thermostatic heads and the room thermostat, was a breeze.
But there is a major drawback to the Tado system – it’s not local. And without internet it doesn’t work… Anyone has an idea how to make it work locally?
Yes, and the customer service at Tado is atrocious. All and all, I reckon there must be a better system out there.
Thermostat requires cloud connectivity directly: Enabling NAT64 in the OpenThread Border Router add-on helped to get that going
This was the only issue i was having but after waiting a couple minutes and enabling it the thermostat showed as online in the app, about an hour later the firmware was updated.
Thanks for the great write-up
Any news on that topic?
Is it possible to reference the current temperature as a proper sensor?
I can only see Humidity listed under sensors.
Also, what’s the update frequency on temperature changes when connected through matter?
Many thanks!
Do you have the same result as me using the official tado integration: Tado integration - Add Support for tado X devices ? The home is added, but no devices.
@takenit2far you can use template sensors for this: with this code you can get it working:
{{ state_attr(‘climate.heizung_badezimmer’, ‘current_temperature’)|float }}
Does that mean the Tado X uses internet over Thread to update firmware, and that is why it needs to be connected? Or is Tado X still as cloud dependent as it used to be (aside from Homekit, which was equally limited). Because that was Tado’s worst downside with older models, and it seems it has gotten even worse if Thread/Matter won’t work without internet.
1 Like
Same for me. I just added them via matter to HA.
Yes, me too, but that is very limited unfortunately. Would be great if the integration maintainers could add support for the new tado X Accounts.
Seems to be working okay for the both the smart thermostat and the smart radiator thermostat. However I am having issues updating the temperature set point of the wireless temperature sensor through matter. The temperature and and humidity values are visible in home assistant. This seems to be a bug to me. But I have no idea where to report this. Any advise?
I have got TADO X. I think I have got a similar issue. If I update heating point to 22deg in tado app, in HA it will not update. Also when I set heating point in HA to lets say 23deg, it will not update in tado and heating it is not starting. I can see the temperature accurately and live but I cannot control it via HA through matter. Even if I modify the temperature in Homekit Iphone, the temp in tado will not modify and it will not start/stop the heating. I am tempted to buy tado bridge and perhaps it will work. Or anyone have any ideas?
I found out this is a hardware issue with the wireless temperature sensor X. Apparently tado made different batches of this sensor/thermostat and only the newer batches work as a thermostat. Tado has promised to send me a replacement unit after I got in touch with support. So I would advise you to do the same.
2 Likes
Yes you can add the sensor for temperature.
You have to make a helper, template, template a sensor.
Give it a name, and in the template enter the following:
{{ states.<>.attributes.current_temperature }}
Fill in the rest of the fields. Don’t forget to link it to the right device at the bottom.
After that, return to the device, and you find the sensor listed.
How do you know if the wireless temperature sensor x works as a thermostat or not?
There is also temperature and set temperature that can’t be used as entities for triggers. It would be lovely to find out how that can be done.
Brilliant, thank you. Just need to find out what the update interval is now, I noticed the V3 stuff through Homekit is every 1 minute. And whether the Temperature Sensors can actually update the setpoint!
Yeah, I figured that out. Thanks. Now I’m trying to read the set temperature. That still escapes me.
I use this: {{ states.climate.radiator_knop_slaapkamer_luka_bank_thermostaat.attributes.temperature }}