Well, just a few days after moving from 0.4.0-beta to the dev version of the Frigate container, my machine locked up again. I noticed I wasn’t the only one with the issue:
https://github.com/blakeblackshear/frigate/issues/107
Are the Coral drivers different between those containers?
What is the last thing in your container logs?
When I had this problem with the 0.5.0 betas, I vividly remember there was nothing unusual in the container logs. With dev, I didn’t check the logs before I recreated the container based on the 0.4.0-beta image.
Based on the Github issue though, it seems like the problem is not with Frigate as the poster reported that the system froze with the Coral getting started guide.
I could run dev again and check the logs next time it freezes if you think that would be helpful.
Running Dev image over 3 days with 2 cameras without having to restart container.
@blakeblackshear - I seem to get several notification with same timestamp. You mentioned in past that the object tracking keeps same id for about 10 seconds. How has that changed in the latest Dev image?
It hasn’t changed. It is probably a timing issue with your notification images updating slower than the mqtt sensor changing.
Only time I saw a freeze lately was a USB bus error. Had to unplug and replug the coral. But that is once in over a month.
Got it.
I didn’t unplug the Coral at all when I downgraded from 0.5.0 back to 0.4.0-beta about 6 weeks ago, and the system hangs went away. So it’s something that changed between 0.4.0-beta and 0.5.0.
To rule out an issue with your code, I unplugged the Coral a few hours ago and I’m trying 0.5.0 in CPU mode. There’s not a lot of activity on my cameras so I’m fine with slower detection rates for a bit.
That’s the size of the object in pixels so that you can decide on settings for the minimum and maximum detection size of the object.
I merged and released 0.5.1 with all the latest changes from the dev image. If you are having any hanging issues, please make sure you are using the 0.5.1 image. All other 0.5.x versions have known issues with hanging.
Looks like the spiders are attracted to IR light. It’s trigeering my lights at night. 
Best solution to this is external IR illuminators. I have zero issues since I moved the IR source elsewhere.
Hi,
I’m considering moving from DOODS to frigate as well as purchasing a USB Coral device but I am on Hassio on a RPi 4 (4GB).
Is Frigate compatible? if not, is there plans to support it?
Thanks
How many cameras do you have? It is unofficially compatible for now via this issue: https://github.com/blakeblackshear/frigate/issues/109
You may want to look at an Atomic Pi because it has an x86 processor and its simpler to get the hardware accelerated video decoding to work. That’s what I am using for my setup with less cameras. It’s not as simple to get up and running, but it’s nice to not have to juggle ARM compatibility all the time.
Yeah I don’t think any of that is possible with hassio. Think that’s for people running it in docker.
You can run Docker containers with the Portainer addon. The container would need USB access, not sure if there are any restrictions with that method.
Before I go pull the trigger on this, since my motherboard doesn’t have a USB-C port, anyone know if the PCIe coral will or won’t work?
You don’t need USB-C. The cable it comes with isn’t even usb-c. It’s just USB 3.0 that you want but I think some people are even running limited frame rates on 2.0.
