https://www.reddit.com/r/homeassistant/comments/18c5dxc/any_......I got the OG yellow/amber when it was kickstarted, and have added a 1tb NVME and a z-wave dongle (it came with zigbee).
The newer ones (green) have "ditched" internal networking other than wifi for compliance / regulatory reasons (eg: 1 hardware radio == complex, 2-3 hardware radios == exponentially more complex and requires differing international certifications).
https://www.home-assistant.io/green/
https://www.home-assistant.io/connectzbt1/
https://www.home-assistant.io/docs/z-wave/controllers/
https://www.home-assistant.io/common-tasks/os/#home-assistan...
...as that reddit thread alludes to: you're fairly better off chasing an old NUC-type-thing and just plugging in the extra dongles to that anyway (potentially zip-tying a hub, or maybe getting some 90º USB connectors so you're less worried about snapping things off if it gets bumped, dropped, or stepped on).
The software is pretty darned solid, I've dug into it a fair amount and haven't had much issues with it in the ~3-4 years I've had it.
As the CLI link describes, there's 2-3 layers of "reliability" going on: core => supervisor => host. Basically the supervisor will restart / rotate / backup the HA-core (aka: docker image), and you can occasionally update the "Host" (aka: OS). https://www.home-assistant.io/installation/linux/#install-ho... ...their HomeAssistantOS basically wraps all that up, and if you install it "that way", you effectively turn whatever hardware you're using into an "appliance"... really, just depends on what layer you want to handle your O.S. updates (ie: throw HA on as "just another service" on your homelab? ...or "let the little box manage itself").
The reason I added Z-Wave (eventually) was to get access to an exterior-rated, dimmable plug/extension cord (dimmable string lights) ... HomeKit ones were finicky, and I couldn't find any good ZigBee ones. The reason I added an NVMe inside (eventually) was I wanted to chase using it as kindof a plex-ish / backup / media server, but there's "gross" issues with HA's backup strategy by default (ie: it backs up the "whole HD", including `/Media/...`, which makes backup times exponential compared to "just the *.config.yaml", and effectively halves your usable disk space).
Since you'll have to buy some of those dongles anyway, start with that and do the "home assistant OS running on a rpi" route. Get a feel for it, and then jump in to a NUC which you can air-drop next to your family's cable modem.
I've got 80-90% of everything bridged over to Siri/HomeKit (all devices are treated "as good as apple home app", and only a few HA-specific "super-nerd stuff" that I've set up in the HA gui itself (ie: timed scripts for turning things on/off when we have a party in the back yard). You still have to pop in to HA when adding a new device, new device-type, or to update any of the three layers (integrations => home assistant => kernel/os/core), so like once every few months like any potentially vulnerable IoT device.
Overall, a solid 7-out-of-10 (because it's OSS) ... as OSS it's 9-out-of-10... just desperately needs some cohesion, GUI-love, simplification, etc, but the compatibility and power is all there!