No video stored when doorbell pressed.

[Apial]

No video is stored when the doorbell is pressed. An indoor nestcam picks up the visitor doorbell announcement but when checking the history of the doorbell it is blank. 
It’s a battery doorbell with 52% battery left. 

[MplsCustomer]

@Apial 

Do you have a Nest Aware subscription?

If you do not, then you only have access to event video history for the most recent 3 hours.  So if your doorbell was rung 4 hours ago, you do not have access to that event.

If you do, then you should have access to event video history for the last 30 days.

If you go to your doorbell in the Google Home app and go to Video | Video history, what option is checked?

https://support.google.com/googlenest/answer/9681538

[Apial]

Yes I have the subscription and all the boxes are ticked. I also have had this happen before. The NestCam records the sound of the doorbell but the Nest Doorbell doesnt. Other events before and after are being recorded. Could there  be done sort of interaction between the two devices that prevents both recording simultaneously?

[MplsCustomer]

@Apial 

There are lots of reports about the battery doorbell and battery camera not waking up from "Idle" mode in time to detect and record an event, but when the doorbell button is pressed, that should force the doorbell's camera to wake up and record the event, although it might not wake up to record the doorbell sound.

We have the battery camera, plugged in with the optional power cable, and it does well at detecting and recording events (at least in the daytime). But if we unplug it and walk in front of the camera, it does not detect that as an event.

I'm not aware of any issues with having 2 cameras record an event at the same time. We have numerous cameras and if there's a lightning flash and thunder, for example, all the cameras will record that.

You could try contacting Support about your doorbell not recording when the doorbell is rung:

https://support.google.com/googlenest/gethelp

[janthadeus]

Hi folks,

Checking in — were you able to speak to our support team as shared by MplsCustomer? If so, how did it go? Let me know if you need more help.

I appreciate your help, MplsCustomer.

Thanks,

JT

[EmersonB]

Hello everyone,

@Apial, we wanted to follow up and see if you are still in need of any help. Please let us know if you are still having any concerns or questions from here, as we would be happy to take a closer look and assist you further.

I appreciate the help, JT.

Regards,
Emerson

[janthadeus]

Hey Apial,

Just checking in to make sure that you've seen our responses. Please let me know if you have other questions or concerns as I will be locking this in 24 hours if I won't hear back from you again. Feel free to start a new thread and we'll be happy to help. 
 

Thanks for chiming in, Emerson.

Best,

JT

[Apial]

I can’t check anything at the moment as my doorbell is 3500 miles away. The batteries are about to go flat in a few days too, so until I get back next week I can’t reply. 

[janthadeus]

Hi there,

Understood — we'll leave this thread open until next week so can have enough time to check it. Keep us posted.

Thanks,

JT

[janthadeus]

Hey there,

It's me again. I want to check if you still need help. Don't hesitate to reach back if you do.

Regards,

JT

[janthadeus]

Hello there,

I haven't heard from you in a while so I'll be locking this thread if there is no update within the day. If you have any new issues, updates or just a discussion topic, feel free to start a new thread in the Community.

Best,
JT

[Apial]

I increased the sensitivity of the detection.  The recording now works. But I can’t understand how it failed to work correctly in the first place. 

[janthadeus]

Hey there,

Happy to hear that! I appreciate the gesture. It looks like we can consider this one complete, so I will be locking this in 24 hours if we won't hear back from you again. Feel free to start a new thread and we'll be happy to help.
 

Cheers,

JT