I use the exact same workaround and I’ve timed it several times. The average time between person detected/button press and the announcement/streaming of the video on the nest hub is about 7 seconds. Far from immediate but good enough for a hacked together solution.
This is interesting and a promising development. Unfortunately I have the battery doorbell pro and I can’t even see the device to add it as the trigger in Google home when creating a household automation. It seems they’ve only enabled this for the wired versions of the doorbell. Unfortunately par for the course with Wyze to add a feature to one device in a product line but not others.
Instead of all motion detected they definitely need to change it to trigger on person detected only… That’s a no brainer, otherwise you’ll get a ton of false positives. The hacked together solution several of us use of doorbell person detection/button pressed+Wyze rules+Wyze plug+Google home automation to make Google home household announcements and streaming to nest hub screen proves they can make this work if they want to.
It’s the Video Doorbell v2, as I noted up there 
. 
Since you mentioned that, I decided to poke around in Google Home and saw this:
I guess I have something else to try playing with now, because I don’t recall seeing that as an available option before. I’m guessing that showed up at the same time as the voice notifications that @Levistras mentioned.
My bias would be to have it triggered on a doorbell press, but ideally it would be user-selectable for either case.
You certainly have my vote. 
I haven’t timed multiple trials, but I believe your data. What I quoted above was for a single trial, but without timing it I feel that the sequence happens faster sometimes.
1 Like
Looks like there is positive progress going on in the backend with the developers even if they aren’t updating in this thread which is promising. I can only hope they add it to all the doorbells and not just the v2. I don’t have a low voltage line from an existing wired doorbell so I’m stuck with the battery pro.
1 Like
Our team added the AI detection announcements to try and give you folks in this thread some similar functionality. We are still being told by Google that button press announcements are not available to third parties — I’ve seen the posts in here about Tuya and similar and passed them along but if they don’t give us API access to whatever Tuya/etc. are using there’s not gonna be much we can do here. I’m assuming there’s a reason it isn’t in their API documentation other than as a feature that can be declared as supported by the hardware (which doesn’t help us integrate).
Just an aside, my role isn’t as a community manager or on product directly—I’m actually in charge of TikTok—so I may not be able to keep you folks posted for updates here. Please let our volunteers and relevant employees keep you folks posted. 
3 Likes
OMG! Actually, I can now see VDBv2 showing an option for a starter of “Doorbell Rings”!!! But no AI detections for automations/rules:
I haven’t tested it to see if it works, but it is now showing “Doorbell is Ringing” as a starter option!
Did you have that backward? I didn’t see AI detections on any of the camera models, and none of the other VDB’s had anything, just the VDBv2 showing “is ringing” as a starter. Hopefully that is the same as pressing the button.
EDIT UPDATE: OK, so the above screenshots were in the Automations section. I guess the “Voice Notifications” for AI stuff is actually in the camera settings, but not in the automations/rules starters/triggers:
Again, the above is only showing up on the VDBv2, not the others at the moment.
I’m not sure how to pick which spaekers/displays will do the voice notifications or how to schedule WHEN it should do the voice notifications though 
I don’t want it announcing everything on my toddlers’ speakers while they sleep, but I would like them on my office display and kitchen display.
Yeah I just checked and that’s still not showing up for the Doorbell Pro. Looks like they’ve limited the implementation/availability of this feature to the new V2 doorbell only, at least for now.
I dig. I tagged you previously because you’d provided input earlier in this topic, so I figured it was reasonable to expect your voice as official Wyze word on the matter. Thanks for taking the time to provide an update!
Yeah, I’m seeing it as a Household Automation Starter option in Google Home, as well. I won’t be able to play with it until later in the week, but that seems like an encouraging development. Thanks for pointing that out!
Right. That’s what @Levistras pointed out earlier in a different topic:
1 Like
When you’re building your Google Home routine, what happens if you choose + Add action > Communicate and announce > Make an Announcement > [enter your message] & select Play on > Custom device(s)?
Isn’t that in one of your screenshots? There’s a Conditions section for setting Time and days.
I’d do some testing myself, but I’m not currently in my Video Doorbell v2’s physical location.
Thanks! I will try this.
That works for the “doorbell ringing” starter in the automations section, but I was taking about the voice announcements toggle.The voice announcements toggle (for AI detections from the camera) didn’t exist as a starter option and can’t be used in the automations area. We turn them on as a toggle in the camera settings area, but it doesn’t let me choose which speakers it should do those voice announcements on. It might be an oversight.
Yeah, I dunno, and I won’t have an opportunity to test this myself for at least a few days, so I appreciate your feedback. In any case, it looks like at least some progress is being made on this, since new stuff is appearing where it wasn’t before, so that’s encouraging.
(I say that and then I think about how some things in Google Home/Assistant have recently begun behaving differently, and not in a good way—completely unrelated to integration with Wyze—which is frustrating, so I imagine that it’s frustrating from a third-party developer standpoint when the ecosystem you’re trying to integrate into is moving fast and breaking things.)
2 Likes
First off. Thanks @carverofchoice I used your workaround to get my vdbv2 to show my doorbell on my nest hub.
I do see the button is pressed starter as an automation but I haven’t had any luck with it actually working. The trigger just doesn’t seem to work. Again, using the workaround to turn on my v4 in the wyze app then have a Google automation show the camera has worked.
I also tried having the VDBv2 use the voice commands on the Google homes. But those seemed to be very delayed >1 mins. So this workaround has been nice.
I bought this and installed just today. So far I am very pleased with the functionality.
As for which device you want the announcement on, I believe you can set this in the Google home automation. I don’t have any in my kids room, but it’s nice to get the notification throughout the house and even in my back yard. I moved the basement one outside.
1 Like
So I just recently bought and installed a Wyze doorbell v2, I tuned on Google home “voice notifications” for the doorbell but I’m in the boat where my Google home speakers now announce ANY PERSON WALKING IN FRONT OF THE DOORBELL.
So annoying as I take my dog out multiple times a day and my family is pissed off that the speakers wake them up at 6am or whatever because I passed in front of the doorbell
I’ve seen people doing workarounds with Wyze plugs and rules but do we know if Wyze and/or Google is working on this issue so that we can control the voice notifications to only happen when the doorbell button is pressed?
My workaround now is to turn off Google home voice notifications when I go to bed and then turn it back on the next day when everyone in the family is awake. Not ideal
Great to hear the team is working on stuff Jimmy! I hope that this notification stuff between Wyze and Google home can be worked out. All we want is a proper notification on the google home speakers when someone presses the doorbell. I hope it happens soon.
1 Like
Ya unfortunately it seems the workaround I did, doesn’t last for some reason. Within a day the door press to speak on the Google home minis stopped working.
I have had zero luck getting a doorbell press to work. Even though, Google Home lets you create an.automation action. Seems only smart alerts get announced and that is overkill. Would seem if they treated doorbell press as a smart alert that could work.
There has to be an easy solution to this between Wyze and Google. I’ve read earlier in this thread that Google does not allow 3rd party doorbells to trigger doorbell presses which seems stupid if true. If Google wants Home to be the automation hub for people, it has to work correctly with 3rd party providers, not just Google products.
The doorbell has the ability to communicate with Google Home already as people are receiving alerts for every event, surely it’s just a matter of fine tuning this behavior to only trigger events for doorbell presses, or at the very least have a toggle option for people that want more alerts to announce.
3 Likes
Based on reported experiences with other third-party products, I’m not convinced that this is actually true. 
1 Like
Nor do I, so I assume there’s some communication gap here between Wyze and Google. I hope this gets sorted out.
3 Likes