Closed theDontKnowGuy closed 2 months ago
Hard to tell, but you must be using the most recent version of both Frigate and the integration.
Are you running this version of Frigate?
@theDontKnowGuy @dermotduffy
I had the same issue and it seems to have reolved by reloading the HomeAssistant Frigate Integration...
Running the latest Frigate 0.13.1 image: "ghcr.io/blakeblackshear/frigate:stable"
Running the latest HomeAssistant 2024.2.1 Running the HomeAssistant HACS Frigate Integration v5.0.1: https://github.com/blakeblackshear/frigate-hass-integration The Lovelace card is HomeAssistant HACS FrontEnd frigate-hass-card v5.2.0: https://github.com/dermotduffy/frigate-hass-card
The Frigate HACS Integration failed to load but after reloading the HACS integration seemed to now work and streams get displayed in HACS card correctly.
Experienced the same thing. Got it working by upgrading the docker image for my seperate Frigate server. Was on version 0.12..something, upgraded to 0.13.1-34...
@runegang Hi guy, thanks for this information. But sorry i'm noob with docker, how to update frigate stack?
my stack image : ghcr.io/blakeblackshear/frigate:stable Can i change this image, beacause last updated is a year ago?
thanks you in advance.
@Fr3n3z1 I'm no expert at this. I use portainer and recreated the docker image there while also pulling the latest image.
I have a same issue after ~8s when viewing the frigate card in home assistant.
The frigate card was working perfectly for one year, except in the last two weeks, probably since the last update.
I reinstalled both addons and the frigate docker image, these did not help. It is strange, that the issue arises only on 2 type of cameras, the other 2 are working normally. In the error log of HA I se these:
2024-02-15 21:16:09.745 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0:
2024-02-15 21:20:32.085 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0:
2024-02-15 21:20:47.987 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0:
2024-02-15 21:21:37.870 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0:
2024-02-15 21:25:51.848 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0:
2024-02-15 21:29:04.267 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0:
2024-02-15 21:29:04.876 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0:
2024-02-15 21:29:46.323 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0:
@runegang Thk you for fast reply. I solved it and find solution.
to share the solution to everyone:
First of all, make a backup of the docker or stack, or portainer... it's very important.
In portainer go to image section --> at the top of the page in the "pull image" section copy this link:
ghcr.io/blakeblackshear/frigate:0.13.0
and click on “pull image”
Next go on "Stack" section and select the frigate stack
Click on "Editor"
and change the value : image: ghcr.io/blakeblackshear/frigate:stable
by image: ghcr.io/blakeblackshear/frigate:0.13.0
do not forget to add in "Volumes" section : - ./config:/config
In my case, it's my stack :
version: "3.9"
services:
frigate:
container_name: frigate
privileged: true # this may not be necessary for all setups
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:0.13.0
shm_size: "79mb" # update for your cameras based on calculation above
devices:
- /dev/bus/usb:/dev/bus/usb # passes the USB Coral, needs to be modified for other versions
- /dev/apex_0:/dev/apex_0 # passes a PCIe Coral, follow driver instructions here https://coral.ai/docs/m2/get-started/#2a-on-linux
- /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime
- /frigate/config.yml:/config/config.yml
- ./config:/config
# - /path/to/your/storage:/media/frigate
- /NVR:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "5000:5000"
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp
environment:
FRIGATE_RTSP_PASSWORD: "password"
And click on "Update the stack"
And now you can update "Frigate hacs addon" on Home Assistant.
It's work fine for me. Depend of your configuration
Enjoy!!! :-)
Thankyou for posting solution 😀
hi @Fr3n3z1 , had same issue, thx for the guide, this fixed my broken frigate docker, now i can see it again in my HA
First of all, make a backup of the docker or stack, or portainer... it's very important.
In portainer go to image section --> at the top of the page in the "pull image" section copy this link:
Are there any suggestions for someone who isn't using docker? I'm running HA OS and frigate is loaded via HACS. Everything was working good until I upgraded to the latest Frigate and Home Assistant Core. I can get things working by restoring a backup, but that is only a temporary solution.
Ok, I've been playing around with this. My error was "Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:default".
Google searches led me here, but my problem was actually not the same as the original post.
What I've discovered is that when I upgraded Frigate / HAOS / HACore the result disabled my frigate add-on. I realized this when looking at my Frigate add-on and noticed it's not running. I hit "start" and my problems went away. This was strange behavior because I've upgraded HAOS / HA Core / Frigate many times, and this has never happened until now. Frigate has been running so flawlessly for the past couple of years, I didn't even remember there was a "start" button.
I thought I'd share, since other people may have the same problem and need a solution.
This was strange behavior because I've upgraded HAOS / HA Core / Frigate many times, and this has never happened until now. Fri
Just to make sure, is the Watchdog enable? Otherwise a crash would have kept the add-on in stop state.
Yes, the watch dog is enabled. Also "start on boot" is enabled. I'm tempted to restore an old backup and repeat the upgrade process to try to understand this bug.
I repeated the upgrade process and found the issue. My frigate config file had some errors that v0.12.1 tolerated, but V.0.13.2 does not. The errors caused Frigate to stop. After I corrected the errors, I rebooted the system with the expectation that Frigate would start on boot (that's what "start on boot" and "watchdog" should do). But this is not the case, I needed to manually start Frigate.
It's very likely the watchdog gave up after a specific count of failures.
Pre this issue:
Watchdog attempt to restart the service 10 times within 4 mins. This resulting the limit reached.
Aside the above, couldn't find a good reference that clearly state what triggers the Watchdog to give up. I'm just not using the proper keywords in the Search engine ;)
I have a same issue after ~8s when viewing the frigate card in home assistant.
* frigate 0.13.1-34fb1c2 (in docker) from frigate:stable * HA 2024.2.1 * Frigate integration in HACS v5.0.1 * Frigate Card in HACS v5.2.0
The frigate card was working perfectly for one year, except in the last two weeks, probably since the last update.
I reinstalled both addons and the frigate docker image, these did not help. It is strange, that the issue arises only on 2 type of cameras, the other 2 are working normally. In the error log of HA I se these:
2024-02-15 21:16:09.745 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0: 2024-02-15 21:20:32.085 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0: 2024-02-15 21:20:47.987 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0: 2024-02-15 21:21:37.870 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0: 2024-02-15 21:25:51.848 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0: 2024-02-15 21:29:04.267 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0: 2024-02-15 21:29:04.876 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0: 2024-02-15 21:29:46.323 ERROR (MainThread) [custom_components.frigate.api] Timeout error fetching information from http://192.168.10.63:5000/api/events?cameras=doorbell&limit=50&include_thumbnails=0:
I am having the same issue, except that it's happening on all my cameras. I'm running Frigate and HA on separate Docker containers:
* frigate 0.13.2-6476f8a
* HA 2024.3.1
* Frigate integration in HACS v5.0.1
* Frigate Card in HACS v5.2.0
These errors also appear to cause a gradual increase in the memory usage for the HA container, until it eventually results in the container being restarted after anywhere from 4 to 8 hours. The host system has a Ryzen 5 Pro 4650G (6C/12T) , 32GB RAM, and a Google Coral stick for Frigate among other things.
EDIT: I managed to fix the timeout errors on my end by moving frigate.db to an SSD, instead of having it on the same hard drive where the recordings are stored. However, the memory leaks and eventual restarts of the HA container still happens.
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.
I am also experiencing this issue. It is happening across all my cameras. In two different HA/Frigate installs. Any troubleshooting tips to get this working? Everything is up-to-date...
I am also experiencing this issue. It is happening across all my cameras. In two different HA/Frigate installs. Any troubleshooting tips to get this working? Everything is up-to-date...
It has been a little while, and I have forgotten most of the details. I remember finding bad syntax or structure in my "frigate.yml" file. The errors had been either accepted or ignored in the older version, but the new version rejected the errors and crashed. I suggest two things for you: a) check the frigate error log carefully. For me there were errors about the config file that led to the line or lines with errors. b) go thru your YML file and make sure it follows the official structure
Another option for troubleshooting would be to delete or comment out large sections of your YML file until frigate works. Then start inserting sections of YML until it breaks.
My setup includes Frigate runs on one server (V13, docker, TPU device), and the latest HA runs on its own server (latest version, now 2024.2.1).
Using cameras live views on different Lovecase dashboards using the FE integration V5.2.0.
When upgrading to 5.0.1 of the integration, these cards stopped working and display "Camera unavailable " along with the card's configuration (attached below). Functionality of the cards seems to be working except of live view.
Rolled back Home Assistant from backup (hence V4.x of the Frigate integration) all works again.
Card configuration:
Testing http://frigate_server_ip:5000/api/stats:
No Frigate related errors in the HA log.