Frigate issue - CCTV

[getafix33]

I have Frigate installed in a Docker Container and it keeps restarting - basically stuck in a loop

I have removed, pruned and reinstalled and still the same.

I have attached my compose and frigate_config files

 

[Tinuva]

You need to look at the logs. Only way to know.

From the cli, docker compose logs

 

[acidrain]

I have Frigate installed in a Docker Container and it keeps restarting - basically stuck in a loop

I have removed, pruned and reinstalled and still the same.

I have attached my compose and frigate_config files

Looks like your detector config has an issue. "type" is not correctly indented.

Yours:

detectors:
  cpu1:
   type: cpu

From frigate docs:

detectors:
  cpu1:
    type: cpu
    num_threads: *

Also make sure to set the num_threads tag as it would default to 3, and if your cpu doesn't have that many, it likely may be an issue.

That said, they do recommend you rather use OpenVINO in CPU mode for detection.

 

[getafix33]

Thanks for the replies. I have corrected my config file and at least its not rebooting, but cameras arent showing although the rtsp stream displays fine in VLC.

Attached is my log file.

 

[acidrain]

There are a few things that could cause this, but what comes to mind is:

1. Codec issues. VLC generally can play just about anything, whereas frigate may not be able to decode the stream unless you have hardware acceleration. If you are using an Intel CPU try this config

mqtt:
  enable: true
  host: 192.168.40.99
  port: 1883
  topic_prefix: frigate

detectors:
  cpu1:
      type: cpu
  
cameras:
  Parking: # <------ Name the camera
    enabled: true
    ffmpeg:
      hwaccel_args: preset-vaapi
      inputs:
        - path: rtsp://username:[email protected]:554/live/video/Profile1
          roles:
            - detect
    detect:
      enabled: false # <---- disable detection until you have a working camera feed
      width: 1280
      height: 720

2. Ensure you have sufficient shared memory. This can be set in the compose file using the --shm-size=*** flag.

 

[getafix33]

Thanks for the replies.

I added the hwaccel_args: preset-vaapi setting.

I also noticed that the path for the rtsp stream was incorrect. Should have copied it from VLC, not gone with my memory.

All seems to be working now.

The PCi adapter for my Coral arrived. Now to get that set up correctly.....

 

[acidrain]

Thanks for the replies.

I added the hwaccel_args: preset-vaapi setting.

I also noticed that the path for the rtsp stream was incorrect. Should have copied it from VLC, not gone with my memory.

All seems to be working now.

The PCi adapter for my Coral arrived. Now to get that set up correctly.....

Pretty easy to get the coral tpu setup.

Just pass the device to the container.

in the config it's just 3 lines

detectors:
  coral:
    type: edgetpu
    device: pci

 

[getafix33]

Pretty easy to get the coral tpu setup.

Just pass the device to the container.

in the config it's just 3 lines

detectors:
  coral:
    type: edgetpu
    device: pci

I have made the necessary changes and frigate doesnt see the coral. Is there a way I can check if its recognised in Ubuntu?

 

[hilt_ctn]

I have made the necessary changes and frigate doesnt see the coral. Is there a way I can check if its recognised in Ubuntu?

I'm not Linux guru. But in a console / terminal window, running the lspci command will list your PCI devices. It will be a long list ( lists ALL PCI devices ), so you need to scrutinize.

At the risk of asking something obvious - Have you installed the drivers like so ?

 

[acidrain]

As stated above, you will need to install the drivers on the host first in order for the device to pass-through.

 

[getafix33]

As stated above, you will need to install the drivers on the host first in order for the device to pass-through.

I followed that tutorial and although got a few errors, it is now showing up in Frigate.