HACS for Home Assistant: integrations and add-ons worth knowing

HACS provides access to extensions created by the Home Assistant community. It can fill a device support gap, add specialist data, or enhance a dashboard. It is not a quality seal or a replacement for the official integration catalogue.

This guide is not an installation tutorial or a list of the most popular repositories. It focuses on cases where a community project adds specific value and on situations where the official option remains the better choice.

Official integrations are part of Home Assistant Core. They follow the project's review, testing, and release process. Changes are coordinated with future Home Assistant versions.

A project delivered through HACS remains an independent repository. HACS downloads files and reports releases, but it does not guarantee code quality, security, compatibility, or maintainer response time. Each project has its own lifecycle. HACS is not a store for Home Assistant system add-ons. It manages custom integrations, dashboard cards, themes, templates, and similar repository types.

If an official integration reliably covers the required features, start there. HACS makes sense when it solves a defined gap, enables required local control, or provides a feature that official Home Assistant does not offer.

• Official equivalent: check the Home Assistant integration catalogue and its actual feature set.
• Project activity: review releases, commits, open issues, and maintainer responses.
• Access: an integration may receive tokens, passwords, local network access, or control permissions.
• Cloud dependency: a vendor may change authentication, API limits, or service terms.
• Failure impact: a dashboard card is less critical than code controlling an inverter, alarm, or lock.
• Exit plan: make a backup and know how to remove the project without orphaned entities and automations.

What it does and who it helps: Powercalc creates virtual power and energy sensors for lights, fans, and devices without native metering. It uses device profiles or models based on brightness, colour, and operating mode.

Official equivalent and why HACS makes sense: Home Assistant supports meters and the Energy dashboard, but it has no official integration with this library of estimation models. This is a genuinely different function.

Status and limits: the project is actively developed and releases regularly. Its results remain estimates and cannot replace certified metering or direct measurement for billing and highly variable loads.

What it does and who it helps: Solcast PV Forecast retrieves solar production forecasts that can support scheduling of charging, water heating, and other flexible tasks.

Official equivalent and why HACS may make sense: Home Assistant includes the official Forecast.Solar integration. Solcast is justified only when its model, multiple-array configuration, or data better suits the installation. It is not automatically superior.

Status and limits: the repository is active and publishes releases. It depends on an external API, key, and query limits. Forecast error must be allowed for in every automation.

What it does and who it helps: Huawei Solar exposes inverter, battery, meter, and optimiser data over Modbus. With suitable permissions it can also provide advanced export and battery control.

Official equivalent and why HACS makes sense: the official catalogue contains Huawei LTE, but that is not a Huawei Solar inverter integration. HACS fills a real gap here. For Fronius, SolarEdge, SolaX, GoodWe, and other brands, check the official integration first.

Status and limits: the project is active and releases regularly. Modbus usually permits one connection, compatibility varies by firmware, and write operations can affect the installation. Control features require particular care.

What it does and who it helps: the Frigate integration exposes cameras, detected objects, events, snapshots, performance sensors, and recording controls. It is useful for people already running Frigate as a local NVR.

Official equivalent and why HACS makes sense: Home Assistant provides official ONVIF and vendor integrations, but they do not reproduce Frigate's event model. Frigate calls this its official project integration, yet it is technically installed through HACS and is not part of Home Assistant Core.

Status and limits: both projects are actively developed. The integration requires an operating Frigate instance, correct networking, and MQTT for many entities. HACS does not install the NVR or solve storage, performance, and image privacy concerns.

What it does and who it helps: the community OPNsense integration provides richer firewall and router telemetry, with selected controls on supported firmware. It suits advanced networks where infrastructure data belongs in diagnostics and automations.

Official equivalent and why HACS may make sense: Home Assistant has an official legacy OPNsense integration focused mainly on presence detection. If that is sufficient, it is the simpler choice. HACS is justified for the broader sensors and features.

