Home Assistant blueprints worth installing first

Blueprints are one of Home Assistant’s most underrated features. They let you import a ready-made automation, script, or template entity and then fill in a few fields, no YAML required. One blueprint can be reused many times, so the same “motion lights” logic can drive your hallway and your bathroom as two independent automations. Here’s what actually matters when you’re getting started.

First, understand what a blueprint is (and isn’t)

A blueprint is a reusable recipe for an automation, script, or template entity. You import it, pick your entities, and Home Assistant builds the automation for you. Because your automation inherits from the blueprint, updates to the blueprint flow through the next time Home Assistant reloads.

Blueprints live in config/blueprints/ and you import them from Settings → Automations & scenes → Blueprints → Import blueprint, pasting a link from the Home Assistant forums, GitHub, or a gist. A good curated source to browse is the community “Blueprints Exchange” forum and collections like EPMatt’s Awesome HA Blueprints.

What blueprints are not: dashboard cards. Popular tools like Auto-entities (auto-populates cards with entities matching filters) and card-mod (applies CSS styling to cards) are frontend cards you install through HACS, not blueprints. They configure your Lovelace dashboard, not your automations. Worth installing, but in a different part of the app.

Good blueprints to start with

You don’t need many. Pick blueprints that match hardware you actually own:

• Motion-activated light — the classic. Turn a light on with a motion or presence sensor, off after a delay, often with conditions for time of day or sun elevation. This is the single most useful automation pattern in most homes.
• “Everyone left / someone’s home” style presence automations — drive an away mode from your phone device trackers or presence sensors.
• Notify on low battery — scans your battery sensors and pings you before a sensor dies silently. Saves you discovering a dead door sensor at the worst moment.
• Zigbee/Z-Wave remote or button blueprints — most popular remotes (IKEA, Hue, Aqara, etc.) have a community blueprint that maps button presses to actions, which is far easier than wiring up device triggers by hand.

Presence and device tracking

Presence detection is the backbone of useful automations. Start simple: the Home Assistant Companion app on your phone provides a device tracker over GPS and your Wi-Fi network, which is enough for “is anyone home” automations. Router-based tracking (your phone’s connection to Wi-Fi) is another low-effort option.

For room-level detection, mmWave presence sensors are the upgrade. The Aqara FP2 is a capable pick: it’s a Wi-Fi mmWave sensor that supports up to ~30 zones and, once set up, runs locally in Home Assistant through the HomeKit Controller integration. It is a practical compromise rather than a purist local choice, though — initial setup goes through the Aqara app, and it sits on Wi-Fi rather than a mesh protocol. It’s overkill for most rooms, though, so reach for it only where simple motion sensors fall short.

Garage and cover control

Garage door automations are a common need. For Chamberlain/LiftMaster (MyQ) openers, the ratgdo32 control board is a popular local-first fix: it wires to the opener and exposes it to Home Assistant over your LAN via ESPHome or MQTT, no cloud account required. Check your opener’s learn button first: ratgdo speaks Security+ and Security+ 2.0 (purple/red or yellow button), but openers with Security+ 3.0 (round white button, November 2025 and newer) removed the wired data line entirely and moved accessory control to encrypted Bluetooth LE, so no third-party board can drive them (see local-first garage door controllers). Once the door is a normal cover entity, generic cover blueprints (auto-close after N minutes, alert if left open) work fine.

What to skip initially

• Don’t import blueprints for hardware you don’t own yet. Collecting blueprints leads to automation sprawl you won’t maintain.
• Be cautious with blueprints that depend on add-ons or extra integrations until you know you need them. (Add-ons, note, are one-click Docker services that require Home Assistant OS or a Supervised install — they aren’t available on a plain Container install.)
• Skip elaborate “AI assistant” blueprints early on. Built-in voice control via Home Assistant Voice Preview Edition handles basic commands without the overhead.

---

Bottom line: Import a motion-lights blueprint, a low-battery notifier, and a button blueprint for any remote you own. Add Auto-entities and card-mod from HACS to tidy your dashboard. Don’t chase features for hardware you might buy later — start simple and expand when you hit a real need.