blakeblackshear / frigate

NVR with realtime local object detection for IP cameras
https://frigate.video
MIT License
18.24k stars 1.66k forks source link

[Support]: Coral Dev Board 1GB recommended? #2721

Closed antonbek89 closed 2 years ago

antonbek89 commented 2 years ago

Describe the problem you are having

This days impossible to get Coral USB

Does anyone here or the developers can give same recommendation about Coral Dev Board 1GB (it's the only one with available suppliers)?

I want to run Frigate and want its work amazing!!!

Version

.

Frigate config file

.

Relevant log output

....

FFprobe output from your camera

.

Frigate stats

No response

Operating system

Other

Install method

Docker CLI

Coral version

Dev Board

Network connection

Mixed

Camera make and model

.

Any other information that may be helpful

No response

nickrout commented 2 years ago

I am interested in this answer too.

blakeblackshear commented 2 years ago

I don't recommend it. The CPU isn't powerful enough to handle the other parts of frigate unless you have cameras with good configurable substreams that support low resolutions. It also has other known issues with the current version.

nickrout commented 2 years ago

Thanks, I found an online retailer with a NZ branch (RS online) who say they expect a usb coral on 25 February, so fingers crossed.

gszakacs commented 2 years ago

Lead times for USB/PCI/M2 boards seemed ridiculous so I ended up buying the 1GB dev board for ~$60 on ebay and followed the process below:

  1. Burn mendel image to sd card per https://coral.ai/docs/dev-board/get-started#flash-the-board

  2. Install sd card, move home to sd and add swapfile (low swappiness) per https://github.com/f0cal/google-coral/issues/61

  3. Install docker per https://github.com/f0cal/google-coral/issues/32 sudo apt-get install apt-transport-https ca-certificates curl gnupg2 software-properties-common curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add - echo "deb [arch=arm64] https://download.docker.com/linux/debian buster stable" | sudo tee /etc/apt/sources.list.d/docker.list sudo apt update sudo apt install docker-ce docker-ce-cli containerd.io sudo groupadd docker sudo usermod -aG docker $USER sudo reboot now

  4. Install docker compose: Check the current release and, if necessary, update it in the command if necessary. As of 20220205 a working command is: sudo curl -L https://github.com/docker/compose/releases/download/v2.2.3/docker-compose-$(uname -s)-$(uname -m) -o /usr/local/bin/docker-compose

  5. Enable putty to access dev board over LAN: Edit the /etc/ssh/sshd_config file: PasswordAuthentication yes ChallengeResponseAuthentication to yes

  6. Run frigate via docker-compose.yml. I suggest using the latest version which improved the detections of stationary objects.

Additional step - if docker compose fails with cannot autolaunch D-Bus without X11 $DISPLAY` Per https://www.codegrepper.com/code-examples/shell/%60Cannot+autolaunch+D-Bus+without+X11+%24DISPLAY%60 sudo apt-get install pass gnupg2 gpg2 – gen-key pass init $gpg_id

Caution ! Understanding the limitations (coral dev board has no HW encoder, limited ram/storage), I decided to use it only for object detection/tracking and taking snaphots for which it has been working great ! A miniPC is running separately to run a docker serving as an rtsp bridge for some cheap wifi color night vision cameras (wyze v3) and saving the HD streams 24/7. This way, I get ~ 15ms inference time for 4 cameras and the coral dev board CPU utilization is < 50% (max permissible utilization is 400% because of the quad core cpu of the coral dev board).

You can further improve this system by using mqtt to automate tasks or even integrate with Blue Iris: https://community.home-assistant.io/t/person-detection-with-blue-iris-google-coral-and-frigate-v0-8-0/254747

Shred99 commented 2 years ago

(RS online) who say they expect a usb coral on 25 February

Unfortunately, I think RS Online's ETAs for the Corals are just broken.

I ordered one in Mid November 2021 - ETA late January 2022. In early December, the ETA on the web site for new orders was early January, so I ordered another. Here we are in February, with the one I ordered FIRST being due in late April and the one I ordered later, having an ETA of 25/2/2022. Each day, I log in and check the ETAs and find that both ETA dates have increased by one day.

I think this is RSOnline's way of telling me that their actual ETA is "early 2023" like everyone else!

nickrout commented 2 years ago

I fear you are right, just got an email pushing mine back to 28.2.22, but it probably won't be the last one like that.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.