I have been using Tado to control the heating in my house for a while now and it has always worked with no problem.
Recently, when updating to 2024.3 the tado hot water is failing to switch to heat. I downgraded back to 2024.2.2 and the problem went away again but reappears whenever I update back.
Changes in the tado app to the hot water also do not seem to be reflected in home assistant unless I reload the integration.
The rest of tado works fine it is just the hot water.
I am fairly competent user and in my 5/6 years of using home assistant I have always been able to fix my own problems but this one has me stumped and I feel might be a bug in 2024.3.
It looks like the issue has been merged for the next release. Does anyone know when this will be available or if there is a way to install a patch to temporarily fix this?
I upgraded to this version and it worked!! BUT… now its not working again!! not sure why this has broken again. This is really annoying! is this working for anyone else? Is there a way i can get any logs to find out whats going on?
This issue is not fixed. I read it had been fixed in 2024.3.3. I updated to 2024.3.3 and the tado hot water bug is still there for me. Had to downgrade to 2024.2.5 and Tado hot water is back working in HA
Thank you. Yes, after further reading and reloading the Tado integration, all now seems OK on 2024.3.3. Hopefully hot water for a shower in the morning .
I only recently added a sonoff thermometer to my solar water hot tank, so I was now hoping to control my hot water tado on the cloudy days where we don’t have enough hot water.
But I’ve noticed that the automation arent turning the water on.
I was trying to edit the yaml in the automation to something different like;
type: heat instead of the default
type: turn_on
Or is this bug still an issue in the latest home assistant release?
EDIT: I can see in the trace that it says the water_heater domain has a NotImplementedError
In my setup its still not fixed went wrong for me in the same update as OP but still not triggering even tried using a scene in the hope that way would work.
Manual triggering from the device works fine its just automations