12 Best Home Assistant Integrations for 2025 and 2026

I've installed and ripped out more Home Assistant integrations than I'd like to admit. Some lasted a weekend. A few have run on my Intel N100 box for two years straight without a single restart. This list is the short version: the ones I'd reinstall on day one if my config blew up tomorrow. It's also the list I'd hand a friend setting up their first server in 2025.

Home Assistant ships with over 3,000 official integrations (Home Assistant integration directory). That's overwhelming. Most you'll never touch. So which ones actually earn their place going into 2026?

TL;DR: HACS, ESPHome, Zigbee2MQTT, Frigate, Node-RED, Mushroom, Adaptive Lighting, Browser Mod, Spotify, Mobile App, Local Tuya, and Scheduler are the integrations I keep across two homes. HACS unlocks most of the rest. The Home Assistant project reports over 1 million active installations as of 2024 (Home Assistant Analytics), and the community add-ons below are why people stay through 2025 and beyond.

Which Home Assistant Integration Should You Install First?

HACS (Home Assistant Community Store) comes first, every time. It's the gateway to thousands of community integrations, custom cards, and themes that aren't in the core install. The Home Assistant Analytics dashboard shows HACS running on roughly 60% of reporting installations as of 2024, which tells you how essential the community treats it.

Without HACS, half this list is unreachable. Mushroom, Adaptive Lighting, Browser Mod, all of them install through HACS. Setup takes about ten minutes through Settings, then a GitHub token paste. Annoying once. Worth it forever.

One gotcha worth flagging: HACS changed its onboarding flow in 2024, so older tutorials that tell you to add a custom repository URL by hand are out of date. You now authorize through a device-code prompt on github.com instead. If a guide written before 2025 sends you hunting for a "custom repositories" button in the wrong menu, that's why. The current flow is simpler, but the stale docs trip people up constantly.

Why does HACS beat just downloading custom components manually? Updates. HACS tracks every community integration you install and tells you when a new release drops. Doing that by hand across a dozen add-ons is a part-time job nobody wants.

The Core Three for Local Control

These three handle your actual hardware, locally, no cloud round-trips. They're the foundation everything else sits on.

• ESPHome turns a $4 ESP32 chip into a temperature sensor, a garage door opener, or a 12-button wall panel. You flash firmware from the HA dashboard. I run nine ESPHome nodes, and the oldest has 412 days of uptime. The setup gotcha: the very first flash has to happen over USB, because the chip has no firmware yet to accept a wireless update. After that, every change goes over Wi-Fi. Beginners get stuck here, plug it in once and you're past it. ESPHome beats buying a finished Zigbee sensor because you control the exact reporting interval and you'll never wait on a vendor's firmware roadmap.
• Zigbee2MQTT replaces the proprietary Zigbee hubs (Hue Bridge, SmartThings) with one $20 Sonoff dongle. It supports over 4,000 Zigbee devices (Zigbee2MQTT supported devices). Pairing is faster than any vendor app I've used. The concrete example that sold me: I moved 23 Aqara sensors off a SmartThings hub onto one dongle in an afternoon, and response time dropped from roughly half a second to nearly instant. The catch is USB interference. A USB 3.0 port sitting next to the dongle creates 2.4GHz noise that wrecks range, so use a cheap extension cable to move the stick a foot away from your server.
• Local Tuya pulls cheap Tuya Wi-Fi plugs and bulbs off the cloud and onto your LAN. Setup is fiddly, you need device-specific local keys, and extracting them got harder after Tuya tightened their developer API in 2023. The payoff is sub-100ms response instead of waiting on Tuya's servers, plus your plugs keep switching even when your internet is down.

Is ESPHome harder than buying a finished sensor? Sure. But nothing else gives you this much control for the price of a coffee.

What Are the Best Home Assistant Dashboard Integrations?

Mushroom is the dashboard card set most people land on, and for good reason. It gives you clean, mobile-friendly cards without writing custom CSS. According to the Mushroom GitHub repository, the project has over 4,000 stars, making it one of the most adopted Lovelace card packs in the community.

