I have just tried it according to your instructions and unfortunately still no success.
I really don’t understand what the difference is.
I’m afraid the behaviour didn’t change a bit. Same set of errors using the fix provided 3 weeks ago.
OK. One more thing:
Custom components require translation files to be added manually.
They are not in @dmho s repo, because these files are generated for core components.
That’s why the dialogs with the URL and verification codes are empty, when you click on Reconfigure.
Quick fix: Copy custom_components/tado/strings.json to custom_components/tado/translations/en.json.
The error Device login flow status is PENDING appears when PyTado fails to get a new refresh token during startup. I don’t know why this happens, it might be fixed by the PR in version 0.18.14, which you can set in mainfest.json. Fix threading lock by erwindouna · Pull Request #206 · wmalgadey/PyTado · GitHub
It could also be something else, like a network error or something with Tados auth server.
I have this problem every few weeks (with PyTado <0.18.14), but clicking “Reconfigure” and re-authenticating fixes it without any problems.
1 Like
I’ll try it out later…
edit:
I have just tested it, i.e. created the en.json and set the version to 0.18.14.
Still the PENDING message
Even after clicking “Reconfigure” and reauthenticating with Tado again?
yes, unfortunately the message remains.
Tested following this instruction along with previous ones (doing a full restart before copy the module), but same error. Quick “Index out of range” and end with PENDING issue, no matter how many times I hit reauthenticate, it last just a couple of seconds.
“requirements”: [“python-tado==0.18.14”]
And en.json created.
same here
[%key:common::config_flow::abort::reauth_successful%]
and then
Failed to set up: Device login flow status is PENDING. Starting re-authentication.
@virusczz @JDaniel, I went through the same trouble today and fixed it as it was mentioned in other posts before. In the manifest.json file, you have to add a new line stating the version of HA. Like this: “version”: “2025.5.2”. You can get your version inside the about tab in HA.
I don’t think that’s the issue in this case. The version field is mandatory in the manifest.json. You know it works because HA display an icon along with “Overwrited by custom integration”, otherwise it won’t load the integration at all. As far as I know, the value of that field is not relevant.
Have tried all sorts of suggestions here and found that none fixed the issue for me. Seems winter came and went and there is no fix in sight. Pity, as there was some data I used from Tado in my automations, but had to find an alternative. Seems that the Tado-X integration is either not being worked on, or not anyone’s priority unfortunately