Top HACS Integrations for Home Assistant: Best Community Packages Reviewed

This post may contain affiliate links. As an Amazon Associate we earn from qualifying purchases. Disclosure.

HACS has roughly 2000 community integrations. Maybe 30 of them are worth installing. The rest are hobby projects, abandoned forks, or niche edge cases for hardware nobody owns. The list below is the best subset I have reviewed against three years of production use -- the top integrations that survive my install rebuilds because they solve real problems no official integration handles.

I've installed and removed something like 80 HACS integrations across my main install and various test setups since 2019. The list below is the survivors -- packages I still run after three years and three full rebuilds. Each one solves a problem that the official Home Assistant integrations cannot, and each one has held up against multiple HA Core releases without breaking.

Dashboard and UI Picks

The category where HACS earns the most casual user time. Three integrations transform the default Lovelace dashboard from functional to genuinely modern.

Mushroom Cards by @piitaya is the dominant Lovelace card library in 2026. The card set covers buttons, sliders, media players, person tracking, lights, climate, fans, and templates. The visual style is unified and modern; the configuration is simpler than the older custom-cards alternatives. Once Mushroom is installed, very few people go back to default Lovelace cards for the main dashboard.

Browser Mod by @thomasloven unlocks popups, toasts, and per-browser conditional content. The use cases that change everyday experience: a popup confirmation when arming the alarm, different dashboards on the kitchen tablet versus the bedside iPad, full-screen weather mode triggered by a button press. The Browser Mod feature set is impossible with stock Lovelace.

Card-mod by @thomasloven (same author) enables CSS overrides for any Home Assistant card. The use cases are smaller -- fixing visual inconsistencies, theming individual cards, hiding specific elements -- but the cumulative result is dashboards that feel polished rather than templated.

Lighting and Climate Picks

Adaptive Lighting by @basnijholt is the integration that pays back hardest in daily use. It tracks the sun automatically and adjusts colour temperature plus brightness on tunable-white bulbs continuously. Replaces dozens of manual scenes with one circadian configuration: warm white at dawn ramping to cool 6500K by noon, then back to warm by sunset. Works with Hue, Nanoleaf, LIFX, and any Z2M-paired tunable bulb.

Smart Thermostat (PID Climate) by @ScratMan replaces basic on/off thermostat logic with PID control. The result is room temperature stability within 0.3 degrees C versus the 1-2 degree swings of stock thermostat logic. For households running cheap dumb thermostats with smart radiator valves, this single integration delivers most of the comfort improvement a Nest or Tado would provide.

Voice and Media Picks

Alexa Media Player by @alandtse is the integration Echo households need but Amazon won't ship officially. Real per-device control: announce to the kitchen Echo only, TTS routing, last-spoken voice command capture, custom routine triggers. Without this integration, Alexa-as-output is essentially limited to broadcast-everywhere mode.

Spotcast by @fondberg casts Spotify content to specific Chromecast or smart speakers from Home Assistant automations. Critical for music-as-automation routines -- a wake routine that starts playing your morning playlist on the bedroom speaker, a movie scene that pauses Spotify across the house. Spotify Connect alone cannot do this from HA without Spotcast.

Ecosystem Bridges

HomeKit Bridge is technically built into Home Assistant Core now, but the HACS-distributed enhanced versions add per-entity include/exclude filters, custom name overrides, and device class fixes that the official bridge handles awkwardly. Lets non-Apple smart home devices (Ikea Tradfri, Aqara, Sonoff, generic ESPHome) appear in Apple Home cleanly.

Mqtt Discovery for IKEA Tradfri and other custom MQTT bridges fill gaps where the official integration handles the basics but misses the latest devices. The pattern is to use the official integration where it exists and fall back to community MQTT discovery for the long tail of unsupported hardware.

Niche Hardware Support

SmartThinQ by @ollo69 covers LG ThinQ appliances. The official Home Assistant integration is limited; this one supports more device types and exposes more sensors. Worth installing if you own LG washing machines, fridges, or air conditioners.

Wyze Bridge by @mrlt8 streams Wyze cameras via RTSP to Home Assistant without modifying the camera firmware. The official Wyze integration relies on cloud APIs that frequently break; the Wyze Bridge runs locally and survives Amazon shutting down (Wyze cloud features) without warning.

Tuya Local by @rospogrigio replaces the cloud-dependent Tuya integration with local control. Required for any non-trivial Tuya device automation because the cloud version adds 2-5 seconds of latency per action. Tuya Local responds in under 200ms.

Utilities and Diagnostics

