lldap VS frigate

Good to hear, I think it'll make many users happy. For me, I've migrated back to Authelia. I moved to authentik because at the time Authelia had no user management. After all of authentik's sharp edges, I've found lldap[0], and was able to implement a pilot in a few hours. I haven't looked back, since everything was converted.

[0]: https://github.com/lldap/lldap

I wrote LLDAP (https://github.com/lldap/lldap) after struggling to install and configure openLdap on my homelab.

I've recently installed and configured LLDAP (Lightweight LDAP) - More details here if you've never heard of it before: GitHub - lldap/lldap: Light LDAP implementation

I've an LLDAP instance running to make managing users easier.

I'm trying to integrate LDAP into my small homelab but I'm extreme noobie in it. So far I've tried: 1. OpenLDAP - not so resource heavy but I found it difficult go get working correctly with NextCloud, Keycloak and Jellyfin. Maybe someone could recommend an easy to follow guide? 2. LLDAP - honestly it's almost prefect. Nice clean UI, great guides how to setup with everything I need, but it's a read-only LDAP, so I cannot create or manage users with Keycloak or NC, that's about the only downside and probably bugs me more than it should. 3. 389ds - has everything I need (and probably some more), super easy to setup with this guide but the elephant in the room is that it uses 700MiB of RAM (whereas LLDAP uses only 7-8MiB). That's a big difference which really makes me question whether I want to use this particular solution.

Note that if you want to use KeyCloak for the OpenID but want to still have a LDAP source of truth, you can use LLDAP + KeyCloak together, with LLDAP as the source of truth and KeyCloak giving you the fancy features: https://github.com/lldap/lldap/blob/main/example_configs/key...

To be fair, their respective documentations (here and here) are pretty comprehensive.

Am in to selfhosting and homeserver, finally got to try Frigate with some aliexpress camera that was not mine. Love it.

However, I have had success using IP Camera app with Frigate. https://play.google.com/store/apps/details?id=com.pas.webcam https://frigate.video/

Frigate https://frigate.video/ and ZoneMinder https://zoneminder.com/ come to mind. Blue Iris https://blueirissoftware.com/ is not open source but is what I prefer to use for my PoE systems ($80/yr)

Logger: custom_components.frigate Source: custom_components/frigate/__init__.py:201 Integration: Frigate (documentation, issues) First occurred: 1:59:34 AM (2 occurrences) Last logged: 1:59:48 AM

Engineering implies working within constraints. Most people in this realm only have to deal with the spouse acceptance factor as a limiter.

Went from openhab -> homeassistant -> Node-RED. Then sprinkle in MySensors, Frigate, and Double-Take, but not on just the entrance, go for the perimeter then defense in depth.

https://www.mysensors.org/

https://frigate.video/

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

- https://github.com/blakeblackshear/frigate/discussions/7932#...

I have found my frigate+ model to be much more accurate and crazy good even at night. Will be curious how things change when it snows here more often, since I've not submitted any examples of winter at this house yet.

According to the author of that PR, they're using 10% of 1 NPU core on 3 cameras: https://github.com/blakeblackshear/frigate/pull/8382#issueco...

The bottleneck instead will probably be the video stream decoding speed, especially as the SoC's hardware decoder isn't being used yet.