-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nest Camera API Call high error rate ExecuteDeviceCommand endpoint #132438
Comments
Hey there @allenporter, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) nest documentation |
I keep experiencing issues on any version above 2024.10.4. There are still lots of errors, leading to the stream not working. In the scrrenshot you can see the errors are increasing over time. A reset of home assistant seems to help? @allenporter any clues? Happy to dive in deeper...
|
How many cameras is this? These all appear to be separate webrtc sessions created. Can you describe your frontend dashboard configuration for showing your camera streams? I'm curious if it's set to |
It might be easier to diagnose if starting from a fresh integration startup so we can see why all those extra sessions are being created. We should see a session created, then scheduled for expiration when it expires a few minutes later, and that should be it. If there are more requests than that then there is a problem. Would be helpful to know how many cameras and what you're doing from the viewing side, and also to have a diagnostics trace along side the logs. A separate issue might be better at this point given it's a new separate issue with the same symptoms. |
I have 1 camera, it is displayed in 1 dashboard, the card is set to The frontend setup is as follows
I already re-setup the integration, or do you mean something different? |
OK -- that sounds like it is leaking WebRTC sessions, causing new sessions to be created without closing the old ones.
No, not setup, but startup of home assistant. The log has a bunch of existing sessions, but not showing how the problem starts given the sessions all already exist. |
ok, is there a way to close the WebRTC sessions? Will look at generating a better log. |
My impression is they are typically closed by the frontend browser when the stream is closed in the browser (e.g. navigating away, closing the window) or when the websocket is closed by the browser. I'm not sure how that differs from reloading the view. Perhaps you can share details about how the reloading works? I'm not familiar with this. |
That all looks fine -- |
I do see 33 start vs. 20 close operations in my logs this morning. home-assistant_nest_2024-12-16T12-50-54.102Z.log Any suggestion how to go about this. Btw HACS WebRTC is not used, now have removed it. |
Looks like it is resolved now, thanks! |
The problem
This is a follow up of #130061
After upgrading to 2024.12.0 I get the Nest Error again within a few hours, causing the stream not to start.
In the screenshot the Google Cloud data can be seen.
The error on screen of the dashboard is:
Error:
Failed to start WebRTC stream: Nest API error. Bad Request response from API (400): INVALID_ARGUMENT
(400): offerSp contains an invalid value.
If there are any clues how to troubleshoot it myself, Id be happy to research.
I understood the delay should be 30 seconds for API calls, however it shows a lot more calls.
What version of Home Assistant Core has the issue?
core-2024.12.0
What was the last working version of Home Assistant Core?
core-2024.10.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Google Nest
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nest
Diagnostics information
nest-01JC3TA0GB3ERTT0B3CHQ61AJZ-Voordeur camera-2cefd9efacad846c2479e67be34470f2.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: