#Tado Home Kit bridge availability issues.

1 messages · Page 1 of 1 (latest)

strong cloud
#

A while back Tado has announced that they will be imposing strict rate limiting on the API due to financial decisions. The fix was to move to local support using Home Kit bridge. I have done that.

However, I have noticed that my Tado thermostats drop from the integration and become unavailable after a while. They do not come back when I reboot HA or reload the integration. The only way to get 'em back is to adjust the temperature in the Tado app and then reload the integration. The app itself does not have this connection issue.

What I have done so far to debug the issue:

  • Verified that both HA and Tado Bridge are on the same VLAN.
  • Tado Bridge has a fixed IP
  • mDNS has been enabled and working
  • Disabled IGMP snooping
  • Moved the Tado Bridge to another location

Does anyone have any pointers on what this issue could be? I am about to cry

hoary jackal
#

are you on 2.4ghz wifi only for thermostat?

strong cloud
hoary jackal
#

ah ok

strong cloud
#

This is the IB01 bridge from the starterkit. They name it the V1 iirc

hoary jackal
#

maybe set static ip in router and tado on dhcp?

strong cloud
#

That is for sure. I cannot change the settings on the Tado device itself. The thing is VERY limited

#
  "data": {
    "config-entry": {
      "title": "tado Internet Bridge <snip>",
      "version": 1,
      "data": {
        "AccessoryIP": "**REDACTED**",
        "AccessoryIPs": [
          "192.168.1.17"
        ],
#

it does report the correct IP

#

(I am also dumping/monitoring traffic from the hypervisor to see whatever schizophrenic traffic Tado sends/receives)

hoary jackal
#

using honeywell lyric t6, so can't reproduce nor check 😉

#

Could it be HA DNS fallback issue?

#

try to disable in cli:> login
then ha dns options --fallback=false otherwise revert to true

strong cloud
#

I did disable that a while back due to that bug

#

that might be something actually. I'll check :D

strong cloud
hoary jackal
#

running for 3 years now without issues.