I have Tado X thermostatique head and I just received my ZBT-1, set up openthread border but impossible de find the devices through the tado app. any hint?
Is there an incompatibility after all?
Thanks
I have the same problem. I can change the temperatur by hand in the dashboard and that works. But I cant change it when I want to create an automation
You can do that via a climate action where you have actions to change the hvac mode, but also the temperature. Works fine for me.
Ahh yes, found it. Thanks!
1 Like
Not possible to add to tado app without tado router. Only to HA.
Thank you. So I bought a ZBT-1 for nothing ><"
That is not true, I run the a Tado Thermostat X with OTBR here, and can control it through Tado App as well. As I wrote in the initial post, make sure to enable NAT64.
I switched to HAOS and was able to get past the initial pairing screen, but it still ended with “Something went wrong”. I tried both comissioning through the HA app and the half-screen pop up.
2025-01-16 19:10:37.369 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning using Node ID 2 and IP fde9:a8f9:2bc9:1:25ce:c181:6852:6e9a.
2025-01-16 19:10:39.992 (Dummy-2) INFO [chip.ChipDeviceCtrl] Established secure session with Device
2025-01-16 19:10:41.814 (Dummy-2) CHIP_ERROR [chip.native.CTL] Error on commissioning step 'AttestationVerification': 'src/controller/CHIPDeviceController.cpp:1283: CHIP Error 0x000000AC: Internal error'
2025-01-16 19:10:41.814 (Dummy-2) CHIP_ERROR [chip.native.CTL] Failed verifying attestation information. Now checking DAC chain revoked status.
2025-01-16 19:10:41.815 (Dummy-2) CHIP_ERROR [chip.native.CTL] Failed in verifying 'Attestation Information' command received from the device: err 101. Look at AttestationVerificationResult enum to understand the errors
2025-01-16 19:10:41.815 (Dummy-2) CHIP_ERROR [chip.native.CTL] Error on commissioning step 'AttestationRevocationCheck': 'src/controller/CHIPDeviceController.cpp:1332: CHIP Error 0x000000AC: Internal error'
2025-01-16 19:10:41.995 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to send Solitary ack for MessageCounter:77208815 on exchange 11087i with Node: <0000000000000000, 0>:src/messaging/ExchangeContext.cpp:99: CHIP Error 0x00000002: Connection aborted
2025-01-16 19:10:41.995 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to commission: src/controller/CHIPDeviceController.cpp:1332: CHIP Error 0x000000AC: Internal error
2025-01-16 19:10:41.996 (MainThread) ERROR [matter_server.server.client_handler] [140071091780544] Error while handling: commission_on_network: Commissioning failed for node 2.
You are right. After enabling NAT I was able to add valves to Tado as well! Pairing proces over iphone wasnt sucessful, but device was added anyway. Thanks
May I ask: which hotfix? I am currently struggling with automations of my Tado X through matter because I cannot activate the schedule again. Would be nice to use the Tado API even if it’s just beta stage at the moment.
Hello there!
Technically possible to add Tado X wired thermostat to Tuya matter/thread hub? I know that is no OTA and only basic functionality, but possible?
I’ve just managed to get all my X devices connected after alot of issues and engaging with Tado support. I’ve read various people having issues and this might help.
Firstly, the matter credentials are sent to the Tado Receiver from the phone. So whatever creds you have on the phone, will push to the receiver when you click configure within the Tado App. This was important for me as my creds where “hinky”. When I factory reset my Tado Receiver and I could not understand why Tado within HA was coming up as “home-assistant” when everything was reset and rebuilt. To fix I cleared my phones cache for Tado, HA companion and “Google Play Service”, however this will reset other stuff on your phone like wallets, so do that with caution. Starting fresh I created a new HA thread network with matter creds, configured the Tado receaver and added it to my new ha-thread network. Then configured the HA companion app.
Secondly, In a good clean state, I had issues connecting devices, they would connect, but the process would pause on communicating with device over wireless and then fail and disconnect. I had to shut down HA to get the devices to join the thread network. Tado seam to be aware of this issue using other border routers, NAT64 may help, but this was disabled for me. Either way, its a known issue.
Thirdly, I had issues getting matter link to work, it was either greyed out or said “Something went wrong”. Talking with Tado support, I was told to keep factory resetting the device, until it starts working. This is again a known issue. I had to factory reset devices 2 or 3 times to get matter link to work.
Hope this helps anyone,
1 Like
Now I have Tado X connected to HA via matter, I’m finding it to be limited.
- How do people take over scheduling? So I can configure via HA/mode red for scheduling and fall back to Tado if needed.
- Is there a way to show when my boiler is on or off? Even when heat is deminded.
- Is there a means to manage or control Tado scheduling?
- Is there a way to set heat with infinity from HA?
Just to be clear, the Connect ZBT-1 does work just as well, it is the same device essentially.
Hi Did you manage to make this work?
I’m in the same situation where I managed to make the Tado X Thermostat work with HA through Matter using the Google Nest Hub 2 as Bridge, but can’t make the thermostat show up online in the app?
Did some more reading on the Tado community pages and found the following in a discussing:
“Apparently the thread router needs to support “NAT64” and there are only a few brands that do that. (Google Nest not at least).”
So I’m guessing I need to find a way to force my HA to use the Skyconnect to connect the Tado X over matter instead of my Google Nest Hub 2 which is also a boarder router in my HA.
1 Like
Or if you have a Sonoff Zigbee 3.0 Dongle Plus (ZBdongle-E), use that.
Install OTBR add-on Link to Integrations: add integration – My Home Assistant
How do I figure out, if my thread router supports it? In my case an Apple TV 4K Gen2.
If it’s on the list with interchangeable bridges (which also support NAT64), which in your case it is.
1 Like
Great, thanks a lot!
1 Like