-
-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Live camera view in Picture Glance eventually timeout/freezes, with a 404 loading playlist.m3u8 #34966
Comments
camera documentation |
I have tried removing the
I also found several other people with the same issue, so can confirm its not unique to my environment or setup. |
Issue persists on Home Assistant 0.109.1. |
Are your cameras WiFi or PoE? This is generally related to a stability problem with the video feed. |
I keep seeing the same Demuxing error in my logs; 2020-04-28 00:31:18 ERROR (stream_worker) [homeassistant.components.stream.worker] Error demuxing stream: No dts in packet Using 2 Wyze cams with the RTSP firmware. But other than the errors in the logs I dont see anything broken. Both cams always work fine. Currently running version 0.108.9 |
@hunterjm Perhaps, but video feeds are always likely to have errors, due to the high bandwidth requirement of trying to throw a ton of traffic over lines. Any errors should be handled gracefully. The RTSP stream works fine in VLC, Android VLC, through the camera web UI, and various other apps both on PC and Android, so if there are errors, every other platform handles them. It's only HA that does not gracefully handle whatever errors may be in the stream. FWIW HA is also the only platform where the stream consistently shows a ~30 second delay. |
The problem is with this line:
Clearly many of our cams are sending a "flushing packet" but not actually done with the stream. The same issue is present in #22840. I suspect commenting out that line would resolve things (even if it needs a better solution). |
I agree that dropped or late packets can be handled better, but commenting out that line won't solve your issue. In fact, it will put the stream in a perpetual error state, because we are not re-connecting to the feed, which is what needs to happen in this case. The delay is related to a mixture of your camera's settings and how HLS works to enable broad browser support without requiring a plugin (like your camera's web UI likely does). If you are curious, you can find more info about that at #34605 (comment) Home Assistant is doing things very differently than your standard RTSP viewing app all in the name of simplicity and performance so users running on a Raspberry Pi don't burn out their SD cards or over tax their CPU transcoding video. |
@geiseri - H265 is not supported in Home Assistant at this time. Unrelated to this issue. |
@hunterjm ah, okay. Well, that explains my issue. Thanks! |
I'm also having this issue with a Wyze V2 cam running RTSP firmware. I don't recall seeing this prior to .111 |
Having the same issue with DLink DCS-825L |
This is still a problem, many versions later, even using a totally different camera and stream. I'm now using the stream provided by motion-eye, i.e. my camera is defined as:
and yet, if HA is left open the browser too long: I do not think it is stream related, it is an issue with the picture glance card. If it is stream related, then the card is extremely sensitive to any stream issues, because viewing the stream in VLC or on my phone does not show any stream issues whatsoever. Once again, I think it is more an issue with the generated token timing out, because I see the card is trying to load the following resource:
but this returns a |
Seeing same error wyze cam v2 |
Hello, same issue with an Amcrest camera. I use both the Camera and Amcrest platforms to control the camera PTZ and take snapshots every 5 seconds when my alarm triggers. Everything seems to be working fine but I get these errors at least 2 or 3 times a day.
Cheers |
@hunterjm Just a thought, but maybe now that the "official" HA hardware is a lot more powerful, camera handling can be not completely nerfed just so that Pi users get the best experience? Or two options for stream handling can be provided? |
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 experiencing this. Does anyone have any work arounds, i like the glance cards |
I am also experiencing this, but only on 2 of my 3 dashboards that have glance cards on them. On the mushroom-loaded mobile-friendly dashboards, it locks up after a bit. On my 2 standard OOB dashboards, it works just fine. Not sure if that helps in the least. It's not an issue with the camera, because I'm streaming the same camera to my TV through HA -> Chromecast and it hasn't stopped. It has blipped for a couple of seconds, but it comes right back. |
The problem
Camera live view in Picture Glance card eventually stops working and either freezes the image or displays a broken link.
When checking chrome dev tools, the card is trying to load a resource that no longer exists, e.g.
http://hassio.home:8123/api/hls/32ed95d8af4b58633ba73d95c20ca18b05e0886ba5d2b4d95f91963421c8a490/playlist.m3u8
On refresh, a new /api/hls/..... URL is generated and the card works again for a while, until 404 again on the new playlist.m3u8.
To recreate:
I'm unsure if it's an issue with the card itself, or Core, as it seems like it would be Core thats removing access to the playlist.m3u8 and causing the card to fail.
Environment
Additional information
The text was updated successfully, but these errors were encountered: