OK…You mean it is better to use a container?
I tried at first the Container-Installation; it worked fine. But I couldn’t get any connections between e.g. HA and NodeRed …
some months ago I installed docker (container) and inside the docker Home Assistant (but without Supervisor)…
And now I use HA-Image:
Home Assistant Operating System : Minimal Operating System optimized to power Home Assistant. Comes with Supervisor to manage Home Assistant Core and add-ons pre-installed. Recommended installation type.
(https://www.home-assistant.io/installation/raspberrypi)
What is the best version to stay flexible. I want to be able to access to all features on my Raspberry Pi 4 either over commandline or via GUI.
Thanks a lot!
Those are your official choices. Rasperry Pi OS, although based on Debian is not among the list of supported OS for Home Assistant Supervised, so it’s not supported on Raspberry Pi.
You could use Home Assistant Container with Portainer or Docker Compose to orchestrate, but you will loose the Add-On-Store.
Geht. Docker containers are like virtual machines, but for processes. Command line is executed at container level, not at host level. Even if you could manage to bring nmcli into the container, you would still lacking access to the host’s WiFi hardware. And that’s for a reason, for example /sys/class/thermal/thermal_zone0 exists on my RPi4, but not on my amd64 host.
If you want to communicate with the host, you need network services or file-system bases “semaphores”. That is:
You bind a host directory to a location into the container
You create something in HA, that puts a “marker” into that container directory (touch /my/special/dir/myfile)
You make something (like Cron) on the host monitor that directory and react on changes.