Google Nest Cameras not working after latest Home Assistant Update

Configuration
22

I’m also experiencing this issue with 2024.11.1 but it is mainly affecting the Android companion app. Via the web UI, the cameras generally work, but they will not work at all in the Android app - they just immediately show the rate limit error.

23

I would do but don’t know where.

I also have a Nest learning thermostat and just found this gives the same error too when I tried to change its mode. So whatever the bug is it’s affecting all Nest devices. Actually, thinking about it, is the issue occurring for people with and without thermostats?!

24

And just came across this: Nest Cameras/Doorbell showing too many API calls since latest HA update · Issue #130061 · home-assistant/core · GitHub!

25

Yes, I have a Nest learning thermostat too and it’s also being impacted

1 Like
26

I don’t have a Nest thermostat but I’m affected by the issue. I have 7 Nest devices and they’re all cameras (2 indoor, 4 battery outdoor, and a wireless doorbell). Thanks for the link to the Github issue. Can see they’re onto it :+1:

27

Failed to start WebRTC stream: Nest API error: Too Many Requests response from API (429): RESOURCE_EXHAUSTED (429): Rate limited for the ExecuteDeviceCommand API for the user.

Same here… is there a solution, maybe in de google developer mode…?
https://console.nest.google.com/device-access/project-list

28

https://status.nest.com/posts/details/P2FFRGD

Nest App is having issues - can only assume it’s related.

29

Same, Nest thermostats are showing old or incorrect temp data etc.

1 Like
30

I got excited too thinking the latest HA update solved it, but yes it is intermittent here as well. Sometimes it works, but most of the time I see the 429 error. Also can’t figure out if the rate limit resets at midnight as I see this at 1am or 1pm. No pattern.

There was a recent WebRTC update that I was hopeful would resolve, but nada. I’m fully updated across my HA and integrations. No joy. This applies across all devices and definitely something recent as this was rock solid for very long time. …provide additional context for anything that may be working on a fix.

31

Same problem here …