Open civita opened 6 months ago
I would like to know if there's better way to do that. Thanks.
this is the best way until frigate natively supports saving this data
go2rtc supports multiple configs. And it will use first config as main config. So main config may be placed in the /config/go2rtc.yaml
and second config may be placed to frigate.yaml
go2rtc supports multiple configs. And it will use first config as main config. So main config may be placed in the
/config/go2rtc.yaml
and second config may be placed tofrigate.yaml
And what happens if the camera name will changed through the frigate configuration?
Anyway homekit section should be added manually to main config. If user has streams section in the frigate, he should sync names manually in two configs.
@civita - are you running host networking in your compose? I'm using the addon for HomeAssistant and can't get the pairing to complete unless I run the go2rtc addon directly. Trying to see if I can modify the frigate addon to work properly with homekit pairing.
Hi @kidhasmoxy, sorry for the late reply. I am running Frigate docker version with privileged mode. If it's a pairing problem not sure if it's due to mDNS port used by multiple apps.
I don't have problems with mDNS on server with go2rtc and some other software, that also using mDNS
Describe the problem you are having
I am using HomeKit module from go2rtc and am able to pair cameras and view them in Apple Home app. However, it works until Frigate restarts.
In go2rtc logs, it shows the following error after restarting Frigate:
ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:179 > error="hap: PairVerify from: 10.8.0.86:49347, with unknown client_id: ..."
It looks like go2rtc will append client_id to config.yml after successful pairing. However, the file go2rtc uses in Frigate instance is located in
/dev/shm/go2rtc.yaml
which is atmpfs
filesystem and will be re-generated from Frigate'sconfig.yml
after restart.The workaround I am using is looking at the
go2rtc.yaml
(directly or via :1984), findingclient_id
, and manually add it intoconfig.yml
in Frigate:I would like to know if there's better way to do that. Thanks.
Version
0.13.0-C35C7DA
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
No response
Operating system
Debian
Install method
Docker CLI
Coral version
USB
Network connection
Wired
Camera make and model
N/A
Any other information that may be helpful
No response