Home Assistant HACS in 2026: The Community Store Explained, and the Hardware Worth Running It On

HACS — the Home Assistant Community Store — is the reason a lot of smart-home enthusiasts stay on Home Assistant instead of drifting back to Alexa or SmartThings. It is a free, open-source catalogue layer that unlocks the long tail of community-built device integrations, dashboard cards, themes and automation blueprints that never made it into Home Assistant core. It is also, notoriously, the part of a Home Assistant setup most likely to break after a software update — and understanding why that is true matters far more than understanding what HACS is.

This guide covers what HACS does in 2026, how installation actually works, where the genuine risks sit, and — because HACS itself costs nothing — which hub, dongle or mini-PC is worth buying to run a HACS-heavy setup properly. Everything below is drawn from manufacturer specifications, Home Assistant’s and HACS’s own documentation, and aggregated owner feedback on Reddit and the Home Assistant community forums. It is research, not hands-on lab testing.

Quick picks at a glance

What HACS is — and what it isn’t

HACS is a custom integration for Home Assistant, created by developer Joakim Sørensen and maintained by a volunteer team. Three things it is not: it is not made by Nabu Casa, it is not part of Home Assistant core, and it is not available in the official Add-on Store.

Architecturally, HACS is a thin catalogue layer with a frontend panel bolted on — lightweight Python that browses GitHub repositories and installs what you pick. That design has a practical consequence worth internalising: HACS itself rarely breaks. The breakage people complain about after a Home Assistant update comes from the individual third-party integrations installed through HACS, not from the store layer itself. Blaming HACS for a dead integration is like blaming a bookshop for a bad novel.

Once installed, HACS gives you a searchable panel inside Home Assistant where you can browse and one-click install community content across four categories:

• Integrations (custom components) — device and service support that has not been merged into Home Assistant core, installed into your custom_components folder
• Dashboards — Lovelace cards, themes and frontend resources that extend the interface
• Automations — community blueprints, which are reusable YAML automation templates with configurable inputs
• Templates — Jinja template helpers and snippets for use in automations and dashboards

Category counts shift constantly as repositories are added, archived or abandoned. Per-category figures are published on hacs.xyz, and that is where you should check them rather than trusting any fixed number quoted in a blog post — including this one.

What HACS 2.0 changed

HACS 2.0 rolled out in 2024 and has been refined through the 2024–2026 release cycle. It did two things worth knowing about:

1. It dropped the AppDaemon and NetDaemon categories, trimming the interface to the content most users actually install.
2. It added update entities, so HACS-managed integrations now surface in Home Assistant’s own native update panel alongside core updates. Before this, keeping community integrations current meant going into the HACS panel and checking manually; now the update panel lists them for you, which is a genuine quality-of-life improvement and a real reason to keep HACS current.

The current release line and full changelog live at github.com/hacs/integration/releases — check there for the exact version at the time you install, since HACS ships updates regularly.

HACS versus the official Add-on Store

These two get confused constantly, and the distinction genuinely matters.

The official Add-on Store is not a Nabu Casa-only walled garden. It hosts Nabu Casa-maintained add-ons and community add-on repositories — Zigbee2MQTT and Mosquitto are the classic examples of community software that lives there. Add-ons are a separate concept from HACS entirely: they run as their own containers under the Supervisor, sandboxed away from the core Home Assistant process.

HACS covers a different territory: custom_components (integrations) and frontend resources. Those run inside the Home Assistant process itself.

In practice, most experienced users run both. The official store handles the big, well-supported infrastructure pieces; HACS fills the gaps with the long tail. If someone tells you HACS is “an add-on”, they have the mental model wrong, and that misunderstanding is exactly what feeds the safety worry below.

Is HACS safe? The honest answer

Owner sentiment is broadly positive, but the caveats are real and specific. HACS has been used and audited widely for years, its code is public, and its install process is transparent. The risk sits with the individual repositories you choose to install — and the single most important fact is this: custom integrations run unsandboxed, with full access to your configuration, your secrets, your tokens and your network. That is confirmed in Home Assistant’s own documentation on custom integrations, and it is the mechanism behind every other caveat here. Unlike an add-on container, a custom component is not walled off from the rest of your Home Assistant instance.

Owner reports on Reddit and the Home Assistant community forums routinely cite three failure modes:

1. Abandoned integrations that quietly stop working after a Home Assistant core update, because nobody is maintaining them against the new release.
2. Breaking changes pushed without a changelog, sometimes within hours of a core release — the integration updates, an entity changes ID, and an automation silently stops firing.
3. Support friction. Home Assistant’s own support channels routinely ask users to disable custom integrations before troubleshooting, precisely because an unsandboxed third-party component can cause symptoms anywhere in the system. If you file a bug, expect “does it happen with custom integrations disabled?” as the first reply.

There is a second, quieter risk that has nothing to do with security: removing an integration can orphan entities and break automations. Delete a custom component and the entities it created do not always disappear cleanly, and any automation referencing them fails. Uninstalling is not as tidy as installing.

The HACS project documents its own answers to these questions in the FAQ at hacs.xyz/docs/faq, which is the right place to check before installing anything you are unsure about.

Backup is not optional

Because custom components sit in the same process as everything else, the practical mitigation is a genuine backup habit rather than caution alone:

• Home Assistant’s built-in backup (Settings → System → Backups) captures your configuration, including your custom_components folder.
• The Google Drive Backup integration — itself available through HACS — pushes those backups off-device, so a corrupted instance or a failed eMMC does not take your only copy with it.
• A weekly automated schedule is the sensible minimum, with an extra manual snapshot before any Home Assistant core update or any change to a HACS-managed integration you depend on.

If you take one thing from this section: the risk in HACS is not the store, it is the long tail of code behind it, and the remedy is backups plus update discipline rather than avoidance.

Installing HACS: prerequisites and the process

Installation is deliberately a little manual. That friction is a feature — it signals you are stepping outside officially supported territory.

What you need beforehand:

• Home Assistant OS or a Supervised install. The documented minimum is HAOS or Supervised; confirm current requirements in the HACS documentation at hacs.xyz.
• Home Assistant 2024.x or later — again, check hacs.xyz for the exact version floor at the time you install, since it moves.
• Terminal or SSH access, or the File Editor add-on as an alternative way to reach the filesystem.
• A GitHub personal access token (PAT). This is mandatory: since the HACS 2.0 rate-limit change, HACS authenticates its requests to GitHub with your token, and without one those requests get throttled, causing installs and updates to fail. The mechanism is simple — GitHub caps unauthenticated API calls, and a token raises your personal ceiling.

The install itself:

1. Run the single wget script in the Home Assistant terminal.
2. Restart Home Assistant.
3. HACS then appears as a sidebar panel. On first run it prompts you to enter your GitHub PAT.

Dropping the files into custom_components manually is the alternative route if you prefer not to run a script — same result, more steps, and you will still need the PAT for the panel to work properly.

What people actually install

If you want a sense of what a HACS-heavy setup looks like in practice, these are among the most frequently installed items. Search each by name inside the HACS panel — every one is hosted on its own GitHub repository, and HACS links you straight to the source before you install, which is worth reading.

Integrations:

• Adaptive Lighting — adjusts colour temperature and brightness across the day
• Frigate — an NVR with object detection, and by far the heaviest thing most people run
• Spook — a diagnostics and safety-net integration for Home Assistant
• Tuya Local — the HACS-distributed route to Tuya devices without the cloud round-trip
• Browser Mod — turns browsers into controllable, addressable Home Assistant entities

Dashboard cards:

• Mini Graph Card — compact history graphs
• Mushroom — a clean, mobile-friendly card collection
• Button Card — highly customisable buttons
• ApexCharts Card — rich, chart-heavy dashboards

Blueprints:

• Motion-activated light — Freek van der Graaf’s blueprint is the canonical example, and the one most new users install first as a template for how blueprints work.

How to choose hardware for a HACS-heavy setup

HACS adds essentially nothing to your hardware load — it is lightweight Python and a web panel. What strains a box is everything HACS lets you run. The realistic stressors are:

• 20 or more active custom integrations, each loaded at startup and polled on its own schedule
• Recorder database growth — every entity you add writes history to the database, so more entities and more frequent state changes mean a bigger file and more disk I/O
• Frigate object detection, which is genuinely compute-hungry and the single most common reason people outgrow a small ARM box
• Zigbee/Z-Wave coordinator polling, which scales with the size of your device network

So the buying decision comes down to three things: storage reliability (eMMC or NVMe rather than a microSD card, which is the classic point of failure), whether you need a built-in radio (a Zigbee/Thread radio means one less USB dongle), and raw compute for the heavy end. Everything below is reframed around those three, since HACS itself will run on any supported install.

The hardware options

1. Home Assistant Green — the sensible default

Best for: most people running HACS who want a quiet, official box that just works.

Specs: Rockchip RK3566 processor, 4GB RAM, 32GB eMMC storage, no SD card, no built-in radio.

Why it stands out: the 32GB eMMC matters more than it sounds. MicroSD cards are the most common hardware failure in DIY Home Assistant builds, and Green removes that failure mode entirely. It is silent, it is an official Nabu Casa device with supported updates, and setup takes minutes. For a setup running a moderate load of custom integrations and dashboard cards rather than Frigate, it is the least fussy option.

The honest caveat: there is no built-in radio, so Zigbee or Thread means adding a USB coordinator — see the combination pick below. And 4GB of RAM sets a ceiling: it is not the box to buy if Frigate object detection is on your roadmap.

Verdict: the default recommendation for a HACS-driven setup that does not need local video analysis.

Where to buy: stocked at Amazon UK, Currys and Argos, typically around £95–£130.

2. Home Assistant Green + ZBT-1 or ZBT-2 dongle — the radio workaround

Best for: Green owners who need Zigbee, Thread or both, and anyone who cannot get hold of a Yellow.

What’s included: the Green hub as above, plus Nabu Casa’s own USB coordinator in either the ZBT-1 or ZBT-2 variant. Nabu Casa makes both, which means the radio and the hub come from the same vendor and the same support path.

Why it stands out: this is the current recommended alternative if Yellow stock is uncertain. It also gives you a flexibility that the all-in-one Yellow does not — you can move the dongle to a different host later, or reposition it on a USB extension to get it away from interference.

The honest caveat: it is two devices and two purchases rather than one, and the dongle occupies a USB port you may want for something else.

Community-consensus alternatives: if you would rather not buy Nabu Casa’s dongles, the Sonoff ZBDongle-E / ZBDongle-P and the SMLIGHT SLZB-06 are the USB coordinators most often recommended by owners on the Home Assistant forums and Reddit. Note that the SLZB-06 is network-attached rather than USB, which suits boxes placed away from your Zigbee mesh.

Verdict: the pragmatic route to Zigbee and Thread on a Green, and the safest buy while Yellow availability remains unpredictable.

Where to buy: ZBT-1 and ZBT-2 from the Nabu Casa store; Sonoff and SMLIGHT dongles from general online electronics retailers.

3. Home Assistant Yellow (PoE) — one box, built-in radio

Best for: Zigbee and Thread users who want the radio, the compute and the storage in a single chassis.

Specs: built-in Silicon Labs Zigbee/Thread radio, plus an M.2 slot for NVMe storage and Power over Ethernet on the PoE variant — one cable for both power and data.

Why it stands out: the built-in radio is the headline. No dongle, no USB port sacrificed, no extension cable to route. Add NVMe storage and you have a fast, silent, single-box Home Assistant host with no microSD card in sight, which is exactly the profile a HACS-heavy setup wants.

The honest caveat — read this before buying: the Yellow requires a Raspberry Pi Compute Module 4, which is not included. Budget for the CM4 separately, because the realistic total cost sits meaningfully above the board price once you add one. The PoE variant is typically around £160–£250 depending on the Compute Module 4 specification you fit, so the cheaper end of that range reflects a modest CM4. There is also an end-of-life and availability caveat: check the Nabu Casa store for current stock and status before you commit to Yellow as your plan, and treat the Green-plus-dongle combination above as the fallback if it is out of stock.

Verdict: excellent hardware if you can source a Compute Module 4 at a sensible price — but verify availability first, because this is the one pick here with a real supply question attached.

Where to buy: the Nabu Casa store — check stock before ordering.

4. N100 mini-PC (Beelink EQ12, GMKtec G3) — the heavy-duty pick

Best for: setups running 20+ active custom integrations, Frigate object detection, or a large Recorder database.

Specs: Intel N100-class processor, typically around £120–£180, with idle power draw of roughly 6–10W — low enough that leaving it running continuously is not a meaningful running-cost concern compared with a desktop PC.

Why it stands out: community consensus on the Home Assistant forums and Reddit is that an N100 mini-PC is the right upgrade when a small ARM box starts to struggle. The extra CPU headroom is what makes Frigate object detection viable without an external accelerator, and the higher RAM ceiling absorbs both a growing Recorder database and a large set of custom integrations. It pairs best with a bare-metal HAOS install — that keeps the Supervisor and add-on model intact, so installing HACS works exactly as documented above.

The honest caveat: it is a generic PC with no built-in radio and no first-party smart-home support path, so you supply your own Zigbee/Thread dongle and you manage updates on your own schedule. Idle draw of 6–10W is also higher than an ARM hub, though still modest.

