Skip to content
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

HA media playback does not work with 2024.11 #757

Closed
andreasbuff opened this issue Nov 2, 2024 · 62 comments
Closed

HA media playback does not work with 2024.11 #757

andreasbuff opened this issue Nov 2, 2024 · 62 comments
Labels
bug Something isn't working

Comments

@andreasbuff
Copy link

andreasbuff commented Nov 2, 2024

Hello
I am using Frigate-Card with HA 2024.11.0b1 Release.
The friagate-card was working fine, until I upgraded to newest Beta. Now , the available clips are showed correctly,

image

but after clicking on a click, the playback fails. Playback of clip is "starting", but nothing is displayed...

image

type: custom:frigate-card
cameras:

  • camera_entity: camera.vorplatz_3
  • camera_entity: camera.eingang_3
  • camera_entity: camera.eingangstuere_2
  • camera_entity: camera.g3_strasse_high_insecure
  • camera_entity: camera.parkplatz
  • camera_entity: camera.gartenahus_stream0_0
@anybody84
Copy link

It seems it also doesn't work when trying to open it from the left panel (Media -> Frigate -> Recordings -> [camera_name] -> [date] -> [recording])

@felipecrs
Copy link
Contributor

felipecrs commented Nov 6, 2024

@anybody84, @andreasbuff, you can work around this issue by selecting go2rtc as the live provider in the Frigate card.

The card is probably using HA's live provider, which is not working due to:

@felipecrs
Copy link
Contributor

@anybody84, @andreasbuff, can you test if this fixes your issue?

image

@andreasbuff
Copy link
Author

andreasbuff commented Nov 7, 2024

Hello, thank you for your answer. No, unfortunatly it is not resolving this problem. The funny thing is, that, if you are hovering over the clip and if you are clicking on the Downloading-Link, then, the download of the correct clip is done. Hence, the pointer to the clip must be correct.
On the other hand, as mentioned allready by @anybody84, the clip is shown also in the media section of HA, but a playback from the Media-Folder (without using the Frigate-Card) is not possible either (see 2nd Screenshot)
image

image

It looks like it is rather a Codec-Problem than related to Frigate?

@anybody84
Copy link

Correct, I don't use the Frigate-Card. What I'm referring to is a playback from the Media side panel. Upgraded HA to version 2024.11.0 and the issue still persists.

@ohadlevy
Copy link

ohadlevy commented Nov 7, 2024

I can confirm, the computed url seems wrong (regardless if webrtc is enabled or not on the frigate integration configuration )

/media-browser/browser/app%2Cmedia-source%3A%2F%2Ffrigate/video%2Cmedia-source%3A%2F%2Ffrigate%2Ffrigate%2Fevent-search%2Fclips%2F%2F%2F%2F%2F%2F/undefined

@DbilliT
Copy link

DbilliT commented Nov 7, 2024

I have exactly the same issue for information. Download work but media and card doesn't.
(HA 2024.11.0)

@Boztekke
Copy link

Boztekke commented Nov 7, 2024

