Thank you. When I have free time - I will explore your project. If it's not too difficult, I can try to add logic inside go2rtc, so that everything works without external dependencies.

Thanks. The prerequisite is that a user needs to start the AWS Kinesis stream and get the credentials, etc., via the Abode API, which is what the 'abode' CLI that is called by 'go2rtc' handles. Once that is done, the rest is pretty straightforward.

I have an Abode IOTA that supports HomeKit and can be paired with Home Assistant and the stream shows up in the dashboard, but I have not been able to get it to work with go2rtc.

I tried pairing it directly to go2rtc and proxying it, but go2rtc doesn't see it natively for some reason, although Home Assistant does find it without issue.

I also tried taking the hass device and that fails to play in go2rtc as well. Interestingly, I then tried proxying the hass device and paired it with Apple Home on my ios device and it plays properly and 2 way audio even works that way.

My best guess is there's some filter in place that is preventing it from being seen by go2rtc. I've worked with HomeKit protocol in the past and even submitted some patches so I plan to take a look and see if I can figure out how to pair it with go2rtc directly.

Even if proxying the hass device did work properly it really doesn't fit my needs as I run go2rtc bundled with Frigate on a separate machine from Home Assistant and don't really want to push the video through HA, then pick it up on Frigate when I could just eliminate the extra hop for streaming video

I have a branch I'm working on this in and have it functioning over HomeKit directly. I didn't have to do much to get it going, first was to allow bridge devices to be displayed in the UI then the TLV8 parsing needed a slight tweak to account for the fact this particular device sends 0xff, 0x00 in between it's TLV8's. I've got some additional testing to do with it still but I'll send a PR over.