Issue Joining Google TV Streamer to existing Thread Network

Configuration Matter/Thread
1

I recently purchased a Google TV Streamer to replace an old Chromecast that was falling offline intermittently. One of the selling points (for me) of the Streamer over a traditional Chromecast was that it has a built in Thread radio. While I’d say my Thread network is in its infancy as far as client devices (I currently have 6), I do have pretty solid reliability/coverage with the TBRs listed below:

  • (3) Nest Hub v2
  • (1) Nest Hub Max
  • (1) Home Assistant SkyConnect

When I decided to build a Thread network, I purchased the SkyConnect (I already had the Nest Hubs and Hub Max). When I commissioned the SkyConnect and installed the OpenThread Border Router Add-On and Thread Integration on Home Assistant, I was able to see an existing Thread network that was automatically created by my four Google devices (as expected). All four of those devices were already on the same Thread Network. Luckily, Home Assistant allows you to select your preferred Thread Network to join, so I did that. Therefore, I have a single Thread network with (5) TBRs showing correctly in the Thread integration within Home Assistant. This setup has been working to commission, monitor, and operate Matter-over-Thread devices.

So naturally, I bought the Google TV Streamer 4k when I needed to replace the dying Chromecast. I commissioned it with the Google Home app (with ethernet connected initially) and the normal cast/control features worked fine. Then I went to the Thread Integration in Home Assistant to make sure the Streamer joined my existing Thread network, and it did not. It had created its own separate network.

I understand that Matter devices can talk to each other over ethernet, making it possible to have multiple Thread networks without causing interruptions, but not having these devices on the same network defeats the purpose of Thread altogether in my opinion - the reliability and performance associated with a strong mesh network. If I was going to have multiple Thread networks, I would have just gone the Matter-over-Wifi route.

I have factory-reset and recommissioned the Streamer twice, one of which I unplugged the ethernet cable and commissioned using the same wifi network as the Nest Hubs to no avail.

Has anyone been able to get their Streamer to join an existing Thread network? Any suggestions?

2

Did you setup the Streamer with the same phone used to setup the previous Nest and the SkyConnect?

If you are using another device, the Thread credentials might not be there and that’s why the Streamer created a new one. Google introduced few months ago a way to save the credentials in the cloud, but before September 2024, the credentials were only stored in the phone.

3

Yes, I used the same phone for the original Streamer when it set up its own Thread network. I’ve since purchased a second Streamer and coincidentally got a new phone before onboarding it. The second Streamer is having the same issue while commissioning on my new phone, even after syncing the credentials via the Home Assistant Companion App (Android).

You mentioned Google introduced a few months ago a way to save Thread creds to the cloud. Is there a way to force it to sync and/or manage them? I’m wondering if my Nest environment has Thread credentials saved and it’s using those instead of the creds I sync to my phone via the Companion App.

I did test adding a Matter-over-Thread device by resetting an existing device and re-adopting it using Home Assistant. It correctly passed the Primary Network’s credentials to the device and worked as it should. Therefore, I know it has the correct credentials (or at least the Home Assistant app on my phone does). Can/will the Google Home app use a different set of credentials since it can sync to the cloud and how do I force a sync?

4

Last time I checked it was automatic and there was no way to manage anything or even delete them.

Just came across this article, don’t know the state of the feature since I no longer use Google Home speakers / displays, it’s indeed there in Settings - Google - All services - Thread networks:

I guess eventually Thread border router vendors will make it easier for all to join the same network, so far the mechanisms are there (APIs to share credentials) but they don’t seem to use it.