I got the same thing with the same setup (beta release of HA and the custom component by Karl. The thing that fixed it for me was a reboot of the VM hosting my HA install. Only a restart (or a reboot) initiated from home assistant itself was not enough; reauthentication was still unsuccesfull. After a compleet reboot of the server, the reauthentication succeeded and i got everything working again.
Iāve tried rebooting (HA Green) and even turning off and back on. Doesnāt help in this case.
unfortunately doesnāt work for me, I have restarted my Proxmox HA OS VM and still have an āAuthentication expiredā notification.
Under devices >>> tado I see the following messageā¦
āFailed to set up: Device login flow status is PENDING. Starting re-authentication.ā
Same for me. Removed Tado integration and any custom tado folders. Updated to Beta, Tado detected, tried to authenticate but after 5sec error. Added custom tado code as above, restarted VM completely, re-authenticated, but fails after a matter of seconds
The .5 beta killed it for me, now I have the same as the others above
Have any of you gotten tado x to work in homeassistant, or is it just a matter of hoping 2025.4 solves the problem?
it was working fine for me using the custom integration, though this morning (coincidence itās a change to summer time?) I started getting errors in the logs regarding the auth token. Looks like Iāll need to wait until the April release as well.
Thank you I wait until 2025.4 before I doing more
I think I itās working for me again (HAOS on Yellow).
- Latest beta (2025.4.0b9
- Remove Tado integration
- Remove custom component
- Add new Tado integration through OAuth flow
- Add custom component
- Reboot
- Re-authenticate
The heating percentages for rooms still donāt get recognized @dmho , their entity IDās show as sensor.ZONE_none
Apart from that, great that you keep investing in this! 
How do you do this? On my system, the native Tado integration just shows as āDiscoveredā and the only option is āReconfigureā, which doesnāt workā¦
Hey! Iāve tried that several times already, but I always get stuck during re-authentication.
A white modal appears with just a loading spinner, and if I cancel, I get this error:
āConfig flow could not be loaded: 500 Internal Server Error. Server got itself in trouble.ā
I assume thereās something different in our setups, even though weāre on the same beta version and followed the same steps.
Scroll down the list of integrations and click Tado there, and actively remove the integration that needs to be " reconfigured".
1 Like
Oh, I think I got it!
After adding the custom component, I opened DevTools before clicking the re-auth button. When I got the empty modal with the spinner loader, I accessed the Tado login link from the network tab (without closing the modal). After that, the login flow worked!
2 Likes
Well done @polamoros. That has worked for me too, but finding the URL is hard. For anyone who isnāt sure, you need to look in the Developer options within your browser and search for flow_id to find it.
1 Like
I assumed that anyone downloading this custom component to support Tado X on the latest HA beta would be able to find the request under the DevToolsš
2 Likes
Hi there, itās working! You only need to search for the payload under Networking tab in Development Tools in your browser! Thanks for sharing @polamoros! Apart from that @dmho , updating to 2025.03.4 is not solving the login issueā¦ Let us know if we can further test in any beta.
1 Like
Many thanks to @dmho for continuing with this.
Now that it is working (if you do what @polamoros described), I have the following comments about the latest implementation.
- It now seems to find the Tado Matter bridge, which it didnāt before.
- It still does not include any water_heater entity
- Any changes made from HA are immediately reflected in the Tado app
- Any changes made in the Tado app take about 5 mins before they are reflected in HA
The last effect is due to the very infrequent polling by the custom integration, which is controlled by the following lines that appear in __init__.py and coordinator.py
MIN_TIME_BETWEEN_UPDATES = timedelta(minutes=4)
SCAN_INTERVAL = timedelta(minutes=5)
SCAN_MOBILE_DEVICE_INTERVAL = timedelta(seconds=30)
If you update these to poll more frequently then things run a lot smoother. For my own use I have changed these to:
MIN_TIME_BETWEEN_UPDATES = timedelta(seconds=30)
SCAN_INTERVAL = timedelta(seconds=30)
SCAN_MOBILE_DEVICE_INTERVAL = timedelta(seconds=30)
This reduces the lag to a more reasonable timescaleāI have not experimented further though.
1 Like
Unfortunately, it still doesnāt work for me.
I have HA OS with the current 2025.4.0b12 and when I take the URL from the DevTools, I get the familiar error message again after a few seconds.
Did you follow all the steps that @jelmer detailed here?
And after that, did you try the steps I mentioned?
That should work for everyone afaik 
Exactly, I followed the instructions.
However, what surprises me is that after deleting the tado integration and the custom_integrations directory tado, the Custom_Integration logo is still displayed when adding the tado integration!
Only when I restart HA OS or HA alone is it displayed without the custom symbol.
Is this correct?