Synology DS718+ DSM 7.2 Update 3 With Coral USB using Container Manager

[chrisuthe]

Hello all, after a bit of trail and error I got Frigate running successfully on my Synology DS718+ (Celeron J3455) using the currently latest DSM version (7.2-64570 Update 3) with the Coral USB TPU by creating the frigate container in container manager.

For the Coral USB detection

I have installed from the SynoCommunity:
"SynoKernel USB Serial drivers"
"SynoCLI Kernel Tools"
I am unsure if either of these are required or doing anything but they were already installed prior to me starting setup so I wanted to ensure I listed them
My Coral is plugged into a front USB port on my Syno and I have restarted syno since plugging it in

Here is what shows under "Control Panel -> Info Center -> Hardware":

As you can see I have a Zwave stick, a UPS and the Coral plugged in and detected.

Other packages that might be relevant:

FFmpeg 4
Python 2
PHP 7.4
Advanced Media Extensions
(Again, these may have zero to do with this working, I am not a docker or frigate guru by any stretch)

Setup/Install on Syno

First I created a new folder in /volume1/docker/ called frigate - I had previously used the "Docker" package to run Home Assistant and others prior to upgrading to 7.2.x so this is my first project but the path /docker/ existed)

I created a new project in Container Manager and named it frigate.

I selected create YAML, and this is the sanitized version (customize volumes as needed):

version: "3.9"
services:
frigate:
container_name: frigate
privileged: true # this may not be necessary for all setups
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:0.13.0-beta2
shm_size: "256mb" # update for your cameras based on calculation above
devices:
- /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
volumes:
- "/dev/bus/usb:/dev/bus/usb"
- /etc/localtime:/etc/localtime:ro
- /volume1/docker/frigate/config/:/config/
- /volume1/frigate-media:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "5005:5000"
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp
environment:
- LIBVA_DRIVER_NAME=i965 # if hwacl isn't working properly with the default iHD driver

As you can see it's a mix of the default suggestion and moving the USB item into volumes for some odd reason instead of devices. I also modified the port 5000 as it conflicts with the DSM CP.

Note this is referencing a specific beta image don't do that use the stable version instead!!!
(13.0 beta 2 is working fine for me in this configuration)

I started with the suggested minimum config and expanded from there and have added 4 cameras, detection is working and CPU usage is acceptable.

I have the HA Integration running and Go2rtc is working great.

[Devstored]

hi @chrisuthe , add - "/dev/bus/usb:/dev/bus/usb" in "devices" list

[chrisuthe]

hi @Devstored doesn't seem to need it?

[chrisuthe]

Side note, I set HWAccel to VAAPI, and now each camera is taking about 2% CPU down from 9-10% without hardware accel.

[igalg99]

Thank you for sharing. this has helped me to setup the container on my DS923+
although I cant find anywhere yet any info what hardware accel is suitable to use on my NAS as I am AMD Ryzen R1600. I can't understand if hardware acceleration is even supported with AMD Ryzen R1600.

[NickM-27]

Most AMD cpus do not contain a GPU so they do not support hwaccel

[igalg99]

Oh that's a shame i guess. I am still confused about all this configuration options and hardware acceleration but this is also the conclusion i was getting at . Was just hoping I am wrong. So I just comment out everything related to hardware acceleration I guess. It does make it simpler though :) although probably less effective.

…

On Sat, Nov 4, 2023, 22:49 Nicolas Mowen ***@***.***> wrote: Most AMD cpus do not contain a GPU so they do not support hwaccel — Reply to this email directly, view it on GitHub <#8127 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AURNINWZDUMEYBYTOAVOUPDYC2Z7ZAVCNFSM6AAAAAA54B4XE2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINZWGQ3DA> . You are receiving this because you commented.Message ID: ***@***.*** com>

[aisbergde]

@igalg99 - did you find a way to use hardware acceleration on a DS923+? For now I am using CPU for detection. And what I read about using Coral on Synology - maybe it's not just plug and play.

[igalg99]

No I did not. In my searches I concluded (maybe wrong) that it is not possible due no GPU in Ds923+
I use coral via Docker with frigate but it's just for detection not for hardware encoding/acceleration

