[Camera Support]: Reolink Cameras are constantly dropping their connection to Frigate #14903
Replies: 7 comments 33 replies
-
These errors are happening right at 2 am which is the typical time that cameras are set to reboot by default |
Beta Was this translation helpful? Give feedback.
-
So I had been putting this on hold thinking that some of the updates going into frigate related to WebRTC might fix my issues. I just updated to the beta HA Core update. I also updated my frigate integration to 5.5.1. I just had one of my cameras drop. Here is the supported log:
|
Beta Was this translation helpful? Give feedback.
-
Try setting up rtps instead of ffmpeg in the go2rtc section. In my configuration with Reolink cameras it works well (I had a very unstable experience with ffmpeg and Reolink before): > rtsp://user:[email protected]:554/h264Preview_01_main |
Beta Was this translation helpful? Give feedback.
-
I'm on beta 15 and my logs are similar to yours. I'm using Reolink on ethernet and wifi. No issues over ethernet but the wifi cams drop out and usually come back if I restart frigate or sometimes if I just leave frigate they come back after a day or so. I'm putting this down to crappy wifi on my part and I will switch to ethernet eventually. I'm already using rtsp in go2rtc. I also dont use home assistant not until I'm happy with a stable setup. Running frigate in container on bare metal ubuntu. |
Beta Was this translation helpful? Give feedback.
-
I just had another property's VM just run OOM while running rtsp.... @NickM-27 is there a way for me to grab the logs after frigate has crashed? Do they get stored somewhere between runs? |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm facing the same issues with reolink NVR and 5 POE cameras. After a while, every single stream goes offline. Checking from logs they go offline at the same time, when the NVR reboots. No idea why they can't just recover the stream automatically after NVR rebooted. Frigate restart fixes the issue. I am using https stream through the NVR (cause I can't get it work to the cameras directly even if they are in my LAN) |
Beta Was this translation helpful? Give feedback.
-
So I was never able to get this to be completely fixed, but I have some workarounds in place that are helping things. Switching to use RTSP keeps the cameras from dropping. However, I then run into OOM issues at least once a day with at least one of my 3 properties. To circumvent this, I run a cronjob ever 10 minutes that checks the current memory usage of the container and if its above 98%, I force a reboot of the container. This is keeping things running smoothly. I was never able to get the logs for the OOM issue because, the container stops responding when it gets to that point. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
Hello, I have posted several issues related to this in the past. I currently have 3 servers running Frigate on Proxmox. I use reolink cameras exclusively. At least once a day, at at least one of the properties, one of the cameras goes down. The only way I am able to bring the cameras back online is to restart the VM node. When the issue occurs, I will check the cameras and Reolink, and they are still streaming properly there. I really need these cameras to stay online, as two of the properties are AirBnBs. I am not sure if it is the cameras I am using or Frigate. In the files and logs I am attaching, it is Driveway Camera that is down.
Version
0.14.1-
What browser(s) are you using?
No response
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
Operating system
Proxmox
Install method
Proxmox via TTeck Script
Object Detector
Coral
Network connection
Wired
Camera make and model
Reolink Doorbell and Reolink CX410W
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions