question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Config Support]: the same file works on Frigate add-on and not on Frigate LXC

See original GitHub issue

Hi everyone, I have a particular problem. I have used Frigate as a Home assistant add-on until now. I use a mini-pc with proxmox, and therefore I wanted to use Frigate on lxc. I managed to do everything without problems, but I can’t use the config.yml file that I have used up to now, because in the Portainer log it still gives me an error. I would like to point out that I am using EXACTLY the same file that still works in the add-on version currently. With this configuration I get this error

  • Starting nginx nginx …done. Error parsing config: expected a dictionary for dictionary value @ data[‘cameras’][‘Ingresso’][‘detect’]

Version

latest

Frigate config file

mqtt:
  host: 192.168.1.56
  user: xxxx
  password: xxxx
  topic_prefix: frigate
  client_id: frigate
cameras:
  Ingresso: 
    ffmpeg:
      inputs:
        - path: rtsp://xxx:xxx@192.168.1.65:554/live2.sdp
          roles:
            - detect
    rtmp:
      enabled: false 
    detect:
      width:480
      height:272
      fps:7
    objects:
      track:
        - person
        - dog
        - cat
        - car
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
  Sala: 
    ffmpeg:
      inputs:
        - path: rtsp://xxx:xxx@192.168.1.64/Streaming/Channels/2
          roles:
            - detect
    rtmp:
      enabled: false 
    detect:
      width:352
      height:240
      fps:15
    objects:
      track:
        - person
        - dog
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
birdseye:
  enabled: True
  mode: continuous

Relevant log output

* Starting nginx nginx
   ...done.
Error parsing config: expected a dictionary for dictionary value @ data['cameras']['Ingresso']['detect']

Frigate stats

No response

Operating system

Proxmox

Install method

Docker Compose

Coral version

CPU (no coral)

Any other information that may be helpful

No response

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:10

github_iconTop GitHub Comments

1reaction
NickM-27commented, Oct 17, 2022

Glad it worked, going to close this, feel free to create a new issue if something else comes up

1reaction
NickM-27commented, Oct 17, 2022

Are you sure you’re on the right version of frigate? What version is installed?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Frigate or Frigate Full access ? Not sure what to ... - GitHub
config file that contains the passthrough info (I assume leave it alone to make it available to the Frigate docker container); LXC docker ......
Read more >
Network share on Frigate HASSOS with nabucasa(SSL) and ...
I have sucessfuly install Frigate on Proxmox LXC with network share. I would like to share it with you, feel free to give...
Read more >
Configuration File - Frigate Docs
For Home Assistant Addon installations, the config file needs to be in the root of your Home Assistant config directory (same location as...
Read more >
Proxmox + Frigate in Docker LXC + 2xCoral - USB ... - Reddit
Hi. I have Frigate on Docker. I have 2x Coral TPU USB plugged into the server. After starting Frigate, the logs say that...
Read more >
Home Assistant | Pros/cons running Frigate in HA as an add ...
I am running proxmox. HA is running on VM. Frigate is running on CT, docker container.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found