video1.0<iframe src="https://www.loom.com/embed/9ba4457939304ff0846e1962353483e7" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/9ba4457939304ff0846e1962353483e7-81e33477e3634956.gif412.501This Loom walks through Harbor’s beta HomeKit integration using a WebRTC HTTPS ingestion endpoint and an open source RTC media bridge to convert camera H.265 to HomeKit’s required H.264. The setup requires a more tech-savvy user and a server, with a Mac demonstration noting about 6 percent CPU for two cameras and auto-restart after laptop reboot. The WIP endpoint is entered in the Harbor mobile app under camera advanced settings, then HomeKit pairing uses the code 2254-0434. The creator emphasizes setting a DHCP IP reservation because the endpoint does not support MDNS camera reachability, and suggests rebooting the camera or expecting improved resilience in version 2.8.1.