Hmm, then again, mine has started doing it again?
1 Like
Mine are doing it too, on 2024.11.1. Not all the time. Some of the time they stream just fine.
1 Like
mine don’t work anymore either unfortunately. hopefully there will be a solution soon.
I added my nest cameras (various models, but x6 in total) back around easter.
For me it’s always been the case that the api is rate limited for non-google devices (ie home assistant dashboards)
Yes they stream, until they hit the rate limit, they they’ll error out.
However, if your viewing your cameras via Google home app / nest app / Google or nest websites etc you won’t get rate limited, thus won’t see the error.
Read here towards the bottom of the page for actual rate limits by device type Límites de usuarios y frecuencia | Device Access | Google for Developers
There is definitely something not right! The error occurs intermittently as others have indicated. It’s doing it now this morning. However, I haven’t used it since last night so it’s hard to see how I can have hit a rate limit unless somehow it’s being used in the background?
2 Likes
That’s why I asked, in another thread, whether the things go on streaming in the background rather than closing the stream when I close the dashboard page the picture card is on. Didn’t get a reply, I guess it’s an unknown right now.
Can you link to that thread so I can reinforce your post. Also, I guess this should be raised as an issue in GitHub but I’ve no idea where - any suggestions?
Though I framed it as a general question because at the time I was just trying to find out what is supposed to happen. Unfortunately I only started adding the camera streams after this latest update so I have nothing to compare with.
Also having the same issue on my side since updating to 2024.11
I can temporarily resolve it, by disabling/re-enabling the entities, then restarting the integration. Works for an hour or so, then same issue happens again. This also effects the Nest Thermostat.
Here is the error when adjusting the thermostat:
Failed to perform the action climate/set_temperature. Error setting climate.thermostat temperature to {‘entity_id’: [‘climate.nest_thermostat’], ‘temperature’: 21.4}: Too Many Requests response from API (429): RESOURCE_EXHAUSTED (429): Rate limited for the ExecuteDeviceCommand API for the user.
Has anyone posted this on GitHub as a bug? I can also add a comment to get it more visibility/urgency.
Well the release came just as the weekend was starting, so there may not be anyone to look at these problems till tomorrow.
1 Like
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.
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?!
And just came across this: Nest Cameras/Doorbell showing too many API calls since latest HA update · Issue #130061 · home-assistant/core · GitHub!
Yes, I have a Nest learning thermostat too and it’s also being impacted
1 Like
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 
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
https://status.nest.com/posts/details/P2FFRGD
Nest App is having issues - can only assume it’s related.
Same, Nest thermostats are showing old or incorrect temp data etc.
1 Like
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.
Same problem here …