Hey all, we got a good build that our beta testers confirmed late on Friday that resolves the issue experienced by our testers that matches what has been reported in this thread. We will be having our release go/no-go meeting in the next couple of hours and likely be targeting a release of updated firmware for Thursday (I believe the plan for this one will be to announce in advance [today] on the community forums).
In order to receive the update, the hub will need to be online and talking to the servers. This could take the form of:
- If claimed, plugging the hub into ethernet until the update is completed. At that point if the hub was originally setup with Wi-Fi you should be able to move it and have it connect on next power on.
- In not claimed or if Wi-Fi is unavailable, going through the setup process again should allow the device to connect and download the latest updates.
Thank you all for your help in diagnosing this issue and your patience in waiting for a resolution. This particular issue required specific timing on startup (influenced by a confluence of factors) resulting in the failure that resulted in it not being hit by a majority of customers as well as anyone in our internal alpha/beta/rc test pools as well as QA testing. With info from the beta testers, we feel confident that we were able to isolate the root cause (and source of nondeterminism) and have the right fix for this issue.