[Config Support]: Config validation suddenly failing with TypeError: '<' not supported between instances of 'str' and 'float' #14173

victorhooi · 2024-10-06T10:50:29Z

victorhooi
Oct 6, 2024

Describe the problem you are having

I've upgraded my development Frigate instance from b4acf4f to 039ab1c.

(I do know this is a Dev build - but I'm trying to figure out if this is a bug/regression, or just something I need to change in the configuration that might need to be documented).

For some reason, the same configuration YAML file is now causing an error in 039ab1c:

2024-10-06 21:19:39.998338514  [2024-10-06 21:19:39] frigate.app                    INFO    : Starting Frigate (0.14.1-039ab1c)
2024-10-06 21:19:39.998347674  [2024-10-06 21:19:39] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-10-06 21:19:40.027131721  [2024-10-06 21:19:40] frigate.util.config            INFO    : copying config as backup...
2024-10-06 21:19:40.027495164  *************************************************************
2024-10-06 21:19:40.027506404  *************************************************************
2024-10-06 21:19:40.027507284  ***    Your config file is not valid!                     ***
2024-10-06 21:19:40.027508124  ***    Please check the docs at                           ***
2024-10-06 21:19:40.027508884  ***    https://docs.frigate.video/configuration/index     ***
2024-10-06 21:19:40.027512764  *************************************************************
2024-10-06 21:19:40.027534885  *************************************************************
2024-10-06 21:19:40.027545045  ***    Config Validation Errors                           ***
2024-10-06 21:19:40.027545885  *************************************************************
2024-10-06 21:19:40.027546645  '<' not supported between instances of 'str' and 'float'
2024-10-06 21:19:40.028138490  Traceback (most recent call last):
2024-10-06 21:19:40.028139570    File "/opt/frigate/frigate/app.py", line 645, in start
2024-10-06 21:19:40.028140130      self.init_config()
2024-10-06 21:19:40.028140930    File "/opt/frigate/frigate/app.py", line 137, in init_config
2024-10-06 21:19:40.028141610      migrate_frigate_config(config_file)
2024-10-06 21:19:40.028142450    File "/opt/frigate/frigate/util/config.py", line 41, in migrate_frigate_config
2024-10-06 21:19:40.028143090      if previous_version < 0.14:
2024-10-06 21:19:40.028143930  TypeError: '<' not supported between instances of 'str' and 'float'
2024-10-06 21:19:40.028145050
2024-10-06 21:19:40.028153850  *************************************************************
2024-10-06 21:19:40.028154690  ***    End Config Validation Errors                       ***
2024-10-06 21:19:40.028155450  *************************************************************
2024-10-06 21:19:41.370393505  [INFO] Service Frigate exited with code 1 (by signal 0)

I know this is a development build - but I'm keen to see why the config is suddenly failing.

Also - in the error message, it doesn't seem to give a line number for the configuration error - do you know if I missed it somehow? (The line 41 seems to be a reference to /opt/frigate/frigate/util/config.py) Or is it normal that configuration validation errors won't have a line number?

The error itself seems to be some kind of str and float casting?

Version

0.14.1-039ab1c

Frigate config file

mqtt:
  enabled: false

cameras:
  dummy_camera: # <--- this will be changed to your actual camera later
    enabled: false
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:554/rtsp
          roles:
            - detect

  bedroom:
    enabled: true
    ffmpeg:
      inputs:
        - path:
            rtsp://root:[email protected]:554/axis-media/media.amp?streamprofile=hdwitnessSecondary&event=on
          roles:
            - detect
        - path:
            rtsp://root:[email protected]:554/axis-media/media.amp?streamprofile=hdwitnessPrimary&event=on
          roles:
            - record
    # detect:
    #   width: 640 # <- optional, by default Frigate tries to automatically detect resolution
    #   height: 360 # <- optional, by default Frigate tries to automatically detect resolution

    zones: {}
    review: {}

  kids_bedroom:
    enabled: true
    ffmpeg:
      inputs:
        - path:
            rtsp://root:[email protected]:554/axis-media/media.amp?streamprofile=hdwitnessSecondary&event=on
          roles:
            - detect
        - path:
            rtsp://root:[email protected]:554/axis-media/media.amp?streamprofile=hdwitnessPrimary&event=on
          roles:
            - record
    # detect:
    #   width: 640 # <- optional, by default Frigate tries to automatically detect resolution
    #   height: 360 # <- optional, by default Frigate tries to automatically detect resolution

    zones: {}
    review: {}

  living_room:
    enabled: true
    ffmpeg:
      inputs:
        - path:
            rtsp://root:FOOBAR:554/axis-media/media.amp?streamprofile=hdwitnessSecondary&event=on
          roles:
            - detect
        - path:
            rtsp://root:[email protected]:554/axis-media/media.amp?streamprofile=hdwitnessPrimary&event=on
          roles:
            - record
    # detect:
    #   width: 640 # <- optional, by default Frigate tries to automatically detect resolution
    #   height: 360 # <- optional, by default Frigate tries to automatically detect resolution

    zones: {}
    review: {}

  stairway:
    enabled: true
    ffmpeg:
      inputs:
        - path:
            rtsp://root:[email protected]:554/axis-media/media.amp?streamprofile=hdwitnessSecondary&event=on
          roles:
            - detect
        - path:
            rtsp://root:[email protected]:554/axis-media/media.amp?streamprofile=hdwitnessPrimary&event=on
          roles:
            - record
    # detect:
    #   width: 640 # <- optional, by default Frigate tries to automatically detect resolution
    #   height: 360 # <- optional, by default Frigate tries to automatically detect resolution

    zones: {}
    review: {}

version: 0.15-0

model:
  path: plus://FOOBAR

objects:
  filters:
    dog:
      min_score: .7
      threshold: .9
    cat:
      min_score: .65
      threshold: .8
    face:
      min_score: .7
    package:
      min_score: .65
      threshold: .9
    license_plate:
      min_score: .6
    amazon:
      min_score: .75
    ups:
      min_score: .75
    fedex:
      min_score: .75
    person:
      min_score: .65
      threshold: .85
    car:
      min_score: .65
      threshold: .85
  track:
    - person
    - car
    - dog
    - cat

detectors:
  coral:
    type: edgetpu
    device: usb

record:
  enabled: true
  retain:
    days: 7
    mode: motion
  alerts:
    retain:
      days: 30
  detections:
    retain:
      days: 30
snapshots:
  enabled: true
  retain:
    default: 30

ffmpeg:
  output_args:
    record: preset-record-generic-audio-aac

Relevant Frigate log output

2024-10-06 21:19:39.619124175  127.0.0.1 - - [06/Oct/2024:21:19:39 +1100] "" 400 0 "-" "-" "-"
2024-10-06 21:19:39.998338514  [2024-10-06 21:19:39] frigate.app                    INFO    : Starting Frigate (0.14.1-039ab1c)
2024-10-06 21:19:39.998347674  [2024-10-06 21:19:39] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-10-06 21:19:40.027131721  [2024-10-06 21:19:40] frigate.util.config            INFO    : copying config as backup...
2024-10-06 21:19:40.027495164  *************************************************************
2024-10-06 21:19:40.027506404  *************************************************************
2024-10-06 21:19:40.027507284  ***    Your config file is not valid!                     ***
2024-10-06 21:19:40.027508124  ***    Please check the docs at                           ***
2024-10-06 21:19:40.027508884  ***    https://docs.frigate.video/configuration/index     ***
2024-10-06 21:19:40.027512764  *************************************************************
2024-10-06 21:19:40.027534885  *************************************************************
2024-10-06 21:19:40.027545045  ***    Config Validation Errors                           ***
2024-10-06 21:19:40.027545885  *************************************************************
2024-10-06 21:19:40.027546645  '<' not supported between instances of 'str' and 'float'
2024-10-06 21:19:40.028138490  Traceback (most recent call last):
2024-10-06 21:19:40.028139570    File "/opt/frigate/frigate/app.py", line 645, in start
2024-10-06 21:19:40.028140130      self.init_config()
2024-10-06 21:19:40.028140930    File "/opt/frigate/frigate/app.py", line 137, in init_config
2024-10-06 21:19:40.028141610      migrate_frigate_config(config_file)
2024-10-06 21:19:40.028142450    File "/opt/frigate/frigate/util/config.py", line 41, in migrate_frigate_config
2024-10-06 21:19:40.028143090      if previous_version < 0.14:
2024-10-06 21:19:40.028143930  TypeError: '<' not supported between instances of 'str' and 'float'
2024-10-06 21:19:40.028145050
2024-10-06 21:19:40.028153850  *************************************************************
2024-10-06 21:19:40.028154690  ***    End Config Validation Errors                       ***
2024-10-06 21:19:40.028155450  *************************************************************
2024-10-06 21:19:41.370393505  [INFO] Service Frigate exited with code 1 (by signal 0)

Relevant go2rtc log output

N/A

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

docker-compose file or Docker CLI command

version: "3.9"
services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    #    image: ghcr.io/blakeblackshear/frigate:stable
    #image: ghcr.io/blakeblackshear/frigate:b4acf4f-standard-arm64
    #image: ghcr.io/blakeblackshear/frigate:9c75123-standard-arm64 # crashes with some go2rtc index out of range issue
    image: ghcr.io/blakeblackshear/frigate:039ab1c-standard-arm64
    shm_size: "64mb" # update for your cameras based on calculation above
    devices:
      - /dev/bus/usb:/dev/bus/usb  # Passes the USB Coral, needs to be modified for other versions
      #- /dev/apex_0:/dev/apex_0    # Passes a PCIe Coral, follow driver instructions here https://coral.ai/docs/m2/get-started/#2a-on-linux
      #- /dev/video11:/dev/video11  # For Raspberry Pi 4B
      #- /dev/dri/renderD128:/dev/dri/renderD128 # For intel hwaccel, needs to be updated for your hardware
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /home/victorhooi/frigate-docker/config:/config
      - /home/victorhooi/frigate-docker/storage:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5000:5000"
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
    environment:
      FRIGATE_RTSP_PASSWORD: "password"
      PLUS_API_KEY: ${PLUS_API_KEY}

Object Detector

Coral

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

NickM-27 · 2024-10-06T10:59:50Z

NickM-27
Oct 6, 2024
Collaborator Sponsor

You're trying to use a build off of the master branch after you've updated to dev

2 replies

victorhooi Oct 6, 2024
Author

Ah gotcha - sorry, I didn't realise they were from different branches.

Firstly, just to confirm - master is the latest commits for the current release, and dev are the latest commits for the next Frigate release - is that correct?

Secondly, If I'm browsing the container images on:

https://github.com/blakeblackshear/frigate/pkgs/container/frigate

Is there some way to see which builds are from which branch easily?

Or alternatively, is there some way to see what the latest image for each branch is?

(I know there's no "dev" label, which would point to the latest dev image - but just curious why that is?)

NickM-27 Oct 6, 2024
Collaborator Sponsor

Correct. You can tell what builds belong to which branch based on the latest commit for that branch and the tag in the image.

banthungprong · 2024-10-07T12:59:33Z

banthungprong
Oct 7, 2024

Simply deleting the version line solved this for me when switching from dev to master again.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Config Support]: Config validation suddenly failing with TypeError: '<' not supported between instances of 'str' and 'float' #14173

{{title}}

Replies: 2 comments 2 replies

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Config Support]: Config validation suddenly failing with TypeError: '<' not supported between instances of 'str' and 'float' #14173

victorhooi Oct 6, 2024

Describe the problem you are having

Version

Frigate config file

Relevant Frigate log output

Relevant go2rtc log output

Frigate stats

Operating system

Install method

docker-compose file or Docker CLI command

Object Detector

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 2 comments · 2 replies

NickM-27 Oct 6, 2024 Collaborator Sponsor

victorhooi Oct 6, 2024 Author

NickM-27 Oct 6, 2024 Collaborator Sponsor

banthungprong Oct 7, 2024

victorhooi
Oct 6, 2024

Replies: 2 comments 2 replies

NickM-27
Oct 6, 2024
Collaborator Sponsor

victorhooi Oct 6, 2024
Author

NickM-27 Oct 6, 2024
Collaborator Sponsor

banthungprong
Oct 7, 2024