When I do this it says that Matter coupling is not available. I have a complete Tado X setup that works perfectly, but I can not couple it to Homey because of the message that Matter coupling is not available.
Have you installed the Tado app?
Yes, both the Tado app and the Tado Zones app. With the Tado Zones app it works, but with the Tado app I can not use matter to connect. The advice I get is to completely re-install my whole Tado setup as apperently something went wrong during innitial setup. Since it works with the Tado Zones app I will let it go for now. Re-installing my whole setup is too complicated for now.
You make it sound like the tadoZones app is of a questionable quality?
The ‘official’ tado app is just very limited compared to it 
Plus the support is great.
Then you have misinterpreted me. The Tadozones app works fine, not the Tado app. I am just frustrated that I can not add Tado devices via Matter.
You have to add them via Sharing the matter code from the official Tado app, then add them into Homey.
There is A LOT of past discussion about this on the forum
I previously added the Tado devices as a Matter device in Homey Pro, but then I started to experience erratic behaviour. The Tadozones app worked perfectly until Tado decided to put in place the maximum limit of 20K API calls / day. Extremely annoying.
I think there may be a misunderstanding here.
Matter is designed as a multi-admin standard. The original pairing code remains valid and can be reused after the device has been fully factory-reset. Using that initial code, the device joins a Thread fabric (a logical network, which is called a fabric in Matter terminology).
Each ecosystem can have its own fabric — for example, Homey may have a fabric, Tado may have one, and Apple Home may have one as well.
When you generate a new Matter code in the Tado app, you are not changing the device’s original pairing code. Instead, you are generating a sharing (multi-admin) code. This code allows you to add the device to an additional controller. After that, both controllers can operate the same device.
However, it’s important to understand what happens at the network level in this case:
The device remains on the original fabric (in this example, the Tado fabric) and is still owned by the Tado controller. Homey is granted access to the device, but the device is not moved to the Homey fabric, nor is it owned by Homey.
This distinction matters because each fabric has its own Thread mesh. Pairing a mains-powered device to Tado adds a Thread repeater to the Tado fabric; pairing a mains-powered device directly to Homey would add a repeater to the Homey fabric instead. The more separate fabrics you create, the more fragmented and potentially less stable the overall Thread environment can become.
That’s why I personally pair all my Matter devices to Apple Home first and then share them with other controllers (mainly for testing). All Apple Home controllers participate in a single shared fabric, and if one controller fails, another automatically takes over without losing the fabric or the devices. Combined with generally strong radio performance, this has proven to be the most stable setup for me, while other controllers can still be used for advanced automations on top.
Does this imply the Matter connected tado X devices use the tado cloud, while it shouldn’t be necessary?
1 Like
That part was about the tadoZones app, not about the Matter devices
