Estimated reading time: 25 minutes
At the time of recording the video and writing the blog post, it was not clear that Supervised would no longer be supported. You should switch to one of the other two variants. Either your own device with OS or as a Docker container like myself.
It is recommended to switch from Supervised to Docker. You can find everything else here: https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/#:~:text=The%20Core%20and%20Supervised%20installation,more%20resources%20to%20run%20them
Migration guide: https://www.diyenjoying.com/2025/06/15/migrating-from-home-assistant-supervisor-to-docker-a-step-by-step-guide/
If you are entering the world of Home Assistant or want to optimize your existing smart home setup, sooner or later you will be faced with a central question: Which Home Assistant installation is right for me?
There are three main variants: Home Assistant OS, Home Assistant Supervised and Home Assistant Container (Docker). Each has its own advantages and disadvantages - and is suitable for different target groups.
In this article I will show you in detail:
- Which one you should choose - depending on your experience level, hardware and use case
- What makes each variant special
- What differences there are in operation
For detailed instructions and an explanation of all configuration options, I recommend the YouTube video linked below. In this video, every single setting is explained in detail so that you receive comprehensive instructions for the exact setup. You can find any code from the video in this article so that you can use it directly without having to type it in.
What is Home Assistant?
Home Assistant is an open source platform for home automation that aims to connect and centrally control all devices in the home. It is designed to provide a unified user interface and simple, flexible control for a variety of smart home devices from different ecosystems. Here are some points in favor of Home Assistant:
- CompatibilityHome Assistant supports thousands of devices and services from various manufacturers, including lighting, air conditioning, heating, cameras, weather sensors, voice assistants and more.
- Local controlUnlike many commercial smart home platforms that rely on cloud services, Home Assistant runs locally on your network. This means increased privacy and reliability, as your smart home devices work even without an active internet connection.
- Automation and scenesOne of the main features of Home Assistant is the ability to create complex automations and scenarios. For example, you can have lights switch on automatically when it gets dark or turn on the heating when the temperature falls below a certain level.
- Simple user interfaceHome Assistant offers a user-friendly interface that makes it easy to monitor and control devices. This interface is fully customizable.
- Integration with voice assistantsHome Assistant can be integrated with voice assistants such as Amazon Alexa or Google Assistant to enable voice-controlled control of your smart home devices.
- Open source and community-drivenSince Home Assistant is open source, it is supported by an active community that is constantly developing new integrations and improving existing ones.
- Data protection and securityAs a locally running platform, Home Assistant has the advantage that the data remains within its own network. This protects privacy and increases security compared to cloud-based solutions.
In summary, Home Assistant is a powerful and flexible solution for those who want to design their own smart home and control their devices centrally, regardless of the manufacturer or ecosystem.
⚙️ The three variants at a glance
🧩 Home Assistant OS - The complete solution
Description:
Home Assistant OS is a complete, self-contained solution. It comes with its own minimalist operating system that only runs Home Assistant and the Supervisor.
Typical hardware:
- Raspberry Pi (recommended: Pi 4 with SSD)
- Intel NUC
- Virtualizations such as Proxmox or VMware
- Odroid, ASUS Tinkerboard, etc.
Advantages:
✅ No Linux knowledge required
Add-ons such as Node-RED, MQTT or Samba backup can be installed directly in the UI
✅ Automatic updates (also for add-ons)
✅ Very low maintenance
✅ Good documentation & community support
Disadvantages:
❌ No other services possible (e.g. web server on the side)
❌ Limited customizability at operating system level
Can be problematic on exotic hardware
Particularly suitable for:
- Installations on dedicated hardware
- Beginner
- Users who simply want a stable, functioning smart home
🧑🔧 Home Assistant Supervised - The hybrid solution
Supervised is a kind of interim solution. You install Home Assistant next to your own Debian system, but retain the convenient administration via the supervisor and the add-on store.
Technical structure:
- Host system: Debian (strongly recommended)
- Supervisor manages containers for HA Core, add-ons etc.
Advantages:
Supervisor + add-on system available
✅ Parallel operation of other services on the same system possible (e.g. Docker container)
✅ More control over the base system
Disadvantages:
❌ Only officially supported on Debian
Requires Linux knowledge
❌ Updates can fail if too many changes are made to the system
❌ More maintenance effort than HA OS
Particularly suitable for:
- Users who want to run other services on the same machine (e.g. Nextcloud, Plex)
- Advanced users
- DIY servers, Intel NUCs, Mini PCs
🐳 Home Assistant Container (Docker) - The developer's choice
Description:
Here you install Home Assistant Core directly in a Docker container - without a supervisor and without add-ons. Everything runs smoothly, but you have to take care of updates, backups and services yourself.
Technical structure:
- Only the HA core container
- Add-ons (e.g. MQTT, Node-RED) must be managed as separate containers
- No supervisor, no web add-on management
Advantages:
✅ Very flexible and lightweight
✅ Fits perfectly into existing Docker environments
✅ Maximum control over components and updates
Runs on almost any hardware (Synology, NAS, server, cloud)
Disadvantages:
❌ No add-on store
❌ No supervisor → No simple UI management
❌ Higher manual effort
❌ Not suitable for beginners
Particularly suitable for:
- Professionals with Docker experience
- Developer
- Self-hosted NAS/server systems with Docker Compose
- Anyone who already operates many services in containerized
📄 Example: docker-compose.yml for Home Assistant Container
If you opt for the Docker variant, you will need a docker-compose.yml File. Here is a simple starting point:
services:
homeassistant:
container_name: homeassistant
image: ghcr.io/home-assistant/home-assistant:stable
volumes:
- /path/to/your/config:/config
- /etc/localtime:/etc/localtime:ro
environment:
- TZ=Europe/Berlin
restart: unless-stopped
network_mode: host🔧 Notes:
- Replace
/path/to/your/configwith the path to your configuration folder. network_mode: hostis important so that Home Assistant recognizes UPnP or mDNS, for example.- You must create your own containers for add-ons such as MQTT or Node-RED.
📦 Example: Mosquitto MQTT as an additional service
mosquitto:
image: eclipse-mosquitto
container_name: mosquitto
ports:
- "1883:1883"
- "9001:9001"
volumes:
- ./mosquitto/config:/mosquitto/config
- ./mosquitto/data:/mosquitto/data
- ./mosquitto/log:/mosquitto/log
restart: unless-stoppedThis allows you to use MQTT conveniently without a supervisor. You store the configuration files in the ./mosquitto/config-folder (e.g. mosquitto.conf).
🧪 Comparison: What differences are really important?
| Criterion | Home Assistant OS | Supervised | Docker/Container |
|---|---|---|---|
| Installation | Simple | Medium (Debian required) | Advanced (Docker) |
| Supervisor | ✅ Yes | ✅ Yes | ❌ No |
| Add-ons | ✅ Yes | ✅ Yes | Manually via Docker |
| Updates | Automatic | Partially automatic | Manual |
| Flexibility | Low | High | Very high |
| Maintenance effort | Low | Medium | High |
| System customization possible | ❌ No | ✅ Yes | ✅ Yes |
| Parallel services possible | ❌ No | ✅ Yes | ✅ Yes |
📦 Exemplary application scenarios
- Beginners with Raspberry Pi: Use Home Assistant OS - Simple, stable, everything inside.
- Power user with NUC and Linux experience: Supervised gives you control and comfort.
- DevOps with Docker on the NAS: Use Home Assistant Containerintegrate everything with Docker Compose.
💡 Tips for making a decision
- No idea about Linux or Docker? → Home Assistant OS
- Do you also want a web server or other services on the side? → Supervised
- Do you have experience with Docker and want to manage your system yourself? → Container
🛠️ Common errors & troubleshooting tips
Even if Home Assistant runs very stably - minor stumbling blocks can occur, especially at the beginning or during updates. Here are the most common problems and how you can solve them:
❌ Error: Supervisor missing during Docker installation
Problem: After installation, the add-on store and supervisor area are missing.
Solution: This is not a mistake - the Docker variant does not include a supervisor. You have to set up add-ons such as MQTT or Node-RED yourself via Docker Compose.
🔄 Error: No access to Home Assistant after reboot
Problem: You can no longer reach Home Assistant after a restart.
Solution:
- Check whether the container (or your Raspberry Pi) is booted correctly.
- With Home Assistant OSConnect monitor - does it show boot errors?
- With Docker:
docker psto check running containers. - Check network mode:
hostis required for HA to recognize devices in the LAN.
⛔ Error: Add-on no longer starts
Problem: An add-on such as Mosquitto or File Editor suddenly won't start.
Solution:
- Log files in the Supervisor or directly in the
config-View folder - Check the storage space on the device (
df -h) - Remove add-on and reinstall (note: make a backup beforehand if necessary)
📡 Problem: Zigbee devices no longer respond
Causes:
- USB stick was not mounted correctly during reboot
- Insufficient power supply (especially with Raspberry Pi)
- Conflicts due to new firmware or radio interference
Solution:
- Test USB stick in another socket
udev-Create rule for fixed assignment of the port- If necessary, move the Zigbee stick with USB extension away from the Pi
💻 Recommended hardware for Home Assistant
Whether beginner or professional - here is an overview of proven hardware for different variants:
| Device / System | Variant | Recommendation |
|---|---|---|
| 💡 Raspberry Pi 4 (with SSD) | Home Assistant OS | ✔️ Inexpensive & popular for beginners |
| 💼 Intel NUC / Mini-PC | Supervised, OS | ✔️ Powerful, future-proof |
| 📦 NAS (e.g. Synology) | Docker / Container | ✔️ Ideal for Docker environments |
| 🧑💻 Proxmox VM / VMware ESXi | Home Assistant OS / Docker | ✔️ Flexible for virtualization |
| 🖥️ Self-build server (Debian) | Supervised | ✔️ Maximum control & expandability |
| 📱 Odroid N2+, Tinkerboard | Home Assistant OS | ✔️ Faster alternative to the Raspberry Pi |
💡 Tip: Make sure the Raspberry Pi has a good power supply (at least 3A power supply unit) and, if possible, use an SSD instead of microSD - this massively increases stability and longevity.
YouTube video implementation
🏁 Conclusion: Which variant suits you?
| Variant | Target group | Special feature |
|---|---|---|
| Home Assistant OS | Beginner | All-round carefree package |
| HA Supervised | Advanced | Comfort + control |
| HA Docker | Professionals / Developers | Max. Flexibility, no comfort |
If you value ease of use and support, go for Home Assistant OS. Do you want more control with a little more maintenance? Then Supervised is perfect. And if you're already running your system via Docker anyway, the container version is your thing.
0 Comments