Home Assistant Add-ons Explained: What They Are & Which to Install
Home Assistant add-ons are self-contained applications—packaged as Docker containers—that run alongside Home Assistant on the same machine and are installed, started, and updated from inside the Home Assistant interface. They extend what your server can do beyond home automation itself: hosting a database, a file editor, an MQTT broker, a backup uploader, or an ad-blocker. The key thing to understand up front is that add-ons are only available on certain installation types, and they are not the same as integrations. Most people should install just two or three to start, then add more only when a specific need appears.
Add-ons vs. integrations: the distinction that trips people up
This is the single most common point of confusion, so it's worth being precise. An integration connects Home Assistant to a device or service—your smart bulbs, a weather API, your robot vacuum—and surfaces them as entities you can control and automate. An add-on is a whole separate program running on the same hardware. Integrations live inside Home Assistant; add-ons sit next to it.
The two often work together. For example, the Mosquitto MQTT add-on runs a message broker on your server, and the MQTT integration is what lets Home Assistant talk to that broker. You frequently install an add-on to provide a service, then enable an integration to use it. If you're still deciding which device connections to set up at all, our guide to the best Home Assistant integrations to start with is the better starting point for that side of the equation.
| Aspect | Add-on | Integration |
|---|---|---|
| What it is | A separate app (Docker container) | Code inside Home Assistant |
| Purpose | Provides a service or tool | Connects devices and services as entities |
| Where you find it | Settings → Add-ons | Settings → Devices & Services |
| Availability | HA OS & Supervised only | All install types |
| Example | Mosquitto broker, File editor | Philips Hue, Google Cast |
Do you even have access to add-ons?
Add-ons depend on the Supervisor, the management layer that handles Docker containers for you. That means add-ons are only available on two installation methods:
- Home Assistant OS — the recommended full appliance image, common on a Raspberry Pi or a dedicated mini PC.
- Home Assistant Supervised — a more advanced setup on your own Debian system.
If you installed Home Assistant Container (a plain Docker container) or Home Assistant Core (a Python virtual environment), you won't see an Add-ons menu at all—you'd run the equivalent tools as your own separate containers or services instead. If you're not sure which you have, or you're still choosing, see our walkthroughs on how to install Home Assistant and the dedicated Raspberry Pi setup guide. Home Assistant OS is the path that keeps add-ons simplest.
How installing an add-on actually works
The flow is deliberately simple, because the Supervisor does the container work behind the scenes. From the Home Assistant interface you browse the add-on store, pick an add-on, install it, optionally adjust its configuration, then start it.
- 1Open Settings then Add-ons and choose the store
- 2Pick an add-on and select Install, then wait for the download
- 3Open the Configuration tab to set any required options
- 4Start the add-on and enable “Start on boot” plus “Watchdog” if offered
The official store ships with first-party add-ons, and you can add third-party repositories by URL to expand the catalog—the popular community add-ons collection is the usual next step. Treat third-party repositories the way you'd treat any software source: stick to well-known, actively maintained ones, since an add-on runs with real access to your server.
Which add-ons are worth installing first
You don't need many. Resist the urge to install a dozen at once—each one consumes memory and CPU, and an idle add-on is just overhead. Here are the categories that earn their place for most people, roughly in order of how commonly they're useful.
- A configuration editor — File editor for quick YAML edits in the browser, or Studio Code Server if you want full VS Code with autocompletion and validation. One of these is the most universally recommended first add-on, especially once you start hand-writing automations or tidying a dashboard.
- Mosquitto broker — a local MQTT broker. You'll want this the moment you run Zigbee2MQTT, ESPHome devices that use MQTT, or any sensor that publishes over MQTT. It keeps that traffic on your own network rather than a cloud service.
- Zigbee2MQTT — if you've chosen the Zigbee2MQTT route for your Zigbee radio. Whether that's the right route versus the built-in ZHA integration is its own decision, covered in our ZHA vs. Zigbee2MQTT comparison.
- A database engine — Home Assistant records history in SQLite by default, which is fine for most homes. Heavy users sometimes add the MariaDB add-on for a more robust database, or InfluxDB plus Grafana for long-term graphing.
- Backup helpers — add-ons that push your snapshots to Google Drive, a network share, or another off-box location. Crucial, because a backup that only lives on the same SD card it's protecting isn't really a backup.
- Network tools — AdGuard Home or Pi-hole for network-wide ad and tracker blocking, or Z-Wave JS UI if you run Z-Wave gear.
- Lightweight, fast, minimal RAM
- Best for small, occasional YAML tweaks
- Full VS Code with autocomplete and error checking
- Better once your config grows complex
Add-ons and the cloud question
One reason add-ons are appealing is that many of them let you keep services local. Running your own MQTT broker, ad-blocker, or database means that data never leaves your house. That fits the broader philosophy of moving your smart home off the cloud. The trade-off is responsibility: a local service is only as reliable and secure as your own maintenance habits, so keep add-ons updated and be deliberate about anything you expose to the internet—see our notes on secure remote access before opening any ports.
Frequently asked questions
Are Home Assistant add-ons free?
The official and community add-ons are free and open-source. Home Assistant itself is free software. The one common paid service is Home Assistant Cloud (Nabu Casa), a subscription that funds development and offers easy remote access and voice-assistant linking—but that's a service, not an add-on you pay per-item for.
Why don't I see an Add-ons menu?
Because you're almost certainly running Home Assistant Container or Home Assistant Core, neither of which includes the Supervisor. Add-ons require Home Assistant OS or Supervised. To get add-on support you'd migrate to one of those install types; your configuration and entities can usually move across with a backup.
Will running lots of add-ons slow my system down?
It can. Each add-on is a running container using memory and some CPU, and database or analytics add-ons in particular can be demanding on a small device like a Raspberry Pi. Install only what you'll use, and if performance dips, stopping or removing unused add-ons is one of the first things to check.
Is an add-on the same as a HACS integration?
No. HACS (the Home Assistant Community Store) distributes custom integrations and dashboard cards—code that runs inside Home Assistant. Add-ons are separate containers managed by the Supervisor. They're different mechanisms, even though both extend what your system can do.
