@Solla-topee New update to 3.37.55.2, but still no resolution to the issue. Unfortunately

  @Solla-topee ,
Is there indeed any update on this issue?, because in the recent Google Home App release notes it mentions the following from version 3.36 and newer:
 

• Reduced "no video available" errors: Camera users will see fewer cases where a recent video is not yet available for streaming.

• Camera stream reliability: Fixed an issue where turning a camera off and on during a live stream would result in a "Camera Unavailable" error, ensuring the stream recovers properly

  @Solla-topee 
 

Let’s be real here: TP-Link knows this is misleading.

On your own forums, you admit:
 

• “This is a known issue being followed up on the Google side to resolve…” (Apr 15 post)

• “This issue is still being analyzed by Google side. If any solutions become available, we will update this thread accordingly.” (May 29 reply)

• “Our Tapo Camera features the ‘works with Google Home’ logo… it’s important to note that this logo does not imply that the Tapo Camera supports viewing through the Google Home app, and it does not constitute false advertising.” (Jun 15 reply)
   

So which is it? On the product page and Amazon listings, you plaster the “Works with Google” badge and tell buyers:

“Works with Alexa and Google… use your favorite screen assistant like Alexa and Google with the D225 doorbell camera to view and answer those at your door.”

 

That clearly implies parity with Alexa. But here in the forums, you admit:

• It doesn’t work in the Google Home app (despite the logo).

• You have “no information” on when it will be resolved.

• And you fall back on legalistic language about how the logo doesn’t actually mean app support.
   

That’s not just disappointing — it’s purposefully deceptive marketing. You’re selling this product as if it works with Google Home the same way it works with Alexa, but in reality customers get a broken, half-working experience and then discover in the fine print (or buried in support threads) that it’s “Google’s fault, no ETA.”

Here’s the bottom line:
 

1. Stop advertising the D225 as “Works with Google Home” without a clear disclaimer that it only works on Nest Hub/Chromecast and not the Google Home app. Right now, it’s false advertising by omission.

2. Give customers an honest timeline. If Google told you it may never work, say that. If you have no idea, admit it. Don’t just keep stringing people along with “we’re consulting, no ETA.”

3. Acknowledge the trust issue. People bought this doorbell expecting Google Home parity. Instead they get a bait-and-switch. That’s why you see so many in this thread returning their cameras.
    

Until you come clean, TP-Link is burning its reputation. This isn’t about “patience”, it’s about honesty.

@nfenster I completely agree with you.

I bought a Tapo camera months ago specifically because it was compatible with Google Home.

I replaced a low-quality camera that worked perfectly with Google, and now I have a Tapo camera that's fine on its own, but it hasn't worked correctly with Google Home for months. I expect clarity and transparency, but unfortunately, right now, Tapo and Google are just blaming each other, and no one is fixing the problem.

  @ClaudioLR 

I have reached out to Google as well. As far as I am concerned, both companies are at fault here.