[Config Support]: Recording Required Zones

[AriaGen]

Describe the problem you are having

Since updateing to 0.14. The option for setting what zones were allowed to record seems to have gone, The YAML entry was automatically removed when I updated it but it seems to have stuck with the original settings I had set. I would now, like to change it so I get the clips for everything again, which is what I would expect to happen if the option has been removed.
Adding it back into my config.yml throws a config error and I can't find it within the new UI.

Version

0.14.0-da913d8

Frigate config file

cameras:
  driveway:
    ffmpeg:
      inputs:
        - path: rtsp://**@**/Streaming/Channels/102/
          roles:
            - detect
            - record
            - audio
      output_args:
        record: preset-record-generic-audio-aac
    objects:
      track:
        - person
        - umbrella
        - bicycle
      #  - car
      filters:
        person:
          min_area: 100
          max_area: 300000
          threshold: 0.65
        umbrella:
          min_area: 5000
          max_area: 400000
          threshold: 0.65
        bicycle:
          min_area: 5000
          max_area: 400000
          threshold: 0.65
        car:
          min_area: 2000
          max_area: 500000
          threshold: 0.50
    record:
      enabled: true
      retain:
        days: 3
        mode: active_objects
      events:
        retain:
          default: 3
          mode: active_objects
        objects:
          - person
          - umbrella
          - bicycle
  #        - car
  ##    ORIGINALLY HAD THIS NEXT SECTION HERE::: ###
        required_zones:
          - driveway_zone
          - caverswall_zone

Relevant log output

N/A

Frigate stats

N/A

Operating system

UNRAID

Install method

Docker CLI

Object Detector

Coral

Any other information that may be helpful

Admittitly, I might just be missing where the option is now.

[NickM-27]

The required zones are taken from the review section now

[AriaGen]

Thank you, I just needed clarification as it wasn't clear.
I had throught that this was just to define, wether they appear as alerts or detections.
It's odd, that for example with my driveway camera I have 4 zones:

• driveway_zone - Views as alert, that records
• caverswall_zone - Views as Detectioin, that records
• caverswall_ext_zone - Views as Detection, that doesn't record, snapshot only
• edenhurst_zone - Views as Detection, that doesn't record, snapshot only
  I will, change my config to this for my driveway and see if it performs any differently:

    review:
      alerts:
        required_zones: driveway_zone
      detections:
        required_zones:
          - caverswall_ext_zone
          - caverswall_zone
          - door_zone
          - edenhurst_zone

[NickM-27]

because we did not want to refactor the entire recording config and add another thing for users to reconfigure / re-learn, we decided to use the required zones field here to control the recordings required zones. I expect this to become more explicitly configurable in a future version.

[AriaGen]

Fair enough, this does seem to be working now. Thanks for your help on that front.

Is it also worth noting that I have now seem to have lost audio detection since updating too. Or is that processed differently now too?

[NickM-27]

It is shown as a detection by default

[AriaGen]

Okay, so nothing has changed really with it?

I've been deliberatly setting my house alarm off this evening and it hasn't picked it up (monitoring in home assistant).

[hawkeye217]

Worth mentioning that you can adjust these directly via the UI now in Settings --> Camera Settings.

[AriaGen]

This only appears to define whether the detection is just a detection or an alert. Not to choose whether it is just a snapshot or to take a clip.