Closed clowncracker closed 2 weeks ago
I too am having this issue after recently updating. Difference is I'm using HA OS and frigate in a docker container.
Core 2024.6.2
Supervisor 2024.06.0
Operating System 12.3
Frontend 20240610.0
Frigate: SYSTEM 0.13.2-69D9A261
HA Logs Log details (ERROR) This error originated from a custom integration. Logger: custom_components.frigate Source: helpers/update_coordinator.py:344 integration: Frigate (documentation, issues) First occurred: 12:52:20 PM (3 occurrences) Last logged: 1:48:47 PM
Error fetching frigate data:
I too am having this issue after recently updating. Difference is I'm using HA OS and frigate in a docker container.
Core 2024.6.2
Supervisor 2024.06.0
Operating System 12.3
Frontend 20240610.0
Frigate: SYSTEM 0.13.2-69D9A261
HA Logs Log details (ERROR) This error originated from a custom integration. Logger: custom_components.frigate Source: helpers/update_coordinator.py:344 integration: Frigate (documentation, issues) First occurred: 12:52:20 PM (3 occurrences) Last logged: 1:48:47 PM
Error fetching frigate data:
I'm using Frigate in an unraid Docker and Home Assistant in an unraid VM, so it sounds like we have the same setup.
@blakeblackshear any chance you can take a look at this?
Are you certain frigate is running without restarting itself?
Are you certain frigate is running without restarting itself?
Frigate itself isn't restarting at all, it's 100% stable. It's like the connection from Home Assistant to Frigate is unstable.
This keeps popping up in my logs. Is there anything I can do?
@blakeblackshear just wanted to follow up on this, it isn't getting any better. I'm getting hundreds of disconnects a day.
Having this issue too, Frigate is running but loses connection in Home Assistant.
Also started getting the "Detected Blocking Call" issue around the same time but thats from a Discord integration problem (I think).
It seems, random, nothing seems to trigger the disconnect.
` This error originated from a custom integration.
Logger: custom_components.frigate
Source: helpers/update_coordinator.py:344
integration: Frigate (documentation, issues)
First occurred: 20 June 2024 at 20:52:46 (57 occurrences)
Last logged: 08:25:20
Error fetching frigate data: `
My setup is running on Ubuntu Server with Frigate and Home Assistant Core running in Docker.
The integration doesn't maintain a persistent connection. It simply polls an endpoint every few seconds. Do you see a corresponding error in frigate's nginx logs?
I don't personally. I just see the usual and expected GET requests.
Its just strange that after the HomeAssistant update I'm now seeing the "Frigate Server Unavailable" "Frigate Server turned off" log messages, and it's also causing the Frigate cards to not display an image until I refresh Home Assistant.
If that's the case, then it seems like the integration is attempting to make an outbound network request, but it's never being received by Frigate. I'm not sure what changed in Home Assistant that would cause these timeouts. I just updated to 2024.6.3 to see if I can reproduce this. If I can't, I am not really sure where to look for issues or whether it's a problem with the integration or Home Assistant.
@h3x1e are you running the Mail and Packages addon? Even though it doesn't show in any debug logs, I think that might actually be the root cause of the issue. I disabled the addon for 12 hours and I haven't run into this issue since. I'm going to try reenabling it and see if I run into the issue again.
@clowncracker yes I am running it. Disabling it now to check!
It's been 15 hours since I disabled the Mail & Packages Integration, and Frigate in Home Assistant hasn't disconnected once. Something to do with the "Camera" part of the M&P Integration I guess, but idk.
I'm going to close this ticket, the issue wasn't with Frigate at all but with an unrelated addon. Sorry for assuming the worst of Frigate, I should have known better!
For anyone curious, it's being tracked here: https://github.com/moralmunky/Home-Assistant-Mail-And-Packages/issues/906
System Info
custom_component: 5.2.0 Frigate: Unraid Docker Frigate Version: 0.13.2-6476f8a OS: HAOS HAOS: Unraid VM HA Version: 2024.06.1
Configuration
Logs
Frigate logs
HA Logs
Describe the bug
I'm getting these errors in my HA logs fairly constantly after updating to HA 2024.06.x. I don't know if something in HA changed, but I didn't have this issue before this update. Note that I restarted Home Assistant and Frigate to get fresh logs, but this happens every 10 minutes or so.
Debug log