Home Assistant automation planner
Plan a Home Assistant automation before you buy the devices
Start from an automation goal, then check the required entities, hubs, connection path, feature limits, reliability risks, and Home Assistant YAML starter. Use it before buying Matter, Thread, Zigbee, camera, lock, sensor, or lighting devices.
What it checks
Entities, hubs, limits, reliability, and YAML
Home Assistant can automate many devices, but only if the right entities are exposed and the setup path is reliable enough. This page focuses on the automation path, not generic product specs.
Common Home Assistant automation goals
Start with the outcome
Presence lighting
Choose a presence or motion sensor, verify light entities, add delay-off logic, and generate YAML.
Front door security
Plan door sensor, lock, camera, notification, hub needs, and safe confirmation rules.
Smart lock access
Check Matter over Thread lock paths, door-state sensors, access-code limits, and fallback notifications.
Device health report
Plan low battery, unavailable, unknown, last_seen, and maintenance notifications.
Notify, record, light the entry, and optionally unlock when someone approaches or opens the front door.
Devices you already own
Security automation
Front door security automation
Notify, record, light the entry, and optionally unlock when someone approaches or opens the front door.
Local risk
high
Security scene
Yes
Owned matches
0
- Use a door sensor or camera event as the trigger, not only a cloud notification.
- Add a light or siren action only after the trigger is reliable.
- Use a local camera/NVR path for privacy-sensitive recording when possible.
- Aqara Door and Window Sensor P2
- Eve Door & Window
- Aqara Smart Lock U200
- Nuki Smart Lock Ultra
- Philips Hue Bridge
- door or window sensor
- camera or doorbell path
- notification target
- optional smart lock
- optional local NVR
- Cloud doorbells can delay events or require subscriptions.
- Matter camera support is emerging, but Home Assistant users still commonly rely on RTSP, ONVIF, vendor integrations, or Frigate.
- Security-critical unlock automations should require extra confirmation.
These checks come before copying YAML. They reduce false triggers, stale states, manual-control conflicts, and unsafe security or power actions.
- Use at least one local trigger such as a door sensor, lock state, camera event, or NVR event.
- Avoid auto-unlock from a single presence or camera trigger; require confirmation for risky actions.
- Add notification fallback when the camera, cloud service, or NVR is unavailable.
- Check whether person, package, or doorbell events are exposed to Home Assistant before buying.
Recommended devices
alias: Notify when front door opens
trigger:
- platform: state
entity_id: binary_sensor.front_door
to: "on"
action:
- service: notify.mobile_app_phone
data:
title: Front door opened
message: The front door sensor changed to open.
mode: singleNeed a final setup and reliability path?
$1.99 setup + reliability report
Send your scene, devices, hubs, and target ecosystem. We will return what to connect, what hub is missing, which features may not work, reliability risks, fallback checks, and what to buy or avoid.
Share or save this result
Copy the current setup URL or a concise diagnosis summary.
FAQ
What is the Home Assistant Automation Planner?
It is a scene-first planning tool for Home Assistant automations. It maps an automation goal to required devices, exposed entities, hubs, compatibility paths, reliability checks, and YAML starters.
Can it tell me which entities I need?
Yes. The planner highlights the trigger and action entities a Home Assistant automation needs, such as motion, presence, contact, lock, light, power, camera event, or notification entities.
Does it check Matter, Thread, Zigbee, and hub requirements?
Yes. It flags missing Matter Controllers, Thread Border Routers, Zigbee coordinators, vendor bridges, Home Assistant controllers, and local or cloud path risks.
Does it generate YAML?
Yes. It links each supported scene to a Home Assistant-compatible YAML starter that uses editable entity placeholders.