[Config Support]: problem car detection

[pilot1981]

Describe the problem you are having

Hi,
I would obtain only events with type car, but I see only person in my events...

Version

0.13.2

Frigate config file

detectors:
  coral:
    type: edgetpu
    device: usb
mqtt:
  host: 192.168.6.31
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: xxxxxx
  password: xxxxxxxx
  stats_interval: 60
cameras:
  cancello:
    detect:
      width: 2560
      height: 1440
      fps: 5
    ffmpeg:
      inputs:
      - path: rtsp://192.168.4.11:554/user=xxxx&password=xxxxx&channel=1
        roles:
        - detect
        - rtmp
    snapshots:
      enabled: true
      retain:
        default: 30
    objects:
      filters:
        car:
          mask: 1121,248,1175,1374,2511,1394,2498,531
      track:
      - car
environment_vars:
#  LIBVA_DRIVER_NAME_JELLYFIN: i965
#  LIBVA_DRIVER_NAME: i965
  LIBVA_DRIVER_NAME: iHD

Relevant log output

s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
2024-03-21 08:54:33.318330017  [INFO] Starting NGINX...
2024-03-21 08:54:33.318697615  [INFO] Preparing Frigate...
s6-rc: info: service legacy-services successfully started
2024-03-21 08:54:34.918990995  [INFO] Preparing new go2rtc config...
2024-03-21 08:54:34.959370271  [INFO] Starting Frigate...
2024-03-21 08:54:35.216967181  [INFO] Got IP address from supervisor: 192.168.6.31
2024-03-21 08:54:35.285068103  [INFO] Got WebRTC port from supervisor: 8555
2024-03-21 08:54:39.234630865  2024/03/21 09:54:39 [error] 141#141: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "ccab4aaf-frigate-fa:5000"
2024-03-21 08:54:40.513227916  [INFO] Starting go2rtc...
2024-03-21 08:54:43.166944276  [INFO] Starting go2rtc healthcheck service...
2024-03-21 08:54:44.225010848  2024/03/21 09:54:44 [error] 141#141: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "ccab4aaf-frigate-fa:5000"
2024-03-21 08:54:45.804436321  09:54:45.804 INF go2rtc version 1.8.4 linux/amd64
2024-03-21 08:54:45.806158872  09:54:45.805 INF [api] listen addr=:1984
2024-03-21 08:54:45.806534257  09:54:45.806 INF [rtsp] listen addr=:8554
2024-03-21 08:54:45.807049596  09:54:45.806 INF [webrtc] listen addr=:8555
2024-03-21 08:54:47.311102373  2024/03/21 09:54:47 [error] 140#140: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", upstream: "http://127.0.0.1:5001version", host: "127.0.0.1:5000"
2024-03-21 08:54:49.224634743  2024/03/21 09:54:49 [error] 141#141: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "ccab4aaf-frigate-fa:5000"
2024-03-21 08:54:53.815835550  [2024-03-21 09:54:53] frigate.app                    INFO    : Starting Frigate (0.13.2-6476f8a)
2024-03-21 08:54:53.815842476  [2024-03-21 09:54:53] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-03-21 08:54:54.049607926  [2024-03-21 09:54:54] peewee_migrate.logs            INFO    : Starting migrations
2024-03-21 08:54:54.177842761  [2024-03-21 09:54:54] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-03-21 08:54:54.224328966  2024/03/21 09:54:54 [error] 141#141: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "ccab4aaf-frigate-fa:5000"
2024-03-21 08:54:54.388413578  [2024-03-21 09:54:54] frigate.app                    INFO    : Recording process started: 242
2024-03-21 08:54:54.419398871  [2024-03-21 09:54:54] frigate.app                    INFO    : go2rtc process pid: 89
2024-03-21 08:54:54.599119858  [2024-03-21 09:54:54] detector.coral                 INFO    : Starting detection process: 252
2024-03-21 08:54:54.633470937  [2024-03-21 09:54:54] frigate.app                    INFO    : Output process started: 254
2024-03-21 08:54:54.635702619  [2024-03-21 09:54:54] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2024-03-21 08:54:55.047419392  [2024-03-21 09:54:55] frigate.app                    INFO    : Camera processor started for cancello: 268
2024-03-21 08:54:55.058861728  [2024-03-21 09:54:55] frigate.app                    INFO    : Capture process started for cancello: 269
2024-03-21 08:54:57.579798675  [2024-03-21 09:54:57] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found

Frigate stats

NA

Operating system

HassOS

Install method

HassOS Addon

Coral version

USB

Any other information that may be helpful

I'm interested only in car detection; already definied motion mask

[NickM-27]

it would be impossible to only see person events with this config as person detection is disabled. Perhaps this config has not been applied due to frigate not being restarted

[pilot1981]

what it means? config not beeen applied? why you think it?

In this image you can see result...after last reboot I see two false positive cars:

[NickM-27]

right, looks like the config is working as expected in terms of detecting cars. The docs cover handling false positives https://docs.frigate.video/configuration/object_filters

[pilot1981]

ok, I can go to correct them to prevent false positive...but why it find also person events? I don't want them...

[NickM-27]

I think it was because of an outdated config. if the config above is the config that is used then person events will not be created

[pilot1981]

solved itself