[Camera Support]: Homemade PiCamera has stopped working after migrating Frigate from HASS to Docker Container on NAS #13533
Replies: 2 comments
-
enable trace logs for go2rtc to get more information
|
Beta Was this translation helpful? Give feedback.
-
Ok I was able to get it up and running here. Steps I took to resolve: I also realized I didn't need the curly brackets in The main camera url is set up with some html and after trying bunch of combos pointing the direct feed in the go2rtc worked. I think these 3 problems were causing issues. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
Hi! I just set up a fresh Frigate install on my Synology NAS, previously running it on my Home Assistant server. I was having a lot of stability issues and thought this my be the better path. I currently have 2 cameras, a Reolink E1 which seems to be working just fine, and a Raspberry Pi I've set up to be a front door camera. Prior to migrating both cameras "worked" although the front door camera had been a little finicky. Now I've been unable to get the front door camera working at all.
I tried the original config as well as the recommended go2rtc route which I've most likely not set up properly since I haven't been able to figure it out. Both configs are attached.
Connecting directly to the camera feed via web browser and VLC works as well, so I know it's up and running. I'm just having trouble figuring out who to get Frigate to play nice with it.
Version
0.14.1-f4f3cfa
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
No response
Operating system
Other
Install method
Docker Compose
Object Detector
Coral
Network connection
Wired
Camera make and model
Homemade Pi Camera Utilizing PiCamera2
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
I'm on the dumb side.
Beta Was this translation helpful? Give feedback.
All reactions