With the Tado app v1.4.2 keep getting the error “Token cannot be refreshed” for all my devices when a flow is triggered. The devices don’t give an error when I control them directly within Homey. Everything was working fine before the update.
I repaired every device multiple times. Restarted Homey Pro 2019. Still the error persists.
I can’t fix it. Anyone got ideas?
By repairing one of the devices the problem was solved for this person:
Do you get a login prompt when you repair a tado device?
Yes I do get a login page and I can login. According to Tado Homey is logged in. Repaired all devices multiple times.
I can control them within Homey, but not thru a flow.
Removed the app, fixed the flows… Works 2 times and the error is back
the same problem here!
Now I am using Tado zones as a backup. So I have a redundant setup if the Tado app is F#-ed.
Same problem here! 
Same problem here with the new 1.4.x.
Access token is working but refresh token isn’t. So have to repair a tado device nearly every time.
Thanks for the feedback everyone, we’ll have a look at it
Issue should be fixed with the latest test build! Let me know 
Tried the 1.4.3 test build. The errors are gone. Tested it as following:
Results are all good.
Still the same issue here, also with v1.4.3 test build. This issue occurs since 11 March.
I re-tested the experimental version and it still works for me. Does it show experimental on the app page? I had to install it twice before it got installed.
I had the same problem but… After you have connect again to the Tado server you can add and mod your Tado system again. Go to an Tado device in homey, and press repair. Login into Tado and after that you can add.
Works for me, thanks 
After 10 minutes, the token is no longer available and you have to reconnect, or am I missing something?
Does it show experimental if you check the app? Did you repair all devices?
Yes, I repaired all devices.
The experimental version is not available (Homey Pro 2023)
Found it, I had forgotten to add /test to the App Store URL
If people are still experiencing this issue even with the experimental version, feel free to send me a DM with your email address. I’ll connect you with our development team so they can take a closer look!
Just for your information on installing test versions:
