homebridge-unifi-protect VS double-take

For several years I've been relying on an authentication mechanism with my main UDM (v3.1.16) that relies on the X-CSRF-Token header returned when doing a GET request directly to the UDM's IP address, as per the instructions found here (https://github.com/hjdhjd/homebridge-unifi-protect/blob/main/docs/ProtectAPI.md).

Nice suggestions using relays as. Alternatively, if you can use a Protect Chime (may require multiple as they are not very loud) - https://eu.store.ui.com/collections/unifi-accessories/products/smart-chime or if you are feeling adventurous, you can use existing smart speakers as chimes with a Home Assistant (https://johnzanussi.com/posts/unifi-g4-doorbell-chime-with-sonos) or Homebridge integration (https://github.com/hjdhjd/homebridge-unifi-protect).

I also have only HSV cameras or Ubiquiti ones for this reason. Everything I care about is stored on-site or in the cloud with end-to-end encryption, no privacy or surveillance state enablement concerns.

There's a great HomeBridge plugin which enables HomeKit Secure Video on my UniFi Protect cameras: https://github.com/hjdhjd/homebridge-unifi-protect

Which Homebridge Unifi Protect plugin did you try? This one worked well for me, but I eventually got tired of maintaining 2 camera systems and gave up on HKSV. My wife actually prefers the Unifi Protect app anyway since it has continuous history and a decent UI- so why bother with HK?

This one https://github.com/hjdhjd/homebridge-unifi-protect

For the plug-in ? There’s the repository.

How does scrypted compare to https://github.com/hjdhjd/homebridge-unifi-protect ? This works pretty well but does have some delays loading cams at times.

Homebridge UniFi Protect

# Learn more at https://github.com/jakowenko/double-take/#configuration

I looked at Double Take (UI that lets you do the training of your face recondition easily) and found CompreFace as one of models they support. It looks like what I need but there is a catch... no OpenVino (intel CPUs AI accelerator) support. I really like my low power NVR setup and would like keep it that way. Running AI on CPU without acceleration is both power inefficient and much slower. I have a spare low end GPU but if dump it in the system the current AI acceleration brakes... (I know I can prob fix it but that is a rabbit hole I would prefer to avoid).

CompreFace can be used "in addition" via Double-Take but that is additional detection based on frigate object events.

Not OP, but I _love_ talking about this stuff, so you're stuck with me. :D

I'm a big fan of this project:

https://frigate.video/

It's open source, and you can hook it up to a Coral (or some other things, I think) to get crazy-fast classifications. But CPU is fine for only a few cameras.

Once you get something like that setup, it's just a matter of finding cameras that support RTSP. You get them setup however you like (but preferably wired, with PoE), point Frigate at the RTSP stream, and that's it. Now you've got home security footage that never leaves your house. You can set up a VPN to watch the feeds from elsewhere. Frigate supports MQTT as well, so you can hook it into Home Assistant to get notifications, and even pipe person events into something like Double Take to get face detection:

https://github.com/jakowenko/double-take

have you checked out double take?

I purchased this device off eBay the week of July 4th, and willingly paid scalper prices with the idea that I'd spend much of that week learning Frigate, double-take, and DeepStack; turns out, I had the ML-powered facial recognition, alerts and Home Assistant automations up and running in an hour.