Same here last weekend, not the first time this happened unfortunately.
I was only able to relink through the Homey app, browser progress wheel kept running indefinetely.
All these annoying things just dim my initial Homey enthusiasm.
The issue seems to be known since August 3rd: https://github.com/athombv/com.tado/issues/16 @Bram Is there any news about when this issue might be fixed? Since my presence detection works pretty much based on Tado, all the automations that work with this currently fail to execute properly. The WAF of Homey is dropping every day now.
A few weeks ago I noticed that the connection between Homey and a number of tado devices was broken. If I remember correctly this was after a Homey update (experimental) but it could also have been an update of the tado app.
I think I solved it by removing all tado devices and adding them again, but I do not know for sure. In any case, the tado app has been running here for a while without any problems. tado v2.0.1 on Homey 1.5.13-rc.11 (experimental).
About the development of the app. I stopped after version 2.0.0 was completed. Further development is now in the hands of Athom.
Removing and re-adding the tado devices is only a temporary fix. The problem comes back as soon as there is a single issue with contacting a device, e.g. internet disconnects or even a simple timeout. A single failure to connect permanently marks the device as unauthorized and then no further attempts to connect are made.
Is there any way to roll back until the problem is fixed?
Right: remove and readd the devices only Works for one or two days. Then the chains are seen as the device icon.
When @OpenMind_NL was the Developer of the app you could be save that the issues were fixed. But from the Point of Athom develope the app nothing is made. @Bram do you have an answer from your Developer now? It is a heating app! One of the Most important apps now. Music apps etc. can really wait but a heating app which is Broken really sucks!!
I will do some QA testing this week with the Tado app to see if I can reproduce this bug. Please report the issues you have via the “report an issue” button in the Appstore. Try to give a clear explanation what the exact issue is. This way I can forward it to the developers so they can try to fix it asap.