Does the “retain” only deletes from the db or does it also delete the actual files from the folders?
actual files
1 Like
Hi!
I’m struggling with Reolink 510W camera. RTSP stream is not good but cannot get rtmp-stream working. Anybody have same model (or 410 or similar) and get rtmp working with Frigate. I’d like to get verified rtmp-address config and also rtmp config.yml settings to get this working… Thx a lot!
i run frigate in docker
I also use portainer to manage containers. In portainer you are able to connect to console of container and run commands. you can use this to check for device. Docker commands allow running console as well
I have a mix of RLC-520, RLC-410 and RLC-510A …
All working smooth with RTMP streams.
What CPU do you have and what it is your ffmpeg settings?
I’m running a sperate ubuntu server with i5-2500 and 8gig ram.
These are my ffmpeg settings:
ffmpeg:
hwaccel_args:
- -hwaccel
- vaapi
- -hwaccel_device
- /dev/dri/renderD128
- -hwaccel_output_format
- yuv420p
And this for RTMP streams:
input_args:
- '-avoid_negative_ts'
- make_zero
- '-fflags'
- nobuffer
- '-flags'
- low_delay
- '-strict'
- experimental
- '-fflags'
- +genpts+discardcorrupt
## - -rw_timeout
## - '5000000'
- '-use_wallclock_as_timestamps'
- '1'
And my camera rtmp settings in config.yml is this:
frigate_parkering:
ffmpeg:
inputs:
- path: rtmp://192.168.1.216/bcs/channel0_main.bcs?channel=0&stream=1&user=admin&password=*holyshit*
roles:
- record
- detect
- path: rtmp://192.168.1.216/bcs/channel0_sub.bcs?channel=0&stream=1&user=admin&password=*holyshit*
roles:
# - detect
- rtmp
Thx for these… have to check… At the moment I have zero settings at ffmeg or input_args because all my other cameras are working with rtsp (one Hikvision and 3 Dahuas) without any problem. Only problem here is my Reolink rtsp stream. But I have problem to get connection with rtmp…
Also I’m testing 0.9.0 RC2 version… I wonder why (at birdseye) I see only one camera even if I choosed continuous mode?
Hi @cooloo, are you using Proxmox LXC with Coral (m.2 pci version)? Can you share your config? Would it require to follow installation of coral module on proxmox host?
Will have to look into this thanks!
I changed the detect stream to the higher resolution. Now the snapshots are in the same resolution. So the snapshots are generated from the detect stream. Unlike the clips,for which the stream can be freely selected.
@blakeblackshear Propably a new feature: set stream for snapshots
@blakeblackshear could you give me some advice on how to setup custom model on HassOS Frigate addon?
Hi guys, I hope it is ok to post a question here as I have not found a frigate sub group or FB page.
Hi guys, I would love some help from one of you Frigate experts.
I have decided to ditch Blue Iris and use only Frigate.
My current set up is:
NUC i7 Intel NUC Kit NUC7i7BNKQ Small Form Factor PC Core i7 (7567U) 4.0GHz 16GB 512GB
Proxmox with HA OS and Open Media Vault
I currently have frigate installed on the HA supervisor and it is working but I do not have pass through of my USB Coral accelerator and I can not save the video to an external drive.
The reason I used Proxmox was to be able to also have a Win 10 machine with Blue Iris, but now all I have is Open media vault and HA. I’m not that bothered about OMV either if I can just use the hard drive currently used by it directly from frigate and have it available to view on my network.
So what should I do?
Keep Proxmox and add another VM for Frigate, which I believe can be installed on a VM running Ubuntu and docker? Will I be able to pass through the HDD and the Coral accelerator?
Ditch Proxmox and install HA and Frigate in some other way?
I could get rid of OMV if I could somehow use frigate to save all streams to a USB drive connected to the NUC and make that available for viewing on the network. Is that asking too much?
How to avoid saving static objects?
If a person or another object is moving, it should be saved in Events List, but when the same object (in my case - a still car) is not moving, it always gets saved by Frigate in “Cars” labels section.
Mask that area
OR
Since frigate looking at whole image for motion then check for object, you generally won’t have capture for even parked vehicle unless something moving or trigger by timestamp from camera video. Sometimes reducing or masking the common movement item like tree branch may solve your issue
Increasing confidence, for only car on the one camera in this case, may also be key
Any luck getting this recognized by your Blue?
I’ve got an issue that I’ve been troubleshooting for a couple weeks now.
I’m running Frigate in a docker container – not the HA add on. I have the M.2 coral installed in my mini pc server. All of my cameras work fine except for one.
The one that isn’t working is my Nest Outdoor Cam. I’ve read everything I can find on how to make these work and here’s where I’m at… I’ve got it configured and I can get the clips to record fine. Totally flawless. The issue is with the detect stream. I only get about two seconds worth of frames on the detect feed. Then, it’ll skip like 4-5 seconds. It repeats that condition continuously. This is obviously an issue for motion detection.
For the life of me I can’t figure out why it’s doing this. As I said… it’s recording fine. I’m not seeing massive CPU spikes and I’ve tried masking out anything that’s moving at all. No improvement. Here’s my configuration. I’ve tried every combination of input_args… no improvement.
frontdoor:
rtmp:
enabled: true
objects:
track:
- person
- car
- truck
ffmpeg:
hwaccel_args:
- -hwaccel
- vaapi
- -hwaccel_device
- /dev/dri/renderD128
input_args:
- -avoid_negative_ts
- make_zero
# - -fflags
# - nobuffer
# - -flags
# - low_delay
# - -strict
# - experimental
- -fflags
- +genpts+discardcorrupt
# # - -r
# # - "3" # <---- adjust depending on your desired frame rate from the mjpeg image
# - -use_wallclock_as_timestamps
# - "1"
output_args:
detect: -f rawvideo -pix_fmt yuv420p
record: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v libx264 -an
clips: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v libx264 -an
rtmp: -c:v libx264 -an -f flv
inputs:
- path: https://stream-us1-alfa.dropcam.com:443/nexus_aac/UNIQUE_ID/chunklist_w1453522418.m3u8?public=Sas7t9F9DM&maxfps=5
roles:
- detect
- rtmp
- path: https://stream-us1-alfa.dropcam.com:443/nexus_aac/UNIQUE_ID/chunklist_w1453522418.m3u8?public=Sas7t9F9DM
roles:
- record
- clips
width: 1280
height: 720
fps: 5
motion:
mask:
- 997,219,985,0,824,0,618,42,477,74,360,109,219,157,162,181,138,204,233,315,302,361,991,484
record:
enabled: true
retain_days: 4
Nope, tried everything but it will not work with my blue 
I believe we need a mini-PCI → PCI adapter - which would of course require a PC.
USB power may be issue for running on blue.
I had similar issue on my server when using USB2.0 ports. power too little
I was able to use on some port but other result in “look like working (lights) but no work”
I think similar issue was happening when using RasPi and coral with Doods users. I think recommendation was external power somehow.
I’m using Frigate for a week already and constantly experiencing 1-2 cameras randomly “freezing” during Frigate operation (some after 1-2 hours, some after 5). There is no exact regularity for this, but it’s pathetic that this NVR is so unstable. Only Frigate Docker restart helps until the next freeze occurs.
frigate.mqtt INFO : MQTT connected
detector.coral INFO : Starting detection process: 42
frigate.app INFO : Camera processor started for front: 45
frigate.edgetpu INFO : Attempting to load TPU as usb
frigate.app INFO : Camera processor started for back: 56
frigate.edgetpu INFO : TPU found
frigate.app INFO : Camera processor started for sosed: 57
frigate.app INFO : Camera processor started for trucks: 65
frigate.app INFO : Capture process started for front: 66
frigate.app INFO : Capture process started for back: 69
frigate.app INFO : Capture process started for sosed: 70
frigate.app INFO : Capture process started for trucks: 74
frigate.mqtt INFO : Turning on snapshots for front via mqtt
frigate.mqtt INFO : Turning on snapshots for back via mqtt
frigate.mqtt INFO : Turning on snapshots for trucks via mqtt
frigate.mqtt INFO : Turning on snapshots for sosed via mqtt
Fatal Python error: Bus error
Thread 0x00007f9ee4a91700 (most recent call first):
File "/usr/lib/python3.8/threading.py", line 302 in wait
File "/usr/lib/python3.8/multiprocessing/queues.py", line 227 in _feed
File "/usr/lib/python3.8/threading.py", line 870 in run
File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap
Current thread 0x00007f9ee7292700 (most recent call first):
File "/opt/frigate/frigate/video.py", line 117 in capture_frames
File "/opt/frigate/frigate/video.py", line 231 in run
File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap
Thread 0x00007f9ee9a93700 (most recent call first):
File "/opt/frigate/frigate/video.py", line 205 in run
File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap
Thread 0x00007f9eec294700 (most recent call first):
File "/opt/frigate/frigate/log.py", line 71 in run
File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap
Thread 0x00007f9efdc8a740 (most recent call first):
File "/usr/lib/python3.8/threading.py", line 1027 in _wait_for_tstate_lock
File "/usr/lib/python3.8/threading.py", line 1011 in join
File "/opt/frigate/frigate/video.py", line 245 in capture_camera
File "/usr/lib/python3.8/multiprocessing/process.py", line 108 in run
File "/usr/lib/python3.8/multiprocessing/process.py", line 315 in _bootstrap
File "/usr/lib/python3.8/multiprocessing/popen_fork.py", line 75 in _launch
File "/usr/lib/python3.8/multiprocessing/popen_fork.py", line 19 in __init__
File "/usr/lib/python3.8/multiprocessing/context.py", line 277 in _Popen
File "/usr/lib/python3.8/multiprocessing/context.py", line 224 in _Popen
File "/usr/lib/python3.8/multiprocessing/process.py", line 121 in start
File "/opt/frigate/frigate/app.py", line 182 in start_camera_capture_processes
File "/opt/frigate/frigate/app.py", line 228 in start
File "/opt/frigate/frigate/__main__.py", line 15 in <module>
File "/usr/lib/python3.8/runpy.py", line 87 in _run_code
File "/usr/lib/python3.8/runpy.py", line 194 in _run_module_as_main
Fatal Python error: Bus error
Thread 0x00007f9ee4a91700 (most recent call first):
File "/usr/lib/python3.8/threading.py", line 302 in wait
File "/usr/lib/python3.8/multiprocessing/queues.py", line 227 in _feed
File "/usr/lib/python3.8/threading.py", line 870 in run
File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap
Current thread 0x00007f9ee7292700 (most recent call first):
File "/opt/frigate/frigate/video.py", line 117 in capture_frames
File "/opt/frigate/frigate/video.py", line 231 in run
File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap
Thread 0x00007f9ee9a93700 (most recent call first):
File "/opt/frigate/frigate/video.py", line 205 in run
File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap
Thread 0x00007f9eec294700 (most recent call first):
File "/opt/frigate/frigate/log.py", line 71 in run
File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap
Thread 0x00007f9efdc8a740 (most recent call first):
File "/usr/lib/python3.8/threading.py", line 1027 in _wait_for_tstate_lock
File "/usr/lib/python3.8/threading.py", line 1011 in join
File "/opt/frigate/frigate/video.py", line 245 in capture_camera
File "/usr/lib/python3.8/multiprocessing/process.py", line 108 in run
File "/usr/lib/python3.8/multiprocessing/process.py", line 315 in _bootstrap
File "/usr/lib/python3.8/multiprocessing/popen_fork.py", line 75 in _launch
File "/usr/lib/python3.8/multiprocessing/popen_fork.py", line 19 in __init__
File "/usr/lib/python3.8/multiprocessing/context.py", line 277 in _Popen
File "/usr/lib/python3.8/multiprocessing/context.py", line 224 in _Popen
File "/usr/lib/python3.8/multiprocessing/process.py", line 121 in start
File "/opt/frigate/frigate/app.py", line 182 in start_camera_capture_processes
File "/opt/frigate/frigate/app.py", line 228 in start
File "/opt/frigate/frigate/__main__.py", line 15 in <module>
File "/usr/lib/python3.8/runpy.py", line 87 in _run_code
File "/usr/lib/python3.8/runpy.py", line 194 in _run_module_as_main
Move along now…’Super-something’… Maximus, no.
With posts like that, I doubt (hope) no one will help you. I’m sure not going to bother.