me 2 :(

@woempiej
Copy link

woempiej commented Nov 8, 2024

Hi,

Same issue.

afbeelding

Frigate card: Video's doesn't play anymore
afbeelding

HA sidebar > Media > Frigate > Clips: Video's doesn't play anymore

@r4h1mfr
Copy link

r4h1mfr commented Nov 8, 2024

Hello,
Same thing for me

@bsr203
Copy link

bsr203 commented Nov 8, 2024

The patch release 2024.11.1 mentions about go2rtc, ffmg etc

see https://github.com/home-assistant/core/releases/tag/2024.11.1

but, still can't play the videos from media folder.

@dermotduffy dermotduffy changed the title Playback with HA 2024.11.0b1 not working anymore HA media playback does not work with 2024.11 Nov 9, 2024
@dermotduffy dermotduffy added the bug Something isn't working label Nov 9, 2024
@dermotduffy
Copy link
Collaborator

Suggest we keep the Frigate card out of this issue, as it confuses things. This problem is simpler: Frigate + HA Media browser should work, but doesn't. This is either a HA bug, or a Frigate integration bug. The Media URL being composed appears incorrect:

GET https://$HA_INSTANCE/media-browser/browser/app%2Cmedia-source%3A%2F%2Ffrigate/video%2Cmedia-source%3A%2F%2Ffrigate%2Ffrigate%2Fevent-search%2Fclips%2F%2F%2F%2F%2F%2F/undefined 404 (Not Found)

Note the "/undefined" in the path.

@Nikhilse120
Copy link

Nikhilse120 commented Nov 9, 2024

I am getting the same issue not able to play recordings as play button is greyed out , any solutions ?

Update , i have rolled back HA version 2024.10 aand now its working fine

@ivanjx
Copy link

ivanjx commented Nov 9, 2024

i tried reverting to 2024.10 but still not working.

update: nvm i spoke too soon. i restarted HA once again and it starts to work.

update 2: the url does not seem to be the problem as the working version (2024.10) also has undefined in it: https://xx.com/media-browser/browser/app%2Cmedia-source%3A%2F%2Ffrigate/video%2Cmedia-source%3A%2F%2Ffrigate%2Ffrigate%2Fevent-search%2Fclips%2F%2F%2F%2F%2F%2F/undefined

@dermotduffy
Copy link
Collaborator

Thanks @ivanjx , I suspected this might be a red-herring. In any case, for now, sounds like sticking with HA v2024.10 and integration v5.4.0 is the best idea until we can figure this out.

I still strongly suspect this is a Home Assistant bug. I think the issue is the entityid property is not being set by ha-hls-player in the frontend (when I manually set this in the player via JS, the HLS stream starts correctly). I can understand why that value would be present for a camera, but not sure about media items that may or may not related to an entity. I suspect the cultprit is: home-assistant/frontend#22585

@dermotduffy
Copy link
Collaborator

dermotduffy commented Nov 9, 2024

I think that is the issue. For viewing live cameras (which is what the PR author probably tested), entityid is set correctly, but in the web-browser based media view it is not set at all.

./panels/media-browser/hui-dialog-web-browser-play-media.ts:

                  <ha-hls-player
                    controls
                    autoplay
                    playsinline
                    .hass=${this.hass}
                    .url=${this._params.sourceUrl}
                  ></ha-hls-player>

... yet in the components/ha-hls-player.ts...

  protected updated(changedProps: PropertyValues) {
    super.updated(changedProps);

    const entityChanged = changedProps.has("entityid");

    if (!entityChanged) {      <--- Won't ever get past this point without the entityid attribute.
      return;
    }
    this._getStreamUrl();      <-- Stream is started here.
  }

Adding original PR author to consider: @bramkragten . It seems like home-assistant/frontend#22585 may not have considered usecases related to media playing that have no entity at all (e.g. HA media player, and derivative usecases of that like frigate-hass-card). For example, it makes the url attribute private, which is likely a mistake unless there is a different HLS player entirely envisaged for media playing.

@srajones
Copy link

srajones commented Nov 9, 2024

Same issue here I've tried everything

@Lesswood2322
Copy link

Same issue

@dermotduffy
Copy link
Collaborator

dermotduffy commented Nov 10, 2024

(No need to chime in additional support, this likely effects all users of HA >= 2024.11 whether they use Frigate or not)

@dennisct
Copy link

Same issue here

@spec8320
Copy link

+1 here - life is working fine but media dont:

image

Problem is when I try to go to media -> frigate -> recordings. It looks like this:

image

The undefined part in request is suprising for me.

http://ha-link:8123/media-browser/browser/app%2Cmedia-source%3A%2F%2Ffrigate/video%2Cmedia-source%3A%2F%2Ffrigate%2Ffrigate%2Frecordings%2F%2F%2F/video%2Cmedia-source%3A%2F%2Ffrigate%2Ffrigate%2Frecordings%2Ftylsrodek%2F%2F/**undefined**

@dermotduffy
Copy link
Collaborator

dermotduffy commented Nov 12, 2024

Please stop updating the bug if you have nothing new to add. Nothing will happen here until the bug is fixed in the Home Assistant frontend, in the next release. For now, if this is important to you, please stick with a prior version of Home Assistant.

@kgiedrius
Copy link

I have the same issue: in 2024.10.3 - worked fine

@shpitz461
Copy link

Had the same issue with latest HA OS, I've downgraded the core to 2024.10.4 and it works now.

ha core update --version 2024.10.4

Core 2024.10.4 Supervisor 2024.11.2 Operating System 13.2 Frontend 20241002.4

@mapsindustrial
Copy link

The same problem for me.

@dermotduffy dermotduffy closed this as not planned Won't fix, can't repro, duplicate, stale Nov 17, 2024
@ZogrimNL
Copy link

Had the same issue with latest HA OS, I've downgraded the core to 2024.10.4 and it works now.

ha core update --version 2024.10.4

Core 2024.10.4 Supervisor 2024.11.2 Operating System 13.2 Frontend 20241002.4

Same issue where rtsp stream is working, snapshots can be viewed and only video media will not start. Downgrade core as mentioned works for me.

@PablaV
Copy link

PablaV commented Nov 22, 2024

2024.11.3 also does not fix this issue

@felipecrs
Copy link
Contributor

We've got news though: home-assistant/core#129990 (comment)

@PablaV
Copy link

PablaV commented Nov 22, 2024

That's for the streaming issue though not the media player playback issue

@felipecrs
Copy link
Contributor

Oh, I'm sorry, you're right.

@Codelica
Copy link

It looks like a fix was merged into frontend. So an updated frontend that includes it just needs to make its way into 2023.11.x.

@shwarnock
Copy link

Sorry to necro a closed ticket. I've been sitting through all the linked issues on HA and frigate. I am trying to figure out what updates I am waiting for across frigate and ha. I am currently on frigate 0.14 and HA 10.4. Am I just waiting for an HA update? And HA and Frigate Addon update? Frigate, Frigste add on, and HA?

@felipecrs
Copy link
Contributor

You just need to wait for the next HA release. 2024.11.3 still doesn't contain the fix. The Frigate version or the integration version doesn't matter for this bug.

@shwarnock
Copy link

You just need to wait for the next HA release. 2024.11.3 still doesn't contain the fix. The Frigate version or the integration version doesn't matter for this bug.

Thanks, that's what I was gathering but wanted to make sure because I saw somewhere that someone mentioned Frigate was misusing the camera entity in HA.

@shwarnock
Copy link

#759 this is the one I was mentioning. Curious if this could be related to my streams constantly dropping

@felipecrs
Copy link
Contributor

That issue is already fixed by the integration 5.5.0.

@shwarnock
Copy link

shwarnock commented Nov 27, 2024

That issue is already fixed by the integration 5.5.0.

Ok thanks. I'm still on 5.4.0 it seems. I'll update and see if that fixes my issue.

Edit: ah nvm it requires HA 11.x. I'll wait for the update from HA and then grab the update here and hope all my problems are solved lol

@Barley194
Copy link

Frigate integration 5.5.1
Home Assistant 2024.11.3

still not working for me.
obraz

@dermotduffy
Copy link
Collaborator

Home Assistant 2024.11.3

That's your problem. The fix is in 2024.12.0b0.

@elpabre
Copy link

elpabre commented Nov 28, 2024

Frigate HA integration 5.5.1
HA 2024.12.0b1
All is up !

Thanks you for the good job 👍

@almissag
Copy link

Still not working

Frigate HA integration 5.5.1

Home Assistant

Core
2024.12.0b1
Frontend
20241106.2

@Barley194
Copy link

I can confirm that:

Frigate integration 5.5.1
Home Assistant 2024.12.0b2

WORKS

@mapsindustrial
Copy link

I can confirm that:

Frigate integration 5.5.1
Home Assistant 2024.11.3

NOT WORKS

@felipecrs
Copy link
Contributor

The Frigate integration version doesn't matter for this but, by the way.

@timsavory
Copy link

Home Assistant 2024.12.0 does not fix for me (is using frontend version 20241106.2)...Still getting same error in Frigate camera view:

Failed to start WebRTC stream: webrtc: streams: dial tcp 192.168.0.90:554: connect: connection refused, exec/rtsp [rtsp @ 0x7fc984590000] method DESCRIBE failed: 404 Not Found [in#0 @ 0x7fc984812c00] Error opening input: Server returned 404 Not Found Error opening input file rtsp://127.0.0.1:18554/camera.reolink?audio&source=ffmpeg:camera.reolink%23audio%3Dopus%23query%3Dlog_level%3Ddebug&log_level=debug. Error opening input files: Server returned 404 Not Found (camera.reolink)

and also cannot play back clips, etc

@felipecrs
Copy link
Contributor

This seems like a different issue.

@timsavory
Copy link

This seems like a different issue.

The video appears briefly before this message, only started after updated to 2024.11.xx

@mapsindustrial
Copy link

I can confirm that:

Frigate integration 5.5.1
Home Assistant 2024.12.0

WORKS !!! 👍

@timsavory
Copy link

I can confirm that:

Frigate integration 5.5.1 Home Assistant 2024.12.0

WORKS !!! 👍

Thanks, I am not running the very latest version of Frigate, nor the latest Frigate integration so will do when I have a bit more time...

@francescopeloi
Copy link

francescopeloi commented Dec 5, 2024

I can confirm that:
Frigate integration 5.5.1 Home Assistant 2024.12.0
WORKS !!! 👍

Thanks, I am not running the very latest version of Frigate, nor the latest Frigate integration so will do when I have a bit more time...

If you see 20241106.2 as front end version in HA, you installed the new core with the new front end (that should be 20241127.4 not 20241106.2), but the new front end is not loaded in your browser yet. Clear your browser cache.

@timsavory
Copy link

I can confirm that:
Frigate integration 5.5.1 Home Assistant 2024.12.0
WORKS !!! 👍

Thanks, I am not running the very latest version of Frigate, nor the latest Frigate integration so will do when I have a bit more time...

If you see 20241106.2 as front end version in HA, you installed the new core with the new front end (that should be 20241127.4 not 20241106.2), but the new front end is not loaded in your browser yet. Clear your browser cache.

Thanks, its loaded now, the clips replay works but still the same error in camera view...

@dermotduffy dermotduffy unpinned this issue Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests