The camera must not be paired with anything over homekit. If you have paired it with HA you have to unpair it first. Then you can find it in go2rtc in homekit section. To add the doorbell back to HA you can create a new homekit feed and duplicate the original videofeed shown in my yaml:
streams:
klingel:
- homekit://...... (Homekit link taken from the "Add"-Tab under Home-Assistant)
- ffmpeg:klingel#audio=opus
homekit:
klingel:
If you paired it with your iPhone before, you have to delete it from the home app. You can still use the Aqara app.
Once the doorbell isnât paired to anything via Homekit, you can pair it with HA as a Homekit Device. For me the doorbell was automatically discovered. When youâre running into problems I suggest to reset the doorbell to factory settings.
Now the doorbell streams to your HA. You can use the entinities but the video is quite laggy and you are not able to pair it to another device like your iPhone, since Homekit only allows one connection to one IP. Since go2rtc runs on the same IP as your HA-Server (mandatory) you can replicate the videostream via go2rtc.
When paired with HA, go to the go2rtc panel and in the âadd/devicesâ tab you find the section âHome Assistantâ. There youâll find your with HA paired doorbell with the Homekit Link. Copy the link and add it to your config in go2rtc like my yaml shown above.
To duplicate the stream you use the second part of the yaml, telling go2rtc to use the same videofeed url and broadcast it as a new device. Your iPhone will think its a new device, so you can pair it and use it in your Homekit app.
I hope this helped. Let me know if that worked for you, since we have very various feedback here.
so i only need to pair G4 doorbell with HA as a Homekit Device,i dont need to go to the go2rtc panel and click the "pair " button under the âadd/devicesâ tab?
Really? The event is way more reliable than the feed in my case. I actually find my set pretty satisfying, with working PiP to TV and all homekit functionality.
My doorbellâs on 6 triple-A batteries so sometimes the feed takes time to initialize.
One real problem is the feed being used (doorbell with red light on) for an extended period of time (the length also seems random) while the go2rtc says no device is streaming. It was mostly nothing except it drains battery fast.
What is the consensus on the current reliability of the camera? Given new updates and stuff?
Is it safe enough to be used day to day (with two way audio!)
The feedback here differs. Some users are having no issues.
I gave up a few months ago, I had problems with the connection. But since this thread is getting more activity lately Iâm willing to test it again. I had two or three updates since then, maybe itâs better now. But Iâm still hoping for the matter update.
Beside from Home Assistent Iâm pretty satisfied with the doorbell. Quick connection, good video quality, nothing to complain until now.
You can only integrate it via homekit, and I donât think two-way audio on this source was ever supported by go2rt, maybe someday. That said, it doesnât compromise the two-way audio on hk if you use transparent proxy.
No else found the issue of the device running out of streams? Maybe just me.
More generally (not HA-related), I found that when the device gets too hot, the periodic snapshot of the device fails. This shows as âNo Responseâ on the thumbnail but when you clickthrough to the live stream the stream itself always works. Seems like a bug but maybe Aqara put it this way to reduce the load on the device when hot.
Hello AlexxIT! Iâm having a similar problem⌠After some hours it stop to share the live on the dashboard. If i change the PIN (for example adding a number ) it start to work again for some hour⌠What could be the problem ?
Just set it up, go2rtc connects directly to the camera via the HomeKit protocol, and exposes the stream to HomeKit (transparent proxy) and to frigate. It works perfectly! havenât yet added it to home assistant but I wouldnât see why it wouldnât work!