Frigate Card makes Home assistant UI non-responsive

Hi all,

I have Home assistant running in a VM on proxmox and Frigate running in an LXC which runs a docker container. I understand this would all be totally unsupported as it’s a difficult to trouble shoot.
Frigate is running really well (gpu passthrough, low inference, low cpu usage, etc) and i have no issues with it using it’s own interface direct and have fulfilled all of the requirements to run it with home assistant.
On the home assistant install i have installed Mosquito for mqtt as specified in the frigate docs.
On home assistant i installed the integration (via HACS i think as it’s not official)
On Home Assistant i have installed the associated card and added it to my dashboard and get the feed and it operates as it should.

This is then where it all goes wrong. The Dashboard becomes unresponsive you can click on items in the side menu but you just get the loading circle and no response. This happens randomly but pretty consistently including while trying to make edits to the dashboard. The only way to recover is kill the browser tab and reload. If you remove the card the Dashboard stops crashing.

MQTT server Log extract

2024-05-29 19:29:29: New connection from 172.30.32.2:42524 on port 1883.
2024-05-29 19:29:29: Client <unknown> closed its connection.
2024-05-29 19:31:29: New connection from 172.30.32.2:48400 on port 1883.
2024-05-29 19:31:29: Client <unknown> closed its connection.
2024-05-29 19:32:29: Saving in-memory database to /data//mosquitto.db.
2024-05-29 19:33:29: New connection from 172.30.32.2:42966 on port 1883.
2024-05-29 19:33:29: Client <unknown> closed its connection.

Home Assistant Core Log

Log Details (ERROR)
Logger: homeassistant.components.stream.stream.camera.rearcam
Source: components/stream/__init__.py:448
integration: Stream (documentation, issues)
First occurred: 17:25:21 (7 occurrences)
Last logged: 19:33:51

Error from stream worker: Error opening stream (ERRORTYPE_111, Connection refused) rtsp://192.168.2.35:8554/RearCam

Frigate log

2024-05-29 19:40:02.632068151  192.168.2.201 - - [29/May/2024:19:40:02 +0100] "GET /api/events?cameras=FrontCam&limit=50&include_thumbnails=0 HTTP/1.1" 200 24573 "-" "HomeAssistant/2024.5.4 aiohttp/3.9.5 Python/3.12" "-"
2024-05-29 19:40:02.654116384  192.168.2.201 - - [29/May/2024:19:40:02 +0100] "GET /api/events?cameras=RearCam&limit=50&include_thumbnails=0 HTTP/1.1" 200 24317 "-" "HomeAssistant/2024.5.4 aiohttp/3.9.5 Python/3.12" "-"
2024-05-29 19:40:02.669137729  192.168.2.201 - - [29/May/2024:19:40:02 +0100] "GET /api/events?cameras=SideCam&limit=50&include_thumbnails=0 HTTP/1.1" 200 7420 "-" "HomeAssistant/2024.5.4 aiohttp/3.9.5 Python/3.12" "-"
2024-05-29 19:40:02.729120220  192.168.2.201 - - [29/May/2024:19:40:02 +0100] "GET /api/FrontCam/latest.jpg HTTP/1.1" 200 54371 "-" "HomeAssistant/2024.5.4 aiohttp/3.9.5 Python/3.12" "-"
2024-05-29 19:40:02.736927653  192.168.2.201 - - [29/May/2024:19:40:02 +0100] "GET /api/RearCam/latest.jpg HTTP/1.1" 200 66947 "-" "HomeAssistant/2024.5.4 aiohttp/3.9.5 Python/3.12" "-"
2024-05-29 19:40:02.740740609  192.168.2.201 - - [29/May/2024:19:40:02 +0100] "GET /api/SideCam/latest.jpg HTTP/1.1" 200 79805 "-" "HomeAssistant/2024.5.4 aiohttp/3.9.5 Python/3.12" "-"
2024-05-29 19:40:31.574680044  [2024-05-29 19:40:31] frigate.comms.mqtt             ERROR   : Unable to publish to SideCam/motion: client is not connected
2024-05-29 19:40:43.261578211  [2024-05-29 19:40:43] frigate.comms.mqtt             ERROR   : Unable to publish to FrontCam/motion: client is not connected
2024-05-29 19:40:52.446451508  [2024-05-29 19:40:52] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-05-29 19:41:52.506257289  192.168.2.153 - - [29/May/2024:19:41:52 +0100] "GET /ws HTTP/1.1" 101 44704 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36" "-"
2024-05-29 19:41:53.015930929  [2024-05-29 19:41:53] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-05-29 19:42:00.305413908  [2024-05-29 19:42:00] frigate.comms.mqtt             ERROR   : Unable to publish to FrontCam/motion: client is not connected
2024-05-29 19:42:34.443726629  [2024-05-29 19:42:34] frigate.comms.mqtt             ERROR   : Unable to publish to RearCam/motion: client is not connected
2024-05-29 19:42:53.579073220  [2024-05-29 19:42:53] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-05-29 19:43:04.519969096  [2024-05-29 19:43:04] frigate.comms.mqtt             ERROR   : Unable to publish to RearCam/motion: client is not connected
2024-05-29 19:43:54.148116765  [2024-05-29 19:43:54] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-05-29 19:44:54.148393402  192.168.2.153 - - [29/May/2024:19:44:54 +0100] "GET /ws HTTP/1.1" 101 22280 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36" "-"
2024-05-29 19:44:54.798716805  [2024-05-29 19:44:54] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected

It looks to me as if Home assistant loses the feed from frigate which for some reason makes the dashboard none responsive. How home assistant/Frigate works under the hood is a little beyond me. It feels like a config problem but not where to start.

Any ideas?

Ok i think i have 2 issues going on.

I think i have figured out one problem. It’s a MQTT issue. Frigate by default uses port 1883 but mqtt/mosquito has been configured to use port 8883 with TLS by default. I have changed mqtt to accept port 1883 without tls temporarily until i figure out how to get frigate to work properly and securely using 8883.
But the dashboard still hangs but at least it will clear the issue from the logs and hopefully point to the real issue.

You can set the port in frigate config.

mqtt:
  enabled: true
  host: 172.22.2.111
  port: 1884
  user: user
  password: password
  client_id: frigate
  topic_prefix: frigate

Did you ever sort this? Having the same/similar issue.

1 Like