I totally agree that it ‘should’ work. Its the reason I bought the doorbell in the first place. I’m hoping the engineers are working on fixing it and this was something that didn’t quite make Google certification in time for the launch but we’ll see it soon… But Wyze hasn’t made any comments about it being absent that I’ve seen.
No, it doesn’t work - not for Google Home if you want them to play a “doorbell” sound.
It apparently can through Alexa but I have a GH house.
Per the post from Brenda:
- Google Home doesn’t support 3rd-party doorbell ring notifications.
…after fighting to get the doorbell chime to work, I’m ready to send the V2 back.
I have my Wyze Doorbell V2 getting my Google Home speakers all announcing in unison saying “There is somebody at the front door.” But it’s a pain to set up.
I also have to go through hoops, Wyze could easily fix this by exposing the doorbell press as a ‘starter’ for Google Home automation.
They can do this without google supporting “3rd-party doorbell ring notifications”.
Also checked on Google’s side. They seem to imply that 3rd party doorbells can be compatible with visitor notifications, but they don’t show any sort of list of models:
Google Nest or Home speakers and displays can announce when someone rings your Google Nest doorbell, or other compatible doorbell. With a smart display, Chromecast or Android TV, you may also be able to see who’s there.
Note: Visitor announcements may not be available on all 3rd party doorbells that work with Google. To find out if they’re available on your doorbell, check with your doorbell manufacturer.
This makes it sound like it’s up to Wyze to ensure their doorbell is compatible with Google’s ecosystem… however I’m not sure what the requirements or certification process is like there.
It is ridiculous that this is not integrated yet, although I suspect this is mostly on Google. There is a pretty easy workaround for this that I’ve found to work just as well as my Nest hello worked.
First, this only works if you have another Wyze device that can be monitored by Google. In my case this was a camera.
In the Wyze app, add a rule where the trigger is the doorbell is pressed. The action is that it turns on any camera in your account. If your camera is already on (which mine are always recording) this does nothing and is almost instant.
Next, in the Google Home app go to “Automation” and add a Household Routine. The starter will be the camera you selected in the Wyze app turning on. The action is that Google assistant announces to all devices in your household (or whichever ones you’ve liked). I’ve set it to say “Someone’s at the door” which is the same thing that happened when I had a nest hello minus the doorbell noise. You can also set it to stream the doorbell video to any device if you’d like.
This routine would be made so much easier if Wyze was able to make the doorbell a trigger in Google home. This method seemed to work within 2-3 seconds when I tried it, I’d like to hear others experiences.
When I follow your instructions I am having trouble setting up any type of automation in the Home app. What kind of camera’s do you have? I have a pan cam v2 and the doorbell wyze pro. Trying to select the camera turning on is what would not work. B/c my Pan Cam V2 is not listed in my google list. I am going to keep trying different ways of doing this. If you think of anything let me know.
I didn’t consider that, my cameras are all Cam V3 so maybe the V2 cams do not allow the trigger in Google home
Yep, you’re totally right. device.event.DoorbellPress is only available on Google Nest devices. We can look into this if/when Google ever decides to open it up to third party devices, but for now this functionality is limited only to Alexa.
More info on what is supported from third-party doorbells on the Google side:
Hi Brent,
I can confirm that I see V2 cameras in my google home app but I do not have a V2 Pan Cam to confirm. A suggestion I can make is reconnect your Wyze account to google home app. This might fix the Pan Cam V2 issue in the Home App.
Although the direct doorbell press event is not available for doorbells, is there an indirect way Wyze could make the doorbell press considered a “trigger” in Google home automation? Even a cheap dummy “toggle” through Wyze would work pretty well. For now triggering the camera is an easy and relatively cheap solution.
Hmm…how sure are you of this? The documentation doesn’t seem to indicate that it is limited to Nest, and if it was, why did Google even bother to share/publicize it? Nobody needs to see it besides Google, themselves if that’s the case. I also distinctly remember reading an article in fall 2020 that specifically said that Google had finally expanded Video Doorbell API stuff to 3rd parties…so I would be pretty surprised if that still hasn’t happened 3 years later…
But even if that is the case, how are 3rd parties integrating Google Assistant notifications into their video doorbells when their button is pressed? For example, take Reolink Video Doorbell which supports Google Assistant Voice Notifications to cast an alert on Hubs and minis anytime the doorbell is pressed:
People have been reporting that works for Reolink already…how is Reolink doing this if it is all limited to Nest only and Wyze can’t do it? That doesn’t make sense. And if it isn’t limited to Next only, then maybe Wyze could implement the same thing so that we can get Google Assistant Voice notifications on Wyze stuff too.
I guess my main question is…if everything is limited to Nest Devices, then how is Reolink doing it? And if Reolink can do it, why can’t Wyze?
I mean, I love/respect you and all Jimmy, I’m just trying to understand the situation given many of the above variables…it just doesn’t seem to add up, logically for me.
I believe the Reolink integration is for when there are detections, not for a button press. Correct me if I’m wrong and I will raise it to the internal team! We are looking into detections, but it seems like it could be deceptively long dev time due to how things are currently set up.
Unfortunately not, as we have to declare the type of device for the integration and are limited to what is available on the device type. Any kind of trickery, such as trying to declare two devices, will fail the review that Google does when we publish the integration.
I found some people saying it works for button presses now. Here’s an example:
Toggle on “Voice notifications” will cast an alert on all my Hubs and mini’s when the doorbell is pressed. I suspect eventually it will cast the video feed onto the Display in a future update.
Another user:
Google made a ton of updates a couple of months ago. I think a lot more things are now available than way back when you guys did your initial integration. They’ve been promoting it since like end of August that they launched a ton of new starters and actions for 3rd parties to use. I’ve been trying to push for someone to look into it.
Bravo! I have been trying to figure this out for while. Your instructions worked… many thanks. It is a little glitchy and slow but a great work around.
I have the home app announce “someone is at the door” on the google speakers and stream the front door V3 camera on one google hub display and the door bell camera stream on another google hub. I found the doorbell camera is a little slower to stream but worked.
A tip: Use the display (you want the camera to stream on) to trigger the commands in the google routine “stream the doorbell camera”. I have a separate routine for each google hub started by the same camera turned on from the wyze app rule (not the camera you want streamed). Can also turn on the porch lights in the same home routine.
Still working on how to automatically stop the streaming and turn off the porch light after some time. Home app has a delay action (which would work) but only in the personal automations and the household automations only has the starter for the camera on (but no delay action). Strange.
Thanks for this detail.
Do none of the available traits that they claim you can mix and match allow for toggling a button press that can be actioned via Google Home as an automation starter?
Just saw @carverofchoice 's response… sounds like doorbell presses might be supported more broadly than before, that sounds like the best option.
Implement DoorbellPressEvent For Wyze Doorbell V2 For Google Audio Notifications
Hi this would be for the Wyze Camera Doorbell V2. Even though the documentation mentions Google does not support 3rd party Doorbell notifications, they actually provide the DoorbellPressEvent for this exact purpose. Here is the documentation link.
Would you please implement this feature in a future update? Thank you for your consideration.
A quick look into the Reddit link posted by @carverofchoice shows visitor notifications at the Gear/Options level for the device in Google Home, and they also mention a Automation Starter event for “Doorbell rings”.
Looks like both of these trigger on button press.
Looks like I can see both of my cameras now my pan cam v2 and my doorbell cam. Problem is I do not see these devices available for a starter like the directions suggest.
Wish Wyze would research this and resolve it considering when I bought this it was supposed to be supported.
FYI I can confirm that the door bell will not appear as a starter when turned on which makes sense, it is a hardwired camera. As for the Pan Cam, I can confirm that my Pan Cam version 3 DOES appear as a starter in the home app. Not sure why version 2 would not.
One more suggestion that might help. Make sure you create a HOUSEHOLD automation in the home app. The device (camera) starters only show up in the HOUSEHOLD automations (device starters will not be in the PERSONAL automations).
Interesting. If this is available it is entirely undocumented and might be invite only. I let our internal team know and they will be reaching out to Google.