Powercalc by @bramstroker estimates per-device energy consumption from a lookup table of LED bulb wattages, smart plug power curves, and appliance profiles. Useful for households that want energy dashboards without buying smart plugs for every appliance. The accuracy is roughly +/-15% versus a metered plug, which is enough for trend analysis.

HACS itself -- worth listing because newcomers often miss it. HACS auto-updates by default but you can pin specific versions if a release breaks your install. The version selector lives in the integration detail page; check it before updating if any other package depends on a specific HACS feature.

What I Install in Order

The order matters because some integrations depend on others. The sequence on a fresh install:

1. Mushroom Cards plus Card-mod plus Browser Mod (dashboard foundation)
2. Adaptive Lighting (immediate daily value if any tunable bulbs)
3. Alexa Media Player or HomeKit Bridge (whichever ecosystem the household uses)
4. Spotcast (if any music automation is planned)
5. SmartThinQ or Wyze Bridge or Tuya Local (only if you own that hardware)
6. Powercalc (only after a few months of data accumulates)

Steps 1-3 happen in the first weekend. Steps 4-6 happen over the following months as use cases emerge. Resist the urge to install 15 integrations on day one.

What I Used to Run But Have Removed

Five integrations that earned their place years ago and have since been removed:

Variable -- the variable storage component became redundant when Home Assistant Core added input_text and input_number. Officially-supported state storage replaced the community package.

Browser_mod (legacy v1) -- the rewrite to v2 broke many of my dashboards, and I migrated to its newer features rather than living with the old.

Lovelace UI Editor (yaml mode) -- the official Lovelace UI editor caught up to the community version. Now the official UI is preferred.

Switchbot integration (community version) -- the official integration absorbed most features. The community version is no longer needed.

Custom climate template -- replaced by the official template climate platform.

The pattern is that HACS integrations sometimes graduate into Home Assistant Core. When that happens, switch to the official version even if the community one still works. The official version gets long-term maintenance guarantees the community cannot match.

How to Spot Worth-Installing Packages

Five quick checks before installing any HACS integration:

• Star count above 500 and growing
• Last commit within the past 60 days
• Open issues responded to within 30 days
• Clear README with screenshots
• Released versions tagged in GitHub (not just rolling main branch)

Anything that misses two of these five is probably not worth the maintenance risk. Anything that hits all five is usually safe.

The full HACS catalogue lives in the HACS default repositories list. The Home Assistant quality scale documentation explains the official integration rating system that HACS packages aspire to. Browsing both gives a sense of which community packages are likely to graduate to official status -- and therefore stay around long enough to justify learning their conventions.

The 10 integrations above are the ones that survive my own install rebuilds. Your shortlist will diverge based on the specific hardware in your house, but the underlying principle holds: HACS is high-value when used selectively and high-risk when used impulsively. Pick deliberately and the community ecosystem becomes one of Home Assistant's biggest practical advantages.

Pairing Patterns That Multiply The Value

Several of the picks above work better in combination than they do alone. Three pairings I run that compound into more value than the sum of the parts.

Adaptive Lighting plus Mushroom Cards is the first pattern. The adaptive system runs the temperature shift automatically; the Mushroom light card exposes a clean per-room dimmer that respects the adaptive setting. The combined experience feels like a high-end lighting system that costs a tenth of a comparable Crestron or Lutron installation. Without one or the other, the experience drops considerably.

Alexa Media Player plus Spotcast is the second. Voice trigger to a routine that announces ("playing your morning playlist in the kitchen") while simultaneously casting Spotify content to the kitchen speaker. The two integrations work independently but together create a voice-first audio routine that the official Amazon and Spotify integrations cannot match.

HomeKit Bridge plus HACS Tuya Local plus Z2M is the third. Tuya devices via local control flow through MQTT to Home Assistant; HomeKit Bridge re-exposes those devices into Apple Home; Apple users see Tuya devices as if they were native HomeKit. The whole household runs HomeKit on the iPhone while the backend uses cheap Tuya hardware Apple would never officially support.

The Trap of HACS Maximalism

A common path I see in newer Home Assistant users: install HACS, browse the catalogue, get excited, install 30 integrations in a weekend. Two months later the install is unstable, updates break things weekly, and the user is on Reddit asking why HA is unreliable.

The cause is not Home Assistant or HACS. It is unchecked installation. Each integration adds a small failure surface. Stack 30 of them and the failure rate compounds. The same person running only the 10 integrations above would have a stable install for years.

Resist completionism. The catalogue is interesting but most of it is not relevant to your specific household. Install the 5-10 that solve real problems you experience daily, ignore everything else, and the Home Assistant install stays stable enough to live with rather than constantly debug.