-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
First Camera stream in the dashboard not starting automarically #19799
Comments
I'm experiencing the same thing. I have a Additional findings:
And sure enough this part of the frontend bundle doesn't seem to play well. The offending bundle file "96996.w7vKRby48d0.js" is attempting the following near its end: var oi = $.KeySystemFormats
, li = $.KeySystems
, di = $.SubtitleStreamController
, hi = $.TimelineController But above that, var $ = void 0
, G = s($); It is not reassigned between the two code blocks. I'm fairly certain this code comes from https://github.com/video-dev/hls.js, but due to being minified and lacking sourcemaps I'm unable to locate exactly where in ETA: Still present on Home Assistant v2024.2.2, frontend v20240207.1 |
yeah I am experiencing the same problem |
Came here for this issue. |
Experiencing the same issue after updating to 2024.2.x |
Same problem for me since version 2024.2.x |
It's likely one of the dependency bumps for hls broke this and they need to revert until it's fixed upstream? I'm surprised more users aren't reporting this. |
There have been multiple bumps of hls.js in 2024.3, can anyone check if this issue is still there in the beta of 2024.3? |
Just checked... But wondering... I didn't get notified that there's new frontend and that I should reload home assistant... Is it maybe that I need to force? Or is that same as ctrl+f5? Force refresh in chrome etc... |
Reproduced the issue in dev 👍 |
Think you already know... but just in case:
|
Yeah, we use the light dist of hls, and they replace some packages with |
Same issue here! I'm back to 2024.1.6 and everythig works fine. |
Any idea if this can be fixed for 2024.3.x? If we have to wait for upstream? |
Same issue 2024.2.5 |
Is it possible it will be fixed in 2024.3.x as it seems as if a lot more users are experiencing this issue? |
I'm experiencing the same since 2024.2 and above. |
It looks like there was a patch pushed to the frontend which could fix this in 2024.4.0? |
Hi all, The issue is fixed in HA 2024.3.0 |
Version 2024.3.0 haven't resolved that issue for me. |
Did you clear cache? |
2024.3.0 is working for me 👍 |
Ditto, 2024.3.0 also seems to work here (first playback of recordings from Frigate now works again). |
Ok for me now in 2024.3.0 |
Yep confirm in 2024.3 it's working again.. all streams are loading and playing |
Adding my vote that upgrading from
to
Resolved this issue for me on both Firefox and Android. |
Checklist
Describe the issue you are experiencing
When loading a specific dashboard in Lovelace with multiple cameras to stream, the first one do not starts automatically while the others do.
Changing the order of the devices causes always the first one to fail doing autoplay. (E.g. it is not an issue related to an entity but only to the first entity in the dashboard whatever it is).
The dashboard has only cameras to steam from UNIFI protect.
If I switch to another dashboard and then I go back to the one with the cameras, then all streams start normally.
the issue happens then only when loading the page directly to the specific dashboard
It happens to all browsers and app too.
Describe the behavior you expected
All cameras should start streaming when opening the specific dashboard (Autoplay)
Steps to reproduce the issue
What version of Home Assistant Core has the issue?
Core 2024.2.1
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
No response
Which operating system are you using to run this browser?
No response
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: