[Config Support]: Line Unknown: - Value error, could not convert string to float: ''

[backcountrymountains]

Describe the problem you are having

tl;dr I may have found the problem while writing this, read the "any other info" section first pls.

I'm trying to adjust my detect: width and height but the config validator is fighting me. I had a completely working config, but I was reading and I had the width/height set suboptimally.
This was my working config:

 detect:
      enabled: true # <---- disable detection until you have a working camera feed
      width: 3840 # <---- update for your camera's resolution
      height: 2160 # <---- update for your camera's resolution

My detect stream is actually only 896x672. I can change the width to 896, but if I change the height to anything less than 964, I get an "invalid config" error and I can't save my config.
This throws a validation error:

detect:
      enabled: true # <---- disable detection until you have a working camera feed
      width: 896 # <---- update for your camera's resolution
      height: 672 # <---- update for your camera's resolution
      fps: 5
      stationary:
        interval: 50
        threshold: 50

This does not throw a validation error:

 detect:
      enabled: true # <---- disable detection until you have a working camera feed
      width: 896 # <---- update for your camera's resolution
      height: 964 # <---- update for your camera's resolution
      fps: 5
      stationary:
        interval: 50
        threshold: 50

Version

System 0.16.0-c2f8de9

Frigate config file

doorbell_reolink:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://127.0.0.1:8554/doorbell_reolink
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/doorbell_reolink_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
      hwaccel_args: preset-vaapi

    detect:
      enabled: true # <---- disable detection until you have a working camera feed
      width: 896 # <---- update for your camera's resolution
      height: 672 # <---- update for your camera's resolution
      fps: 5
      stationary:
        interval: 50
        threshold: 50

    objects:
      track:
        - person
        - car
        - motorcycle
        - dog
        - bicycle
      filters:
        person:
          # Optional: minimum width*height of the bounding box for the detected object (default: 0)
          #min_area: 5000
          # Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
          #max_area: 24000000
          # Optional: minimum score for the object to initiate tracking (default: shown below)
          min_score: 0.7
          # Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
          threshold: 0.7
        # car:
        #   mask:
        #     - 563,1394,490,1674,0,1920,0,967,207,964,733,1101,799,1161,784,1316


    snapshots:
      enabled: true
      clean_copy: true
      quality: 100
      # required_zones:
      #   - street
      #   - front_door
    live:
      streams:
        doorbell_reolink: doorbell_reolink
    motion:
      improve_contrast: true
      mask:
        - 0.745,0.134,0.792,0.598,0.428,0.582,0.44,0.1
        - 0.346,0.458,0.347,0.497,0.3,0.5,0.299,0.46
        - 0.248,0,0.244,0.076,0.386,0.075,0.385,0
        - 0.191,0.143,0.39,0.093,0.589,0.101,0.964,0.267,0.974,0.363,0.601,0.278,0.553,0.183,0.19,0.192
        - 0.514,0.669,0.509,0.87,0.678,0.859,0.845,0.792,0.833,0.656
        - 0.731,1,0.763,0.845,0.806,0.714,0.822,0.593,0.886,0.596,0.874,0.368,0.97,0.149,1,0.141,1,1
    zones:
      car_park:
        coordinates: 327,1038,394,1077,549,1665,311,1896,148,956,266,966
      driveway_entrance:
        coordinates: 874,1427,1082,1271,427,1209,434,1356
      front_door:
        coordinates: 
          710,1443,1206,1487,1441,1434,1446,1646,1569,1920,0,1920,540,1565
      no_patio:
        coordinates: 
          2560,0,2560,1084,2066,1195,1776,1228,1500,1278,1500,1920,0,1920,0,1249,0,161,0,154,0,0
      street:
        coordinates: 
          860,1227,1644,1259,2080,1201,2468,1115,2477,902,1287,861,283,797,305,1030,760,1064

    review:
      alerts:
        labels:
          - person
          - car
          - dog
        required_zones:
          - front_door
          - driveway_entrance
      detections:
        labels:
          - person
          - car
          - bark
          - dog

Relevant Frigate log output

Your configuration is invalid.
See the official documentation at docs.frigate.video.

Line Unknown:  - Value error, could not convert string to float: ''

Relevant go2rtc log output

Doesn't seem to be relevant, it's a validation error of the config editor.

Frigate stats

No response

Operating system

Other Linux

Install method

Docker Compose

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    # cap_add:
      # - PERFMON
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable
    network_mode: host
    shm_size: "284mb" # update for your cameras based on calculation above     
    group_add:
      - "109"
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/apex_0:/dev/apex_0 # passes a PCIe Coral, follow driver instructions here https://coral.ai/docs/m2/get-started/#2a-on-linux
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /mnt/lenovo12700/frigate/frigate-7500:/config
      - /mnt/lenovo12700/frigate/frigate-7500/frigate2.yml:/config/config.yml
      - /home/point/frigate-docker/media:/media/frigate:rw
      - /home/frigate:/db
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5000:5000"
      - "8971:8971" #for HA integration
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
    environment:
      TZ: "America/Denver"

Object Detector

Coral

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

So, I thought that there might be some validation error with zones, like if the zones were set up using coordinates of the larger stream size and were outside the dimensions of the smaller stream size. I commented out the

# car:
        #   mask:
        #     - 563,1394,490,1674,0,1920,0,967,207,964,733,1101,799,1161,784,1316

and it would let me change the detect width and height without validation errors.
Unfortunately, the dimensions of all of my zones are absolute and I'll have to re-create them. Interestingly, the motion masks are all relative and are correct after reducing the dimensions of detect.

Is there a reason that motion masks are relative locations and zones are absolute pixel locations?

Thanks.

[inkeep-ai-assistant[bot]]

Your config validation error is caused by zones and masks using absolute pixel coordinates that exceed the new detect resolution dimensions(1).

When you change the detect resolution from 3840×2160 to 896×672, any zones or masks with coordinates outside the new dimensions (like coordinates referencing 1920, 2560, etc.) will cause validation failures(1).

Solution:

Delete the absolute coordinate zones and masks, then recreate them using the mask/zone editor in the Frigate UI(2). The editor will automatically create relative coordinates (0.0 to 1.0 range) that scale properly regardless of resolution changes(2).

Why motion masks work but zones don't:

Motion masks in your config already use relative coordinates (values between 0 and 1), which automatically scale to any resolution(2)(3). Your zones use absolute pixel coordinates, which don't scale and become invalid when the resolution changes(1).

Steps to fix:

1. Remove or comment out all zones: sections with absolute coordinates
2. Save the config (should now validate successfully)
3. Restart Frigate
4. Use Settings → Mask/zone editor to recreate your zones(2)
5. The editor will generate relative coordinates automatically(2)

The relative coordinate format looks like 0.000,0.427,0.002,0.000... instead of 327,1038,394,1077...(2)(3).

📚 Sources:

1. Feature Request: Detect stream - auto determine frame width, height, & rate - no longer need to specify detect stream settings per camera & restart Frigate
2. Masks
3. Full Reference Config

---

Have another question? Just tag @inkeep.

[backcountrymountains]

wow. The ai took two seconds to solve this. yikes.
Is it possible to just chat with this ai to solve problems?

[NickM-27]

Use the ask AI button in the bottom right https://docs.frigate.video/

[backcountrymountains]

nice.