[Support]: Go2RTC camera not available in HomeKit after Frigate restart #13610

jerome71 · 2024-09-07T14:58:33Z

jerome71
Sep 7, 2024

Describe the problem you are having

I added a camera from Frigate/Go2rtc to HomeKit (the Home app on Apple devices)
Initially, it works beautifully on my iPhone, iPad, Apple TV, Mac ...

But, after I restart Frigate, the camera is "not responding" in the Home app, and Frigate and Go2RTC show a lot of errors.
192.168.42.8 is my Apple TV, which acts as a HomeKit hub.

Initially tried with 6 cameras, that all worked well, until I restarted Frigate.
If I remove the cameras from HomeKit, I get no more errors in the logs.

The config file and logs are after adding just this camera.
The 1st Go2rtc log is just after adding the camera to HomeKit. The 2nd Go2RTC log is after restarting Frigate.

Please advise if you think this should be posted to the Go2RTC pages.

Version

0.14.1-f4f3cfa

What browser(s) are you using?

Not relevant / iOS 17.x (current)

Frigate config file

homekit:
    Escalier_Hameau:                   # same stream ID from streams list
      name: Escalier      # custom camera name, default: generated from stream ID
      pin: 12345678           # custom PIN, default: 19550224

Relevant Frigate log output

I saw errors in the Frigate log after adding the camera to HomeKit but could not reproduce them.

Relevant go2rtc log output

2024-09-07 16:34:37.039501507  [INFO] Preparing new go2rtc config...
2024-09-07 16:34:37.452694601  [INFO] Starting go2rtc...
2024-09-07 16:34:37.537543585  16:34:37.537 INF go2rtc platform=linux/arm64 revision=b2399f3 version=1.9.2
2024-09-07 16:34:37.537550788  16:34:37.537 INF config path=/dev/shm/go2rtc.yaml
2024-09-07 16:34:37.538044288  16:34:37.537 INF [api] listen addr=:1984
2024-09-07 16:34:37.538124288  16:34:37.538 INF [rtsp] listen addr=:8554
2024-09-07 16:34:37.538425288  16:34:37.538 INF [webrtc] listen addr=:8555/tcp
2024-09-07 16:34:46.902121007  [INFO] Starting go2rtc healthcheck service...
2024-09-07 16:46:06.737098965  16:46:06.736 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50752, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"


2024-09-07 16:48:51.800833216  [INFO] Starting go2rtc...
2024-09-07 16:48:51.920985301  16:48:51.920 INF go2rtc platform=linux/arm64 revision=b2399f3 version=1.9.2
2024-09-07 16:48:51.921085690  16:48:51.921 INF config path=/dev/shm/go2rtc.yaml
2024-09-07 16:48:51.921777708  16:48:51.921 INF [api] listen addr=:1984
2024-09-07 16:48:51.922045485  16:48:51.922 INF [rtsp] listen addr=:8554
2024-09-07 16:48:51.922320189  16:48:51.922 INF [webrtc] listen addr=:8555/tcp
2024-09-07 16:49:01.219381482  [INFO] Starting go2rtc healthcheck service...
2024-09-07 16:49:01.806790713  16:49:01.806 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50761, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:01.848717289  16:49:01.848 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50762, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:01.869373124  16:49:01.869 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50763, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:06.948694395  16:49:06.948 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50764, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:06.975301243  16:49:06.975 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50765, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:23.999892246  16:49:23.999 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50766, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:24.019435933  16:49:24.019 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50767, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:24.048593205  16:49:24.048 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50768, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:24.063152453  16:49:24.062 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50769, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:26.805677979  16:49:26.805 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50770, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:26.833870178  16:49:26.833 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50771, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:26.873436182  16:49:26.873 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50772, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:26.887761948  16:49:26.887 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50773, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:26.919700476  16:49:26.919 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50774, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:26.933305798  16:49:26.933 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50775, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:26.961847126  16:49:26.961 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50776, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:26.979986000  16:49:26.979 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50777, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:29.215138006  16:49:29.214 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50778, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:29.237115358  16:49:29.236 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50779, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:39.366786302  16:49:39.366 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50780, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:39.385055898  16:49:39.384 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50781, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:49:59.481681946  16:49:59.480 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50782, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:49:59.497577211  16:49:59.497 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50783, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:50:11.324190806  16:50:11.324 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50784, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:50:11.350666766  16:50:11.350 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50785, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:50:12.689868783  16:50:12.689 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50786, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:50:12.705575881  16:50:12.705 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50787, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:50:15.921800191  16:50:15.921 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50788, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:50:15.944934987  16:50:15.944 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50789, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:51:11.329104642  16:51:11.328 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50790, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:51:11.354355899  16:51:11.354 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50791, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"
2024-09-07 16:52:11.329815853  16:52:11.329 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50792, with unknown client_id: 5AB2670B-569A-491D-BA2B-371EFA72826C"
2024-09-07 16:52:11.354424833  16:52:11.354 ERR github.com/AlexxIT/go2rtc/internal/homekit/homekit.go:178 > error="hap: PairVerify from: 192.168.42.8:50793, with unknown client_id: 0C2E018B-61A0-4ED6-ADE2-496ADD1DD8AF"

