It would be amazing if it doesn’t disintegrate if it rains, too.
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.
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.
I’ve used a ton of ubiquity unifi cameras and they have a solid range on pricing. I think you need the unifi software to commission them though. For what it’s worth they don’t use the cloud for storage and don’t require any sort of subscription.
Ubiquity is the definition of vendor lock in.
deleted by creator
I’ve had four cameras running for a few years, streaming over RTSP and powered over ethernet. Works well!
Is this something a complete novice could do, with reasonable effort and cost? If so would you be able to eli5, or point me in the direction of somewhere that does?
Ideally, for my current situation anyway, I’d like to set up a camera indoors by a window (with IR switched off and a proper mount) and be able to see what it sees from a device (phone pc or even dedicated pad if it helps with security) in the other room, and if it can also record and save the video locally for me to be able to access from the remote device, that’d be good too. Privacy and security of the data are top priority.
Every time I start looking in to it my brain gets completely overwhelmed by options and information and scrambles, and I have to back away 😑 I’d love for there to be a way to set this up that was near as straightforward as the privacy abusing options…
It’s not too difficult, I figured it out and I eat crayons.
Here’s the software I use but there are other options: https://github.com/BreeeZe/rpos - That runs on the camera Pi and provides the video stream.
I use a Pi, a camera module like this https://www.raspberrypi.com/products/raspberry-pi-high-quality-camera/ and a suitable lens. You can get cheaper camera modules, IR modules, etc.
Also, something like this to power it: https://www.tp-link.com/us/business-networking/omada-switch-unmanaged/ds105gp/ You could just use a regular switch and power the Pi with a power adapter if that works better. My cameras are all ceiling mounted so having one cable for data and power made sense for me.
I use this to split the ethernet into power and data when it reaches the Pi: https://www.amazon.com/UCTRONICS-PoE-Splitter-USB-C-Compliant/dp/B087F4QCTR/130-2310467-3870744
Then I have this running on a Linux VM to collect the camera feeds and display them in a web browser: https://github.com/motioneye-project/motioneye
You’ll also need a case, my solution was to buy a metal Pi case and mount the module onto that, feeding the ribbon cable back into the case.
If you decide to go ahead and need help, just ask.
Oh wow, thanks so much for all the info, I really appreciate it! I’m bookmarking you reply and all the links, but it’s a bit much for me to process right now lol (I saw your comment about pretty much what I want to set up and just had to ask, fully meaning to get in to it, but it’s been a long morning and my brain is now mush)
Just to give you an idea, I’ve never set up or even used a Pi or used Linux, I’ve done very basic pc building and troubleshooting, but have no programming knowledge, so when I said novice I meant it 😂 I’m mostly good at following directions as long as they’re clear. Are there any manuals that would tell me how to put all the different parts you mentioned together?
There are plenty of guides but I just took it step by step. The links I provided have instructions for each bit of software needed. You’ll need to be able to do things like flash the OS to a SD or USB drive and then be able to ssh into the Pi to install the camera software. Start here: https://www.raspberrypi.com/software/
There’s no programming skill needed but you should be comfortable with using the terminal, or at least be willing to learn. You don’t need to install a OS with a desktop, everything is done via the terminal.
After that’s done you can use VLC to view the feed and check it’s working before installing motioneye on a server. You just get the IP address of the camera and give the URL to VLC like this: rtsp://xxx.xxx.xxx.xxx:8554/h264
If you look at the whole thing in one go, it’s overwhelming, but if you break it into chunks it’s not too bad and it’s a good learning opportunity, if that’s your thing.
If you look at the whole thing in one go, it’s overwhelming, but if you break it into chunks it’s not too bad and it’s a good learning opportunity, if that’s your thing.
This is very encouraging and helpful, I will try to keep it in mind! Do I just go in the order of the links you posted in the previous reply?
Also just to make sure I understand correctly - at the end of it I should have a camera setup that I can access, via VLC, from the device of my choosing over ethernet/intranet?
Thanks again for taking the time to talk me through this.
Do I just go in the order of the links you posted in the previous reply?
Yes. Get a working camera feed and go from there. For that, tackle the hardware side first - Pi, camera, power/ethernet, case, storage for the OS. Then install the OS and the camera software and test it. Mine are all indoors so you’ll have to see what kind of cases are weatherproof if you’re using it outside.
Also just to make sure I understand correctly - at the end of it I should have a camera setup that I can access, via VLC, from the device of my choosing over ethernet/intranet?
Exactly. VLC will be fine if you only want to view one camera. If you want to add more, do recording/motion detection, view them in a browser, etc. then MotionEye on a server works but there are other options. I know that the Synology NAS’ DSM OS has its own solution for managing all that stuff.
