explaingit

hacs/integration

7,352PythonAudience · generalComplexity · 3/5Setup · moderate

TLDR

A graphical store built into Home Assistant that lets you browse, install, and update community-made smart home extensions without manually copying files onto your server.

Mindmap

mindmap
  root((HACS))
    What it does
      Browse community addons
      Install without file copying
      Track updates
    Supported content
      Custom integrations
      Themes
      Automation tools
    How it works
      Runs inside Home Assistant
      GUI panel in browser
      Links to GitHub repos
    Setup
      Add as integration
      See hacs.xyz docs
    Audience
      Home automation users
      Self-hosters
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Browse and one-click install community-built integrations for smart devices not officially supported by Home Assistant.

USE CASE 2

Get notified when updates are available for your installed community extensions and apply them from a browser tab.

USE CASE 3

Quickly remove a community integration through the same interface without touching any files on your server.

USE CASE 4

Discover community themes and automation tools through a searchable panel inside Home Assistant.

Tech stack

PythonHome Assistant

Getting it running

Difficulty · moderate Time to first run · 30min

Requires a running Home Assistant instance, full setup instructions are on a separate documentation site at hacs.xyz.

In plain English

HACS stands for Home Assistant Community Store. It is an add-on for Home Assistant, the popular open-source home automation platform, that adds a graphical panel for browsing and managing third-party extensions that are not part of the official Home Assistant catalog. Home Assistant supports a large community of developers who build custom integrations for smart devices, themes, and other automation tools. Without HACS, installing one of these community-built extensions typically means finding the code on GitHub and copying files manually into the correct folders on your server. HACS replaces that process with a screen inside the Home Assistant interface where you can search for, download, and update community contributions directly from your browser. The store keeps track of everything you have installed and alerts you when updates are available. It also provides shortcuts back to each project's source repository and issue tracker, making it easier to check on a project's development activity or report a problem. Removing an installed item happens through the same interface, without touching the file system directly. Installing HACS itself requires adding it as an integration within Home Assistant. The README is brief and points to a separate documentation site at hacs.xyz for full setup instructions, configuration options, and answers to common questions. Bug reports go to the repository's own issue tracker. The project also accepts support through GitHub Sponsors and a donation link maintained by the primary developer.

Copy-paste prompts

Prompt 1
I have HACS installed in Home Assistant. Help me write an automation that sends me a notification whenever HACS detects a pending update for any installed integration.
Prompt 2
Walk me through installing a custom Home Assistant integration using HACS, from opening the HACS panel to restarting Home Assistant after installation.
Prompt 3
I want to develop a custom Home Assistant integration and submit it to the HACS default store. What structure and metadata files does my repository need to be accepted?
Prompt 4
Explain what HACS does differently from the official Home Assistant integration catalog, and help me decide which community integrations for Zigbee devices I should look for in the store.
Open on GitHub → Explain another repo

← hacs on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.