Rob8
August 15, 2023, 2:28pm
1
I’m running frigate on an Intel NUC under proxmox in a separate LXC container.
I can not get detecting a person activated. Furthermore, I have tried many things. Hopefully, someone can help and point out what I am missing?
Thanks for your help!
I have the following config.yml file
mqtt:
host: mqtt://192.168.178.183
port: 1883
topic_prefix: frigate
user: admin
password: 'password'
stats_interval: 60
logger:
default: info
logs:
frigate.mqtt: debug
birdseye:
enabled: True
mode: continuous
detectors: # <---- add detectors
coral:
type: edgetpu
device: usb
go2rtc:
streams:
voordeur:
- rtsp://admin:[email protected] :554//cam/realmonitor?channel=1&subty>
#- "ffmpeg:voordeur#audio=opus"
voordeur_sub:
- rtsp://admin:[email protected] :554//cam/realmonitor?channel=1&subt>
#- "ffmpeg:voordeur_sub#audio=opus"
oprit:
- rtsp://admin:[email protected] :554//cam/realmonitor?channel=1&subty>
#- "ffmpeg:oprit#audio=opus"
oprit_sub:
- rtsp://admin:[email protected] :554//cam/realmonitor?channel=1&subt>
#- "ffmpeg:oprit_sub#audio=opus"
achterdeur:
- rtsp://admin:[email protected] :554//cam/realmonitor?channel=1&subty>
#- "ffmpeg:achterdeur#audio=opus"
achterdeur_sub:
- rtsp://admin:[email protected] :554//cam/realmonitor?channel=1&subt>
#- "ffmpeg:achterdeur_sub#audio=opus"
cameras:
voordeur:
ffmpeg:
hwaccel_args: preset-vaapi
output_args:
record: preset-record-generic-copy
inputs:
- path: rtsp://192.168.178.184:8554/voordeur
input_args: preset-rtsp-restream
roles:
- record
- detect
#- path: rtsp://192.168.178.184:8554/voordeur_sub
# input_args: preset-rtsp-restream
# roles:
# - detect
oprit:
ffmpeg:
hwaccel_args: preset-vaapi
output_args:
record: preset-record-generic-copy
inputs:
- path: rtsp://192.168.178.184:8554/oprit
input_args: preset-rtsp-restream
roles:
- record
- detect
#- path: rtsp://192.168.178.184:8554/oprit_sub
# input_args: preset-rtsp-restream
# roles:
# - detect
detect:
width: 1280
height: 720
objects:
track:
- person
- dog
- cat
- car
achterdeur:
ffmpeg:
hwaccel_args: preset-vaapi
output_args:
record: preset-record-generic-copy
inputs:
- path: rtsp://192.168.178.184:8554/achterdeur
input_args: preset-rtsp-restream
roles:
- record
- detect
#- path: rtsp://192.168.178.184:8554/achterdeur_sub
# input_args: preset-rtsp-restream
# roles:
# - detect
detect:
width: 1280
height: 720
objects:
track:
- person
- dog
- cat
- car
IgorZg
(Igor Simić)
August 15, 2023, 2:40pm
2
How do you configure lxc?
Can frigate see coral and intel gpu?
Rob8
August 15, 2023, 2:42pm
3
Yes, the Coral USB is working
Rob8
August 15, 2023, 2:56pm
5
Frigate werkte ook zonder Coral USB
IgorZg
(Igor Simić)
August 15, 2023, 2:59pm
6
I did recently setup frigate under ubuntu jammy unprotected proxmox lxc container and it wasn’t simple.
Here are my lxc configuration:
arch: amd64
cores: 4
features: fuse=1,mknod=1,mount=cifs,nesting=1
hostname: frigate
memory: 6144
mp0: sata:230/vm-230-disk-0.raw,mp=/opt/frigate/media,size=512G
mp1: local-lvm:vm-230-disk-5,mp=/opt/frigate/storage,backup=1,size=8G
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=EE:D3:F2:4D:28:69,ip=dhcp,type=veth
onboot: 1
ostype: ubuntu
rootfs: local-lvm:vm-230-disk-3,size=16G
startup: order=20,up=5
swap: 6144
tags: privileged;production
lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.cgroup2.devices.allow: c 29:0 rwm
lxc.cgroup2.devices.allow: c 189:* rwm
lxc.cgroup2.devices.allow: a
lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file 0, 0
lxc.mount.entry: /dev/dri dev/dri none bind,optional,create=dir
lxc.mount.entry: /dev/coralptr dev/bus/usb/002/003 none bind,optional,create=file 0, 0
lxc.mount.entry: /dev/coralptr dev/bus/usb/004/003 none bind,optional,create=file 0, 0
lxc.mount.auto: cgroup:rw
lxc.apparmor.profile: unconfined
lxc.cap.drop:
Rob8
August 15, 2023, 3:05pm
7
I am running it on Proxmox 8.0.4
Under datacenter also did resource mappings of the coral-usb
arch: amd64
cores: 4
features: nesting=1
hostname: frigate
memory: 102400
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=22:81:13:9A:8E:D6,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-103-disk-0,size=64G
swap: 512
lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.cgroup2.devices.allow: c 29:0 rwm
lxc.cgroup2.devices.allow: c 189:* rwm
lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=fil>
lxc.mount.entry: /dev/bus/usb/002/ dev/bus/usb/002/ none bind,optional,create=dir 0, 0
lxc.mount.entry: /dev/fb0 dev/fb0 none bind,optional,create=file
lxc.cap.drop:
crzynik
(Nicolas Mowen)
August 15, 2023, 3:08pm
8
this is incorrect, host should not include mqtt://
Rob8
August 15, 2023, 3:10pm
9
Thanks, I changed this. But is not solving the problem of not generation of any motion events.
eftimg
(eftim)
August 15, 2023, 3:16pm
10
Not sure if this is required but try adding …
client_id: frigate
To your mqtt section, right under topic_prefix
Rob8
August 15, 2023, 3:22pm
11
To make it easier, I set enabled: False to cut out mqtt for a later stage.
Do you see anything wrong with the event detection? person, dog, cat, car
IgorZg
(Igor Simić)
August 15, 2023, 3:23pm
12
There is my mqtt section of config if this can help:
mqtt:
host: 10.1.1.20
user: username
password: password
topic_prefix: frigate
client_id: frigate
Rob8
August 15, 2023, 3:24pm
13
Thanks for sharing! do you have ’ ’ around your password phrase?
IgorZg
(Igor Simić)
August 15, 2023, 3:25pm
14
No, I don’t.
If you suspect on mqtt I sugest to observe with MQTT Explorer.
Rob8
August 15, 2023, 3:31pm
15
I disabled MQTT for now. Because events are not detected.
crzynik
(Nicolas Mowen)
August 15, 2023, 5:49pm
16
this is because you do not have recording or snapshots enabled, like the docs say one of these has to be enabled for events
1 Like
flyize
August 15, 2023, 6:15pm
17
Isn’t MQTT a requirement?
edit: I’m wrong. It of course isn’t.
Rob8
August 15, 2023, 6:52pm
18
Hi Nicolas,
Where do I add the recording or snapshot enabled? Hopefully, you can help out or point in the direction?
Thanks!
Rob8
August 15, 2023, 7:41pm
20
Thanks Guys!
I followed Nicolas tips on recording and snapshots.
Searched the docs of Frigate
For Home Assistant Addon installations, the config file needs to be in the root of your Home Assistant config directory (same location as configuration.yaml). It can be named frigate.yml or frigate.yaml, but if both files exist frigate.yaml will be...
Next up is to connect my Proxmox LXC Frigate container first to another LXC container with my MQTT server and another VM with Homeassistant.
Any tips are welcome!
But, thanks for your great support!
1 Like