Clips in media browser do not load

[srt]

Version of the custom_component

5.10.0

Describe the bug

Opening the Media Browser Frigate/Clips results in "Unknown error":

Debug log

The following URL is requested without paging (resulting in a large json response with a size of more than 35 mb:
http://frigate:5000/api/events/summary?has_clip=1&timezone=Europe/Berlin

2025-10-21 20:33:35.055 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://frigate:5000/api/events/summary?has_clip=1&timezone=Europe/Berlin: Response payload is not completed: <ContentLengthError: 400, message='Not enough data to satisfy content length header.'>
2025-10-21 20:33:35.055 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [133742416306208] Error handling message: Unknown error (home_assistant_error) XXX from xx.xx.xx.xx (Mozilla/5.0 (Linux; Android 15; WP55 Build/AP3A.240905.015.A2; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/140.0.7339.209 Mobile Safari/537.36 Home Assistant/2025.8.7-17352 (Android 15; WP55))
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client_proto.py", line 144, in connection_lost
    uncompleted = self._parser.feed_eof()
  File "aiohttp/_http_parser.pyx", line 511, in aiohttp._http_parser.HttpParser.feed_eof
aiohttp.http_exceptions.ContentLengthError: 400, message:
  Not enough data to satisfy content length header.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/frigate/api.py", line 398, in api_wrapper
    return await response.json()
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 100, in json
    return await super().json(*args, loads=loads, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client_reqrep.py", line 744, in json
    await self.read()
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client_reqrep.py", line 686, in read
    self._body = await self.content.read()
                 ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/streams.py", line 418, in read
    block = await self.readany()
            ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/streams.py", line 440, in readany
    await self._wait("readany")
  File "/usr/local/lib/python3.13/site-packages/aiohttp/streams.py", line 347, in _wait
    await waiter
aiohttp.client_exceptions.ClientPayloadError: Response payload is not completed: <ContentLengthError: 400, message='Not enough data to satisfy content length header.'>

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/frigate/media_source.py", line 759, in _get_event_summary_data
    summary_data = await self._get_client(identifier).async_get_event_summary(
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        timezone=info.get("timezone", "utc"), **kwargs
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/config/custom_components/frigate/api.py", line 143, in async_get_event_summary
    await self.api_wrapper(
    ^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    ),
    ^
  File "/config/custom_components/frigate/api.py", line 443, in api_wrapper
    raise FrigateApiClientError from exc
custom_components.frigate.api.FrigateApiClientError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 28, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/media_source/http.py", line 44, in websocket_browse_media
    media = await async_browse_media(hass, msg.get("media_content_id", ""))
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/media_source/helper.py", line 52, in async_browse_media
    item = await _get_media_item(hass, media_content_id, None).async_browse()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/media_source/models.py", line 97, in async_browse
    return await self.async_media_source().async_browse_media(self)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/frigate/media_source.py", line 721, in async_browse_media
    await self._get_event_summary_data(identifier), identifier, events
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/frigate/media_source.py", line 763, in _get_event_summary_data
    raise MediaSourceError from exc
homeassistant.components.media_source.error.MediaSourceError

[kpcz]

Same issue appeared.

Frigate Media Browser loading really slow, but in 80% it is giving Unknown Error.

Frigate version 0.16.1 running in Unraid container
Frigate hassio integration 5.10.0/0.16.1-e664cb2
HA Core 2025.10.3
HA Supervisor 2025.10.0

this in browser debug logs:

Uncaught (in promise) DOMException: DocumentFragment.querySelector: '#grid-Tapo: Recordings' is not a valid selector
    handleForChange tooltip.js:146
    update watch.js:17
    update watch.js:10
    update watch.js:22
    update watch.js:22
    performUpdate reactive-element.ts:1504
    scheduleUpdate reactive-element.ts:1400
    _$EP reactive-element.ts:1372
71977.e68cd4e63cd42032.js:1
Uncaught (in promise) DOMException: DocumentFragment.querySelector: '#grid-Clips [192.168.1.6:5000]' is not a valid selector
    handleForChange tooltip.js:146
    update watch.js:17
    update watch.js:10
    update watch.js:22
    update watch.js:22
    performUpdate reactive-element.ts:1504
    scheduleUpdate reactive-element.ts:1400
    _$EP reactive-element.ts:1372
71977.e68cd4e63cd42032.js:1
Uncaught (in promise) DOMException: DocumentFragment.querySelector: '#grid-Recordings [192.168.1.6:5000]' is not a valid selector
    handleForChange tooltip.js:146
    update watch.js:17
    update watch.js:10
    update watch.js:22
    update watch.js:22
    performUpdate reactive-element.ts:1504
    scheduleUpdate reactive-element.ts:1400
    _$EP reactive-element.ts:1372
71977.e68cd4e63cd42032.js:1
Uncaught (in promise) DOMException: DocumentFragment.querySelector: '#grid-Snapshots [192.168.1.6:5000]' is not a valid selector
    handleForChange tooltip.js:146
    update watch.js:17
    update watch.js:10
    update watch.js:22
    update watch.js:22
    performUpdate reactive-element.ts:1504
    scheduleUpdate reactive-element.ts:1400
    _$EP reactive-element.ts:1372
71977.e68cd4e63cd42032.js:1
Invalid URI. Load of media resource  failed. app,media-source://frigate

this in HA logs

Logger: custom_components.frigate.api
Source: custom_components/frigate/api.py:402
integration: Frigate (documentation, issues)
First occurred: 21 October 2025 at 22:30:32 (10 occurrences)
Last logged: 11:28:59

    Timeout error fetching information from http://192.168.1.6:5000/api/events/summary?has_clip=1&timezone=Europe/Riga:
    Timeout error fetching information from http://192.168.1.6:5000/api/events/summary?has_snapshot=1&timezone=Europe/Riga: 

[kpcz]

Removed integration, removed it from HACS, Reinstalled it in HACS, restart HassOS, added again in integrations, did not fix the issue :(

if I check in browser the link http://192.168.1.6:5000/api/events/summary?has_clip=1&timezone=Europe/Riga: it works and gives me a lot of data.

it looks like Media Browser in 10.2025 HA Core upgrade broke something globally.
https://community.home-assistant.io/t/solved-media-browser-unknown-error/938926/2

[kpcz]

@srt Have you found a solution for this issue?

[srt]

@kpcz No, this is a general design issue. It gets worse if you enable generative AI as the HA extension will pull every detail over the wire just to count the items :(
If we get a hint from @blakeblackshear on how this should be fixed we could try to provide a fix as PR.

[kpcz]

Something is causing frigate to answer api calls slower than usual (as it was prior latest HA version?) so looks like Frigate API doesn’t respond fast enough for Media browser and it times out.
Found a workaround, but I really dont like it, as browsing clips has a big delay now. Check if this workaround works for you as well.

In frigate componets folder find

/config/custom_components/frigate/api.py

and change value from 10 to 30

timeout_value = 30

Restart HA

[kpcz]

That lead me to conlusion that something is not right with the frigate.db.

Deleted db and every file except config. Deleted the recordings, and started frigate. Now media browser loads instantly.

[srt]

Deleted db and every file except config. Deleted the recordings, and started frigate. Now media browser loads instantly.

Sure if there is nothing to transmit it works instantly. If it has so send 35+ megs over the wire it is either slow or times out ;)
Unfortnately removing all recordings somehow defeats the purpose of frigate.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kpcz]

The problem still exists.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kpcz]

I have this setup on Unraid, moved all recordings to SSD disk (from HDD), db and config files are on NVME, Gigabit network between hassio and unraid. So no latency in network or disk IO. At first media browser was fast, but as recordings increment to frigate, media browser starts to load more slowly and slowly and slowly.. looks like it will start to give out timeouts again.
I am out of ideas, what is the curlpit, HA media browser, or something in Frigate. Really no one else has this issue?

[LiquidBlackNL]

I've got the exact same issue. Also SSD storage & gigabit on Proxmox.