home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.32k stars 30.63k forks source link

Tado data stops updating #110111

Closed dennis07527 closed 1 month ago

dennis07527 commented 8 months ago

The problem

Since a few weeks, after some random time the data from the Tado integration get stuck at a value and is not updating (temperature, humidity, etc.) Last week it seems almost once a day this problem occours. A reload of the integration fixes the issue but that can't be the solution...

What version of Home Assistant Core has the issue?

core-2024.2.0

What was the last working version of Home Assistant Core?

core-2023.12.x?

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

I have enabled debug logging. There are no errors as far I can see.

Additional information

I know the provided information is not so much. Ofcourse you need more information but at this point I don't know what. Please let me know and I will upload it.

Here an example of the stuck information and after reload it's fine for some time. Tado 080224

home-assistant[bot] commented 8 months ago

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)

ArieGT commented 8 months ago

Thanks for reporting. I have the exact same issue and already have this for a while. Could not find any information about this issue and was thinking it was only my instance. I am running core 2024.2.1, supervisor 2024.01.1, OS 11.5. Cant recall last version it was working.

Screenshot_20240211-175713_Home Assistant

laroyo70 commented 8 months ago

Same issue here. No updates on temperature and humidity.

2024-02-12_11h19_26

Only when adjusting the temp manually it gets updated (see 7am when temp was set to 20.5). The TADO app on my phone does display the correct values.

HA Core 2024.2.0 running on Docker

Glasofruix commented 8 months ago

Same problem, i believe it started last week from friday when i updated to the latest core and os versions. If i take the last few days i get this

image

Glasofruix commented 8 months ago

Still happening.

pineconepl commented 8 months ago

Same problem, I noticed it today. Running HA 2024.2.2

erwindouna commented 8 months ago

It requires some more investigation. I'll pick it up next week to monitor this on a test setup.

trizmark commented 8 months ago

Same issue on 2024.1.5 image

schnickalodeon commented 7 months ago

Same problem here with HA version 2024.3.1. If I change the temperature for example via the Tado-App the thermostat applies the temperature, but HA did not update. The tile is only updated when I reload the integration

dhoeben commented 7 months ago

Same problem indeed. When changing back to automatic schedule, it won't change back in Home Assistant.

JarnoSt commented 7 months ago

Same problem here with HA version 2024.3.3.

pineconepl commented 7 months ago

Problem still exists in HA 2024.3.3

darconada commented 7 months ago

I can confirm issue still there. Core 2024.3.3 Supervisor 2024.03.1 Operating System 12.1

Downgrade to 2024.3.1 works fine. (i have tkae a VM snapshot before)

Update: After restoring the snapshot in VMware to remove the downgrade and back to 2024.3.3 the Tado integration started to work again with temperature , tado commands etc.. on version.. 2024.3.3 .. strange but working.

DaRockTR commented 7 months ago

I also had to downgrade to 2024.3.1 as tado integration stopped working after 3.3 update

noniq commented 7 months ago

For people experiencing this right now: It’s probably related to the switch to daylight savings time, see #114580. Simply restarting Home Assistant resolves the issue.

Glasofruix commented 6 months ago

For people experiencing this right now: It’s probably related to the switch to daylight savings time, see #114580. Simply restarting Home Assistant resolves the issue.

Nope, restarting does nothing. The integration works for a few hours then stops. Just reloading does the same trick.

loop2 commented 6 months ago

Same issue, reboot is not a solution...

kwaldrant commented 5 months ago

I got the same issue.

DaRockTR commented 5 months ago

Is the issue still there with the latest 2024.5.4?

jelmerkk commented 4 months ago

Still happens here in 2024.6.2 image

bekovan commented 4 months ago

Experiencing this from start of beta 2024.06, at .4:20 recirders are stopping. Reboot solves the issue

ChrisJ60 commented 3 months ago

Hi @chiefdragon and @erwindouna , is anyone looking at this? I also have this issue and it is causing havoc with my automations.

DaRockTR commented 3 months ago

Is anyone looking at this? I have this issue too and it is causing havoc with my automations.

Same question here. I am holding back on updating my HA system due to this issue but will run into issues with compatibility soon I think.

erwindouna commented 3 months ago

Hi @chiefdragon and @erwindouna , is anyone looking at this? I also have this issue and it is causing havoc with my automations.

Currently a new library is in the making. This will allow more flexibility and control over how we can influence the API with Tado. Once this is published I will look into this behaviour and see if I can replicate it. In the current installation I can't reproduce mysel.

ChrisJ60 commented 3 months ago

@erwindouna

Currently a new library is in the making. This will allow more flexibility and control over how we can influence the API with Tado. Once this is published I will look into this behaviour and see if I can replicate it. In the current installation I can't reproduce mysel.

Great to hear. There is so much I would like to do with the Tado integration but the current issues are a big blocker. Surprised you are unable to reproduce. Is there any info or diagnostics we can provide to help? I too have observed that reloading the Tado integration fixes the issue for a while.

erwindouna commented 3 months ago

Most helpful would be to have the logging when the issue arises. I realize this can be rather a commitment to deliver, but it would provide me with valuable insight on what's going on. Please don't forget to enable debugging info for Tado. :)

ChrisJ60 commented 3 months ago

