T-80: Lasted for 34 minutes before succumbing to crippling depression and taking itself permanently offline
Two things:
- I was expecting a recipe at the end of that
- CUT YOUR HAIR, JOSH
Disk space is definitely an issue, but I think I've got my single user instance dialed in on a 2 vcpu/4gb/30GB RAM Hetzner VPS; a cron job that runs at the first of every month deletes pictrs files over 30 days old. Currently at 74%.
A lot of bean memes died the day that job first ran.
Judging by the profile pic, probably factually incorrect animal documentaries
Apparently the island is a barony of Norway and the penguin, Nils Olav III, is a Major General of the Norwegian Army and colonel-in-chief of the King's Guard
Let's hope for more scandals and leaks so we can collectively refer to them as GaetzGates
Yeah, the tablet runs Fully Kiosk and I tried the same thing with the battery percentage thing and ran into the same issue, so I just simplified and made the automation time-based.
The tablet also likes to freeze a few times a day, so I also created an automation that toggles the smart plug power whenever HA loses connection to the tablet for more than 5 seconds, then toggles back to the original state at the start of the automation, which corrects the problem. Until the next time. But hey! It was only $60, so it's fine.
That's a nice setup. I am weirdly jealous of the sliding shelf. The CS350B is very nice as well.
Heat, then suction?
On a related note, I solved the battery issue with my wall mounted Fire tablet (for an HA dashboard) by connecting the power supply to a smart plug and setting up an automation to only give it the juice for about 3 hours per day, spread throughout the day
From top to bottom:
- Patch panel (with artisinal, handmade cables)
- TP-Link managed switch Shelf 1:
- PFSense 4 port firewall
- Lenovo m910q w/Proxmox (cluster node 1) running 2 VMs for docker hosting: Ubuntu for media stuff (arrs, navidrome, jellyfin, calibre, calibre-web, tubesync, syncthing) and Debian for other stuff (paperless-ngx, vikunja, vscodium, redlib, x-pipe webtop, fasten health, linkwarden, alexandrite), 1 Win 10 VM for the very few times I need to use windows, some Red Hat Academy student and instructor RHEL 9 VMs, and an OPNsense VM for testing Shelf 2:
- HP Elitedesk G5 800 SFF w/Proxmox (cluster node 2) with an Nvidia GT 730 passed through to a Debian VM used primarily as a remote desktop via ThinLinc, but also runs a few docker containers (stirling pdf, willow application server, fileflows)
- Shuttle DH110 w/Proxmox (cluster node 3) with 1 VM running Home Assistant OS with an NVME Coral TPU passed through as well as a zooz 800 long range zwave coordinator (the zigbee coordinator is ethernet and in a different room) and two LXCs with grafana and prometheus courtesy of tteck (RIP) Shelf 3:
- WIP Fractal R5 server to replace the ancient Ubuntu file server to the left (outside the rack, sitting on the box of ethernet cable) that is primarily the home of my media drives (3 12 TB Ironwolf drives) and was my first homelab server. The new box will have a Tesla p4 and RX 580 GTX, i7-8700T and 64GB RAM in addition to the drives from the old server. I'll be converting the Ubuntu drive from the old server into an image and will use it to create a Proxmox VM on the new server, with the same drives passed through. Bottom:
- 2 Cyberpower CP1000 UPS with upgraded LiFePO4 batteries. The one on the left is only for servers and only exists to give the servers time to shut down cleanly when the power goes out. The one on the right is only for network devices (firewall, switch and the Ruckus R500 out of shot mounted higher in the closet)
The joke is also that the burning car was a Tesla, and if Elon could, he'd push a patch to copy/paste his face onto any memories of firefighters found in a Neuralink customer's brain
I will definitely add you to the list. And yeah, an older family member living far away who fell is the reason we started this project. We wanted to be able keep an eye on her (and allow other family members to do the same), but there wasn't anything available that met our requirements, either price or privacy-wise, so we built something and preconfigured it, including a Lubuntu VM with a Mesh Central agent installed that we could use for remote access and troubleshooting for the entire system. This has been super useful, and is the basis of our support model.
If a support package is purchased, we'll ship the device with a support VM installed that is shut down at all times EXCEPT when a specific (included) USB key is inserted into a specific USB port (the only USB-C port, located on the front of the device). This starts the support VM, at which point we would be able to remote in to check the system and fix any issues. The VM shuts down again when the USB key is removed, or after a set period of time, like an hour. This will allow us to ship the device and/or cameras to an older or non-tech savvy person and WE can provide them with support so YOU don't have to.
Will do! And thanks, that means a lot!
Done! Thanks for the interest!
Good question! starlight/night color cameras generally just have larger CMOS sensors to capture more light, OR they integrate an LED "spotlight" into the camera housing to increase the amount of light available to the sensor, and if that's not enough, the IR will kick in. Sometimes the sensor IS actually larger, and sometimes it isn't.
We've standardized on Amcrest cameras, and while we haven't actually tested it, Amcrest does have a "night color" outdoor turret camera that appears to support both ONVIF and RTSP, for the same price as the "regular" turret camera. The model number is IP5M-T1277EW-AI.
If it's like other similar Amcrest cameras, you can likely disable the AI stuff via the built-in configuration, especially if you have Frigate doing that for you.
Personally, I prefer a solution that uses a regular IP camera and a separate smart light (or regular light on a smart plug) that kicks on when motion or a tagged object is detected, which will then cause the camera to switch from black and white IR to color, usually in about a second. The separate light will give you a much better image than anything you'll get from a built-in LED or slightly larger sensor, in my opinion.
Home Assistant and Frigate make it easy to set up this kind of automation, and the "regular" Amcrest cameras have pretty good IR, so Frigate has no problem running detection on those feeds. The automation is basically "if a cat is detected on the garage camera, turn on the garage lights for x minutes".
Hope that helps!
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.
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.
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.