Clips and Snapshots not loading

[loadamasta]

Since HA 2024.10.4 (maybe a version earlier) the card does no longer load the clips and snapshots.

The thumbnails however are all there and show up as usual. However, after a clip on the thumbnail the clip or snapshot is not loading.

Issue occurs on Microsoft Edge (Windows), Firefox (Windows), Safari (macos), companion app (iOS).

[francescopeloi]

Happening to me too, I don't see any error on the console. I tried with the previous HA version, working fine, reloaded with the new HA version UI, broken. Same on android app. The new HA version has a change about WebRTC.

[bazzio68]

Same problem here, no live view.. but audio of cam is working

[meliborn]

same for me, I see pictures of clips but I can't load them.

[jeffreyrdubois]

Same issue for me as well

[IsaacInsoll]

Same here

[TheDuffman85]

I can conform this is also an issue on v6.0.0-beta.8

[napper306]

Similar. Clips and recordings won't load. Snapshots do load for me. Browser doesn't seem to matter. Android webview (via the Wallpanel app), Firefox in Windows 11 or Ubuntu 22.04,
I'll post this from Home Assistant Logs... not sure if this is relevant to this issue. I don't believe I have independently installed go2rtc installed on HA.

06:40:25.330 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:230 > error="write tcp 127.0.0.1:18554->127.0.0.1:43930: write: broken pipe"
06:40:35.656 WRN [rtsp] error="streams: exec/rtsp\n[in#0 @ 0x7fe330812c00] Error opening input: Invalid data found when processing input\nError opening input file rtsp://127.0.0.1:18554/camera.birdseye?audio.\nError opening input files: Invalid data found when processing input\n" stream=camera.birdseye
06:40:35.656 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:230 > error="write tcp 127.0.0.1:18554->127.0.0.1:53266: write: broken pipe"
06:40:40.815 WRN [rtsp] error="streams: exec/rtsp\n[in#0 @ 0x7f3d86212c00] Error opening input: Invalid data found when processing input\nError opening input file rtsp://127.0.0.1:18554/camera.birdseye?audio.\nError opening input files: Invalid data found when processing input\n" stream=camera.birdseye
06:40:40.815 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:230 > error="write tcp 127.0.0.1:18554->127.0.0.1:53270: write: broken pipe"

Home Assistant details:
Core 2024.11.0, Supervisor 2024.11.2, Operating System 13.2, Frontend 20241106.0

Until now things have been running smooth for many months. Thank you for the projects.

[Hukuma1]

+1. I thought this was due to my new network and ports being blocked. Guess not!

[dermotduffy]

Thank you all. I will investigate this weekend. If one of you that has this problem could hold down the Frigate menu button in the card for a few seconds, and then paste the diagnostics, that would be great.

[TheDuffman85]

card_version: 6.0.0-beta.8
browser: Mozilla/5.0 (X11; Linux x86_64; rv:132.0) Gecko/20100101 Firefox/132.0
date: 2024-11-08T15:21:59.610Z
frigate_versions:
  aaba97b52574c25c75ecef74a13dc30d: 5.4.0/0.14.1-f4f3cfa
lang: de
timezone: Europe/Berlin
git:
  hash: a869109
  build_date: Mon, 14 Oct 2024 00:01:23 GMT
  commit_date: Sun, 13 Oct 2024 16:50:47 -0700
ha_version: 2024.11.0
config:
  type: custom:frigate-card
  cameras:
    - camera_entity: camera.birdseye
    - camera_entity: camera.driveway
    - camera_entity: camera.corridor
    - camera_entity: camera.front
    - camera_entity: camera.garden
  dimensions:
    aspect_ratio_mode: unconstrained
  menu:
    style: outside
    position: bottom
    alignment: bottom
    buttons:
      display_mode:
        enabled: false
  live: {}
  layout_options:
    grid_columns: full
    grid_rows: full
  status_bar:
    position: top
    style: none
  cameras_global:
    dimensions:
      layout:
        fit: contain
        position:
          x: 50
          'y': 50

[francescopeloi]

{
  "ha_version": "2024.11.0",
  "card_version": "5.2.0",
  "browser": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36",
  "date": "2024-11-08T15:30:47.445Z",
  "frigate_version": {
    "3f32dde608d9d2653462afcc83306c6e": "5.4.0/0.14.1-f4f3cfa"
  },
  "lang": "en",
  "timezone": "Europe/Vatican",
  "git": {
    "build_version": "5.2.0-HEAD+g69249b6",
    "build_date": "Fri, 23 Jun 2023 15:26:26 GMT",
    "commit_date": "Thu, 22 Jun 2023 09:21:26 -0600"
  },
  "config": {
    "type": "custom:frigate-card",
    "cameras": [
      {
        "camera_entity": "camera.ingresso_civico_55",
        "go2rtc": {
          "modes": [
            "mse"
          ],
          "stream": "ingresso-civico-55-sub"
        },
        "live_provider": "auto"
      }
    ]
  }
}

[dermotduffy]

Can reproduce. I think there is actually a tangle of 3 different issues here, all with the same symptoms:

• Issue 1: With HA 2024.11 clips don't appear to work (regardless of card or Frigate version)
• Issue 2: With any version of HA, but Frigate Integration version v5.4.1 clips appear to return forbidden. This is almost certainly related to (my) refactor: Move proxy fuctionality to a common library blakeblackshear/frigate-hass-integration#758 .
• Issue 3: With any version of HA or the card, but Frigate 0.15+ clips don't appear to work (issue, did not test myself)

I plan to address them in this order.

[dermotduffy]