@erwindouna I will try to capture logs showing the issue. I have enabled Tado debug logging. Once I see that the issue has occurred, how do I gather all the required logs (I've not done that before)? Is it just homeassistant.log or are there other files as well?

erwindouna commented 3 months ago

That would be sufficient, thanks @ChrisJ60!

ChrisJ60 commented 3 months ago

@erwindouna Attached is my first attempt (I suspect multiple attempts may be necessary, let's see). At around 2024-07-10 15:43 BST I used the Tado app to set the target temperature for the zone Ensuite to 20.5C. This change did not reflect at all in the Tado info and state in HA until around 2024-07-10 15:50 when one of my automations changed the state of a completely different Tado entity (Hot Water) at which point the Tado integration picked up the change to Ensuite that I had made many minutes earlier.

It seems like changes of state that originate outside of HA are not detected for some types of entity until HA makes an explicit interaction with the Tado backend. This isn't the case for all types of entity / all state changes. For example, Tado person presence and device connected/disconnected state syncs regularly and in a timely fashion.

home-assistant.log.gz

While I have your attention might I ask a question that I have been unable to find an answer to in the Tado integration documentation...

I am able to set the operating mode (off/auto/heat) easily for my Tado device 'Water Heater' (my gas boiler) from an automation by calling the service 'Water Heater: Set operation mode'. I have several Tado zones (rooms) where I would like to be able to do the same for the central heating but I cannot for the life of me figure out how to do this. For example, say I have a zone called Bedroom, I'd like to be able to, from an automation, set the 'heating' state for that zone to off/auto/heat. Any pointers or examples that you could share? Scenes do not work since the climate state set in the scene is not specific to the scene; it just takes effect immediately (though maybe I am doing it wrong).

erwindouna commented 3 months ago

Thanks for the thorough output, @ChrisJ60! I will go through the log output a bit later.

There's a difference in how certain Tado devices may update. This is intended and agreed with Tado. Since HA is not officially supported, they do allow our traffic, yet we have to comply with some agreements. DeviceTrackers are allowed to call every 30 seconds for an update. Other devices are allowed to actively ping every 5 minutes. Pushing data, to set new state are instant.

This would explain your small delay. Did you experience any bigger missing gaps? I'll try to analyse your logs a bit later.

craigmcfly commented 2 months ago

I don't know if this is missing data, or the wrong field being populated, but when the thermostat is in Auto (OFF), HA doesn't always set the setpoint temperature to OFF, it just sets it to the current temperature being reported by the room.

Screenshot 2024-08-09 at 00 30 05

If I set it to manually off (i.e. not by a timer, but me dragging the slider down to OFF) then HA hides the setpoint, which is what I would expect.

This is in 2024.7 (2024.730)

DaRockTR commented 1 month ago

Has this issue been fixed by now? I am still holding up on the update to current HA core which works fine but at some point it will generate other issues. I am quite reliant on the tado integration working :(

dhoeben commented 1 month ago

Has this issue been fixed by now? I am still holding up on the update to current HA core which works fine but at some point it will generate other issues. I am quite reliant on the tado integration working :(

For me, there are no issues. It is slow sometimes, so the climate state changes after 1-30 sec after selecting it on the thermostat. When changing in Home Assistant, the thermostat updates almost immediately. So I guess polling rate is too low. Still it works!

dennis07527 commented 1 month ago

I don't have the issues for quite some time now, but not sure if it is fixed definitely. Should give it a try and otherwise restore from your backup :)

DaRockTR commented 1 month ago

thanks for the quick reply. I will do a full sd backup (anyway long time due) and update. Will let you know how it goes.

trizmark commented 1 month ago

I can confirm that the integration is working OK. I'm on 2024.4.3 with no issues.

DaRockTR commented 1 month ago

I think the integration works (at least it did for around 12 hours) but the whole update to current HA core messed up my complete system to a point I had to restore back to previous state. I should have know. Never change a running system.

dhoeben commented 1 month ago

I think the integration works (at least it did for around 12 hours) but the whole update to current HA core messed up my complete system to a point I had to restore back to previous state. I should have know. Never change a running system.

What happened? Normally core updates dont mess up your system to this degree...

DaRockTR commented 1 month ago

I think the integration works (at least it did for around 12 hours) but the whole update to current HA core messed up my complete system to a point I had to restore back to previous state. I should have know. Never change a running system.

What happened? Normally core updates dont mess up your system to this degree...

No idea really. I think the step was too big between the updates as I did hold back on updates due to the Tado integration. Not only the core but also many other things. It messed up HACS for example and most of the stuff related to it.

erwindouna commented 1 month ago

Has this issue been fixed by now? I am still holding up on the update to current HA core which works fine but at some point it will generate other issues. I am quite reliant on the tado integration working :(

For me, there are no issues. It is slow sometimes, so the climate state changes after 1-30 sec after selecting it on the thermostat. When changing in Home Assistant, the thermostat updates almost immediately. So I guess polling rate is too low. Still it works!

With Tado we have agreements they tolerate, that HA is allowed to poll every 5 minutes for updates made on devices/bridge to be synced with HA. For mobile devices, specifically useful for the geolocation, we handle a 30 second poll. Updates made in HA, towards Tado are instant. Any "slowness" experienced there would be between the Tado device, Tado bridge and internet connection to the cloud.

erwindouna commented 1 month ago

No idea really. I think the step was too big between the updates as I did hold back on updates due to the Tado integration. Not only the core but also many other things. It messed up HACS for example and most of the stuff related to it.

Sorry for the delayed feedback, but indeed this is resolved. Sticking behind on such "old versions", with your valid argument, can indeed lead to bigger compatibility issues when upgrading. I hope you can resolve them quickly. :)