See https://www.home-assistant.io/installation/alternative/#install-home-assistant-container or https://www.home-assistant.io/installation/raspberrypi-other. There are different container solutions but the guide focuses on docker. Docker must be first installed
Running home assistant in docker works well, however soon other docker container applications as MQTT mosquitto, go2rtc or EspHome are desired to be used as well.
Therefore it is recommended to run HomeAssistant with docker-compose https://www.linurs.org/linux/Docker.html#docker%20compose
It is recommended to run Home Assistant using docker compose to be flexible adding additional containers.
Home Assistant can also get installed without docker compose in a single container.
Before starting the installing it decide for:
Time Zone TZ=<Europe/Zurich>
Path where the home assistant docker configuration goes as /opt/docker/homeassistant.
Then create this directory sudo mkdir -p /opt/docker/homeassistant
Give permission for the local user
sudo chown -R $(id -u):$(id -g) /opt/docker/homeassistant
docker run -d --name homeassistant --privileged --restart=unless-stopped -e TZ=Europe/Zurich -v /opt/docker/homeassistant:/config -v /run/dbus:/run/dbus:ro --network=host ghcr.io/home-assistant/home-assistant:stable
If successful docker starts and since home-assistant docker container is not on the local machine it gets downloaded from docker hub and this takes a while.
--network=host makes that the local machines IP address can be used and not the docker one showed by sudo ifconfig
docker ps -a shows if homeassistant is running.
For automatically startup a systemd file needs to be created: sudo touch /etc/systemd/system/homeassistant.service
[Unit] Description=Home Assistant Container Requires=docker.service After=docker.service [Service] Type=oneshot RemainAfterExit=yes WorkingDirectory=/opt/docker/homeassistant ExecStart=/usr/bin/docker run -d --name homeassistant --privileged --restart=unless-stopped -e TZ=Europe/Zurich -v /opt/docker/homeassistant:/config -v /run/dbus:/run/dbus:ro --network=host ghcr.io/home-assistant/home-assistant:stable ExecStop=/usr/bin/docker stop -t 60 homeassistant ExecStopPost=/usr/bin/docker rm -f homeassistant [Install] WantedBy=multi-user.target
docker ps -a check if docker still runs homeassistant
docker stop homeassistant stop it
docker rm homeassistant remove temporary files
sudo systemctl daemon-reload make the system aware of the new service
sudo systemctl enable homeassistant.service tell it to start it automatically next boot
sudo systemctl start homeassistant.service start it manually
sudo systemctl status homeassistant.service check its status
sudo journalctl -u homeassistant.service -f check its log
to update homeassistant
Stop the service sudo systemctl stop homeassistant.service
get the update docker pull ghcr.io/home-assistant/home-assistant:stable it will also tell if there is an update
docker rm homeassistant remove temporary files
sudo systemctl start homeassistant.service start it again
With Home Assistant 202611 the Marketplace replaced HACS the Home Assistant Community Store. The Marketplace will be found under Settings.
The Marketplace contains not yet released features
WebRTC is used among go2RTC the media stream server that can be run as docker application.
It then pops up among the other official integrations (where not much can be configured).
A WebRTC Camera card can be added to the dashboard to show live video streams with relatively slow delay. Add as url the go2rtc stream name.
Read the instructions from Marketplace that also point to links as https://github.com/nordicopen/easee_hass/wiki
When adding the Easee EV Charger Integration, password and username of the Easee account are requested. After this a list of all Easee stations appears where the ones of interest can be selected
Those configuration steps take some time.
,