blakeblackshear
commented
2 years ago It looks like instability in the stream is causing the RTMP relay to fail. It is very sensitive to bad data. I would try disabling RTMP with:
rtmp:
enabled: FalseThe detect role cannot be removed and Frigate is adding it back in automatically. This is the role that decodes the video stream, does motion detection, and provides images for the frontend. Disabling detect just prevents the object detection from being run on motion.
If you are still seeing failures that cause the recording segments to go missing, you can try running a separate process for record and detect like this:
cameras:
yi_outdoor:
ffmpeg:
inputs:
- path: rtsp://192.168.1.XXX/ch0_0.h264
hwaccel_args: -c:v h264_v4l2m2m
roles:
- detect
- path: rtsp://192.168.1.XXX/ch0_0.h264
roles:
- record
detect:
enabled: False
# width: 1920
# height: 1080Lastly, your issues with the Coral sound like the normal power related issues. The Coral uses a lot of power for a USB device, so it is recommended to use a USB hub with an external power supply with a Pi.
tonitonae
NickM-27
stale[bot]
outofsight
cdk222
husnainali09
r00HuNTeR
max-mayorov
harambe88
ale-saglia
Mister-A
Describe the problem you are having
Hi.
I am struggling to have frigate set up for 24/7 recording from two cameras on a RPi 4. I have been stucked as everybody else with the hwaccel bug for some time. With the latest release, now that is working (no more green screens, I can see the images from both cameras). Thanks!
My problem now is that I have a lot of errors on my logs and many frames dropped. Clips are not stored regularly every 1 minute. Instead, I have some clips of 10 seconds, other longer, sometimes no clip for 2-3 minutes. If I go to the recordings page in the UI, the largest aggregated length of a recording is of 8-9 minutes for an hour, which means that a lot of information is missing.
This is due, as the logs say, to the fact that ffmpeg crashes a lot (see below the errors). I do not know if this is due to my cameras or network setup. Which is weird is that this setup (network and cameras) has been working flawlessly most of the time with Synology Surveillance Station. I can also watch the streams with VLC and they seem quite fluent. I did not watch them for a long time, but I do not see those drops in a 3-5 minutes interval in which ffmpeg in the frigate container crashes several times.
As per the logs there is one thing that I do not understand. Whenever an error happens, the logs refer to a detect process which I, supposedly, have disabled in my config of frigate. I do not know if the name of the process does not actually mean that detection is being conducted or if the detection process is used for something else. I also see a warning at the beginning of the log about cpu detection not being recommended though I think that I am explicitly disabling it.
Sorry for the long message. I just wanted to provide enough context.
Thanks in advance for your help.
PS: both cameras are running unofficial yi-hack firmware, just in case someone has experience with those FWs.
PS2: maybe I should tweak some config of fmmpeg to make everything work properly, but I do not have any experience with that, so I do not know what to touch.
Version
0.11.0-3de1948
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Other Linux
Install method
Docker Compose
Coral version
CPU (no coral)
Network connection
Wireless
Camera make and model
Yi Outdoor and Yo Dome 1080p
Any other information that may be helpful
I do have a coral device (USB) but I can not connect it to my RPi as it hangs for some reason :/
I use this box:
https://www.amazon.es/gp/product/B095WD7BTW
Which has a sort of USB bridge to connect the 2.5 HDD to one of the USB 3 ports. If I connect the Coral to the other USB 3 port, then it complains about power during boot. I have a USB hub:
https://www.amazon.es/gp/product/B00TPMEOYM
But, if I connect it to the second USB port, then the RPi does not boot. Or, If I connect it when the Rpi is running, then if hangs at some point. It seems like some kind of interference with the "USB bridge". I need more testing (maybe connecting the HDD to the hub directly with a USB A - USB A cable) but using coral is not an option right now.
Regarding the OS, I use DietPi 64bit.
Thanks for your help.