Closed cryd-s closed 11 months ago
Not directly related but I notice you're running detect at full resolution and 20 fps. This is highly discouraged as in most cases it's not needed and leads to increased resource usage. The default fps is 5 and in most cases 10 is sufficient for scenes with fast moving objects
For this error, you'll need to enable debug logs for go2rtc and run again to paste those here
go2rtc:
log:
exec: trace
Here is my log:
it doesn't look like you've had any crashes yet
after a restart it looks like that
Connection to tcp://192.168.178.98:80 failed: Connection timed out
connection to camera is timing out
hm so its a connection problem :(
Yes, that seems to be the case, camera or network issue most likely
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the problem you are having
Hi i have set up my frigate in a homeassistant vm on a proxmox. The storage is a networkdrive from a proxmox smb server which i include in homeassitant.
Hardware: ryzen 7 4750G PRo 64gb RAM
Version
0.12.1-367D724
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
No response
Operating system
HassOS
Install method
HassOS Addon
Coral version
USB
Network connection
Wired
Camera make and model
Reolink 410 and Reolink 510WA
Any other information that may be helpful