[Config Support]: No Alerts or Detections are appearing #13650
-
Describe the problem you are havingHi All, I have setup Frigate using an Orange Pi 5 using Armbian through a Docker container managed by Portainer. Everything appears to be working well with the inbuilt TPU being detected and used, and both cameras being available in the UI with recording being saved to my local NAS. Motion detection appears to be working but beyond this I am unable to enable/see any object detection working with Alerts and Detections being populated in the UI (Motion is populated). I have tried several configurations but for some reason i keep ending up with the same result, i am sure i have overlooked something basic as everything else works flawlessly, but i just cannot find the issue for some reason. Version0.14 Frigate config file#START OF GLOBAL SETTINGS
mqtt:
enabled: false
ffmpeg:
hwaccel_args: preset-rk-h265
detectors:
rknn:
type: rknn
num_core: 3
model:
path: deci-fp16-yolonas_s
width: 704
height: 480
input_pixel_format: bgr
input_tensor: nchw
labelmap_path: /labelmap/coco-80.txt
go2rtc:
streams:
DrivewayCamera:
- ffmpeg:rtsp://user:password@IP:554/cam/realmonitor?channel=1&subtype=0
DoorCamera:
- ffmpeg:rtsp://user:password@IP:554/cam/realmonitor?channel=1&subtype=0
detect:
width: 704
height: 480
fps: 10
enabled: true
stationary:
interval: 50
threshold: 50
max_frames:
default: 1500
objects:
track:
- person
- bicycle
- motorcycle
- car
- dog
review:
alerts:
labels:
- dog
detections:
labels:
- person
- bicycle
- motorcycle
- car
motion:
enabled: true
threshold: 25
contour_area: 15
record:
enabled: true
retain:
days: 3
mode: motion
preview:
quality: high
events:
retain:
default: 30
mode: active_objects
snapshots:
enabled: true
clean_copy: true
timestamp: true
retain:
default: 3
objects:
person: 30
bicycle: 30
motorcycle: 30
car: 30
#start of specific camera configuration
cameras:
driveway_camera:
enabled: true
ffmpeg:
inputs:
- path:
rtsp://user:password@IP:554/cam/realmonitor?channel=1&subtype=1 # <----- The stream you want to use for detection
roles:
- detect
- path:
rtsp://user:password@IP:554/cam/realmonitor?channel=1&subtype=0 # <----- The stream you want to use for recording
roles:
- record
motion:
mask:
0.003,0.548,0.261,0.484,0.14,0.388,0.443,0.333,0.501,0.426,0.73,0.388,0.999,0.565,0.999,0.002,0.004,0.001
doorbell_camera:
enabled: true
ffmpeg:
inputs:
- path:
rtsp://user:password@IP:554/cam/realmonitor?channel=1&subtype=1 # <----- The stream you want to use for detection
roles:
- detect
- path:
rtsp://user:password@IP:554/cam/realmonitor?channel=1&subtype=0 # <----- The stream you want to use for recording
roles:
- record
motion:
mask:
0.001,0.262,0.189,0.213,0.301,0.198,0.481,0.187,0.665,0.193,0.786,0.21,0.87,0.238,1,0.509,0.996,0.002,0.001,0
version: 0.14Relevant Frigate log outputinfo
2024-09-10 12:32:13
startup
Preparing Frigate...
info
2024-09-10 12:32:13
startup
Starting Frigate...
info
2024-09-10 12:32:15
frigate.app
Starting Frigate (0.14.1-f4f3cfa)
info
2024-09-10 12:32:15
frigate.util.config
Checking if frigate config needs migration...
info
2024-09-10 12:32:15
frigate.util.config
frigate config does not need migration...
info
2024-09-10 12:32:15
peewee_migrate.logs
Starting migrations
info
2024-09-10 12:32:15
peewee_migrate.logs
There is nothing to migrate
info
2024-09-10 12:32:15
frigate.app
Recording process started: 366
info
2024-09-10 12:32:15
frigate.app
Recording process started: 375
info
2024-09-10 12:32:15
frigate.app
go2rtc process pid: 95
info
2024-09-10 12:32:15
frigate.app
Output process started: 397
info
2024-09-10 12:32:15
detector.rknn
Starting detection process: 395
info
2024-09-10 12:32:15
frigate.app
Camera processor started for driveway_camera: 411
info
2024-09-10 12:32:15
frigate.app
Camera processor started for doorbell_camera: 412
info
2024-09-10 12:32:15
frigate.app
Capture process started for driveway_camera: 418
info
2024-09-10 12:32:15
frigate.app
Capture process started for doorbell_camera: 426Relevant go2rtc log outputinfo
2024-09-10 12:32:13
startup
Preparing new go2rtc config...
info
2024-09-10 12:32:13
startup
Starting go2rtc...
info
2024-09-10 12:32:13
startup
go2rtc platform=linux/arm64 revision=b2399f3 version=1.9.2
info
2024-09-10 12:32:13
startup
config path=/dev/shm/go2rtc.yaml
info
2024-09-10 12:32:13
rtsp
listen addr=:8554
info
2024-09-10 12:32:13
webrtc
listen addr=:8555/tcp
info
2024-09-10 12:32:13
api
listen addr=:1984
info
2024-09-10 12:32:23
startup
Starting go2rtc healthcheck service...Frigate statseverything normal with nothing being above 10% utilisedOperating systemOther Install methodDocker Compose Object DetectorRKNN Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 19 replies
-
|
You've specified incorrect dimensions for your model. The model's width and height are not the same as your camera frame's width and height. See the documentation: https://docs.frigate.video/configuration/object_detectors#configuration |
Beta Was this translation helpful? Give feedback.
-
|
I see in the documentation that the width and height are both set to 320, however, in my config this is set to 704x480 which is the resolution of the sub-stream coming off them. Are you suggesting that i try and change my sub-stream resolution to 320x320? |
Beta Was this translation helpful? Give feedback.
-
|
Frigate Go2rtc Nginx |
Beta Was this translation helpful? Give feedback.
-
|
Okay we need to see screenshots of the system and cameras metrics pages in the UI |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
After a while debugging again I have found the issue. It was because in my config i was using deci-fp16-yolonas_s as my model, however, initially I had configured this to use deci-fp16-yolonas_m instead. This was once of the first things i changed when detection was not working as i though i may have been overloading the internal NPU. What appears to have happened is that on initial configuration Frigate downloaded the deci-fp16-yolonas_m model and never rechecked/validated that the file contained in /model_cache/rknn was appropriate for the configuration used which was now deci-fp16-yolonas_s. Removing the model so it would need to redownload or changing the configuration to match the deci-fp16-yolonas_m model has now worked. I believe this can be an improvement point to action, where on startup Frigate can validate that the model downloaded matches the once specified in the configuration file |
Beta Was this translation helpful? Give feedback.
-
|
cc @MarcA711 |
Beta Was this translation helpful? Give feedback.
-
|
Hey,
This is not the bahavior on my system. All models can coexist in However, the user might stop frigate during the download of the model. In this case the file is corrupted. During the next start frigate tries to use this damaged model and crashed. This could be checked by comparing the checksum to make sure that files are healthy. Maybe something else was wrong with the file (for example a bit flip). I am not really sure what caused this issue. Maybe we could also implement a "clear cache" button in frigate that deletes all cached files. |
Beta Was this translation helpful? Give feedback.
After a while debugging again I have found the issue. It was because in my config i was using deci-fp16-yolonas_s as my model, however, initially I had configured this to use deci-fp16-yolonas_m instead. This was once of the first things i changed when detection was not working as i though i may have been overloading the internal NPU.
What appears to have happened is that on initial configuration Frigate downloaded the deci-fp16-yolonas_m model and never rechecked/validated that the file contained in /model_cache/rknn was appropriate for the configuration used which was now deci-fp16-yolonas_s. Removing the model so it would need to redownload or changing the configuration to match the de…