[EdgeTPU Support]: Frigate doesn't see Coral eTPU #4232
Comments
|
What device is this running on? What USB ports are being used? Have you tried a different cable? |
|
Hello - This is running on HAOS>Virtual Box>MacPro>High Sierra. I've tried different USB 3.0 ports only and the included USB cable. |
|
What rules have you setup to pass the device via virtual box? Be aware that the device will change id and name once initialized |
|
Yes - I see/saw that. Here is the latest. Now it seems to be working! Not sure if I reboot/restart HA, it will continue though. This is what happened before
|
|
Protection mode disabled: |
|
Once the coral is initiialized its IDs will change and the name will go from |
|
Okay, working on it. Also, can you suggest the ffmpeg hwaccel_args? These don't work: ffmpeg: |
Those are nvidia and apple doesn't support nvidia GPUs so that makes sense. You'd have to pass a GPU in to virtualbox for starters and I am not sure if that is possible with your setup. I believe the MacPro would only support using the AMD GPUs since the Xeon CPU doesn't have an iGPU |
|
Does the Nvidia not work here? |
Am I doing this under MacOS or within the HAOS somehow? |
|
Interesting, nvidia usually doesn't play nice with Apple. I was thinking the latest mac pro though not the older one. In any case you'd need to pass that GPU in to virtualbox (have you done this?)
You are doing it in virtualbox |
|
Sorry, for the initialization of the Coral. Is this in MacOS or HAOS? |
It is in virtualbox, like I said. Exactly the same way you had the |
|
So in order to initialize the Coral, am I running this within the virtual box or on the host? |
|
The coral is initialized when frigate is run. What I'd recommend is just searching on here and finding another person who went through this and add what they did. Otherwise you can try running frigate and when it fails inside MacOS you should see if the device name has changed. Worst case you can try running those instructions inside MacOS. |
|
So this is not a NVIDIA GPU? |
Like I said above:
|
|
Yeah, it's not possible. I do have more CPUs available. Maybe I will just add those. |
|
Seems to be working although my CPU utilization is very high. I'm trying these options now. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. |
|
Recommend reading #3860 |
|
I have a feeling I should be looking for answers in a forum and not with you. The documentation doesn't really cover all the questions I have like ffmpeg with a MacPro with Xeon processors, detection resolution vs viewing resolution, why doesn't the Coral reduce the CPU usage, what is the TPU actually doing if not doing the detection, etc. Oddly, after a night - the CPU utilization is back in in the 40% range which I think is acceptable. |
I recommend reading #3860 Also the coral does reduce CPU usage but you're not able to use hardware accelerated video decoding which is a large chunk of the work as well. The coral does do object detection and that's the only thing it does |
|
Yes, I did read 3860 and my dimensions are all set exactly to the same as the camera. I also set the FPS. I think my OpenCL arguments should work in reducing the CPU utilizations. I'm also building motion masks. |
|
That explains the high CPU, we absolutely do not recommend running detect on high res stream especially 4K https://docs.frigate.video/guides/camera_setup/#choosing-a-detect-resolution |
|
2 things - After I added the motion zones, Also, the Coral "disconnects" from the host arbitrarily. I've tried different ports, buses, etc. Not sure how to fix that. In any case: Can I add more cpus to my VBox and dedicate them to Frigate detection? |
|
It is seriously discouraged combining coral and CPU detectors as it will essentially remove any benefit of having a coral As far as it getting disconnected, difficult to say why that's happening because frigate is running 3 layers removed from the hardware. |
|
There is an example in the cameras page https://docs.frigate.video/configuration/cameras |
|
Okay, so I can detect on the lower resolution stream, but what stream will be used for the "displaying" in the UI or on the Frigate card in Lovelace? I see where I can setup a role for recording on a different stream, but what about displaying? Is this the same thing? |
|
In the current release In the upcoming release the roles will be changed up and frigate will support full res live view everywhere |
|
En mi caso , frigate instalado como docker-compose, es imposible que me funcione bien coral. En el logs me muestra TPU found, pero no baja nada la cpu. Incluso probe a quitar coral y la cpu sigue igual que con coral. Hay que instalar algo en debian 11? |
Okay, Nick, I've redone everything with the lower "detect" streams and everything seems much better and stable. I also added the Coral back in and it's working too. I think as long as I don't have to reboot my HA, everything should be fine. |
Describe the problem you are having
The edgeTPU is only sometimes seen by Frigate even though HA sees it.
Version
Frigate (Full Access) Beta (0.11.1)
Frigate config file
docker-compose file or Docker CLI command
Not sure what this is?Relevant log output
Operating system
HassOS
Install method
HassOS Addon
Coral version
USB
Any other information that may be helpful
protection mode on or off, doesn't matter. I move the eTPU to a different port as well. No difference.
I was detected once.
The text was updated successfully, but these errors were encountered: