[Detector Support]: Errors when Coral detector enabled #11056
Unanswered
blarg3891
asked this question in
Detector Support
Replies: 1 comment 1 reply
-
this indicates some type of USB error, potentially with the host OS or some other layer, unlikely directly related to frigate |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
With coral enabled, errors in the logs prevent frigate from viewing cameras and any other functionality. I don't see the device reset errors in the Truenas Scale syslog when not connected to Frigate either. The "ws4py.exc.HandshakeError:" does occur when using the CPU detector but doesnt seem to stop frigate from working as expected. I could not find a way to fix this particular error.
Version
0.13.2-6476F8A
Frigate config file
docker-compose file or Docker CLI command
Relevant log output
Operating system
Other Linux
Install method
Docker Compose
Coral version
USB
Any other information that may be helpful
This is running on Truenas Scale (Cobia) / Truecharts latest versions which is k3s not docker. It is running as a Truechart App and pasing /dev for usb access. The frigate config file attached is a working file with CPU detector. I have no issues with the CPU detector, once the coral detector config is uncommented, all the errors begin. I added a pcie usb 3.2 card 25w power, 5w per usb port. I am also using a different usb cable, not the one that came with the Coral as per documentation recommendation.
Beta Was this translation helpful? Give feedback.
All reactions