Status and limits: hass-opnsense is actively maintained and documents firmware requirements. API accounts should have minimal privileges. Firewall or NAT changes carry much greater risk than read-only monitoring.

What it does and who it helps: the Kia Uvo and Hyundai Bluelink integration may provide vehicle state, range, charging, and selected commands in supported regions. Home Assistant currently has no official equivalent for these services.

Why HACS is conditional: the project has an extensive history and still receives changes, but its main author explicitly states that they no longer own a supported car and are looking for additional maintainers. That matters before relying on it in important automations.

Limits: it uses an unofficial vendor API, varies by region, and may break after authentication changes. Excessive polling may burden the service or wake the vehicle. For Tesla, check the official Tesla Fleet or Teslemetry integrations before any old HACS component.

What it does and who it helps: the active LocalTuya fork controls compatible Tuya devices locally during normal operation. This can improve response time and preserve basic control during an internet outage.

Official equivalent and why HACS may make sense: the official Tuya integration is easier and should come first if it provides the required entities. LocalTuya is justified by a conscious requirement for local control or missing functionality.

Status and limits: the xZetsubou fork is active, while the older rospogrigio repository is no longer the best starting point. Setup depends on local keys, DP identifiers, and protocol versions. Cloud access may still be needed during setup.

What it does and who it helps: Browser Mod can register a browser as a device, open a camera view when a doorbell rings, control navigation, show dialogs, and use the screen as a media player. It is particularly useful for wall tablets.

Official equivalent and why HACS makes sense: Home Assistant offers dashboards, kiosk mode, and mobile apps, but no full equivalent for addressing a specific browser session.

Status and limits: the project is actively maintained. It depends heavily on frontend and browser cache changes. A full reload may be required after updates, and critical control should not rely on one open browser tab.

Mushroom: an actively maintained set of consistent, compact cards for mobile and tablet dashboards. Official Tile Cards cover an increasing number of similar needs, so Mushroom should serve a defined layout or feature rather than cosmetic change alone.

Power Flow Card Plus: a more configurable live view of flow between the grid, solar, battery, home, and selected loads. The official Energy dashboard remains the better home for historical energy data.

Risk: custom cards execute code in the browser. Home Assistant updates can require new card versions or configuration changes. Too many custom cards increase load time and maintenance effort.

What it does and who it helps: Watchman scans configuration references and reports missing or unavailable entities and non-existent actions. It is useful after renaming entities, removing devices, and completing major upgrades.

Official equivalent and why HACS makes sense: repairs, logs, and automation traces reveal many issues, but do not provide the same cross-configuration reference report.

Status and limits: the project is actively maintained. Its lightweight parser uses heuristics and does not understand all configuration logic, so false positives and missed references remain possible. It supports review but does not replace testing.

Before updating, read the release notes, check the required Home Assistant version, and create a backup that can be downloaded away from the host. Updating HACS itself does not automatically update every downloaded repository.

Avoid installing several projects for the same purpose. Remove unused extensions together with their entities, dashboard resources, and automation references. After major updates, review logs, repairs, key dashboards, and device behaviour.

The safest system does not have the most extensions. It has only those whose value exceeds the cost of updates, diagnostics, and additional access.

Choose the official integration first when it reliably performs the required task. Use HACS when you can name the missing feature and accept responsibility for another dependency.

Powercalc, specialised solar support, Frigate, local Tuya, and diagnostic tools can genuinely extend a system. Every project still needs its own assessment based on current documentation, activity, and failure impact.

If you want to select an extension safely, assess its current state, or connect several systems in Home Assistant, I can help review the options, limitations, and configuration.

• HACS documentation: repositories and updates
• Official Home Assistant integration catalogue
• Powercalc, Solcast PV Forecast, Huawei Solar, Frigate, hass-opnsense, Hyundai Kia Connect, LocalTuya, Browser Mod, Watchman, Mushroom, and Power Flow Card Plus