HS support for Alex has been a real sticking point. It barely works and when it goes out there's no rhyme/reason or any sort of debugging. It's a must-have here at the house, as per the wife's demand. Yeah, cloud dependency and all that... but Happy Wife, Happy Life.
To my delight HA6.6 has really nice Lutron integration. No importing, it pulled everything in once I added it to the config.
I agree that past versions of HA were much more dependent on text editing of .yaml files. They're not gone, but quite a lot is now handled via the web UI.
I've had HS3 running in a VM for a while, with USB pass-thru for a Z-wave controller. I have HA on the same hypervisor host. With less CPU and memory HA's web UI is still
much faster than HS. Granted I have HS3 running atop Windows, so there's that added overhead. The VM for HS3-Win is setup with 4 CPUs and 16g of RAM. HA6 has two CPUs and 8gb of RAM. These on an Intel i9 host with 64g of RAM and plenty of spare cycles.
I have HA running from their .qcow2 KVM image on an Ubuntu host.
https://www.home-assistant.io/installation/linux
I find docker for the 'main' portion of things is often an added layer of abstraction that prevents getting things tweaked the way I'd prefer. Part of this is my level of comfort for 'bare metal' installs, and a lack of familiarity with adding docker's layer of abstractions.
If I decide to make a go of using HA for 'everything' I'll probably move it onto it's own machine, to avoid any USB/VM abstraction hassles. Whether that's an x86 box or a pi4 remains to be seen. I pi4 with it's own high performance boot SSD (not a microSD card) is a pretty impressive bit of gear. I have two running that way on the boat and they've been remarkably reliable. I suppose it'll come down to how much of what I want is available via x86 vs arm.
A side influencing factor is my 88yo MIL out of state. She's getting on in years and having some early signs of dementia. No official diagnosis yet, but had an MRI just this past Friday. The most common problem for her is missing the time of day. Getting fixated on preparing for an appointment tomorrow, but not recognizing that it's not 'tomorrow' yet. As in, having a 2pm appointment to get her hair done. But waking up at 11pm the night before, getting ready and heading downstairs to the salon and then banging on the door to be let in... at 1:30am. That it's PITCH BLACK outside... yeah, that just gets ignored. It's a great facility and they have ways to transition for memory care, so it's not a complete disaster.
The saving grace here is I gave her Alexa devices years ago, and she's become quite used to asking "Alexa, what time is it?". I'm hoping to find a way to 'catch' those requests and use them to gently remind her that it's in fact the middle of the night, so GO BACK TO SLEEP. The Alexa subsystem alone won't handle this, some combination of routines and maybe some added automation on something like a pi4 running HA may help.
Thus the complete mystery of Homeseer Alexa integration for anything more than on/off lights is driving me to look more closely at Home Assistant. I've gotten a few parts mocked up and hope to poke at it a bit more this week.