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!