-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Support]: Unable to get Reolink camera to work using provided configuration #1974
Comments
Can you try with a simpler password? |
So I went to a much smaller password without symbols and this is what I got in the log:
|
FFMpeg is complaining that it can't access your device for hardware acceleration. See if it works with those removed. |
That did it. I guess it was the complicated password with several symbols throwing off things at first (I almost suspected this) then the hardware acceleration arguments. I was able to add more cameras into the configuration and they work. Thanks |
Describe the problem you are having
I was using the previous version of Frigate and my Reolink 410 cameras were kind of working. After several hours I was starting to get problems. That's not why I am here though I was just pointing out that I never really got them to work properly. That said I basically started from scratch with the latest version (0.9.1-800f33e).
I followed the config file recommended here: #1713 (comment) and now I am getting all sorts of errors. I am only trying to get 1 camera working right now but I have up to 7 more I will be hooking up,
I am running on Unraid docker with a Google Coral edge USB TPU. My current recording path is on an unassigned drive that I will one day replace with a dedicated Surveillance grade drive.
Version
0.9.1-800f33e
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
UNRAID
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
Reolink 410
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: