There might be something that I overlooked?
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 }}
1 Like
I’m thinking using the set temperature of the thermostatic head to potecially trigger things. Can’t find anything anywhere…
I just found something working. If this syntax is better, I totally believe you!
I found out how you read the set temperature through the template again. The variable is called ‘temperature’. I kept trying "set_temperature’!!! 
I wrote that a couple of posts above this 
I was looking for postst to help me with that but didn’t find them…
Thanks again for hiding them so well. 
I wrote to Tado about this, with examples and everything. Reply: put a post in the community to see what they think. Tado X just isn’t consistent. The wireless temperature sensor does have a sensor for temperature, the thermostat or radiator valve doesn’t. So, they know how to do it right, they just don’t do it…
Hi there.
Thanks for all those informations.
I’d like to use Tado thermostat without their cloud/without internet connection. Is this scenario possible? To set desired temperature via thread network in hassio, fully without Tado cloud?
Simple set temperature or at least force open/force close heating circuit.
Thanks
Hi @gimmiereddy , i think i’m having the same problem. Is working as thermostat when use it with tado app, but when you use HomeAssistant thermostat is not acting. Is that your case?
Yes, I got a replacement unit, but that suffers from the same issue…it’s a bit of a shit show to be honest
I’ve opened a support case but they are not giving me a clear solution:
tado° X is still in development, so it could be the cause that your devices are not fully working with your Homekit for now. If you wish, please leave a feedback in our community center so developers have in mind the issue.
There are some posts talking about this in the community forums, but they are not responding. I contacted in one of them , asking for more info if they are pretending to solve or not 
I’ve upgraded from previous version to X just for the option to have them on my local network only.
That’s just wishful thinking because there are many “black-outs” in the Thread network
1 Like
Aside from replacement Wireless Temperature Sensor X devices due to hardware changes in August, there is a known bug with the sync between tado and HomeKit and/or Home Assistant. This was confirmed to me by support and they are working on a fix. I was also informed that I could get this fixed immediately through a firmware downgrade (assume the issue manifested in latest upgraded firmware), so suggest either waiting or asking tado Support for a firmware downgrade.
1 Like
@rjblake many thanks for the info! 
I was talking with the support and they were saying is an under development product and so on, but never confirming if it was recognized.
Did they say how to check if old/new unit sensor?
Thanks for all!
Hi,
I’ve walked through your steps of connecting the thermostat. It connects fine with the tado app and I can control it there. If I click on share to other matter controller I can share it to google home. It does add the device but it keeps displayin offline while it is actually not. When I try to add it to Home assistant it gives me back that the device could not be added.
What steps can I take to check what goes wrong? According to the documentation of the border router it does support NAT64 but I don’t know how to validate that either.
Hope someone on the forum could help me out. Im still learning about Matter and Thread so some things are not that clear to me yet.