It is both.
Home Assistant created an OS for appliance like installations.
But there is also the docker images, repo packages (I know Arch Linux has it in the repo) and pip based packages too.
docker images
Is not distro packages.
Arch Linux
It’s not in Debian. There’s no Red Hat packages either. Or OpenSUSE. It’s not even in OpenWrt which would make the most sense. So it looks like no useful, practical distro packages.
pip
Is not distro packages.
You didn’t mention in your OP that it had to be debian distro packages. I just gave examples of HA being packaged in other ways than a complete OS.
I could have said: “If you want to run HA from packages, you need to install Arch!” But I didn’t. Chill out.
You didn’t mention in your OP that it had to be debian distro packages.
It doesn’t. WTF are you talking about?
It can also be installed using docker containers but that is more difficult to manage as you have to install every component manually.
That’s not how docker works, bud.
I guess that my message wasn’t clear but by “component” I meant a home automation component.
I have the following containers in my HA installation:
- Home assistant
- Node red
- MQTT
- Zigbee2mqtt
- Esphome
And maybe others that I have forgotten.
Each had to be installed manually by adding it to my docker compose file, mapping drives, and editing config files.
Most, if not all, of them (except HA) can be installed from within HA if you’re using HAOS.
Ah, that makes a lot more sense.