Verdict: the pick for anyone whose HACS install is genuinely heavy rather than merely enthusiastic.

Where to buy: typically sold through general online electronics retailers — model lines refresh often, so check current stock and specification at the time of purchase.

Keeping a HACS setup healthy

Two habits do most of the work, and both were covered above in principle — here is the routine in practice.

Backups: set up Home Assistant’s built-in backup (Settings → System → Backups), then add off-device copies via the Google Drive Backup integration, which you install through HACS itself. Weekly automated backups are the sensible minimum, plus a manual one before every core update.

Update discipline: since HACS 2.0, HACS-managed integrations appear in Home Assistant’s native update panel, which means you can see what is pending in the same place as core updates. Update in stages rather than all at once, read the release notes for anything installed from a single-maintainer repository, and be ready to restore a backup if an automation stops firing after an update. That pattern — back up, update a few things, check your automations still run — is what separates a stable HACS setup from the one people complain about online.

FAQ

Do I need a GitHub account to use HACS? Yes. A GitHub personal access token is mandatory — HACS uses it to authenticate its requests to GitHub. The mechanism is a rate limit: GitHub caps how many unauthenticated API calls an address can make, and HACS’s browsing and update checks will be throttled without a token, causing installs and updates to fail. You enter the token on HACS’s first run after installation.

Will official Home Assistant support help me if a HACS integration breaks? Usually not directly. Home Assistant’s support channels routinely ask users to disable custom integrations before troubleshooting, because custom components run unsandboxed and can cause symptoms anywhere in the system. That is why the advice is to isolate the problem yourself — disable the suspect integration, confirm the issue clears, and then take it up with the repository maintainer rather than Home Assistant support.

What actually breaks after a Home Assistant update — HACS or the integrations? The integrations. HACS is a lightweight catalogue and frontend panel, and it rarely breaks. The post-update failures owners report come from third-party custom_components installed through HACS that were not updated in step with the core release, or that have been abandoned by their maintainer. Restoring a pre-update backup is the fastest route back to a working system.

Can I uninstall a HACS integration cleanly? Not always cleanly. Removing a custom integration can leave orphaned entities behind and break any automation that referenced them. Before removing anything, note which entities and automations depend on it, delete or rewrite those automations, then remove the integration and clean up the leftover entities manually. Treat uninstalling as a deliberate three-step job rather than one click.

Does HACS cost anything, and does it need a subscription? No. HACS is free and open source, created by Joakim Sørensen and maintained by volunteers with no Nabu Casa involvement. There is no subscription, no licence fee and no paid tier. The only costs in a HACS setup are the hardware and the electricity to run it.

What hardware do I need if I plan to run more than 20 custom integrations? More than any minimum spec, you need storage that will not fail and enough RAM to hold the extra entities. A box with eMMC or NVMe storage rather than a microSD card is the baseline, and if you also want Frigate object detection, an N100-class mini-PC is the community-consensus answer. If you are nearer ten integrations than thirty, Home Assistant Green is comfortably sufficient.

Is HACS a security risk? HACS itself is widely used, its code is public and its install process is transparent, so the store is not the concern. The risk is that custom integrations run unsandboxed with full access to your configuration, secrets, tokens and network — as Home Assistant’s own documentation on custom integrations confirms. The practical mitigation is to install only actively maintained repositories with visible commit history, and to keep off-device backups so a bad integration never costs you your setup.

The bottom line

HACS is free, and it is the difference between a Home Assistant setup that supports your devices and one that supports the devices someone else decided you should own. The trade-off is that you are trusting individual developers rather than a vendor, running unsandboxed code, and accepting that a Home Assistant update can break something without warning. Back up weekly, off-device, and the downside becomes an inconvenience rather than a disaster.

Because HACS costs nothing, the real spending decision is the box underneath it. For most people, Home Assistant Green at typically around £95–£130 is the right answer — no microSD card to fail, official support, silent operation — paired with a ZBT-1 or ZBT-2 dongle if you need Zigbee or Thread. If your HACS install is genuinely heavy, with Frigate or 20-plus custom integrations, an N100 mini-PC at typically around £120–£180 is the upgrade that community consensus points to. And if you want the built-in radio and can source a Raspberry Pi Compute Module 4, Home Assistant Yellow (PoE) at around £160–£250 is excellent hardware — just check Nabu Casa stock before you plan around it, since availability is the one genuine uncertainty in this list.