It’s “bated”, but I appreciate the thoughtful response. 
Sorry sounds a little more than misleading and it seems a false claim to state “works with hey Google” if you don’t. You don’t. Perhaps you should state “We maybe could work with hey Google”.
This is a requirement for us to have in order to have the functionality where you can ask a voice assistant to show you the camera feed. We will not be removing that functionality while we wait for Google to make it possible for button press to be integrated, so the logo will have to stay.
Here’s Google’s page about the “Works with Google” badge program if you would like to give them feedback on it — looks like there’s a contact form at the bottom of the page:
4 Likes
finally a way to advocate vs complain to Wyze ! Please give us the phraseology of what to request from Google.… it’s a drop in the bucket maybe you never know what one drop can do vs nothing…
Thanks
1 Like
Hello,
Would it be possible for Wyze to become “Works with Google Home” certified? After reading the article from the link you posted I noticed this:
It seems that the additional compatibility we all want may be from a different certification than the one Wyze currently has. I am unfortunately unable to access the purple link in the picture to learn more because I am not a Google partner/ company that works with Google.
It may be worth reading the “Works With Google Home guidelines” link in the article you posted, if you are able.
1 Like
I have an unbranded Tuya Video Doorbell integrated with my Google Home and everytime someone push its button a Visitor Annoucement occurs on all my google home devices.
I bought Wyze Video Doorbell v2 recently but was forced to revert back to my unbranded Tuya compatible doorbell in order to keep receiving Visitors Announcement on Google home devices.
Anxious to get this feature available in order to turn my Wyze Doorbell v2 back on!
2 Likes
Thanks. How do you like that doorbell. Wyze clearly has no intention of actually have true Google Home integration.
Wyzejimmy,
Any comments on how another non Nest Doorbell has integration and Wyze can’t or won’t provide? Yet another example of integration that Wyze can’t achieve. Have you actually even asked Alphabet for access to the API that does stuff?
And why haven’t you responded to the inquiry about:
“Certified Works with Google Home”?
Bill
Making some quick research on Google Developer website I found below URL that explains traits, commands or events related to Wired Doorbells managed by Google SDM (Smart Device Management) API:
As you can see on below screenshot, DoorbellChime is a trait related to doorbell button press events.
This link refers to Nest Doorbell Wired since it’s supported on SDM API, but I understand it’s valid for any SDM API compatible device.
2 Likes
I want this feature as much as anyone (see my prior posts), but to be fair, Jimmy DID respond to that:
In short, what counts as “Works with Google” and using that badge is defined by Google, not other companies. There are a set of guidelines for what a product has to support to say it “Works with Google.” As long as a company meets those standards (which Wyze does), then they are permitted to use that badge.
They even clarify:
Works with products are compatible with Google Assistant-enabled devices but do not share the same capabilities.
Google could change the standards if they want to.
If people believe that Google should change the standards, then that is feedback to give to Google. Google accepts several ways of giving them feedback about things like what “Works with Google” SHOULD mean. You can review those options here:
Again, I am also pushing for this feature, and I personally believe it can be done now since others are somehow doing it, including a fairly generic TUYA device. Hopefully Wyze can figure it out.
Also, thanks @ejuliao2000 for providing a helpful reference! I’d love to see this happen natively.
I do currently have this working on my Wyze VDBv2 through a workaround (I have a Wyze rule send an "“On” command when the doorbell is pressed, and then have Google home watch for that On Command and then play a sound when it happens, so now, anytime someone presses the button, my Google devices play a sound just like we’re asking for, but I would like for this to be built in to make things easier and more intuitive for everyone.
I also hope this is the case. As I’ve said before, I’m not angry and can’t speak for anyone else, but I think I share some frustration and disappointment here about Wyze’s practice of seeming to promise an integration in the marketing of a product (i.e., the original FAQ for the VDBv2 that–at the very least–strongly implied that Google Home/Nest devices could be triggered as accessory chimes out of the box) but then walking back that message with a kind of “Well…no…what we actually meant to say was…”
I think what adds to that frustration is the opacity of the messaging from Wyze about how they’re actually addressing the issue and when users might be able to expect such a feature to be delivered. I have difficulty accepting a we’ve-done-all-we-can-and-can’t-do-more-at-this-time answer when it seems relatively clear–including @ejuliao2000’s most recent example–that other companies have already done the work to make this integration functional. What I would personally find satisfying would be a statement of genuine contrition like “Y’know what? We over-promised, and that’s on us. We’re in the process of remedying this and making it work like it should, and we will regularly update this Topic as we make progress toward that goal. Please be patient, because we’re going to make this happen soon.” That’s not really what I’m seeing here, and that’s disappointing.
This does work, and I genuinely appreciate @carverofchoice’s helpfulness in directing me to @Thesilente’s detailed post describing the work-around. In my case, I’m using a Wyze Plug, two Wyze Rules, and two Google Home Automations to accomplish this:
- First Wyze Rule: IF Doorbell is pressed, DO turn off Doorbell Trigger (Wyze Plug).
- First Google Home Household Routine: Starter Doorbell Trigger turns off, Actions Announce to household “Someone is at the front door” and Stream Front Doorbell on Home Hub.
- Second Wyze Rule: IF Wyze Plug (Doorbell Trigger) has been off for 1 minute, DO turn on Doorbell Trigger. (This is the trigger reset so that the next doorbell button press can act on the rules again, and it also starts the next step so that the video stream will stop automatically.)
- Second Google Home Household Routine: Starter Doorbell Trigger turns on, Actions Go Home (to reset Home Hub).
Personally, I think it’s awesome that people smarter than I am have figured this stuff out and given me the tools and knowledge to customize the Rules and Automations in a way that works for me. I like that flexibility, even if there is some lag between the steps. Having said that, though, setting up these kinds of automations and triggers should be optional–something a user might want to do with the realization that not everyone has the desire, willingness, curiosity, or capacity to do this–and I don’t think it’s unreasonable to expect something similar to this to work out of the box and with minimal lag (and without additional hardware, like a Wyze Plug or spare camera, as at least one other user has apparently done), especially when other hardware vendors have apparently figured out how to make this work.
1 Like
Wyzejimmy: So why can yet another 3rd party doorbell work? And Wyze not. Have you asked for whatever API others are using?
Seems they have access to a better API or Wyze just doesn’t know how to do it.
1 Like
@Crease, regarding the work-around you implemented to get Visitor Annoucement on google devices, I got curious regarding the delay you have between doorbell button pushed up to voice announcement on google devices.
Can you share how long does it takes to annouce?
PS: Using native integration (my unbranded Tuya doorbell) it takes like 1s (one second) between button pressed to voice annoucement.
Sure! When I tested a few minutes ago, there was a delay of roughly 1½ seconds between the button press and the actual ding-dong of the house’s built-in mechanical chime. I’m okay with that, and I expect that’s a function of how the Doorbell and Chime Controller work together to moderate power from the transformer so that the Doorbell has enough current to maintain power while the Chime Controller discharges to actuate the chime.
The announcement on my Google Home devices (a display and several speakers) didn’t begin until around the 12- or 13-second mark. I have this vague feeling that sometimes that lag is less, but this is the first time I’ve actually tried to put a number to it. It’s never anywhere close to immediate. It seems acceptable for now because I don’t have a better solution, though I can’t help thinking that a more-or-less direct API call from the device to the Google cloud would have significantly less lag than a device triggering a rule in Wyze’s cloud, which begins running and then has to make a call to Google’s cloud, which begins running its own routine and then has to make calls back to several devices in the home to initiate the announcement.
Wishful thinking....
Even better would be if this could all be handled locally with Matter, but I think that’s asking a lot right now, and I’m not yet prepared for the hardware replacement just to shave time off the interaction, especially since this doorbell is so new. I don’t know what Wyze’s plans are for Matter compliance, and I think something like this would probably require Google to develop and open a different API, so I’m not holding my breath for any of that, but it’s kind of cool to imagine. Anyway, that’s beyond the scope of this Topic.
Thanks for joining the Forum and offering useful participation, @ejuliao2000!
1 Like
Unfortunately, the lack of this ability (without a significant workaround) is the only barrier to me buying this doorbell. Hopefully, this feature can be added soon.
‘one other user’ here 
I can confirm using a spare camera is still working well, but still has a bit of a delay triggering the notification to my Google Home/Nest speakers. It is “good enough” for the moment but like all of you, proper integration with the button press event would be better!
Using a spare wyze plug outlet would be a slightly better experience as I wouldn’t have to rely on my collection of cameras to trigger events to turn my ‘trigger camera’ off the doorbell is pressed.
If I only had the doorbell and a camera to act as the trigger, I wouldn’t recommend my solution.
My timing is similar to mentioned here, about 1-3 seconds from button press until the mechanical chime triggers, and then an additional 10-15 seconds before my google speakers alert me. In rare instances the speakers take upwards of 30 seconds to react, and in very rare circumstances they don’t trigger at all. I see this very rare frequency of automation events just not triggering on other devices as well, I have some Kasa/TP-link switches that sometimes fail to trigger on occasion.
2 Likes
Yeah, and I like that the Plug and Plug Outdoor both have “Has been on for” and “Have been off for” as available conditions for rules, because that makes it easy to program the reset. I wasn’t able to find the Plug 2-packs on sale that @carverofchoice mentioned in another topic (though I stumbled upon a similar clearance for the Plug Outdoor in November), but I was able to shuffle some other stuff around and use a Plug as my “Doorbell Trigger”. (It’s just got an air freshener plugged into it otherwise, so it’s still serving a purpose by being on and having that turned off for a few seconds during the reset phase isn’t an issue.)
1 Like
As @Levistras noted in another topic, the “Voice notifications” option appears to be available now in Google Home; however, I haven’t yet noted any discernable effect after enabling this feature in my limited testing. For what it’s worth, this is what I see when I go to the doorbell’s device settings in Google Home:
Thanks, when I enabled Home App there is text that says “notifications may also need to be turned on in partner app”
So probably Wyze needs to do something. And given there lack of support probably have no idea that option is there now.
Wyzejimmy care to provide any useful information .
This was my supposition, as well. I’m also eager to hear from @JimmyHa and/or @WyzeJasonJ, as I mentioned elsewhere. If that’s the case, then I also hope to see the status of this topic updated from Maybe Later to In Progress sometime soon (as vague as “soon” is).
@morgawf1
Mine are working. I get voice notifications on my google home speakers now for both motion detection and doorbell button presses. It’s rather nice.
But I have turned down the motion detection sensitivity to 1 and scaled back the detection area so it essentially doesn’t alert for motion any more. I don’t want it alerting the whole house when I step out to go to the garage.