There needs to be a , at the end of L17 to make it valid json
Hi, thank you for testing. I have this infinite spinner as well. It is kind of intended, but what is missing here is the text below the spinner that should normally appear. I have no clue why it doesnāt though, on my dev container it appears just fine:
I did have the infinite spinner initially, but if I click on āreconfigureā manually, I get the following:
Hmm the re-authentication succeeds but 5s later Iām presented with another āauthentication expiredā flow 5s later.
Also had the error 500 on my beta box. Probably still glitchy, letās head to Github and try to provide input for the devs
2 Likes
@jelmer You cool to raise a ticket and post it here? Weāll fill it with logs and any info we have.
Well I wonāt, becuase I think I got it to work. The beta integration (with the core fix) would not succesfully authenticate, but once I again installed the custom component it seems to work now!
Confirmed, I have sensors and control back. Woop woop!
Logged the issue here: Tado OAuth flow succeeds but re-authentication needed after 5s Ā· Issue #141523 Ā· home-assistant/core Ā· GitHub
1 Like
The only thing is I noticed @dmho that all my devices report ādisconnectedā now while that was working perfectly before.
I installed core/homeassistant/components/tado at dev Ā· home-assistant/core Ā· GitHub the folder direct from the HA Core dev branch as custom_component and still get the infinite spinner. Can someone else confirm this? Maybe there are additional files missing that are not included in just downloading the component folder? (that would also explain why it works on beta @jelmer, because any additional changes would be included since the original OAuth PR got merged)
So it might be that one either has to wait for the 2025.4 release for the custom component to work with Tado X or install the beta and custom component
1 Like
Ah indeed itās not perfect yet:
Unexpected device format: [{'serialNumber': 'XXXXX', 'type': 'IB02', 'firmwareVersion': '257.2', 'connection': {'state': 'CONNECTED'}}, {'serialNumber': 'XXXXXX', 'type': 'TR04', 'firmwareVersion': '253.1', 'connection': {'state': 'CONNECTED'}}]
This sort of intended, the Internet Bridge is in a separate List inside the main devices List, which breaks how PyTado parses the API responses. I just added the error message for now, it should not cause any further issues down the line, and there will be a proper fix with PyTado 1.0 
1 Like
Re: connection state:
It shows correctly for devices for me, but zones are shown as disconnected. That is because zones donāt have connectivity information in Tado X, so it just sets False as default.
Typical, it worked until the OAuth changes. No biggie tho
Hi Karl, I allso installed the component you mentioned and am getting the indefinite spinner withoud the text and link below itā¦
1 Like
Thank you for trying. That confirms my suspicion that something else from 2025.4 than just the changes in the tado component are needed for this to work. I donāt have any clue whatsoever though, what might be missing.
So for now, your best bet is to install the beta and the tado X patched custom component, that should hopefully work.
1 Like
I just installed the 2025.4 beta release without any custom components and still the infinite spinner without text appearsā¦ weird.
Oke, finally got it working again. I installed the 2025.4 beta, had to restart my hosting VM and installed the custom component by you Karl.
The authentication finally works correctly and my Tado X devices can be used in HA again. Thanx!!!
1 Like
Installed the 2025.4 beta but still no joy.
HA is now ādiscoveringā a native Tado home configuration as well as the custom integration. The custom integration āNeeds attentionā.
If I click Reconfigure on the custom integration, then click Submit on the resulting dialog box, I either get the infinite spinner, or sometimes the Error āConfig flow could not be loaded: 500 Internal Server Error Server got itself in troubleā or sometimes āUnknown error occurredā
If I click Add entry I get offered to add this to the discovered Tado home, which does nothing, or to āSetup another instance of Tadoā. This sometimes just gives the infinite spinner, but occasionally gives the āTo authenticate, open the following URLā¦ā message. Doing this says the device is already registered, but still the custom integration does not work and āNeeds attentionā.
Appreciate your efforts, but it looks as though there is still quite a bit going wrongā¦
Can confirm got exact the Same issues.
I have currently installed 2025.4.0b1 and your custom_integration package from the link hereā¦
ā¦ and have added the version as known.
Unfortunately it still does not work and I get the messageā¦
āDevice login flow status is PENDING. Starting re-authenticationā