I recently purchased a Nest Wifi router to add to my existing Google Wifi mesh, in part because it is advertised to act as a TBR (thread border router) since version 14150.376.32 and I wanted to extend the range of my thread network to cover the entire house https://support.google.com/googlenest/answer/13800967?hl=en. Took a few attempts to setup but is working fine now as part of the wifi mesh.
However, the thread side is not working as I'd expect. The nest wifi did not join my existing Nest Hub (v2)'s thread network. Instead it's creating a new thread network every few minutes, like it's stuck spinning. Both devices were setup through the Home app on the same Android phone.
I can confirm I have two different thread networks both through Home Assistant and querying mDNS directly:
- Nest\032Wifi\032Router\032#D991._meshcop._udp.local. can be reached at c158604385632c4a5e4b8e68687dcf65.local.:49152
- Google\032Nest\032Hub\032(0cba)._meshcop._udp.local. can be reached at fuchsia-d88c-7959-aa47.local.:49154
I've tried factory resetting the nest wifi a couple of times, the pattern seems to be:
- After factory reset + setup, it will not act as a thread border router at all
- After rebooting once, it will act as a thread border router and commission it's own new network every few minutes, like it's stuck in an error loop
- After some time, it will stop commissioning a new network id and stick with one
Should I return the nest wifi? I bought it expressly to expand my thread network coverage, and it's not doing that.