[mx-vatte]

I can confirm sadly that there is no possibility to use hardware acceleration due to the lack of a GPU. The Ryzen 1600 just don't have a GPU.

[chrisuthe]

FYI @aisbergde HW accel is not the same as different detectors.

HW Accel in this context is just decoding the streams as they arrive

Coral vs CPU detection is doing the actual image analysis and is MUCH more important to accelerate in some way (via coral or vino etc)

[aisbergde]

Yes, I got this. And after adding a coral USB stick for detection I am very happy with the performance and don't need any additional hardware acceleration. I was impressed about the big difference, when using the coral stick. Before using it my NAS CPU was completely occupied by frigate and detection results where not the best. Now the stick is doing the work, CPU is fine and detection results are much better.

[jace]

I tried doing this on a DS920+ with a Coral USB accelerator plugged in, but the Frigate container shuts down shortly after startup, far too soon to even open the terminal in docker. Any suggestions for how I can diagnose what is wrong? Here's my project YAML:

version: "3.9"
services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:0.13.0-beta2
    shm_size: "256mb"
    devices:
      - /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
    volumes:
      - /dev/bus/usb:/dev/bus/usb  # For USB Coral Accelerator
      - /etc/localtime:/etc/localtime:ro
      - /volume1/docker/frigate/config/:/config/
      - /volume1/docker/frigate/media:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5005:5000"
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
    environment:
      - FRIGATE_RTSP_PASSWORD="…"
      # - LIBVA_DRIVER_NAME=i965 # if hwacl isn't working properly with the default iHD driver

[Landonthi]

I have Home Assistant installed on a virtual machine on my Syno DS920+ and installed Frigate through HA, I also have a Coral installed on the 920+. For the install of the Coral I didn't have to install any extra drivers or kernel tools, I just plugged it in and shows up as USBDevice - Google Inc. on DSM 7.2.1-69057 Update 4. I then added the Coral into the VM and restarted it and added the lines in Frigate Config file for the coral. It is showing up in Frigate under detectors. I am having some issues with Frigate not showing video from the one camera I have setup, it just displays a black box saying "No frames have been received, check error logs", once and a while the video will update and show up for a few seconds. So I feel like I am making some progress but am not sure what the errors mean, I have posted them in hopes that someone will have some insight into what's going wrong. I feel like I have just the basics coded in the Frigate config file, but maybe I have screwed something up.

Thanks for any help you can provide

[chrisuthe]

Hey look facebook to Github it all comes full circle @Landonthi... The difference between our setups is that you're running HA in a VM and using the Frigate add on, where as I am running frigate in a docker (HA also in a different docker). I think most people "prefer" the HAOS route as it's more self contained, but that is the only thing I can see different.

First things first, the setup guide for frigate aptly suggests you remove any detection from your config to just get the video going in and out, and I think that is not a bad idea here.

I'd add this above your "cameras" config item to let frigate use HW Accel for video encode/decode:

ffmpeg:
  # NOTE: See hardware acceleration docs for your specific device
  hwaccel_args: preset-vaapi

This works a treat on my DS718 and should also work for you celeron based 920+

[plasmonized]

Hey Chris,

I just wanted to leave some big THX here, you helped me after a days long struggle to finally get frigate working!
my Setup is:
RS2418+ 64 GB RAM
2x Coral USB
4 Reolink Cams. Works brilliant like you adviced. In homeassistant directly I did have big performance problems!

THANKS!!!!
Alex

[bastian1607]

Today I received my DS923+ with newest DSM. I was using HomeAssistant with Frigate on Proxmox before. I installed HA with the virtual machine. In Synology DSM itself I did not see the Google Coral or a USB, but in the VM it detected a USB, but not as Google Coral. Frigate installed the necessary packages in HomeAssistant. Afterwards I needed to mount the USB again but it was recognized as Google Coral and it works finde.

Maybe this helps someone.

[bastian1607]

I have now installed Frigate as a separate Container and linked it with HA via Frigate Proxy. This is working better as sometimes the Coral detection got stucked.