Skip to main content
All CollectionsUsing tado°How tado° works
How do tado° X devices communicate with each other?
How do tado° X devices communicate with each other?
tado° avatar
Written by tado°
Updated over a week ago

tado° X devices use the Thread protocol with IPv6 to communicate with the Thread border router.

A Thread border router is a necessary component of every Thread communication network and tado° X installation:

  • It enables other devices to connect to the internet.

  • It routes the communication between Thread-enabled devices.

  • It functions as a signal extender by expanding the reach of the network to far corners of a home. You can have multiple Thread border routers in different parts of the home.

tado° currently offers three Thread border routers, the Bridge X, the Heat Pump Optimizer X, and the Wireless Receiver X, but also supports several third party Thread border routers: Apple TV 4K (2nd generation or 3rd generation 128 GB), HomePod (2nd generation) or HomePod mini).

Thread devices create an Internet-based mesh network whereby devices from different vendors can communicate with each other without a proprietary bridge. Some devices act as Thread border routers, which repeat signals, strengthen the wireless connection in the home, and are connected to a power source. Other devices, like tado° Smart Thermostats, are battery powered and connect wirelessly. All these Thread devices connect directly to the cloud and communicate with each other. If one device fails, the next closest device will take its place to pass along the data.

For more information about mesh networks, visit thread.org.

Advantages of Thread over Wi-Fi

  • Thread consumes less power.

  • Adding more devices to the network doesn’t weaken the signal.

  • Devices can store heating schedules locally and they will keep working even if they lose connection with the internet.

  • You can extend the range of your network by adding Thread border routers like the tado° Bridge X, tado° Heat Pump Optimizer X, or tado° Wireless Receiver X.

Did this answer your question?