Skip to content
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

Open
Holger237237 opened this issue Jan 26, 2025 · 7 comments
Open

[tado] tado X heating thermostat valve is not dicovered by inbox #18190

Holger237237 opened this issue Jan 26, 2025 · 7 comments
Labels
bug An unexpected problem or unintended behavior of an add-on

Comments

@Holger237237
Copy link

Holger237237 commented Jan 26, 2025

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)

  1. OH: Things +
  2. OH: tado binding
  3. Scan

Context

Your Environment

  • Version used: OH 4.3.2
  • Synology Station 718+

Image

Image

@Holger237237 Holger237237 added the bug An unexpected problem or unintended behavior of an add-on label Jan 26, 2025
@Holger237237 Holger237237 changed the title Tado X thermostat valve is not dicovered by inbox Tado X heating thermostat valve is not dicovered by inbox Jan 26, 2025
@Holger237237 Holger237237 changed the title Tado X heating thermostat valve is not dicovered by inbox [tado] tado X heating thermostat valve is not dicovered by inbox Jan 26, 2025
@andrewfg
Copy link
Contributor

andrewfg commented Jan 29, 2025

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.

@Holger237237
Copy link
Author

Holger237237 commented Jan 29, 2025 via email

@digitaldan
Copy link
Contributor

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
Image

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.

@Holger237237
Copy link
Author

Bridge X and thermostat X are installed via tado app.
Matter Binding ist installed on OpenHab 4.3.2 and I created manually a matter Controller.

Image

Thermostat X should be a real matter device and i only need access to that. Bridge X is not nessesary.
So i createted a new matter code via tado app for the thermostat. This should be valid for 5 minutes. Entering this code in OH creating new things-> binding matter and start "scan".

Image

Unfortunatly the thermostat is not discovered.

Any ideas?

Thanks
Holger

@digitaldan
Copy link
Contributor

Bridge X is not nessesary.

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)

@Holger237237
Copy link
Author

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.

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?)
Right
Also it not clear how you are running openHAB ? Docker, Raspberry pi, vm , etc
OH is running as Docker (Synology NAS). I don't know exactly what else I need to set for ip6 in this case. Everything that is listed in the readme file?

Thanks a lot

@digitaldan
Copy link
Contributor

OH is running as Docker (Synology NAS)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior of an add-on
Projects
None yet
Development

No branches or pull requests

3 participants