-
-
Notifications
You must be signed in to change notification settings - Fork 3.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] tado X heating thermostat valve is not dicovered by inbox #18190
Comments
Are you referring to the Tado binding? If so, then please be aware that neither that binding nor the respective Tado bridge support the Tado X product family. By contrast the Tado X bridge is a Matter bridge, so if you want to integrate that system you need to use the Matter binding. |
I see. Thanks for this information. I tried Matter binding. So far without
success. Tado X Bridge is not discovered. Pity
Am Mi., 29. Jan. 2025 um 16:24 Uhr schrieb Andrew Fiddian-Green <
***@***.***>:
… Are you referring to the Tado binding
<https://www.openhab.org/addons/bindings/tado/>?
If so, then please be aware that neither that binding nor the respective
Tado bridge support the Tado X product family.
By contrast the Tado X bridge is a Matter bridge, so if you want to
integrate that system you need to use the Matter binding.
—
Reply to this email directly, view it on GitHub
<#18190 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWNGKO4JBMBTEQLPXU5SCC32NDXCFAVCNFSM6AAAAABV4LVR62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRRHE2TQOJVGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
hi @Holger237237 can you elaborate ? It looks like Tado Bridge X is a thread border router (not an actual matter device), so once plugged in, you should be able to use the Tado app to set it up and get your matter thermostat connected to it, which in turns makes the thermostat device available on your IP network (this border router just bridges thread to wifi and back). Then using the Tado app again, generate a new matter code and use that to add the device to our matter binding (make sure you are on openHAB 4.3.2). I found these instruction on the Tado site for generating the code once you have it setup in the tado app. https://help.tado.com/en/articles/9242001-where-can-i-find-the-matter-setup-code-for-my-tado-x-device when added to openhab, we talk to it directly through the bridge (wifi -> thread -> wifi) Let us know how this goes! Pretty cool to start seeing thread border routers hitting the market. |
Bridge X and thermostat X are installed via tado app. Thermostat X should be a real matter device and i only need access to that. Bridge X is not nessesary. Unfortunatly the thermostat is not discovered. Any ideas? Thanks |
its necessary in that the thermostat needs to get on your network, and needs that bridge to connect via thread -> wifi. And the bridge will send IPV6 announcements on your network for the thermostat, which openHAB will need to hear about. I'm assuming then you do have the thermostat connected to the bridge and the Tado app is able to communicate with it ? (since it generated a code?) Also it not clear how you are running openHAB ? Docker, Raspberry pi, vm , etc...... There is a section of the readme that addresses thread connectivity specifically on linux hosts, it requires that some IPV6 system level features are enabled. See https://github.com/digitaldan/openhab-addons/blob/matter/bundles/org.openhab.binding.matter/README.md#enabling-ipv6-thread-connectivity-on-linux-hosts Finally if you put the binding in TRACE mode there will be a whole lot of logs when you scan, but i would check the README first to verify your host is able to hear about thread border router clients (its an ipv6 thing) |
I see. "Bridge X is not nessesary" means for using in matter binding. Basically, of course, I use the bridge for normal use via the tado app.
Thanks a lot |
Well that might be a problem, ipv6 is disabled by default in docker and has to be turned on when starting a container. Doing a quick google on Synology looks like they also disable ipv6 on docker, and do not give an option in the UI to enable. I did find some posts about configuring this manually through ssh, but have not tried this myself. I'm running my openHAB under docker with thread connected devices, so that part does work once IPV6 is properly enabled. |
I have a Tado X Starter Kit: Bridge + thermostat valve.
Expected Behavior
After successful discovering of the bridge, bridge is showing "online". The next discover run should discover the devices. In my case valve und via app integrated smartphone.
Current Behavior
Only the smartphone is discovered.
Possible Solution
Is there another possibility to get zone-id and valve-id and use it manually?
Steps to Reproduce (for Bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: