Interesting. I do not know a lot about Home Assistant devices, but I thought they would just be communicating via standard WIFI + data encryption. I definitely didn’t suspect there to be a whole new standard of wireless communication to that.
I understand the thing about downtime, running pihole myself. My setup is rather simple and centralized on purpose and I don’t really mind the few minutes of “filtered DNS” downtime while pihole and pve are rebooting. As my UniFi Dream Router 7 is the firewall / gateway / DHCP server anyway, I just use pihole as primary DNS and 1.1.1.1 as secondary DNS. It’s not filtering “bad domains” via DNS, sure, but I got adblock origin and other browser extensions dealing with whatever comes along anyway.
But, yeah, for redundancy and always-online-production-setups it’s actually great having a secondary pve as a temporary stop-gap. Plus, it’s a nice and kinda fancy setup, of course. Always appreciated in selfhosted :)
IsoKiero@sopuli.xyz
hamsda@feddit.org
doctorflynt@feddit.org 2 days ago
while the machines are physicaly next to esch other i also runy whole home automation over zwave. the reason i have 2 machines currently is that the media server used to run truenas and i virtualized everything there. since truenas is no longer true open source i wanted to replace it with open media vault, but i dont really used shares i figured that proxmox would be better suited. so i set up a machine where i host all the services until i figure out how i want to run my media-server.
i still need to find a way to setup a simple sambashare via a web gui and a good backup solution.
I’m running openmediavault as an VM for file shares and backups with proxmox backup server. Works pretty well. I’ve got a physical backup server in detached garage and another in a VPS which syncs the most important parts to remote location.