Google Nest Cameras: Old nest cameras converted to home app do not send events. New cameras do

[crryp]

The problem

I recently converted my older nest cameras to the new home app (as google finally support this). But now somehow all the events of the older cameras do not trigger in home assistant.

I also have got the newer cameras and those do trigger almost instantly. This tells me my setup is ok, i can see the cameras + also my thermostat works fine.

But i cant get events for the older nest cameras.

Might this be a issue with the old cameras on the home app instead of the older nest app?

What version of Home Assistant Core has the issue?

2024.7.0

What was the last working version of Home Assistant Core?

2024.7.0

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Goolge nest

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @allenporter, mind taking a look at this issue as it has been labeled with an integration (nest) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of nest can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign nest Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

nest documentation nest source _{^{(message by IssueLinks)}}

[macpatrik]

I just ran into this problem with the first gen Nest Doorbell camera when it was moved from Nest to Google Home.

[allenporter]

The integration instructions has troubleshooting steps to help narrow down it the server is publishing messages. Can you check that out?

[crryp]

I did all the steps to solve the issue. All the settings and rights are fine.

As the comment above issue started when moving from the old nest app to the home app. Only those specific cameras stopped working others work fine.

[crryp]

I just ran into this problem with the first gen Nest Doorbell camera when it was moved from Nest to Google Home.

This is what happend here also with the first gen doorbell and 2 first gen nest indoor cameras.

[allenporter]

I've confirmed this on two of my cameras. First gen doorbell and an older outdoor camera.

[crryp]

Is there a solution / work arround? Or do we need to wait for google to change there implementation?

[allenporter]

I've reported the issue to Google https://issuetracker.google.com/issues/358755975 and reported the issue.

Attached to the issue, I created a private google document with the following details:

• My gmail address
• My device access console project id
• Details about my device make and model that are having the issue This is private and I will share with google.com employees as they request.

You could also attach a similar private document if you would like to make it easier for them to diagnose.

[crryp]

Update: My doorbell did push a message in ha this morning.

[Pixel-Gavin]

My doorbell is pushing person notifications - but not Doorbell notifications. Again Nest Doorbell migrated to Google Home from Nest.

[Jonnehs]

Same issue here, since converting to Google Home from Nest the doorbell does not push chime notifications, the chime sensor in Home Assistant just reads "unknown"

[allenporter]

We don't need more reports here as this is not a home assistant issue.

You can help by giving the details about to Google as I have said above with the details I mentioned.

They have fixed some events, but not all of them yet.

[allenporter]

Events are now being published, but media is not working as described in #128035:

Bad Request response from API (400): INVALID_ARGUMENT (400): Command

Nest has been made aware of this issue

[Pixel-Gavin]

Thank you @allenporter - all of your hard work is very much appreciated. I will also report to Google.

[johndeu]

I hit the same issue and added a report to the open Google bug. I see events in the .storage/nest.event_media file, but I do not see any images being written to the config/nest folder any longer past the point of migration to Google Home app.

I'm not sure if this helps them, but I noticed that before and after the transfer, the event types output changed a lot.. Media keys are now omitted, suggesting a shift in the handling of event-related images. Also, I can see that they changed the event_session_id significantly from a long string to a short one.

Key things noted:

Shortened IDs (Session ID and Event ID).

I also spotted several negative value event id's in the event data. For example:

       "event_data": {
                      "event_session_id": "1734018317",
                      "timestamp": "2024-12-12T15:45:22.221708+00:00",
                      **"event_id": "-1442449751",**
                      "event_image_type": "image/jpeg",
                      "zones": [
                        "",
                        "Front Steps"
                      ]
                    },

Zones included, even if empty.

"zones": [
        ""
]

Media keys omitted

These all disappeared from the event logs at the moment of transfer. No event contains them anymore.

 "media_key": null,
        "event_media_keys": {
          "CiUA2vuxrx_NJgqfcEgq_fs1447oLjEZG3fVJLQX3HKn4dakQDhVEo0BAGsO4kHNUdry-hDqj14ywT-Tx7b4cmEUvncE_WVdXSqB3g7YqSQEIJzOX-S9lfp9mCH0Yx_1TX7V6HlGEzMtClemuaUHEed28bdBqDtNwy07p8FEk3hrY_J_UptpAtMccf3nFpUpwXTiRk2Yn4dP-mRV4LL9poSDvPzrSqrIA2nBl8xLFaAwHBzT8cz0": "6374e0b4c750b4105bd9de6a8adcd965/1733962723-camera_person.jpg"
        },
        "thumbnail_media_key": null,

I'll add this to the google bug as well to note it to their team. Not sure if it helps them at all.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[bobbinz]

Dear Mr Bot. Latest version does not help.

[allenporter]

Hi this is not a home assistant problem given it's behind the API so no versions of home assistant will change anything here, just to be clear. Working through the SDM support channels to report or +1 broken existing issues about broken functionality is the way to raise this to nest.

[allenporter]

See https://github.com/home-assistant/core/issues/123478#issuecomment-2282194422 about what to do

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Intecpsp]

Not stale

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.