TADO integration stopped working - Failed to unload

[jeroen7103]

The problem

When I restart HA the integration works for a few minutes. After that, all entities from the integration become unavailable. On the Integrations page of HA, the Tado integrations shows "Failed to unload".

What version of Home Assistant Core has the issue?

core-2024.8.3

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

Tado

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tado

Diagnostics information

home-assistant_tado_2024-08-27T12-52-33.820Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

KeyError: 'tado'
2024-08-25 19:15:14.956 ERROR (MainThread) [homeassistant.components.shelly] Error connecting to Shelly device shellyplusi4-80646fe218d4, error: DeviceConnectionError(DeviceConnectionError(ClientConnectorError(ConnectionKey(host='192.168.10.13', port=80, is_ssl=False, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=1432999572988732864), OSError(113, "Connect call failed ('192.168.10.13', 80)"))))
2024-08-25 19:15:15.403 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry Woonkamer for tado
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 819, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tado/__init__.py", line 154, in async_unload_entry
    hass.data[DOMAIN][entry.entry_id][UPDATE_TRACK]()

Additional information

No response

[home-assistant[bot]]

Hey there @chiefdragon, @erwindouna, mind taking a look at this issue as it has been labeled with an integration (tado) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `tado` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tado` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

tado documentation tado source _{^{(message by IssueLinks)}}

[Bamboooo67]

I have the same problem since I updated to version 2024.8. The problem occurs after reloading the Tado integration and disappears after a restart

[ryebreadsalad]

Having the same issue - barely works a day. Wondering what causes this. However I do have an automation that reloads the tado integration in case it becomes unavailable. It doesn't fix the issue, checking if there is a casual connection.

[jeroen7103]

Having the same issue - barely works a day. Wondering what causes this. However I do have an automation that reloads the tado integration in case it becomes unavailable. It doesn't fix the issue, checking if there is a casual connection.

Unfortunately this does not work for me. I get the error:

Error: The config entry 'XXX' (tado) with entry_id 'XXX' cannot be unloaded because it is in the non recoverable state ConfigEntryState.FAILED_UNLOAD

[ryebreadsalad]

Having the same issue - barely works a day. Wondering what causes this. However I do have an automation that reloads the tado integration in case it becomes unavailable. It doesn't fix the issue, checking if there is a casual connection.

Unfortunately this does not work for me. I get the error:

Error: The config entry 'XXX' (tado) with entry_id 'XXX' cannot be unloaded because it is in the non recoverable state ConfigEntryState.FAILED_UNLOAD

To be clear, this does not work to relieve the issue this bug is about. This was working for the "normal issue" when cloud based integrations become unresponsive due to internet/Server issues or something. I was just mentioning this cause Bambooo67 said it's happening after config reload, which my automation does automatically upon detecting unavailability of the integration.

[jeroen7103]

I have updated HA Core to version 2024.9.0. The TADO integration is working again :-)

[c-kick]

I can confirm that it seems to be working again in 2024.9.0, but it's not been 24 hours yet, so this is not a definitive conclusion.

Also, I haven't seen anything in the release notes that suggests a fix for this issue, except for 2 items that mention Tado (a better config validation for legagy-setup integrations, and an AC fan speed fix).

[DarkAllMan]

Same result here... look ok for now.

[Bamboooo67]

Very nice, we hope for the best, thanks for the information

[c-kick]

At about an hour ago, my tado climate entries became unresponsive again. As I already feared; the issue persists.

[DarkAllMan]

For me all is still online... But I will report back if the same happens.

[rofo69]

its 100% still an issue. I have a rest command I use to restart the integration, and its still consistently fails with this error:-

`Logger: homeassistant.config_entries Source: config_entries.py:819 First occurred: 09:37:50 (1 occurrences) Last logged: 09:37:50

Error unloading entry Our house for tado Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 819, in async_unload result = await component.async_unload_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/tado/init.py", line 154, in async_unload_entry hass.data[DOMAIN][entry.entry_id][UPDATE_TRACK]()

KeyError: 'tado'`

[grebar]

I confirm the issue after upgrading to 2024.9.1 :-(

[grebar]

I confirm the issue in ver 2024.9.1.

[xNUTx]

I am having the same issue... and when it works it 'connects', 'disconnects' and 'reconnects' again. When trying to set a new temperature it will 'crash' and 'disconnect'

Quotes, as it is a state based on the overall health of the integration, I see the same error in my logs as the OP.