Best Home Assistant Add-ons: The Essential Guide

Integrations connect Home Assistant to devices and services (Philips Hue, Google Cast, NWS weather). They run inside the Home Assistant core process and are managed in Settings > Devices & Services. Add-ons are separate applications that run alongside Home Assistant in their own Docker containers (managed by the Supervisor). They provide supporting tools like file editors, MQTT brokers, VPN servers, and backup managers. You can think of integrations as "what HA talks to" and add-ons as "what runs next to HA to help it." Add-ons are only available on HA OS and HA Supervised installations, not HA Container or HA Core.

HACS (Home Assistant Community Store) itself is well-maintained and widely used by the community. However, the individual custom components and Lovelace cards available through HACS are community-contributed and not officially vetted by the Home Assistant team. Most popular repositories (Mushroom cards, HACS integrations with 1,000+ stars) are safe and actively maintained. The risk comes from installing obscure or unmaintained repositories. Best practices: (1) Only install HACS components with active GitHub repositories and recent commits, (2) Read the GitHub issues before installing to check for known problems, (3) Back up before installing any new custom component, (4) If a HACS component breaks after an HA update, disable it and check for an updated version.

It depends on your hardware. Each add-on runs in its own Docker container, consuming RAM and CPU. On a Raspberry Pi 4 (4GB), running more than 8-10 active add-ons simultaneously can cause noticeable slowdowns. On an Intel NUC or dedicated server with 8-16GB RAM, you can comfortably run 15-20+ add-ons. The biggest resource consumers are Frigate NVR (needs a Coral TPU and significant RAM), MariaDB (database engine), and Node-RED (when running complex flows). Lightweight add-ons like File Editor, Samba, and Terminal use minimal resources. Monitor your system in Settings > System > Hardware to check CPU and memory usage.

Yes. Under the hood, every add-on is a Docker container managed by the Home Assistant Supervisor. The Supervisor handles pulling images, configuring networking, managing storage volumes, and restarting containers on failure. You do not need to know Docker to use add-ons. The Supervisor UI handles everything. However, if you run HA Container (Docker Compose install without Supervisor), you do not get the add-on system. Instead, you run the same applications as standalone Docker containers alongside your HA container and configure them manually. This is more flexible but requires Docker knowledge.

For a new installation, start with these five: (1) File Editor — edit configuration files directly in the browser without SSH. (2) Samba Share — access your HA config folder from your computer over the network for easier editing. (3) Google Drive Backup — automated daily backups to the cloud. (4) Mosquitto MQTT Broker — required if you use any MQTT devices (Zigbee2MQTT, Shelly, Tasmota). (5) Terminal & SSH — command-line access for troubleshooting when the UI is not enough. These five cover file management, backups, device communication, and troubleshooting. Add more as your needs grow.