The comments here are interesting, as I’m helping with a project developing the software stack for mini servers we hope to sell that are preconfigured with Home Assistant (home automation) and Frigate NVR (camera control and recording) with local storage, local control, and no cloud component.
The hardware we’re using for prototyping are off-lease Dell 7050 Micros running Proxmox, with 500gb Crucial MX500 ssds and an NVME Coral TPU that Frigate uses for object detection, which reduces CPU usage. 500gb is enough, because Frigate can be set to auto delete recorded clips after a set period of time, and clips can easily be saved.
Frigate can be installed via docker or as an add-on to Home Assistant. If you want to use Home Assistant, you can install Home Assistant OS directly on the SSD via these instructions.
We’re using Amcrest WiFi cameras (IP4M-1041B) that connect to an on-board WiFi network controlled by an OpenWRT VM that uses the WiFi card in the system (not the ones that come with the Dells). Everything on our systems is locked down by an Opnsense firewall vm, so it should be safe to use even in an existing unsecured network.
Personally, for my own system, I’ve been running 4 Amcrest ethernet turret cameras (IP5M-T1179EW) for about 4 years now with no problems. You just need a cheap PoE switch (mine was $20) and then run some cables.
To use Frigate, the cameras must support both ONVIF and RTSP. Pro tip: the Amcrest Smart Home line of cameras won’t work - you need a camera with a built-in web server for direct configuration.
For remote access, you could set up Wireguard (via an official Home Assistant add-on), or you could pay Nabu Casa (Home Assistant’s parent company) $65/year (or 75 EUR), enter your credentials in the Home Assistant app and you’re good to go, while helping fund future Home Assistant development.
Thanks! Since our entire software stack is open source, and since open source software has been so transformative for our lives in general, it’s a priority for us to give back where we can.
The profit will come from labor involved in assembling the hardware, pre-configuring the software for each customer, and providing personalized support via a set of subscription support plans at various prices, including individual one-offs.
We’ll be dedicating a set amount of time every day to read support forums for the software we use (and places like Lemmy) and provide help where we can.
We are not quite ready to roll everything out yet -it’ll probably be another 2 or 3 months, but I’d be happy to shoot you a message when we go live if you’d like.
The comments here are interesting, as I’m helping with a project developing the software stack for mini servers we hope to sell that are preconfigured with Home Assistant (home automation) and Frigate NVR (camera control and recording) with local storage, local control, and no cloud component.
The hardware we’re using for prototyping are off-lease Dell 7050 Micros running Proxmox, with 500gb Crucial MX500 ssds and an NVME Coral TPU that Frigate uses for object detection, which reduces CPU usage. 500gb is enough, because Frigate can be set to auto delete recorded clips after a set period of time, and clips can easily be saved.
Frigate can be installed via docker or as an add-on to Home Assistant. If you want to use Home Assistant, you can install Home Assistant OS directly on the SSD via these instructions.
We’re using Amcrest WiFi cameras (IP4M-1041B) that connect to an on-board WiFi network controlled by an OpenWRT VM that uses the WiFi card in the system (not the ones that come with the Dells). Everything on our systems is locked down by an Opnsense firewall vm, so it should be safe to use even in an existing unsecured network.
Personally, for my own system, I’ve been running 4 Amcrest ethernet turret cameras (IP5M-T1179EW) for about 4 years now with no problems. You just need a cheap PoE switch (mine was $20) and then run some cables.
To use Frigate, the cameras must support both ONVIF and RTSP. Pro tip: the Amcrest Smart Home line of cameras won’t work - you need a camera with a built-in web server for direct configuration.
For remote access, you could set up Wireguard (via an official Home Assistant add-on), or you could pay Nabu Casa (Home Assistant’s parent company) $65/year (or 75 EUR), enter your credentials in the Home Assistant app and you’re good to go, while helping fund future Home Assistant development.
You are my kind of admin, so, any suggestions on hardware that use starlight sensors? Or anything comparable in low light with color?
Kudos to the guy sharing his expertise for free while working on something similar they’re trying to profit from
Thanks! Since our entire software stack is open source, and since open source software has been so transformative for our lives in general, it’s a priority for us to give back where we can.
The profit will come from labor involved in assembling the hardware, pre-configuring the software for each customer, and providing personalized support via a set of subscription support plans at various prices, including individual one-offs.
We’ll be dedicating a set amount of time every day to read support forums for the software we use (and places like Lemmy) and provide help where we can.
Very refreshing to see.
What is the name or your project? I’m interested in being a customer. When do you hope to have the first product released?
We are not quite ready to roll everything out yet -it’ll probably be another 2 or 3 months, but I’d be happy to shoot you a message when we go live if you’d like.