I tried tying it my existing project for rclone, which requires google drive permissions. I guess I’ll have to setup a totally separate project for this.
Hi, I have 2 old Nest cameras (Doorbell Wired & Outdoor IQ) and recently added them to a dashboard with the “Preload Steam” checked.
The Doorbell works just fine and the Outdoor IQ seems to work but sometimes the stream stops working and after a while it works again, I get these error when that happens:
Logger: homeassistant.components.stream.stream.camera.backyard_pool
Source: components/stream/__init__.py:347
Integration: Stream (documentation, issues)
First occurred: 12:55:59 PM (34 occurrences)
Last logged: 2:35:40 PM
Error from stream worker: Stream ended; no additional packets
Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsps://stream-us1-charlie.dropcam.com:443/sdm_live_stream/CiUA2vuxr6PJde-syqMMVHlH0PoMd8AIH7LGxeHICR9gonEe_qADEnEAMPcxGOPd7CHahFBGSbR_S9Y2yPk5B2mthtWm0xMPxhP7xZNTjAv2y_wLZDVTS1OkipCGURk0c6TxdDGLdHKQPiRFz-l50_M726uT8zoowp05iMd4g6rmF1_z6gcwxZZOjLSSx-LgQXttJUlU-xM2_w?auth=****
Error from stream worker: Error opening stream (HTTP_FORBIDDEN, Server returned 403 Forbidden (access denied)) rtsps://stream-us1-charlie.dropcam.com:443/sdm_live_stream/CiUA2vuxr6PJde-syqMMVHlH0PoMd8AIH7LGxeHICR9gonEe_qADEnEAMPcxGOPd7CHahFBGSbR_S9Y2yPk5B2mthtWm0xMPxhP7xZNTjAv2y_wLZDVTS1OkipCGURk0c6TxdDGLdHKQPiRFz-l50_M726uT8zoowp05iMd4g6rmF1_z6gcwxZZOjLSSx-LgQXttJUlU-xM2_w?auth=****
Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtsps://stream-us1-charlie.dropcam.com:443/sdm_live_stream/CiUA2vuxr6PJde-syqMMVHlH0PoMd8AIH7LGxeHICR9gonEe_qADEnEAMPcxGOPd7CHahFBGSbR_S9Y2yPk5B2mthtWm0xMPxhP7xZNTjAv2y_wLZDVTS1OkipCGURk0c6TxdDGLdHKQPiRFz-l50_M726uT8zoowp05iMd4g6rmF1_z6gcwxZZOjLSSx-LgQXttJUlU-xM2_w?auth=****
I just saw some old references to something similar where the URL for the stream is expiring? Is this still an issue? anything I can do to fix or workaround it? seems weird that it one happens with one of the cameras…
I made GitHub issue but wanted to mention, I did a fresh HA install today, I have setup the nest integration many times before, but when trying to stream now I get
Error handling WebRTC offer: Nest API error: Error from API: 500: INTERNAL: Internal error encountered.: Internal Server Error
can’t see anything wrong with permissions.
Looks like Nest Camera stream API returns 404 Not Found · Issue #60353 · home-assistant/core · GitHub – the issue has been reported to nest API team as widespread. Feel free to add your detail to he bug as a “me too”
1 Like
Hi, I about to send you to
Failed to start WebRTC stream: Nest API error: Error from API: 500: INTERNAL: Internal error encountered.: Internal Server Error · Issue #70244 · home-assistant/core · GitHub but then see you’re the same person. Haven’t heard of any other reports about this yet so I still claim it is an account specific issue that we can’t do much about with out help from nest support
Oh wait Failed to start WebRTC stream: Nest API error: Error from API: 500: INTERNAL: Internal error encountered.: Internal Server Error · Issue #22184 · home-assistant/home-assistant.io · GitHub is the other replace I saw this. I got the issues mixed up (on mobile). I recommend tracing out to sdm feedback or nest support explaining the API is not working as I mentioned to he other person.
Thanks Allen. Man it such a shame, this would happen and break every camera I know. I have so little faith in Google Support. But my google home account has been kinda buggy, but the livestream works fine on the google home app. But ye. 2-3 weeks ago, the google home app turned to having 30% English and 70% Norwegian. Even though region and language is set to Norwegian.
Wasn’t like that before, tried every step to change it back. Just a side note, but it was strange.
Sorry for bugging you about it, the problem is somewhere else.
Thanks
1 Like
do you know the link to this SDM feedback thingy, can’t hurt to try them both out
I can’t find it now, maybe I was mistaken…
Let me know how the query goes with support.
1 Like
Hey guys!
I’m struggling with setting up the NEST integration. I got ERROR 400 (invalid_request) message after setting my permissions to acces and manipulate temperature of my nest. Is this a personal error? Or something that others will soon run into as well?
Would love some advice or help
Hi, unfortunately a known issue being worked through, see Warning Message about nest OOB deprecation · Issue #22141 · home-assistant/home-assistant.io · GitHub for context and short term (with huge caveats) workarounds.
1 Like
I also got this when i created a new project in google developers, i got around this by creating web outh instead of desktop app and using a redirect uri
dont know the limitation here, but after adding it trough ha using web app its working fine
Web auth works fine, just complex for users to set-up
2 Likes
When selecting my Google account [email protected] I systematically get this : Error 400: redirect_uri_mismatch
Could this be because I did not pay the $ 5 fee ? I am ok to pay this fee but don’t see where, though I may already have paid this some time ago.
Hi, see Nest - Home Assistant for troubleshooting steps and 2022.6: Gaining new insights! - Home Assistant for context on what changed in Home Assistant (for all integrations) that requires this.
For everyone looking for App Credentials latest, see the Alert with context and Nest - Home Assistant for the migration steps. Basically, you upgrade to 2022.7 and Home Assistant will now walk you through the migration steps to resolve this if you click Reconfigure if you previously setup OAuth for Apps credentials.
1 Like
Thanks !!!
Hi @allenporter - Do you believe they might make this data available in the future/are there any available roadmap documentations from Google that you know of? Just wondering what the most effective way to keep an eye on this would be so I don’t miss if this is implemented.
Update: Apologies, I thought I was replying to a specific post. I am referring to this…
My impression is that they post updates at Release Notes | Device Access | Google Developers when new features are added to the API.
1 Like
Just noticed this error in my logs (happened past couple days):
2022-08-06 05:44:51.911 ERROR (Thread-1652 (_run)) [grpc._plugin_wrapping] AuthMetadataPluginCallback "<google.auth.transport.grpc.AuthMetadataPlugin object at 0x7f702e4a30>" raised exception!
Anyone else see these? Not sure if I should add to GitHub issues with additional logging