There's actually an issue 0 that has to be fixed first, not related to the card at all: blakeblackshear/frigate-hass-integration#757

Until Frigate + HA works (without the card), no point in trying to fix the card.

This is an impressive tangled web of related issues!

[dermotduffy]

• Issue 0: I believe I have traced this down to a Home Assistant frontend bug, follow that issue here: HA media playback does not work with 2024.11 blakeblackshear/frigate-hass-integration#757
• Issue 1: I need 0 fixed first to test, but I'll definitely need to make some card changes, at least these: fix: Adapt ha-hls-player patch to HA 2024.11 code #1679 . I plan to keep that PR open until 0 is resolved so I can know for sure.
• Issue 2: I think this is a red herring, at least I cannot reproduce it anymore (beyond the problems in the above issues)

[remon1496]

Just an FYI. They’re also not playing trough the Media Browser in HA. Not sure if its related. Snapshots load, but recordings (and clips) never load. Just like in the card itself.

— Edit: just read the above posts. You guys are crazy fast! Seems like an easy fix. Let go 2024.11.2 :)

[dermotduffy]

Yes, that is "Issue 0" described above. That must be fixed first in Home Assistant itself.

[macthaidhg]

Clips were not working for me after HA 2024.11.1 update and frigate v0.15 beta. Rolling back to HA 2024.10.4 fixed it for me. I didn't have to roll back to frigate v0.14. Eliminating "issue 3" above? Hope this helps!

[MilesTEG1]

Se problem for me too.
Following this issue.

[Jurgonh]

+1

[dermotduffy]

(No need to chime in additional support, this likely effects all users of HA >= 2024.11 whether they use Frigate or not, you can use the 'Subscribe' button to the right to be notified of updates without needing to spam everyone else on the issue. Thanks!)

[wr420]

+1. I thought this was due to my new network and ports being blocked. Guess not!

lol same, just switched to local ISP to Comcast and KNEW they were the problem :)

[Esp32-zapper]

I don't know if this is related, as I don't use frigate between the cams and HA, but after 24.11 a camera feed can mess up other things on the HA dash.
Everything works fine until you ho to a tab with one or more camera feeds. After that this will happen

1. If you are editing dash, gui for edit cards will come up blank, with just the header.
2. Trying to access "more information" page on a device, typically light or thermostat, that also will come up blank with just the header menu bar.
3. Trying to open device information will result in a completely blank screen. Without even the header.
4. Some cards will no longer be able to access any data. E.g. calendar card will show "no object found"
5. Trying to reload page will result in a timeout. Can not reach server. This happens both on web, ios&android companion apps. Only way out is to kill app and restart or on webb press stop and reload from start page.

After killing app/web page and restarting again, everything is back to normal again, until you go to a tab with camera feeds and the bug will reappear. Note you don't have to restart anything in the server end, just the client.

This is from the system/loggs

Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found, rtsps://:@wework-3-eu.stream.iot-11.com:443/v1/bfb0007feb7325bde9ywiw/css6opnhbmf6r7ds32c0qU1BbaAij5hP?signInfo=jRfl7COIsQk_b44JRxkk4LNvnA-eHINxTUJayaH-K5a_FeL8NDLjMxp0HdKLkfNBPSBwLIIcxAUbxcbJSH3XA498i46qtgEcOH4GZhyfddpmCzBU9rjMuMl3fccohiK4cZp_KEScqR6PVIKAV7HTi5S2kffAKCoAY4-WUieOWSE)

[Mikescotland]

I don't know if this is related, as I don't use frigate between the cams and HA, but after 24.11 a camera feed can mess up other things on the HA dash. Everything works fine until you ho to a tab with one or more camera feeds. After that this will happen

1. If you are editing dash, gui for edit cards will come up blank, with just the header.
   (...)

Unrelated to frigate. You use a stream from Tuya servers.
Take a look here:
home-assistant/core#94004

[hiteshsharma]

@dermotduffy is there an issue open in HA for issue 0? I didn’t find on this thread. If not then I can open one

[dermotduffy]

@hiteshsharma home-assistant/frontend#22755 (fixed as of yesterday, presumably in next release)

[dermotduffy]

Referring back to the list of issues that I think are necessary to close this bug:

• Issue 0: This is now fixed (but not released).
• Issue 1: <-- I will work on this next.
• Issue 2: I will test this when 1 is fixed.

Update: No point on working on 1 beyond what is already in the waiting PR until there is a HA release with the fix for 0.

[TheDuffman85]

@hiteshsharma home-assistant/frontend#22755 (fixed as of yesterday, presumably in next release)

Unfortunately this fix didn't made it to the 2024.11.3 release. It still uses the 20241106.2 Frontend.

[bazzio68]

@hiteshsharma home-assistant/frontend#22755 (fixed as of yesterday, presumably in next release)

Unfortunately this fix didn't made it to the 2024.11.3 release. It still uses the 20241106.2 Frontend.

That's so ridiculous...

[dermotduffy]

Quick update summary for those playing along:

• Issue 0: This is now fixed in HA core, but as per the frustration in this thread, sadly the November releases didn't include it. There's a pre-release v2024.12.0b0 with the fix.
• Issue 1: This is now fixed, but needs a card release. I'll do that shortly, a little before the 2024.12 release goes live as it's not backwards compatible.
• Issue 2: As @macthaidhg said, I think this actually works fine and I have Frigate 0.15, with HA 2024.12.0b0 working just fine with the card.

[zethis]

I can confirm this is fixed using the pre-release home assistant version, in my case this docker image:
image: 'homeassistant/home-assistant:2024.12.0b0'