I am recieving the following error whenever going in to view a feed. I assume this is related to the camera changes in the latest release? Is there anything I can do to resolve this? Thanks!
Core: 2024.11.0
Supervisor: 2024.11.2
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.
I have the exact same problem as you since the last update, and I donāt know how to fix it.
Same here, canāt see to figure out how to revert it from WebRTC to the old method either.
Iām having the same issue - I canāt view any Nest/Google camera feeds in HA after the update. I have the following Camera models and they are all having the same issue (even the older models):
Nest Outdoor Gen1
Nest Hello (Wired Doorbell Gen1)
Nest Cam Indoor/Outdoor Battery
Nest Cam Inddor
Ahh found others in the same boat. I assume at this point we have to wait for an integration update.
Based off the GitHub I think itās already been fixed and the fix will be in 2014.11.1, for now though the stream plays just fine through frigate-card
Iāve just installed 2014.11.1 and Iām still getting the error so fixed in .2 hopefully!
Seems fixed for me in the latest update
Itās now working for me too. I had to reload the integration, disable my doorbell and re-enable it and that seemed to bring it back, phew!
For me, it was resolved with 2014.11.1. I just had to update and reload the integration. Good news!
Hmm, then again, mine has started doing it again?
Mine are doing it too, on 2024.11.1. Not all the time. Some of the time they stream just fine.
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?
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.