-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tado X - Unable to add Matter devices #134145
Comments
Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) matter documentation |
In the log I only have 8 groups of lines like:
|
For your info I've cross checked and enabled IPv6 on the network. HA and the Matter Bridge are on the same network both as IPv4 as well as IPv6 |
The problem
I've moved to Tado X - they should be Matter enabled.
I have a Tado X bridge and several The Smart Radiator Thermostat X, Smart Thermostat X
I've configured them with the Tado App and they are connected.
As explained in the documentation from Tado and for Matter I've opened the Tado app, under the specific device there is the option Device Linking with the matter logo. It generates a code.
The same code should be used to add the device to the matter integration but I end up always with an error.
(Matter -> Add Device -> Yes is already in use -> Other controller -> Enter Setup Code)
The bridge as well as HA are in the same network, everything updated.
Note that the tado X bridge is the Thread Preferred Network
What version of Home Assistant Core has the issue?
core-2024.12.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Matter
Link to integration documentation on our website
https://www.home-assistant.io/integrations/matter
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: