Unsure how new releases Nest changes, especially Media Source is meant to work?

Hi

First a massive thanks to everyone involved in the nest integration especially @allenporter as I know how hard it can be to maintain hobby projects.

I have been keenly following the changes to support the new nest devices, specifically the battery doorbell which I have had for a few months now.

I have had everything setup and working with HA for a few weeks and can see live feeds and get doorbell events but been keen to look at using automation to do more, specifically using doorbell/camera triggers with other devices and getting camera event image/video to display on other devices.

With the latest release it looks like these are now possible but here is where I need a little help.

  1. Should the latest release support motion and person detected triggers on the battery doorbell as I cannot get them to trigger AND they do not appear in the new Media Browser > Nest folder but doorbell events do

  2. Is the new Media Source feature meant to be used to get access to camera images/video within an automation triggered by a nest event? If so can anyone explain how as I cannot see how to do this

Thanks
Brian

Hi, yes, ive been working on documentation for automations for this but it’s not quite ready yet.

You said that you are able to see events working?

So:

  • you should a list of eligible devices in the media browser, then a separate item in the media browser for each event.
  • it’s then possible to fetch the media items from an automation. The nest integration docs currently have an example for older cams which I am updating for newer battery cams.
  • However for new cams it currently publishes a 10 frame MP4 clip and I’d like to transcode it to an animated image on the fly, also work in progress
1 Like

Thanks Allen,

I just need to learn some patience :wink:

Yes doorbell events seem to be working and generating media, person or motion events do not. Not sure if that is expected?

No, I would expect you to get motion and person events.

I think if you turn on this logging in your configuration.yaml you should be able to see all events received by home assistant. This way we can see if we’re dropping them or if they just aren’t being sent by the doorbell.

logger:
  default: info
  logs:
    homeassistant.components.nest: debug
    google_nest_sdm.event: debug
    google_nest_sdm.event_media: debug

When I look at my own feed testing doorbell, I also only see doorbell events too, for what it’s worth. Hadn’t noticed that before, so you may be on to something. I may have just incorrectly assumed that it isn’t super sensitive. If you can collect some data that could be really helpful.

On your point #1 I think you may be hitting Nest integration stopped pushing "person detected" and "doorbell ring" triggers. · Issue #61727 · home-assistant/core · GitHub but not certain. There was an issue with grouping events that happen around the same time that I have a fix for. They can share media for the new cam types but not the old cam types so these cases may be a little mixed up right now.

Thanks I read that thread but as its closed will reply here:

I am running core-2021.12.1 and have enabled debugging in the log. Only pressing the doorbell triggers any sdm events (although one doorbell press seems to generate three google_nest_sdm.event, the first is unique 2 and 3 seem to be a duplicate but all three are a ‘sdm.devices.events.DoorbellChime.Chime’

Let me know how .2 works for you.

.2 doesn’t seem to receive anything other than chime events still but I do get three events, each with a different eventid but the same sessionid and all chime events

Sorry to jump in … :slight_smile:

I have the battery doorbell and have an automation for motion detected (plays a tune via google hubs) and that seems to work fine (although nothing is shown in the media browser for them) The only things that show in Media Browser for me currently are doorbell events.
Happy to assist if needed with logs etc…