Best Home Assistant Integrations & Add-ons UK 2026

The 12 Home Assistant integrations and add-ons that earn their place on a UK smart home in 2026 - Octopus, ESPHome, Mushroom, Z-Wave JS UI and more.

Smart home automation dashboard showing controls and sensors
Updated How we review →
Rob
By Rob13 June 2026 · 12 min read

Home Assistant ships with 2,500+ official integrations out of the box, plus a community ecosystem (HACS) that adds thousands more. The hard part isn't finding stuff to install - it's working out which 10-15 add-ons and integrations are actually pulling their weight on your setup.

This list is the bias I'd carry into a fresh UK Home Assistant install in 2026 - integrations and add-ons that solve a real problem, are well-maintained, and either save real money (Octopus, Energy Dashboard) or take a weekend's worth of yak-shaving off (Z-Wave JS UI, Mushroom). New to Home Assistant? Start with the beginner's guide and the 8 add-ons to install first before going through this list.

What is HACS and why install it first?

HACS (the Home Assistant Community Store) is the gateway. It's a custom integration that lets you install other community integrations, themes, dashboards and front-end cards from a one-click UI - rather than copying files into custom_components/ by hand. Roughly 90% of the picks in this post are installed via HACS rather than the built-in catalogue.

Installation is a 5-minute task: download the HACS install script via SSH, restart Home Assistant, then add HACS as an integration. The official docs walk through it. Everything below assumes you've done that.

Which integrations should every UK Home Assistant user install?

Octopus Energy (HACS)

Octopus Energy (HACS)

By far the most important UK-specific integration. Pulls Agile/Cosy/Go/Saver half-hourly tariff data, current and forecasted prices, your account's consumption, and exposes them as sensors. Pair with the Energy Dashboard for a working real-time bill tracker. Author: BottlecapDave.
Z-Wave JS UI (add-on)

Z-Wave JS UI (add-on)

Replaces the official Z-Wave JS integration's bare-bones inclusion flow with a proper web UI for healing, replacing, and re-naming nodes. If you have more than 10 Z-Wave devices, this is non-optional.
ESPHome (add-on)

ESPHome (add-on)

Compiles custom firmware for ESP32 / ESP8266 boards and flashes them OTA. The fastest route to a homebrew sensor or relay board that talks native Home Assistant - far cheaper than buying branded equivalents. Pairs especially well with cheap eBay/AliExpress dev kits.
Mushroom cards (HACS, frontend)

Mushroom cards (HACS, frontend)

The single biggest improvement to the default Home Assistant dashboard look. Compact, modern card style for entities, chips, sliders and tiles. Pairs with any dashboard layout including the new sections UI.
mini-graph-card + apexcharts (HACS)

mini-graph-card + apexcharts (HACS)

Two graphing front-end cards that fill the gap left by HA's basic history-graph. mini-graph-card for compact tile-sized sparklines; apexcharts for proper styled time-series with multiple Y-axes. Essential for energy + temperature dashboards.
Frigate NVR (add-on)

Frigate NVR (add-on)

Which integrations level up an intermediate setup?

How do you install a HACS integration?

  1. Open HACS from the sidebar

    If you don't have it yet, follow the [official HACS install guide](https://hacs.xyz/docs/use/download/download/) - it takes 5 minutes.

  2. Search for the integration

    Top of the HACS page, type the name (e.g. 'Octopus Energy'). Some popular integrations show up with a verified badge.

  3. Click 'Download' then restart Home Assistant

    HACS downloads the integration files into `/config/custom_components/`. Restart from Settings → System → Restart so HA picks them up.

  4. Add the integration from Settings → Devices & Services

    Click 'Add Integration' and search again - it should now appear in the picker. Follow the integration's setup flow (usually an API key, OAuth login, or local IP).

  5. Check the entities and add to dashboard

    Once configured, the new entities appear under Settings → Devices. Build a dashboard card around them - mushroom and apexcharts make this easy.

Which integrations should you NOT install?

There's a healthy amount of HACS content that's either abandoned, redundant, or actively makes your system flakier. Specific patterns to skip:

  • Old 'Tuya Local' forks. Multiple competing repos exist; the Local Tuya integration is the only well-maintained one. Pick that and ignore the rest.
  • Hue beyond the official integration. The built-in Hue integration in HA is now feature-complete. Third-party Hue HACS integrations exist for historical reasons; don't install them.
  • Anything 'home_assistant_smart_lock_X'. If your lock has a Zigbee or Matter chip, use the native protocol. Custom integrations for specific lock brands are usually thin wrappers around proprietary clouds.
  • Multiple themes simultaneously. One theme is plenty. Two themes fight for the same CSS variables and break dashboards. Stick to Mushroom + one base theme.
  • Automation 'packs' from random GitHub repos. Copying 50 automations you don't understand is how you end up debugging at 2am. Read the existing automation, adapt one rule at a time. See our [25 automation examples](/blog/home-assistant-automations-for-beginners/) for tested starting points.

What's the difference between an integration and an add-on?

The terminology trips up almost every new user. Same word ('add it to Home Assistant') for two completely different things:

  • Integration: Python code that runs inside the Home Assistant process. Talks to an API or device protocol, exposes entities. Lives under Settings → Devices & Services. Updated as part of HA's normal release cycle (or via HACS for community ones). Examples: Octopus Energy, Hue, UniFi, Z-Wave JS.
  • Add-on: A separate Docker container managed by Home Assistant OS / Supervisor. Runs alongside HA on the same host. Lives under Settings → Add-ons. Has its own UI and configuration. Examples: Frigate NVR, ESPHome, Node-RED, AdGuard Home, Z-Wave JS UI.

Critical implication: add-ons only work on Home Assistant OS or Home Assistant Supervised. If you installed Home Assistant Container (raw Docker), you don't get the Add-on Store - you'll need to run each Docker container yourself. That's why we recommend HA OS as the default install method.

Frequently asked questions

Q01How many HACS integrations should I have installed?
Fewer than you think. Each HACS integration is a moving part - the maintainer can break it with a release. A typical well-running UK setup has 8-15 HACS integrations and 5-10 add-ons. If you're pushing 30+, prune the ones you haven't built a dashboard tile or automation around.
Q02Is the Octopus Energy integration safe to give my account credentials to?
It's an unofficial integration, not endorsed by Octopus. The credentials live in your local config; nothing leaves your network except the API calls themselves. Read the source if you want to verify (BottlecapDave's repo is active and reviewed by the HA Octopus community). The official Octopus app gives you the same data; the integration just exposes it as HA sensors.
Q03Does HACS work on Home Assistant Container or Core installs?
Yes for integrations and frontend cards. No for add-ons - those need HA OS or HA Supervised. If you're on Container or Core, install each 'add-on' as its own Docker container manually.
Q04Can I install all of these on a Raspberry Pi?

Mostly yes - except Frigate, which needs either a Coral USB AI accelerator or a fairly capable CPU to do object detection in real time. A Pi 4 will run Frigate on 1-2 cameras with detection, but for 4+ cameras you'll want a mini-PC. See our best mini-PC for Home Assistant guide for the upgrade picks.

Q05What about Matter integrations?

Home Assistant has native Matter support via the python-matter-server add-on (covers Matter 1.4 today; Matter 1.5 cameras and closures are landing across the 2026.7-2026.10 releases). No separate HACS integration is needed; install the add-on and add the Matter integration from the catalogue. See our Matter 1.5 explainer for what 1.5 actually adds.

Q06What's the upgrade path from ZHA to Zigbee2MQTT?
Not in-place - you need to remove devices from ZHA and re-join them under Z2M. Plan a weekend for a medium-sized network (20+ devices). Document the entity names before you start so you can rename in Z2M to match - that keeps your automations working without a YAML rewrite.

The bottom line

Home Assistant's strength is that you can extend it almost infinitely. Its weakness is the same. The 12 integrations and add-ons above are the ones I'd genuinely keep on a clean install in 2026 - Octopus and the energy stack for the UK tariff advantage, Z-Wave JS UI and ESPHome for device freedom, Mushroom and the chart cards for a dashboard that doesn't look like 2018, and Frigate/AdGuard as the headline add-ons that replace separate paid services.

Anything beyond that is shaped by your hardware. A solar-and-battery house adds Givenergy/Solax. A privacy-first household adds Wireguard and an unbound DNS resolver. A 3D-printing household adds OctoPrint or Bambu. Pick the integrations that match the problems you actually have, not the ones that look impressive in someone else's dashboard screenshot.