FFprobe output from your camera

Not relevant IMHO

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

Object Detector

CPU (no coral)

Network connection

Wired

Camera make and model

Dahua and Axis

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

Answered by vigeland

Sep 8, 2024

After add the camera add to home, take a look under /dev/shm/go2rtc.yaml. You see new added entrys. Paring ….
Now add the lines to you frigate yml in the go2trc section.
Then the home Konfiguration will work after restart.
Problem is on frigate side, frigate will not read and add configuartion changes made on go2rtc side.

View full answer

NickM-27 · 2024-09-07T15:01:57Z

NickM-27
Sep 7, 2024
Collaborator Sponsor

yeah this should be posted in go2rtc repo

6 replies

jerome71 Sep 7, 2024
Author

Someone replied there that this is a known issue, linked with the way Frigate integrates Go2RTC and resets its configuration at start, therefore not storing persistently the HomeKit linking stuff.
if that's of interest to anybody, it's here AlexxIT/go2rtc#1343 (comment)
and any workaround would be appreciated 😊

NickM-27 Sep 7, 2024
Collaborator Sponsor

I see, yeah there's not really a good way to facilitate that at this time, will have to see what can be done in the future

jerome71 Sep 7, 2024
Author

OK. They say it's on Frigate's side.
I know how to do in the mean time.

Thanks a lot for this great software.

vigeland Sep 8, 2024

After add the camera add to home, take a look under /dev/shm/go2rtc.yaml. You see new added entrys. Paring ….
Now add the lines to you frigate yml in the go2trc section.
Then the home Konfiguration will work after restart.
Problem is on frigate side, frigate will not read and add configuartion changes made on go2rtc side.

Answer selected by jerome71

jerome71 Sep 8, 2024
Author

Thx @vigeland
I initially created a second docker container with go2rtc, this one in host networking mode, which exposed the streams created by Frigate's Go2RTC to HomeKit. This was a bit more complicated.

Saw your post and used your solution. SImpler and less configuration.
It works well, and I learnt how to execute commands (copy files) within a docker container :-).

Thanks!

mofman · 2024-10-10T21:12:36Z

mofman
Oct 10, 2024

Using vigeland answer in full looks like this:

Configure go2rtc in Frigate

Edit /etc/frigate/config.yml:

go2rtc:
  streams:
    Back_of_House:
      - rtsp://XXXX:[email protected]/live0
      - ffmpeg:Back_of_House#audio=aac#audio=opus
  homekit:
    Back_of_House:
      name: Back of House
      pin: 12345678

Pair the Camera in Apple Home App

Open Apple Home app
Add Accessory
Choose More Options
Select your camera
Enter pin number set in config

Retrieve and Add Pairing Block

docker ps
docker exec -it <container_id> /bin/sh
cat /dev/shm/go2rtc.yaml
--------
nano /etc/frigate/config.yml
# Add the copied pairing block under each camera's HomeKit section

go2rtc:
  streams:
    Back_of_House:
      - rtsp://XXXX:[email protected]/live0
      - ffmpeg:Back_of_House#audio=aac#audio=opus
  homekit:
    Back_of_House:
      name: Back of House
      pin: 12345678
      pairings:
        - client_id=B2DE8430-F16B-4E5B-B6CF-1FDAFBXXXXXXX&client_public=10a01486acf6f19af78830c131be7462966844928e2cd37e8dd341fXXXXXXX99&permissions=1
        - client_id=AEEC6324-C2A2-4477-A7C7-652ECFXXXXXXX&client_public=2a3eef0fdadefd0b0afec36ea6defa4ec260bf7256d8f4f4c30c11cXXXXXXX59&permissions=0

Note: HomeKit only supports Opus audio. If Opus isn’t enabled during initial pairing, you need to remove the pairing block and restart the setup in order to get audio working.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Support]: Go2RTC camera not available in HomeKit after Frigate restart #13610

{{title}}

Replies: 2 comments 6 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

[Support]: Go2RTC camera not available in HomeKit after Frigate restart #13610

jerome71 Sep 7, 2024

Describe the problem you are having

Version

What browser(s) are you using?

Frigate config file

Relevant Frigate log output

Relevant go2rtc log output

FFprobe output from your camera

Frigate stats

Operating system

Install method

Object Detector

Network connection

Camera make and model

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 2 comments · 6 replies

NickM-27 Sep 7, 2024 Collaborator Sponsor

jerome71 Sep 7, 2024 Author

NickM-27 Sep 7, 2024 Collaborator Sponsor

jerome71 Sep 7, 2024 Author

vigeland Sep 8, 2024

jerome71 Sep 8, 2024 Author

mofman Oct 10, 2024

jerome71
Sep 7, 2024

Replies: 2 comments 6 replies

NickM-27
Sep 7, 2024
Collaborator Sponsor

jerome71 Sep 7, 2024
Author

NickM-27 Sep 7, 2024
Collaborator Sponsor

jerome71 Sep 7, 2024
Author

jerome71 Sep 8, 2024
Author

mofman
Oct 10, 2024