-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Frigate working (with Coral TPU) #4
Comments
Downside to Coral support—only the USB Coral module will work with the Raspberry Pi currently (see notes: https://pipci.jeffgeerling.com/cards_m2/coral-accelerator-ae-key.html). The M.2 PCIe versions won't work because of driver issues with the CM4 PCIe bus. (Note: Pi 5 may work with the PCIe version... however that version requires some specific / older Python libraries that could cause incompatibilities with Frigate...). But could still be a good option, we'll see. I might need to use a different CM4 IO board than the one I'm currently using (BitPiRat) so I can have a USB 2.0 interface. |
I have it running: However, nothing happens, and if I go to docker logs, I see:
|
Off to https://docs.frigate.video/configuration/index I go! |
MQTT's auth is a bit annoying. You have to manually create user / password pairs if you want to do that, after the mosquitto container is running... |
Things are mostly working, but MQTT is not starting up correctly because I don't have the automated hashing of the user/pass pair working correctly yet. I might do something like install mqtt client on the managed server (or run it in a Docker container temporarily or something), just to encrypt the auth file passwords. It's a bit annoying but might be doable. Just didn't want to have to add in more mqtt-specific tasks in the playbook. |
I have everything working (including event detection with USB Coral TPU), but I need to clean things up a bit and finish abstracting out the configuration so I can make it work with multiple locations more easily (right now the frigate config hardcodes one camera, my Annke C800 at 4K resolution). There were a few issues I had to sort out. First, I ran into the dumb Python thinks I'm not bright enough to manage my own system install, ha!, so I added this task to fix up the - name: Ignore PEP 668 because it's silly.
ansible.builtin.file:
path: /usr/lib/python3.11/EXTERNALLY-MANAGED
state: absent I also ran into problems with Ansible's current Then I messed with the C800 camera stream settings until I could get it working (it looks like it's a popular enough camera model it has it's own little section in the Frigate docs: https://docs.frigate.video/configuration/camera_specific/#annke-c800). |
This is well in hand at this point, running quite stable. Going to close this issue and move more work to #8. |
I would like to see if I can get Frigate working well... it seems to have a lot of momentum, especially around GPU or TPU-accelerated use.
They have a suggested Docker Compose setup: https://docs.frigate.video/frigate/installation
It looks like they have
arm64
images available, yay! https://hub.docker.com/r/blakeblackshear/frigate/tagsThe text was updated successfully, but these errors were encountered: