The 12 Home Assistant Add-ons Every Serious Install Eventually Runs

Home Assistant ships almost-empty out of the box. The add-on store is where the real power lives, but most of the 200 listed packages are hobby projects with three users. This is the 12 add-ons I run on every fresh install -- official and community combined -- and the order they go in.

I started running Home Assistant in 2019 and have rebuilt the install three times since then -- once for a hardware migration, once after a corrupted SD card, and once when switching from a Raspberry Pi 4 to a Pi 5. Each rebuild teaches you which add-ons are essential versus which were temporary experiments. The list below is the post-three-rebuild shortlist.

Tier 1: Foundation Add-ons (Install First)

These four run on every Home Assistant install I've ever built. Skipping them is technically possible but creates pain quickly.

Studio Code Server is the in-browser VS Code editor. The default file editor in Home Assistant works for typo fixes; Studio Code makes any non-trivial YAML editing dramatically faster. Syntax highlighting, autocomplete for Home Assistant entities, integrated terminal, and Git integration. The 200MB container size is the only cost. Official add-on, install first.

Mosquitto MQTT broker is the message bus most smart home protocols use to communicate. Even if you don't think you need MQTT today, the moment you add Zigbee2MQTT or any ESPHome device you'll need it. Install it preemptively. Official add-on, near-zero resource use, set up once and forget.

Zigbee2MQTT is the community alternative to the official ZHA integration. Both work; Z2M supports about 2000 Zigbee devices versus ZHA's roughly 700, and the documentation is more thorough. Install via the Zigbee2MQTT setup guide using the dedicated add-on. Requires a Zigbee coordinator USB stick like the Sonoff ZBDongle-E.

ESPHome manages ESP32 and ESP8266 firmware for DIY sensors and custom devices. If you have any Arduino-style hardware running smart home logic, you need this. Official add-on, web-based device configuration, OTA updates. Pairs perfectly with the Arduino projects covered in the simple and advanced Arduino smart home guides.

Tier 2: Quality of Life (Install Within The First Month)

These four solve recurring problems that grow with the install.

Frigate NVR runs local AI object detection on camera feeds. Person, vehicle, package, animal classification with sub-second latency on a Google Coral TPU. Coral USB stick adds 60 GBP one-time and lets a Raspberry Pi handle 4-8 cameras simultaneously without melting. Frigate exposes events to Home Assistant for automation hooks (person-at-front-door triggers lights, package-detected sends a notification).

Node-RED offers a visual flow editor as an alternative to YAML automations. Mixed YAML plus Node-RED setups are common -- YAML for simple state triggers, Node-RED for complex multi-step flows with conditional branches. The visual representation makes long automations much easier to debug than scrolling through YAML.

AdGuard Home runs DNS-level ad blocking and tracker filtering for the whole network. Replaces commercial ad blockers, lowers smart-TV phone-home traffic, and gives you visibility into what every device on your network is contacting. The setup requires pointing your router DNS at the Home Assistant IP, which is the only mildly tricky step.

NGINX Proxy Manager lets you expose Home Assistant securely via your own subdomain with automatic Let's Encrypt SSL. Far better than the default port-8123-public exposure. Required if you ever want to access HA from outside the home network without using the (paid) Nabu Casa Cloud subscription.

Tier 3: Long-Term Power (Install When You Have Real Data)

These four matter once you have months of sensor data to mine.

InfluxDB stores time-series sensor data with much better query performance than the default SQLite recorder. Long-term history (months to years) queries in milliseconds rather than minutes. Required if you want graphs showing trends across seasons rather than just the last week.

Grafana is the dashboarding layer on top of InfluxDB. Default Home Assistant Lovelace cards handle current-state views; Grafana handles "show me energy consumption per room over the past 6 months segmented by season". Worth the install effort once you have a few months of InfluxDB data accumulated.

SQLite Web lets you query the recorder database directly via SQL. Useful for diagnosing automations that triggered (or didn't), inspecting state changes, and exporting subsets of historical data for analysis. Read-only by default for safety.

Google Drive Backup automates Home Assistant snapshots to Google Drive on a schedule. The official Home Assistant snapshot feature dumps to local storage; this add-on copies that local snapshot to Drive so a SD card failure does not destroy the entire install history.

Order of Operations: 30-Day Install Plan

The temptation on day one is to install all 12 add-ons immediately. Don't. Each add-on adds load, configuration surface, and a small probability of conflict. The 30-day plan I use:

• Week 1: Studio Code, Mosquitto MQTT, Zigbee2MQTT
• Week 2: ESPHome (assumes you have ESP32 devices to manage)
• Week 3: Frigate NVR (assumes cameras), Node-RED, AdGuard Home
• Week 4: NGINX Proxy Manager (only if exposing to internet)
• Month 2: InfluxDB plus Grafana
• Month 3: SQLite Web, Google Drive Backup

The slow rollout means each addition gets a few days of observation before the next one stacks on top. If something breaks, you know what caused it.

What I No Longer Bother Installing

For completeness, three categories of add-ons I used in the past and have removed:

Spotify-related add-ons: The official Spotify integration is now good enough that the community add-ons no longer add value. Spotcast and other workarounds are mostly obsolete.

MariaDB or PostgreSQL for the recorder: Default SQLite handles 95% of home installs fine. Switching the recorder to a heavier database is a maintenance burden that rarely pays back. Stick with SQLite plus periodic purge.

Custom voice assistants like Rhasspy: The Home Assistant project now has its own voice assistant pipeline that's good enough for most cases. The community voice add-ons require setup effort that the integrated solution avoids.

The list above can shift as Home Assistant Core improves -- features that needed third-party add-ons in 2022 are sometimes built in by 2026. Re-audit your add-on list yearly to remove anything the core has absorbed.

Why Stay With Official Where Possible

Official add-ons (marked with an asterisk in the store) go through Home Assistant review and update with the core release cycle. Community add-ons are maintained by volunteers with varying commitment. After three years I've had two community add-ons abandoned by their maintainers, one of which broke when Home Assistant Core changed its supervisor API.

Where official and community add-ons offer the same function (the recorder DB choice, the Zigbee stack choice, the MQTT broker choice), I now default to official. The slight feature lag is worth the maintenance guarantee.

The Home Assistant add-on documentation lists the full official catalogue with descriptions. Community add-ons appear in the same store interface once you add the community repository URL. The 12 picks above are the genuinely best essential subset; everything else is optional flavour rather than baseline infrastructure.

Honest Trade-offs You Will Eventually Hit

Running 12 add-ons on a single Raspberry Pi is realistic but not free. Three trade-offs serious installs eventually grapple with.

Memory pressure is the first wall. Each add-on Docker container reserves 50-300 MB of RAM. The 12-add-on stack uses roughly 2.5-3 GB total in steady state on a Pi 5 with 8 GB. Run InfluxDB and Frigate heavily and you can push memory use to 5 GB. The Pi 5 8 GB version handles this; the 4 GB version starts swapping which kills SD card lifetime. Always buy the 8 GB Pi for HA hosts.

Storage growth is the second wall. The HA database, Frigate camera recordings, and InfluxDB time series all grow predictably. A four-camera Frigate setup at 720p produces about 50 GB per month of recorded events. Plan for 256-500 GB of SSD storage on serious installs, not the default 32 GB SD card.

Backup complexity is the third. Each add-on stores configuration in its own location. The official HA snapshot mechanism captures most of it, but some add-ons (Frigate's video archive, custom Z2M coordinator backup) need explicit exclusion or inclusion rules. Test restore from backup at least once before you genuinely need it -- I've seen plenty of "we have backups" claims fail at the actual restore step.

The Realistic Maintenance Burden

For honesty about long-term operating cost: a 12-add-on Home Assistant install takes roughly 30 minutes per month of active maintenance once stable. That breaks down as approximately:

• 5 minutes reviewing the Home Assistant release notes for breaking changes before updates
• 10 minutes applying core + add-on updates in batched windows
• 10 minutes checking that any new sensors or devices integrated cleanly
• 5 minutes pruning stale automations, scenes, or template sensors

Plus occasional ad-hoc work when something breaks. The serious installs that hum along reliably are the ones where someone treats this as a real (small) hobby commitment rather than a "set and forget" expectation. Plan for 30 minutes a month and the system pays back daily. Skip the maintenance and Murphy's Law will eventually catch you at the worst possible moment.