False positives not showing up as snapshots

[tinimark]

Describe the problem you are having

This may well be user error.
I have a Node-Red flow set to turn lights on when a car is detected (this all works fine).
When the weather is bad I see the lights come on but no events or snapshots in Frigate+ are showing.
In Node-Red I can see mqtt is triggering binary_sensor.car_park_car_occupancy which is turning the lights on.
What conditions might I look for when Frigate is sending an MQTT msg but no video of snapshot is being recorded?

Version

0.14.1-f4f3cfa

What browser(s) are you using?

No response

Frigate config file

model:
  path: plus://9b45ccdf8d2a8822b5f4ea998ac7823d

detectors:
  coral1:
    type: edgetpu
    device: pci:0
  coral2:
    type: edgetpu
    device: pci:1

mqtt:
  host: 192.**
  user: **
  password: **

record:
  enabled: true
  retain:
    days: 3
    mode: all
  events:
    retain:
      default: 30
      mode: motion


birdseye:
  # Optional: Enable birdseye view (default: shown below)
  enabled: false
  # Optional: Width of the output resolution (default: shown below)
  width: 1280
  # Optional: Height of the output resolution (default: shown below)
  height: 720
  # Optional: Encoding quality of the mpeg1 feed (default: shown below)
  # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
  quality: 8
  # Optional: Mode of the view. Available options are: objects, motion, and continuous
  #   objects - cameras are included if they have had a tracked object within the last 30 seconds
  #   motion - cameras are included if motion was detected in the last 30 seconds
  #   continuous - all cameras are included always
  mode: objects

go2rtc:
  streams:
    car_park:
      - rtsp://**/Streaming/Channels/103

car_park:
    ffmpeg:

      inputs:
        - path: rtsp://**/Streaming/Channels/101
          roles:
            - record
        - path: rtsp://**/Streaming/Channels/103
          roles:
            - detect
    detect:
      max_disappeared: 20
      width: 1280
      height: 720
      fps: 6
    objects:
      track:
        - person
        - cat
        - dog
        - car
        - amazon
        - face
      filters:
        person:
          threshold: 0.8
        car:
          threshold: 0.8
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 10
    motion:
      mask: 
        0,0.336,0.073,0.272,0.042,0.253,0.074,0.232,0.096,0.209,0.186,0.189,0.277,0.175,0.325,0.171,0.343,0.138,0.347,0.114,0.343,0.08,0.358,0.08,0.366,0.105,0.387,0.146,0.406,0.172,0.467,0.173,0.526,0.183,0.628,0.189,0.798,0.209,0.83,0.154,0.834,0,0,0
 version: 0.14

Relevant Frigate log output

Nothing in the Log seems to mention anything useful relating to the issue.

Relevant go2rtc log output

N/A

FFprobe output from your camera

N/A

Frigate stats

N/A

Install method

HassOS Addon

docker-compose file or Docker CLI command

N/A

Object Detector

Coral

Network connection

Wired

Camera make and model

HIK

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[NickM-27]

If you're using MQTT you can look for has_snapshot

[tinimark]

HI Nick,

Thanks for the quick reply. I'm afraid my ability doesn't extend to querying the API.
Normally with false positives I'm able to see them as thumbnails in Frigate+ and then troubleshoot from there but some do not show up either in Frigate+ or the alerts menu.

[NickM-27]

I didn't say anything about the API. If you're using MQTT events topic to trigger the automation then that information is already there for you

[tinimark]

I'm using a state_changed node which is subscribed to binary_sensor.car_park_car_occupancy.
When Frigate sees a car it returns an "on" which is what triggers the automation.
Not too sure where has_snapshot would come from and what to do with it (filter out false MQTTs) still not sure why Frigate sometimes sends the MQTT signal but doesn't record a snapshot. Ideally, the MQTT signal would only be sent when frigate saves a snapshot.

[NickM-27]

Ideally, the MQTT signal would only be sent when frigate saves a snapshot.

Not necessarily. There are additional checks that take place for review items to be created. These checks take time though and often users are relying on the sensor to activate quickly to turn a light on, so the occupancy sensor does not wait for these checks.

You can listen to the /events MQTT topic instead to better customize the behavior

[tinimark]

Ah OK. I understand.
What would be the best way to fine tune the occupancy sensor against false positives if a snapshot isn't available to see what set signal off?
Do the filters in the config file affect occupancy sensitivity?

[NickM-27]

there's not a good way to tune the occupancy sensor, you'd just want to use the /events mqtt topic as I said.

Do the filters in the config file affect occupancy sensitivity?

yes, but also what gets created as a review item in Frigate.

[tinimark]

Thanks for your help. Much appreciated!