Closed rasika-jay closed 7 months ago
Is there a reason why go2rtc.yaml needs to be in /dev/shm? Is it possible to update the code to persist go2rtc.yaml in /config? Thanks!
because frigate applies its own default values that are not set by the user, having a config that is directly persisted would cause confusion and conflicts especially as frigate changes these defaults between versions.
For now you can access the homekit values and then save them in the go2rtc section of the frigate config. In the future we can implement something that does this automatically.
Closing this as a duplicate of https://github.com/blakeblackshear/frigate/issues/9016
Describe the problem you are having
To reduce repetition, I started using go2rtc bundled within Frigate to expose cameras to HomeKit. I'm using go2rtc
1.8.4
and frigate0.12.1
in Docker (compose).I have successfully paired go2rtc cameras to HomeKit and it works as expected until I restart the frigate container (or config->save->restart).
When you pair a go2rtc camera with HomeKit, it seems to add a new section
pairings
withclient_id
togo2rtc.yaml
file:However when Frigate is restarted
/dev/shm/go2rtc.yaml
is recreated from fresh, without the abovepairings
section, which makes the previous HomeKit pairings invalid.I've got around this by making my own Docker image with
go2rtc.yaml
being persisted as/config/go2rtc.yaml
in/docker/rootfs/etc/s6-overlay/s6-rc.d/go2rtc/run
and/docker/rootfs/usr/local/go2rtc/create_config.py
.Is there a reason why
go2rtc.yaml
needs to be in/dev/shm
? Is it possible to update the code to persistgo2rtc.yaml
in/config
? Thanks!Version
0.12.1
Frigate config file
Relevant log output
Frigate stats
No response
Operating system
Debian
Install method
Docker Compose
Coral version
USB
Any other information that may be helpful
No response