How much hurt you're in is largely going to be a factor of how dependent you are on IP addresses between all your services. Moving services into a VLAN is also going to require new IPs. If you're using DNS names between everything that will help, especially if you're mostly using DHCP. If you've got lots of hand configured IPs between you're services you're going to have to chase all those down.

My recommendation is to start small. Create the new VLAN and put a new host in it, make sure you're confident about how you want to set it up in ProxMox and your router, get some experience.

Then think about which services you're actually going to be benefit from the VLAN switch to move. You'll probably do best at this point to just leave your ProxMox management interface where it is and just move services over that need it.

All said, I run a small stack at home and haven't really found any personal need for VLAN segregation for my services, so definitely start with a reason and a plan. Learning can be a reason.

There are lots of good videos on YouTube which I know is not a helpful answer without some links but remember there is no one correct way to do it.

What I wanted to add was once you've watched some stuff practice on a knife you're not precious about is the best thing to do. Using one of the little plastic wedge blocks to get an ideo of what angle is in your hands is really helpful at first, then eventually you won't need it.

The good thing to remember is you basically cannot ruin the knife. The first couple times you try to sharpen you'll probably end up with a pretty dull knife, don't get discouraged. Just try again, you can always bring the edge back. You'll learn a technique that works for you and eventually you'll get it.

Second this. There are so many used cheap on eBay. You can usually upgrade the RAM and storage if needed. For Jellyfin pay attention to what video chipset is embedded. Also, pay attention to the listing, some don't include a power supply, which can get you good deals, but make sure you know so you can price the PSU in.

I've been using Volumio 3 for a while to drive my office setup. I run it on Pi 3, USB to my DAC and play my FLAC over an SMB share. I mostly control it through the web interface or the Android app. I also use it as a Spotify destination.

It's met my needs well, but I'm not doing much complicated with it. Just play and album or playlist from my library.

I never used Volumio 2 so I can't comment about how it compares. I am interested to try Volumio 4 and hear what other people think.

The challenge you have is that a device that meets your spec is going to have to decode the optical surround sound signal from the TV which means it is going to need a chip and support for the codecs such as Dolby Digital and DTS. That is going to drive up the price and why what you're seeing are AV receivers. Unfortunately you don't need a switch, you need a surround sound DAC and those are not very common.

I am a hobbyist photographer. My files come off the SD card from the camera to a external SSD that I use with Lightroom. That drive and the Lightroom Catalog backups get synced to a local NAS that I'm running at home. The NAS gets regularly backed up to a drive that goes to another location. I have two drives for off-site backup so there is never a time when there isn't one off-site. I'd like to replace the off-site drive with cloud of some type. I was previously bandwidth limited but now that I'm not I need to do it.

I feel like I haven't figured out a good sharing solution yet. I usually just use Google Photos to create and album and share that with people. I used to use OwnCloud but I've moved away from that.

I also recently got a set of those. I've really been enjoying them for at the desk and on the go.

Maybe I was too literal in how I answered the question because I do use VLANs in my home network, but just to segregate my guest wifi which I also use for IoT things that I don't need on my main network.

I don't think of this as "home lab" because all my services run on my primary network VLAN and my secondary VLAN only exists at my router, switch and wifi APs.

I haven't found a need for a "no access" VLAN as if I wanted to keep something from going outbound I would just create a firewall rule. I've also found my PiHole to be very effective at blocking telemetry traffic from things.