I go the container route, and have only had one issue: allowing HA to access my system's Bluetooth adapter. I had some ESP32s lying around, so I used ESPHome to make a Bluetooth proxy, which solved that issue.

I don't run addons though, which might be part of it.

Interesting. I also run HA in a container and getting it to pick up my Zigbee dongle was so easy I don't even remember how I did it.

I haven't tried BT, but my HA box lives underneath a couch with a big steel pull-out bed so I don't imagine it would work very well anyway.

The host I run HA on is Ubuntu server. If memory serves me right, the Bluetooth issue was related to apparmor and dbus restrictions on docker

I haven't done it either. But it should just be a case of passing the device to the container. You might need to disable the host from using it and pass admin rights to the container too.

But it was also quite easy to pass a USB device to the HAOS VM in Proxmox.

Add-ons (now apps) can't be done without HAOS. It's one of those non-obvious things.

There's other things I forget which are also more difficult/annoying to manage on the container version.

I have a rather large docker compose stack so my first experiments with HA were as running it there.

That lasted maybe a week before I went and ran it as a VM instead.

Yeah, I ended up buying a dedicated mini PC ($100 refurb) to install HAOS on. HA is pretty much useless without being able to run add-ons. I run everything on k8s in my home server, I don't have a VM system set up and didn't want to bother just for HA. It's funny, the pattern of a central application that uses docker containers to add plugins seems like a perfect fit for a Kubernetes Operator. I suppose it still misses out on some of the advantages of running everything "on metal" for integrating with physical components like USB dongles.

It's kind of silly since they're just containers it runs anyways. I'm sure there's other reasons. At least running it as a VM isn't too hard. Pretty easy to use their image and run from that.

Apps/add-ons is just another container, so you can add them manually in the compose file.

Yep, I run esphome in a separate stack w/o issues.

> I go the container route, and have only had one issue: allowing HA to access my system's Bluetooth adapter

Even without running in a container, I had huge problems with Bluetooth on Linux (it would just ... stop then not reappear or it would only talk to half the devices but a different set of devices every other day, etc.)

(This isn't specifically a HASS problem, mind; I've had countless problems with Linux Bluetooth since 2003 over many different iterations of hardware, OS and dongle.)

> I used ESPHome to make a Bluetooth proxy, which solved that issue.

Same. It's a great solution.

> The fun part is in the building, it's in the understanding, the growth of me.

I agree with this sentiment as well. Without a doubt, my favorite part of the job is coming up with a solution that just 'feels right', especially when said solution is much cleaner than brute force/naive approach. It sounds cheesy, but it truly is one of my favorite sensations.

I'm the senior-most engineer on my team of about 15. I try to emphasize software craftsmanship, which resonates with some but not all. We have a few engineers who have seemingly become reliant on AI tooling, and I struggle with them. Some of them are trying to push code that they clearly don't understand and aren't reviewing, and I think they're setting themselves up for failure due to lack of growth.

I decided to cut an hour out of my in-the-office time recently, figuring that I'm sitting on the bus for any hour anyway, so I might as well use that time to knock some work out instead. Tethering is pretty good other than a predictable problem spot or two.

Much better experience than working on a plane. I've done a handful of cross-US flights this year on Alaska Airlines, and trying to do anything network-related on those flights was torture. Super spotty, high latencies, constant timeouts; very frustrating.

+1. I switched from Pop OS to Debian + KDE last week, and KDE has been solid. I too read a handful of articles calling out the choice fatigue, and other than a few tweaks (maybe half an hour?) I was ready to go. I run old-ish hardware (circa 2013) without any issues.

Something notable is that the all the hotkeys felt 'just right'. I had to tinker a bunch in Pop OS to get satisfying hotkey combos, and the COSMIC upgrade reset them all.

Yeah, I know this feeling very well.

I usually attribute it to people being lazy, not caring, or not using their brain.

It's quite frustrating when something is *so obviously* wrong, to the point that anyone with a modicum of experience should be able to realize that what was implemented is totally whack. Please, spend at least a few minutes reviewing your work so that I don't have to waste my time on nonsense.

My mom was paying a few hundred a year to Wix for a basic single page, static site. I finally decided that it was a waste of money and went down the Hugo-on-cloudflare route a few months ago. Can't beat it - all she's paying for now is the domain.

The only issue I had encountered was moving the domain from wix. If memory serves me right, I had to point the NS records to CF to do the transfer, and Wix doesn't allow control over them. I ended up transferring over to Porkbun instead, but using CF for DNS.

Hugo took some getting used to. Most of the templates I had seen were for blogs, but "hugo-scroll" works like a charm for the basic single page site.

Native WebDAV mount support in Android would be handy. I use davx5 (https://github.com/bitfireAT/davx5-ose), but accessing files is a bit clunky.

I like WebDAV because it 'just works' with the mTLS infra I had already setup on my homelab for access from the outside world.

I use sftpgo (https://sftpgo.com/) on the server side.

Another +1 for miniflux.

Something atypical about my setup is that I wired up miniflux webhooks to n8n and gotify so that when I click "save" on an entry, I get a notification for it. It's a rudimentary way to setup a "read it later" list.

I self-host n8n along with about two dozen other services for personal use.

I make extensive use of the webhook triggers. Being able to spin up an endpoint with minimal effort is quite handy.

The data table feature looks useful. Similar to another poster, I've been using json blobs on disk instead, since I don't have concurrency, scaling, or performance concerns for my use cases.

I get some very weird vibes from the n8n subreddit. There's a bunch of 'get rich quick with AI workflows' posts which feel icky.

Same setup, minus the Pi. That includes originally starting out with jellyfin!

When on Jellyfin, I used to manually transcode the entire library to ogg and use syncthing to replicate it to my devices. Symfonium's ability to cache transcoded files is quite handy (although the initial backfill of ~20K songs took a few tries)