The default Home Assistant dashboard is functional. It's also ugly, and I'll die on that hill. Mushroom fixes it in an afternoon. The gotcha: Mushroom cards need the card-mod helper installed alongside them if you want to tweak colors or spacing, and that dependency isn't obvious from the install screen. Skip it and your styling overrides silently do nothing.

Where Mushroom beats the alternatives like Bubble Card or the stock entities card is consistency. Every Mushroom card shares the same visual language, so a dashboard built entirely from them looks designed rather than assembled. A concrete example from my own setup: my phone wall panel uses nine Mushroom template cards in a 3x3 grid, and a non-technical guest figured out the lights and thermostat without a single instruction.

Pair Mushroom with Browser Mod and your dashboard gets superpowers. Browser Mod can pop up a camera feed on a wall tablet when someone rings the doorbell, or auto-navigate a kitchen display to the recipe view at 6 PM. I use it to turn an old Fire HD 8 into a $50 control panel mounted by the front door. The honest downside: Browser Mod registers each browser as a device, and those registrations pile up. Clear the stale ones every few months or your device list turns into a junk drawer.

Mushroom plus Scheduler

Scheduler adds a calendar-style UI for time-based automations. No YAML. Your partner can change the bedroom light schedule without learning to code, which, in my house, ended a recurring argument. That alone justifies the install.

The setup gotcha is small but real: Scheduler creates its own switch entities for each schedule, and if you delete a schedule from the card without disabling it first, the orphaned entity hangs around. Scheduler beats writing time-based automations by hand because the people who actually live with your smart home can adjust it themselves. That's the difference between a system that gets used and one that gets resented.

How Do You Add Cameras and Notifications?

Frigate is the camera integration worth running on real hardware. It does local, AI-powered object detection, so you get a notification for "person" or "car" instead of every leaf that blows past. The Frigate documentation recommends a Google Coral TPU, which processes inference in around 8 milliseconds versus 100ms-plus on CPU.

I added a $25 Coral USB stick to my setup and false alerts dropped to near zero. Before that, every spider web on the lens triggered my phone at 3 AM. Never again. The setup gotcha that costs people a weekend: Frigate wants two camera streams, a high-res one for recording and a low-res sub-stream for detection. Point it at a single 4K stream for both jobs and your CPU melts. Configure the sub-stream first.

Why Frigate over a cloud camera subscription like Ring or Nest Aware? Cost and privacy. A concrete example: three cameras on Nest Aware would run me around $120 a year, every year. Frigate's recordings sit on a hard drive I already own, and the footage never leaves the house. That math gets better the longer you run it.

For the alerts themselves, the Mobile App integration (the official Companion App) is non-negotiable. It feeds your phone's location, battery, and sensors back to HA, and sends actionable notifications you can tap to unlock a door or dismiss an alarm. It's the backbone of any presence-based automation. The gotcha worth knowing: aggressive battery optimization on Android will quietly kill background location, so your "arriving home" automation just stops firing one day. Whitelist the app and the problem disappears.

Which Integrations Make Automations Smarter?

Node-RED is the integration that changes how you think about automations. It's a visual, drag-and-drop flow editor that handles logic the built-in automation UI can't touch gracefully. The official add-on has been installed on hundreds of thousands of systems per the Home Assistant add-on store, and once you wire your first flow, plain YAML feels cramped.

Here's my honest take: Node-RED is overkill for "turn on a light at sunset." But for "if nobody's home and the washer finished and it's a weekday, text me," it's far easier to read a flow than scroll YAML. A concrete example from my house: my laundry-done flow watches the washer's power draw, waits for it to drop below 4 watts for two straight minutes, then nags my phone every 15 minutes until someone moves the load. Try expressing that cleanly in the stock editor.

