@repomanz commented on GitHub (Feb 2, 2024):
so what is broken about it? based on the config it looks like the release notes were not read, you need to adjust your config and have frigate…
@briodan commented on GitHub (Feb 2, 2024):
The exact same config, permissions and all had been running fine on 0.12 for months.
only thing I did is pull a new docker image.
@NickM-27 commented on GitHub (Feb 2, 2024):
This is your path
path: /trt-models/yolov4-416.trt
That is not /config/model_cache/yolov4 like you are showing.
Also, you are using a 416x416…
@briodan commented on GitHub (Feb 2, 2024):
permissions on the directories
permissions…
@HIB-lager commented on GitHub (Feb 3, 2024):
few more observations after another try with fresh image (bookworm 64 bit): In fresh image Coral is detected as Bus 002 Device 002: ID 1a6e:089a…
@NickM-27 commented on GitHub (Feb 2, 2024):
so what is broken about it?
based on the config it looks like the release notes were not read, you need to adjust your config and have frigate…
@HIB-lager commented on GitHub (Feb 3, 2024):
after some more digging I narrowed it down to power supply issues. Originaly I had Coral connected to USB 3.0 port and noticed that it's drawing…
@NickM-27 commented on GitHub (Feb 2, 2024):
it's not stopping due to the connection that is just an nginx log, there may be some permission issue on the config dir like a few others have seen
@Te-eMster commented on GitHub (Feb 2, 2024):
Thanks, that might actually have done the trick. The "frigate.db" file was still there after docker compose down, but probably the redundant volume…
@mist0706 commented on GitHub (Feb 2, 2024):
Well that is incredibly embarassing. I've spent an hour troubleshooting.... Thanks that fixed it....
@Orion74C commented on GitHub (Feb 2, 2024):
I guess the release notes are there for a reason. My bad. Appreciated!
@NickM-27 commented on GitHub (Feb 2, 2024):
feel free to create a new issue if something else comes up
@NickM-27 commented on GitHub (Feb 2, 2024):
this is redundant, you should just…
@NickM-27 commented on GitHub (Feb 2, 2024):
this was mentioned in the release notes, by default the go2rtc api is not available due to security issues. If you want to access the go2rtc dashboard…