(I am the one who tried to incorporate more error recovery logic to the connector)
Yeah this is promising indeed: the theory was that some cloud endpoint changes / issues surface as issues to the client, in such a way that client will remains offline even though cloud would be up. But I guess we have to just wait and see, perhaps only some particular types of errors are problematic, we have never have gotten bottom of the offline client issue.
With the latest openhab, having debug level logging to the cloud connector will reveal errors that were not logged before. Actually, from the logs we could see if the error recovery improvements “kick in” and if the old version would have gotten stuck as offline. You have to enable TRACE or DEBUG level logging for org.openhab.io.openhabcloud
@digitaldan we could also consider tuning the reconnection parameters such that it would be more graceful to the cloud?