Thanks for all your help. I sure I am not using the legacy “works with Nest” and have moved to the Google API as I had to do this when I paid the $5.00. I believe my issue is that I set it up with TV and limited input or it was converted by Google to this? I really don’t know as it was done awhile ago. There does not seem to have any ability to change it from tv to Web.
It does show Required Scopes
https://www.googleapis.com/auth/sdm.service
In any case it seems to be working correctly and the only error is in the new repair section in the beta. I will leave it as is for now and if I need additional help, I will post in a new forum with logs and my setup.
After updating to the latest beta the repair message for my nest installation is no longer showing up. Very strange.
Bill
Like I said a few times, don’t change anything if you don’t have the reconfigure button shown in the screenshot. The repair message was removed to avoid confusion based on your feedback.
Edit: Also, it is not possible to use TV and LImited Input with Nest so that is not correct. This frankly makes it a little difficult to go back and forth here since I know that is not correct and these credentials are not possibly in use with nest, likely some account confusion going on or used with Google Calendar.
I bit the bullet and deleted the old and reinstalled on a new setup. It took a while to get it correctly until I understood the troubleshooting technique. For some reason I had credentials in Home Assistant before I put them there. It could be I did something wrong not sure. Deleted the credentials and all went per the directions.
For others the video and written instructions are clear but easy to make mistakes as you are using two different locations in Google that have the same names. What I did was have the video on my tablet running while creating the app in Google site so that I was sure which ids I needed to setup the nest app in HA.
I’ve been happily using the integration and new authorization method for many months. Just now today I’m getting a ton of these errors:
Retrying setup: Subscriber error: Failed to create subscriber 'projects/<project-id>/subscriptions/<client-id>': Deadline of 60.0s exceeded while calling target function, last exception: 503 failed to connect to all addresses
I saw in another topic related to the Google Nest integration that there seemed to be some outage. I just checked in on my doorbell in HA, while away and it apparently came back online in HA.
I did the complete setup. Deleted everything and started from scratch about a month ago. Everything works, BUT… There is always a but. My cameras will slowly drop out. (Nest doorbell cameras). I can reload the integration and they will come back about 85% of the time. If they don’t come back I have to restart HA completely. Not sure of why this is happening.
Logger: homeassistant.components.stream.stream.camera.shed
Source: components/stream/init.py:416
Integration: Stream (documentation, issues)
First occurred: August 28, 2022 at 10:40:40 AM (1120 occurrences)
Last logged: 10:11:53 AM
Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsps://stream-ue1-bravo.dropcam.com:443/sdm_live_stream/******************Z5Yeux5bNnve2uXwmxVHRmLitMqnrwbCEXEnEAd8WiqH7m-7McLGuGBN5glEM-tuYJLAsTduCiRFthGpDIuU5Q8yrG466xKvzpHYvBikNHaPTkaKrOLwvd4K-wg3RaSvh-JozPrZ_ChoABxPZadnEHnVyPmrA0xr9UyM8OPF4lqJr5ZPzu9OqXNOJ2Pw?auth=
Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsps://stream-ue1-bravo.dropcam.com:443/sdm_live_stream/***************************9QBTFIgfMKEnEAd8WiqNvPaMlfmp-_9Xx-Qooas2zrZkuc-j5IBuLlVqzmCpz7J1oPKF8HRC3V5-wFJ9deGwc4rGXQv-zth-i1_EdoV18Gy4NF2_Bne_TlmTtkcm6u1KtObJIkw3cb7QUhuRZCBL3gVw0CbXoo4Rx3CQ?auth=
Error from stream worker: Error opening stream (INVALIDDATA, Invalid data found when processing input) rtsps://stream-ue1-bravo.dropcam.com:443/sdm_live_stream/QqMQ7Y6TsAW3v48wJUxFHsFkL3aOBoCoEnEAd8WiqGQtKouhx-avoggQG9Pew7NBT3mwQRwYg6nEuup4VdOki_qFQhZQt8pj8jKbNr9aRuboPmRGI60Z2CiAgaxh5qINQqjuaBp9cTPlf5cQVz9DvTP3ihNN6QdfHkEHb9xB1DhDlRrDWm4ZFoWWaQ?auth=
Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsps://stream-ue1-bravo.dropcam.com:443/sdm_live_stream/CRPmh_BpCpWv_r4OX2CFUM8lXayiiNHxqEnEAd8WiqF8aXM9Htxl9f4hrdx-fQIHV7Ni79LtzaTMXBIpAsHtQA8ddXAXmd2XO7WMT0nhWcilP5dYCtt1SrgV7ScKM3g7oAwNTh5O79y64X-EPrWi97lPdVw4F_SzBMl_QOfKxVirSt_qbglvpkWuEZQ?auth=
Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsps://stream-ue1-bravo.dropcam.com:443/sdm_live_stream/**************************M4fE23tYE-5e2lVGnpo6rdfzGRgT4KLznCxEnEAd8WiqGvArZhGIQkuwqEkJsyFcuxE17N8CzXUGNIQNlJQIx7AeNiT5SYPaQF9kuw4nnAeyRtpfgvUNorrWWpwkmVR0EVI6ClFDYj5iyahY80GcadLhtdzJASHLBqmEcs_9vqJFCTl4Zxt_oTp_t4Vpg?auth=
@allenporter, have you heard anything about this? Is there any update?
I had to reset my doorbell because ti was not sending email notifications. The engineers would not even look at the issue unless I reset it. So I did reset it. I had to set up everything again, as it failed to work with the same setup. Now I have only a 404 error for the stream.
I am quite fed up with the b*llsh!t what Google created with the mess around the Nest products… I just wait for the moment when it ends up in the endless pit of Killed-by-Google.
Thanks! It is just unbelievable that Google killed the Nest API, built this overcomplicated solution that you have to pay for to access it, and it is throwing 404 errors when you want to access the stream. And after a year, it is still an issue…
Meanwhile it just started to work out of the blue. But I have 5 different error messages, 3x 404, 1x 403 and another I/O demuxing one.
(And not talking about the 3-6 SECONDS delays in the solution.)
What would be most helpful is to directly report the issue to google yourself in the issue tracker: Device Access Support | Google for Developers – when i report it, i can’t really give them direct input from end users. They want details like the accounts involved and the timestamps when the 404 errors happened, so if we create a new issue and give a bunch of detail it will go much fastaer.
