Home Assistant Add-ons in 2026: The 12 Most Useful

Home Assistant's, the smart home automation platform's, extension ecosystem has three distinct layers, and beginners conflate them constantly. Knowing which is which prevents 80% of 'why doesn't this work' questions.

The official store does not publish public install counts, so no list is a true ranking. This shortlist reflects the add-ons that consistently top community recommendations and appear in the official Home Assistant documentation's featured set through 2026. Two names that climbed the charts this year are Google Drive Backup, now the default offsite safety net for self-hosters, and the Cloudflare Tunnel add-on, which gives remote access without forwarding a single port. The eight covered in depth below are the install-first subset; the table adds the four that most setups reach for next.

File Editor is the simplest possible YAML editor that runs as an add-on, accessible from Home Assistant's sidebar after install. It opens your config directory directly - configuration.yaml, automations.yaml, scripts.yaml, the lot - with syntax highlighting and a save button. You can edit and save without ever opening a terminal or SSH session.

For most beginners, this is the single most useful add-on. The bulk of Home Assistant configuration in 2026 happens through the UI, but edge-case integrations and custom YAML snippets still require direct config file edits. File Editor turns that from a multi-step SSH operation into a sidebar click.

The official Terminal & SSH add-on gives you a web-based shell that opens directly into the Home Assistant Operating System's container environment. You don't need to set up SSH keys, port forwarding, or anything else - it just opens a terminal in the browser.

You'll need this less often than File Editor, but when you need it you really need it. Examples: clearing stuck log files, manually pulling a custom integration update, running a one-off backup, or restoring from snapshot when the UI is unreachable.

Samba Share exposes the Home Assistant config directory as a network share that mounts on Mac, Windows, and Linux clients. The practical implication: you can edit YAML in your usual desktop editor (VS Code, Sublime, whatever), drop in custom themes and dashboards via drag-and-drop, and access backup snapshots without going through the Home Assistant UI download flow.

It's not strictly necessary if you're happy editing in File Editor or Studio Code Server, but most experienced users end up using Samba for one specific job: pulling backup snapshots to a desktop or NAS as part of a 3-2-1 backup strategy.

MQTT (Message Queue Telemetry Transport) is the lightweight messaging protocol that a lot of smart-home devices use to talk to each other. Home Assistant doesn't bundle an MQTT broker by default - it expects you to provide one. Mosquitto is the official Home Assistant MQTT broker add-on; install it and you can integrate any MQTT-compatible device or service.

You might not need Mosquitto on day one. But the moment you want to add ESPHome devices, Zigbee2MQTT (instead of the built-in ZHA Zigbee integration), Theengs Gateway for Bluetooth sensors, or any custom Wi-Fi sensors with MQTT firmware, you'll need a broker. Installing Mosquitto early is just less friction later.

ESPHome is the single most transformative add-on on this list for anyone interested in cheap DIY sensors. It runs as a web service inside Home Assistant that lets you build firmware images for ESP32 and ESP8266 microcontrollers - environmental sensors, motion detectors, smart switches, energy monitors - by writing YAML configuration rather than C++ code.

The workflow: connect a $4 ESP32 board via USB or use a pre-flashed device's ESPHome-compatible firmware, define what sensors and outputs it should expose in a short YAML file, click Install, ESPHome compiles and uploads the firmware. The device appears in Home Assistant within minutes with proper entity types, automations, and dashboards.

Home Assistant's built-in Automations editor handles simple if-then-else logic well. Once your automations involve multiple triggers, time-of-day conditions, occupancy detection, weather-aware logic, and queued state machines, the built-in editor starts to feel restrictive. Node-RED is a visual flow-based programming environment that integrates with Home Assistant via the official add-on, offering a much richer automation toolkit.

Whether you actually need Node-RED depends on your appetite for complex automations. Most casual users are happy with the built-in editor for the first six months; serious smart-home builders end up in Node-RED for at least their complex flows. Install when you hit your first 'this is too clunky' moment in the built-in editor, not before - Node-RED has its own learning curve and adds a layer of complexity to your automation debugging.

AdGuard Home runs a DNS-level ad blocker that intercepts ad and tracker domains for every device on your network - phones, smart TVs, IoT devices, computers. It's the same idea as [Pi-hole](/blog/what-is-pi-hole-smart-home/) (which we've covered separately), but available as a one-click Home Assistant add-on and arguably better-maintained at the moment.

The setup is two steps: install the AdGuard Home add-on and configure your router to point all DNS queries to your Home Assistant box. From then on, every ad and tracker hostname is blocked at the network level - visible on every device including those you can't install an ad blocker on (smart TVs, set-top boxes, kids' tablets, friends' phones).

Frigate is the most demanding add-on on this list - it does real-time AI object detection on camera feeds and stores recordings locally without sending anything to a cloud service. Think 'doorbell-camera AI' but on your own hardware: tell Frigate to notify you when a person walks up the driveway, a package is delivered, or a vehicle appears, without paying Ring or Nest a monthly subscription.

The catch is hardware. Frigate needs a Coral USB AI accelerator (~£60) for reliable real-time detection on more than 1–2 camera streams. A Raspberry Pi 4 alone struggles past two streams; Pi 5 handles more but is still constrained. Install Frigate later in your Home Assistant journey, once you have cameras and the Coral hardware to run them properly.

Add-ons run as containers with whatever access they request, so they are not all equally safe. The store shows each one a security rating from 1 to 6: 6 is very secure, while a low rating means the add-on asks for host networking, a privileged container, or runs without an AppArmor profile (the Linux kernel module that confines what a process can touch). Official add-ons are maintained by the Home Assistant team; anything you add through a custom repository URL is third-party code with full container access, so install only what you can trace to a reputable project.

The biggest practical risk is exposure. Prefer add-ons that use ingress - where Home Assistant authenticates and proxies the add-on's interface so nothing is open on your LAN - over ones that map a port onto your network. This is not hypothetical: in March 2026, CVE-2026-34205 (CVSS 9.7) let add-ons running in host-network mode expose unauthenticated endpoints to the local network, and it was patched in Supervisor 2026.03.2. That is exactly why keeping the Supervisor updated matters. For remote access, never port-forward port 8123 - use Home Assistant Cloud (Nabu Casa) or a Cloudflare Tunnel add-on instead.

Sources: Home Assistant official documentation (current at 17 June 2026); Home Assistant Add-on Store official repositories; ESPHome project documentation; Mosquitto MQTT broker documentation; Node-RED Home Assistant nodes documentation; Frigate documentation; AdGuard Home Home Assistant integration documentation; Home Assistant 2026.2 release notes (add-ons renamed to Apps, February 2026); Home Assistant security documentation and add-on security ratings; CVE-2026-34205 Supervisor host-network advisory (fixed in 2026.03.2). This is an editorial DIY guide based on the official Home Assistant ecosystem. Add-ons, repositories, and integration details can change with each Home Assistant release - always check the current Home Assistant documentation before installing.