TV Streamer not being recognized as Thread Network for matter devices

[danpryan]

Hello All,
I have been having the hardest time connecting my Aqara P2 Sensors to my existing Google Home. I’m on the most updated version of iOS on and iPhone 16 Pro. Every time I go to add the Aqara P2 Sensor it says “add to iOS and Google home” then says setting up then says there is no thread border router, but I have two Google TV Streamers on the same WiFi network/in the same Google Home app ecosystem, which those are both capable thread border routers. Both Streamers have the Thread network setting enabled. I have factory reset both TV Streamers, I have factory reset the Aqara P2 Sensors, I have deleted and redownloaded the Google Home app. Any other ideas? I downloaded an app called Flame and it looks like it can see the Thread Networks existing on there but for whatever reason Google Home is saying they don't exist.

[arm_dpe]

Thanks for sharing. It will be helpful if you can share the screen video of the entire process. Also, make sure that Local Network access is enabled for Google Home app in iOS settings. Additionally, could you please share the model for your Google TV device.

[danpryan]

Yes local network is enabled. I’m not sure what you mean by model but it’s the Google TV Streamer box. 

[arm_dpe · Accepted solution]

Thanks for sharing, the team is currently looking into this. Meanwhile, can you please share the video of the pairing process where it fails to add a thread device. 

[Isidora84]

First

[KRKovach]

I just bought the google tv streamer and a Yale / Google lock (the new one).. i'm having the same issue. Has this been fixed? 

[danpryan]

Still not fixed. I downloaded the Nanoleaf app because it shows what Thread Networks are enabled on your system and I have 3 Nest WiFi pros all on one thread network and then when I enable the thread router setting on the streamer instead of joining the existing network it creates a new one. I tried this with a new Nest Hub and that connected to the existing WiFi Pro thread network no problem. It’s just the Streamer where the Thread Network doesn’t join the existing network and doesn’t work. I tried to turn off the other thread networks and only leave on the streamer and the thread device won’t even recognize that it exists. Streamer must’ve been half baked when they released it.

[arm_dpe]

Thanks for sharing. Our team is currently working on the fix. We will keep you updated as soon as we have more information.

[cncb]

It seems like this hasn't been fixed.  I am trying to add a matter over thread device to Google Home but it states that a Thread Border Router is needed when the Google TV Streamer 4K is only a few feet away with the Thread network enabled.  This along with my WiFi Matter devices constantly showing offline (in just Google Home) has made the whole Matter experience with Google pretty awful.

[arm_dpe]

Thanks for sharing this. The team has implemented multiple fixes recently and with recent Google Home App version this should be fixed. Can you please check with most recent app version and let us know your experience.

[cncb]

I already have the latest version of the Google Home app.  Is there a Google TV Streamer update that I have to manually install?

[edmcman]

Ever find a solution?

[cncb]

No, I just gave up on using Thread and Matter (Wi-Fi) with Google Home because nothing seems to work.  I don't have these problems in Alexa.

[edmcman]

I returned the streamer and got the Nest Hub gen 2 and it started working almost immediately. Sounds like there's probably some software issue with the streamer. 

[cncb]

Interesting.  I have a Mini that also does not work with the Matter Wi-Fi devices.  You may have found the only Google hub that works correctly.

[JurgenVH]

Same here, new google streamer. Doesn't work at all with matter. Keeps saying 'thread borderrouter not found'...

[heftycookie]

Same here. Bought a brand new one and I can see the thread network via google settings but it's listed as unavailable. I spoke with Google tech support who ran me through a bunch of diagnostics only to tell me "welp, you should probably exchange it for a new one. Its defective".

So I did that. And this new one also behaves the exact same way: while attempting to connect devices, it can find them but Google home app shows the "your device requires a border router" dialogue and the thread network shows as "unavailable".

This is with latest firmware and app versions of everything.

What's the solution here?

[edmcman]

I stated it above but I returned it for a nest hub gen 2 and it all worked immediately. All of this has really made me reconsider using google home for my smart home. 

[danpryan]

I punted on this and returned and sold everything I had Google. Got the streamer over a year ago and support ran me in circles doing factory resets and saying it was only my device and that it’s because my matter devices weren’t compatible and that it was a software bug that they fixed but never did so I just gave up on it and switched to HomeKit for everything smart and matter related and swapped all my cameras for Unifi since they are locally stored (no more monthly subscription fee). Couldn’t be happier and saved me money and headaches. Sadly Nest was the best smart home brand until they were bought. 

[edmcman]

Same. HomeKit works so so so much better. Not having to pay a subscription for my doorbell using HSV is so convenient.