[Rookie needs help] 20 seconds delay when doorbell pressed > light blink

Configuration
1

When I’m working from home I have my headset on most of the time and I don’t see, hear of feel the notification on my phone.

So I have this very very simple automation that when the doorbell (Google) is pressed the lights blink.

It work, but there is a delay of exactly 20 seconds.

Maybe I need to add something to the YAML that can decrease the delay.

Which of you wizards can help me?

The YAML:

alias: deurbel
description: ""
trigger:
  - platform: device
    device_id: 3387e9ca4f9651d1592dd52e86c8b194
    domain: nest
    type: doorbell_chime
condition: []
action:
  - service: light.turn_on
    data:
      flash: long
      brightness: 83
      color_temp: 153
    target:
      entity_id: light.woonkamer_spots
mode: single

Thanks!

2

No there is no config you can add to speed it up. You need a local doorbell that does not rely on cloud services.

2 Likes
3

If it is exactly 20s delay every time, that would sound very strange to me.
I am guessing it is some delay between 5s and 20s.

In that case, that would be a polling interval: homeassistant polling the state of the doorbell in “the cloud”.
Or something similar, like a rate limitation on the side of the cloud provider.

I personally do not use any of theses cloud services, I keep my stuff local.
If switching to a local doorbell is not an option, a cludge may be using a microphone sensor placed close to the ringer.
As an alternative to a microphone, monitoring the ringers power consumption would be a good indication of activity. But for a battery-operated device that is usually a bit tricky.

Commercially available sensors for “home automation” are usually very limited - because product designers have no ideas? Or more likely: because marketing does not see large quantities for anything but a pushbutton…
But pushbutton-sensors are usually hackable:

  • measure the button type (active low/high)
  • desolder the button
  • provide the “button” signal from another source
    (search for Arduino sensor kit on your favorite online market platform).
1 Like
4

It’s supposed to be cloud push (updates sent out by the cloud server, no polling).

Screenshot 2024-01-02 at 22-12-47 Google Nest

20 seconds does seem like a very long time, even for a cloud integration.

5

Thanks for the answers, guys! Unfortunately I’m not that technical, but I’ll look into it.

But when I let HA send me a notification to my phone when the doorbell is pressed, I get the notification within a few seconds.

I don’t see the difference in sending a notification to my phone of to a light to trigger on.

6

Go to Settings → Devices and Services → and open your Goggle Nest device.

Watch the entities when the doorbell is pressed. How quickly do they update?

7

Found that, but what should I see? When I press the doorbell I don’t see anything change or get updated at the entities. Also, the logbook for the doorbell device is empty.

Sorry for the trouble.

8

Take a screenshot of the page and drag and drop it into a post here.

9

Scherm­afbeelding 2024-01-02 om 13.58.19
Scherm­afbeelding 2024-01-02 om 13.58.192362×422 31.6 KB

Scherm­afbeelding 2024-01-02 om 13.58.41
Scherm­afbeelding 2024-01-02 om 13.58.412016×1210 160 KB

10

Oh. I was expecting to see binary sensors. Or the new event sensors.
It does not work like I expected it to.

Check your app settings: Google Nest - Home Assistant (expand the box below the text).

11

Push is on
Away-only is off

Can you see something from the diagnostics file by any chance?

12

To confirm it is the Nest integration with the delay:

Try triggering the automation manually, does the light flash instantly?

Developer tools → Services, select automation.trigger then select your automation entity and click the CALL SERVICE button.

Look at the automation trace after pressing the doorbell: Troubleshooting Automations

Does it trigger 20 seconds after you press the doorbell?

13

When triggering manually, it flashes within a second. Every time.

This is the Trace Timeline after pressing the doorbell, which took 20 seconds te trigger the lights.

Scherm­afbeelding 2024-01-02 om 14.43.32
Scherm­afbeelding 2024-01-02 om 14.43.32898×276 13.9 KB

So, it must be the Nest integration, right?

14

Correct.

1 Like
15

That’s a bummer.

Thanks for the help anyways. Much appreciated, Tom!

16

I am having the same issue but the notification takes ~23s (from Google Home the same noti is only ~3s). As I understand it, the JSON payload from the nest integration is only received once it has finished downloading the video and/or image from the cloud. Perhaps it’s this download delay that we’re seeing? Is it possible to turn off the video posting to potentially speed things up?

17

Actually, theory perhaps debunked, as under Integrations > Nest > Doorbell > Logbook I see the event.front_door_doorbell_chime trigger at the same time as Goole Home. If I set up my trigger based on this

triggers:
  - trigger: state
    entity_id:
      - event.front_door_doorbell_chime

Instead of

triggers:
  - device_id: <MY_DEVICE_ID>
    domain: nest
    type: doorbell_chime
    trigger: device

I get the notification immediately. However, I cannot seem to access the video payload from this event for some reason, so I cannot display a thumbnail in the phone push notification

3 Likes
18

I had the same situation as you, i went looking in the logs of the entity itself, and indeed, the event was triggered at the same time as the actual google home notification.

gonna test the speed later. thanks!

1 Like