Wanted to cross-post this update from the official thread where we're tracking and posting updates on the issue.
We're in the process of exploring cloud-side solutions that will help individuals with no physical access to their hardware to get back online. We'll provide updates on that effort in the thread above.
I'd like to expand on this comment from Matthew. A key tenet of our platform is that we should abstract away connectivity management from our customers and ensure that devices automatically reconnect to the Cloud when their Internet connection is interrupted.
While a hardware watchdog is a great second line of defense that a customer can implement at the application level, I want to make sure it is clear that our team is pursuing a range of platform improvements as a result of this issue which include:
- A cloud side fix that automatically assists devices stuck in this reconnect loop to successfully establish a new session with the Cloud
- A Device OS improvement (scheduled for 1.2.X) which would make stronger guarantees that a session is never reused more than a certain number of times (which will also prevent an endless reconnect loop)
- Infrastructure-level improvements to the caching system which minimize the likelihood and impact of similar failures in the future