The setup gotcha: Node-RED runs as a separate add-on with its own state, so a careless restart can lose flows you forgot to deploy. Hit the deploy button after every change, and back up the flows folder. It beats the built-in automation engine for anything with branching logic, but for simple stuff the native editor is genuinely faster.

Two more I'd never skip:

• Adaptive Lighting shifts your bulbs' color temperature and brightness across the day automatically, warm at night, cool at noon, matching circadian rhythm. Set it once and forget it exists. The gotcha: it fights manual changes unless you enable "take over control," so without that setting your bulb snaps back to the calculated value the moment someone dims it by hand.
• Spotify integration ties your music to automations. Morning alarm fades in a playlist, motion in the kitchen resumes whatever was playing. Small thing. Genuinely lovely every single day. Heads up: it needs a Spotify Premium account and a separate companion add-on (Spotcast) to actually start playback on a speaker, since the core integration alone only reads state.

What ties all of this together is one principle: keep the logic local. When the internet drops, a good HA setup doesn't notice.

How I'd Prioritize These for 2026

If you're starting fresh, don't install all twelve at once. You'll burn out debugging things you don't understand yet. Here's the order I'd actually follow, and the reasoning behind it.

Install HACS first, then the Mobile App, then either Zigbee2MQTT or ESPHome depending on whether you're buying Zigbee gear or building your own sensors. Those four give you a working, locally controlled home in a single weekend. Live with that for a couple of weeks. Notice what annoys you.

Round two is the comfort layer: Mushroom for a dashboard you don't hate, Scheduler so other people in the house can adjust things, and Adaptive Lighting because good light is the kind of upgrade you stop noticing precisely because it just works. None of these add risk. They make the system pleasant.

Save Frigate and Node-RED for last. They're the most powerful and the most demanding. Frigate wants real hardware and careful stream config; Node-RED rewards you only once you have automations complex enough to justify it. In my experience, people who install these on day one end up frustrated, while people who wait until they have a real problem to solve love them. The best integration is the one that fixes something already bugging you, not the one with the most GitHub stars.

Frequently Asked Questions

Do I need HACS for these Home Assistant integrations?

You need HACS for most of them. Mushroom, Adaptive Lighting, Browser Mod, and Scheduler are all community projects installed through HACS. ESPHome, Frigate, Node-RED, and Zigbee2MQTT install as official add-ons instead. HACS itself takes about ten minutes and a GitHub token to set up.

Is Frigate worth running without a Coral TPU?

It works on CPU, but I wouldn't recommend it long-term. Inference time drops from over 100ms on CPU to roughly 8ms with a $25 Coral USB stick, per the project's own benchmarks. Without the Coral, your processor pegs at high load and detection lags during busy scenes. For a single low-traffic camera you can get away with CPU; add a second camera and you'll want the accelerator.

What hardware runs these integrations well?

A Raspberry Pi 4 (4GB) handles most of this list, though Frigate with multiple cameras wants more. I run everything on an Intel N100 mini PC I bought for $89, and it stays under 20% CPU. For heavy camera setups, budget for an N100 or used NUC plus a Coral accelerator.

Can I run Zigbee2MQTT and the official Zigbee integration together?

Not on the same dongle. Pick one coordinator per USB stick. Zigbee2MQTT supports more devices (over 4,000 per its docs), while the official ZHA integration is simpler to start. I switched to Zigbee2MQTT for the wider device support and faster pairing, but ZHA is the easier first step.

Will these integrations keep working after a Home Assistant update?

Mostly yes, but not always. Official add-ons like ESPHome and Frigate track core releases closely and rarely break. Community integrations from HACS occasionally lag a version or two behind a major core update. My rule: read the release notes before any major monthly update in 2026, and wait a few days if a custom integration you depend on hasn't posted a compatibility note yet.

Honestly? Start with five from this list, not twelve. Get HACS, Mushroom, ESPHome, the Mobile App, and Zigbee2MQTT running first. Live with them for a month. Then add Frigate and Node-RED once you know what's actually annoying you, because the best integration is the one that fixes a problem you already have.