[Support]: Frigate may be causing my entire Home Assistant to randomly restart #15447
Replies: 3 comments 23 replies
-
|
is the camera set up with 1x interframe spacing? and constant framerate? |
Beta Was this translation helpful? Give feedback.
-
Is your hardware usage high? (on both systems) |
Beta Was this translation helpful? Give feedback.
-
|
I've now gone for a different approach and completely separated HA and Frigate. I decided to just use the Intel box for HA work and use the spare memory for the mariadb addon. With the spare Pi4 box, I wiped it completely and installed a fresh RaspiOS 64 and installed docker with Frigate on that (with Coral USB). The integration between HA and Frigate still works nicely across the 2 boxes and the difference in performance and responsiveness has been amazing. The docker Frigate install works perfectly (at least for the 1 day I've had it up and run). I think it was perhaps a silly idea to try and get HA and Frigate running on the same box. |
Beta Was this translation helpful? Give feedback.
-
That's good to read, maybe I'm gonna try this too How many cameras are you currently using on Frigate? Do you think it could handle 3 streams with recordings enabled? |
Beta Was this translation helpful? Give feedback.
-
|
My new HW usage on the intel HA box is absolutely nothing - 8% CPU. My HW usage on the PI is also surprising low as well. The system reports CPU usage of 14%, which I find strange as when it was on HA it was up at 60%. I have 4 streams, 1 4k, 2 1080p and one a lot less. Although for detection I obviously use the sub streams. Have to be honest I have had a few drop out and crashes because my shm memory was set to low. I'm 90% happy with arrangement at the moment. I'll have a proper feel for it in a few weeks. |
Beta Was this translation helpful? Give feedback.
-
|
About the Pi HW, is it possible to set a different path to recordings, like an external SSD (via USB) for example? Do you use something like 2-way audio? How is the delay for the streams (in general)? I'll be happy to read your thoughts about this new set |
Beta Was this translation helpful? Give feedback.
-
|
have you found a solution for the reboot of the Intel HA host PC caused by Frigate HA addon ? I too suffer this problem. It takes a couple of hours and out of nowhere with no log entries my Host PC reboots. (Kernel panic?). I tried everything. CPU load is low (20 to 30%), and I am using an external Google Coral USB for the detector. My Intel is en Atom CPU. (without AVX), I tried both regular version (with or without full access), and the "older intel CPU" version, but they all suffer the same problem. When I look at CPU load, before the reboot the CPU load is frozen to a low value, then recovers after the reboot. I think the freezing takes some 5 minutes and then a reboot is done. Don't know if reboot is done by HA supervisor or by the CPU itself. I have checked BIOS settings, and also disabled C-states now. But did not solve it. Last what i did now was move the coral usb to a usb2 port instead of a usb3 port, maybe there is too much current drawn. Will see. |
Beta Was this translation helpful? Give feedback.
-
|
what solved it for me was using a powered USB hub got for the USB coral.... I cant confirm exactly what the issue is/was but I switched that in March and haven't had the issue since |
Beta Was this translation helpful? Give feedback.
-
|
I had similar, and moved Frigate to docker in Unraid - and I really should have done that done to take advantage of the intel CPU's in unraid. I just assumed that frigate and ha needed to be together for the integration - but it works exactly the same when separate. I am enjoying my system so much more now - an no longer sync'ing cctv from HA machine to my unraid - as it is all there. |
Beta Was this translation helpful? Give feedback.
-
|
Last week I also moved my Frigate off my HA to a separate RHL9 machine with Docker. My HA does not crash anymore and the seperate Frigate machine is also stable. And faster than when ran as HA addon. I now use the Frigate proxy addon in HA. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
For the past two months, my Home Assistant has been restarting randomly, and I haven’t been able to figure out why. I tried troubleshooting but had no luck. Eventually, I suspected some custom components might be causing the issue, so I disabled them one by one to see if anything changed.
Frigate appears to be responsible for the restarts. Could it have something to do with my CPU? I’m using an Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (a bit old, right?). I have a dashboard to monitor hardware stats, and the CPU usage has never been high. It sometimes peaks at 20% for a moment but stays very low most of the time. RAM also doesn’t seem to be an issue since it has 16 GB and is barely used. This PC was purchased as a pre-configured plug-and-play system from a local tech store.
I haven’t been able to figure out why Frigate is causing these restarts. I recently noticed that after shutting down Frigate entirely for a few days, Home Assistant stopped restarting. The restarts happen at completely random intervals—sometimes Home Assistant runs for 10 hours, and other times it restarts after just 5 minutes. There aren’t many logs to look at, aside from some Python threading errors.
Additionally, recordings occasionally stop with the following error message:
"WARNING: Unable to keep up with recording segments in cache for camera. Keeping the 6 most recent segments out of 7 and discarding the rest..."
Following this guide (link), I found that the copy times were under 1 second. This might suggest a CPU bottleneck, although CPU usage appears normal.
Should I consider setting up a separate PC just to run Frigate on my network? Or is there something else I should check?
Summary of Issues:
Version
0.14.1-f4f3cfa
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
Frigate stats
No response
Operating system
HassOS
Install method
HassOS Addon
docker-compose file or Docker CLI command
n/aObject Detector
Coral
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
What I’ve tried so far:
• Disabled recording temporarily.
• Switched from Frigate Card to WebRTC Card.
• Used the "Frigate (For old x86_64 CPU without AVX)" add-on.
None of above helped.
Hardware I'm using for now:
Reolink Doorbell PoE
Beta Was this translation helpful? Give feedback.
All reactions