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 stream API returns 404 Not Found #60353
Comments
Hey there @allenporter, mind taking a look at this issue as it has been labeled with an integration ( nest documentation |
Nest server streams are failing. This is not a home assistant bug as far as I can tell. |
@allenporter Stream is working on their Nest/Google Home App, so maybe their API has changed? |
No, that is not the case. This is fairly common unfortunately. I imagine I'd you retry it will work again. |
@allenporter Nope, It is failing for more than a month :( |
OK, the issue is on the nest servers, or with your camera, so there is not a lot we can do on this side. However, I can think about ways to improve the error messages to give more error detail if possible, but unclear that it is feasible. |
@allenporter Well ok. I don't see how the issue could be with my camera as it is working normally when using Google Home. It has been failing for a while, even after refreshing the token. So, I suppose you don't have any advice on how to get it working, or at least on how to provide you better information in order to track down the issue. |
@junalmeida I said the issue is with the nest servers or an issue with your camera. The Nest API may have a specific issues with your camera even if it works in the Google Home app. The Nest API uses a totally different implementation. Your cameras may be fine, i have no idea, just saying i can't do a lot to help you given its working for me and everyone else. There is a lot of information on https://www.home-assistant.io/integrations/nest/#troubleshooting and you can also turn up logging in I'm guessing if you get additional logging, however, it won't give us any more information since the nest servers are failing which is out of our control. As I mentioned, I can look at ways to add additional logging since the existing logging probably won't tell you much new information. Just trying to set your expectations appropriately, but happy to look if you get more logs. |
If you want to really get extreme you could try creating a new test home and moving the camera to it, then adding that to home assistant to see if you have any better luck. Just trying to think out side of the box for how to "reset" things. |
I believe given this exception catch core/homeassistant/components/stream/worker.py Lines 411 to 415 in 5a72c9f
We have no way to know what exactly was the error. The message got swallowed by the except av.AVError
I could change the source in order to make it spit out the original error, but I'm running HA OS so I'm not sure I have access to any source code. |
Yes, that is what I was referring to above. Happy to review a PR to do that. In particular, when I tested locally I didn't get a very good error message so perhaps you can see for your own case what error you get and if it useful. When I did it, it was redundant with what was already there, but it was likely because the way I simulated an error with iptables. You can see here more detail: https://pyav.org/docs/develop/api/error.html and my impression is that Maybe also crank up pyav error logging for yourself as well. |
Ok so I just ssh'd into home assistant docker container, I navigated to
And now I get the following:
So is this URL entirely provided by google SDM API or manipulated somehow by the HA component? |
Provided by Google API. You can turn up logs in |
Actually I don't see logs for the responses. Maybe extra logging here: |
Actually there is one manipulation. The stream token is added to the url as an auth parameter. |
I added the logger you requested, and this is what I see:
|
Ok, I don't see the response for t he generate live stream call logged, but anyway, not sure it's going to tell us much. |
I don't see any code logging the response, just the request. |
Right, I was saying you need to add it "maybe extra logging here.. capturing the response and logging it". |
Adding that I too see the following in my logs, and appear to experience latency issues when loading the stream. Unknown if the two are definitely related or not, but I see the following repeatedly and continuously throughout the day and everyday:
|
I've also seen @potmat see similar issues with homebridge so it seems pretty consistently that its a problem with the nest API. |
I created this issue to alert Google the problem: https://stackoverflow.com/questions/70086032/rtsp-streams-often-fail-with-404-on-describe-method |
Add back some of the error log information from the original exception (error type and string). Issue home-assistant#60353
What is the current status of this issue? Looks like there are some fixes being played with in the dev channel. I have been dealing with this for a while as well, and trying to track down some status on the issue. Thank you, |
Interesting, there is definitely an idle timeout on the streams so it stopping when not in use makes sense. I'm having trouble following the iPad and desktop interactions order. Sounds like you're saying when adding the iPad it will fail after a bit, but not sure how that relates to the desktop going inactive. Maybe you can elaborate on steps that make this happen and I can also try to reproduce or consider where there might be more problems / bugs. |
Not sure if this is exactly the same issue. After upgrading to 2022.2 from 2021.12.10 I'm seeing lots of 404 errors in the log and 'Garage_Camera became unavailable' in my logbook. I have 3 cameras in my setup and all 3 are exhibiting the same errors. My automations aren't capturing snapshots or video until I restart HomeAssistant
|
The symptoms look the same, however, nothing has changed in this stream code since 2021.12.10 so im surprised its correlated. Have you confirmed that rolling back to the prior version that it works? |
Here's my logbook for the garage camera for the time I was running 2022.02 and back to 2021.12.10 (no entries after reinstalling around 15:50) I am still getting errors in the log, but doesn't seem to render the camera unavailable. On 2021.12.10, some of my automations do fail to capture a snapshot, but it is very intermittent (days to weeks).
I even tried removing and reinstalling the integration from scratch (including redoing the registration), but something is different on 2022.02. |
The issue with becoming |
Override behavior in nest cameras to never go unavailable, due to significant nest stream flakiness. Cameras are marked unavailable on stream errors in home-assistant#54659 however nest streams have a high error rate (home-assistant#60353). Given nest streams are so flaky, marking the stream unavailable has other side effects like not showing the camera image which sometimes are still able to work. Until the streams are fixed, just leave the streams as available. I have not seen similar reports for other cameras, so I am only disabling this for nest.
I have been struggling with these 404 (and sometimes 403) errors for a while now. Interestingly, ever since 2022.3 the cameras are more responsive in the UI and load up faster. However, ever since 2022.3, my HA instance becomes unresponsive (happened 3 or 4 times); I'm not sure if this is related, but ever after it becomes unresponsive there still are a few log entries showing up related to Nest. Nothing appears in the "fault" log. Attaching my log file from today (18 March) which has debug turned on for related entities; HA became unresponsive a few minutes before the end of the entries in this log file. Happy to collect / provide more logs / info if it helps. Honestly, the log entries (404, 403) are benign as long as things work. My biggest concern lately is that HA becomes unresponsive |
My UI is still working fine, but I gave up on the camera feed. |
UI is always responsive here, but it is a rare moment to see the stream working, refreshing doesn't do any good. Still seeing the same 404 errors on the logs. |
I see this as well. I tried recreating everything from scratch today to see if that fixed it. I noticed based on the latest instructions I had two things wrong:
So I deleted the integration and remade it with a new client ID. Nothing seems to have changed unfortunately. Going to the dashboard where my camera cards are still just shows nothing and has 404 errors in the logs. I'm not too fussed about it since I still get the person detected events which is the main thing I care about it. But it would be nice to be able to see these streams in HA instead of having to go to the nest app. |
@mdegat01 your issue is probably home-assistant/home-assistant.io#22141 since i think you're talking about an issue getting the integration setup. This issue is about nest servers providing bad stream urls. |
I have this issue as well, 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:
It happens often so please let me know if there is anything else I can provide to help the SDM API team figure out what is the problem... |
@Lumute On my case it won't work most of the times, and it is a brand new Nest Hub Maxx. My nest hub camera can be disabled or enabled by the home/away assist feature, and I suspect that this happens when it is disabled. It would be good if one could confirm that and if that is true research for a way to enable it? |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
I am having this exact same problem. I have a Nest Doorbell and Nest IQ Outdoor and get this error on both devices. I am on HA 2022.08.3 |
This issue has been reported to Google (not a home assistant bug as far as we know, seen by other users of the APIs) |
My latest updated is that the Nest API folks are investigating. |
Hi folks, what would be helpful is if end users that see this go report an issue in https://developers.google.com/nest/device-access/support -- the information that is helpful is:
|
From issue https://issuetracker.google.com/issues/300953239 there is some update from Google
|
The problem
I could see it working only for a couple of times. Now all I see is a broken UI in HA.
What version of Home Assistant Core has the issue?
core-2021.11.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Nest
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nest/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: