The Home Assistant AI roadmap sounds like one official robot is about to move into your smart home and start fixing everything. I wish it were that simple. Home Assistant has several AI ideas on its roadmap, but they are separate pieces with different statuses. One is approved. Two are waiting for approval. One is still being considered. None of these four roadmap items is a finished official AI helper.
I care about this because I already use an unofficial version of the idea. I tested ha-mcp with Claude Desktop and later with Codex. It can inspect a real Home Assistant setup, find entities, read automations, check traces, and help plan changes. It worked amazingly well in my tests, but it also made one thing clear: an AI helper needs limits. I want a careful mechanic, not a new landlord for the house.
Table of Contents
The official helper is four separate ideas
The Home Assistant AI roadmap does not describe one giant feature. It breaks the idea into four smaller jobs: easier AI settings, page-aware context, saved conversations, and automation authoring. That slower approach is less exciting than a big launch announcement, but it is more honest.
The current roadmap status tells the story. The AI settings and global off-switch work in roadmap issue #53 is approved. Page awareness in issue #157 and persistent conversations in issue #159 are awaiting approval. AI-assisted automation building in issue #106 is still being considered.
Approved does not mean shipped. It means the proposal passed one decision gate and can be prioritised. The four issues do not give us a release date, and the proposals can still change. That distinction matters because a mockup on GitHub is easy to mistake for something already running in Home Assistant.
Get the Home Assistant glossary PDF
The Home Assistant AI roadmap includes words such as Assist, AI Task, context, and MCP. If the terminology starts feeling heavier than the actual smart home, get my free Home Assistant glossary. It is a PDF packed with Home Assistant words, acronyms, and their simple, useful explanations.
To get the PDF, type your name and e-mail. You will receive an e-mail from me to confirm you are not a robot, and the PDF will be sent to your inbox. You’ll also be subscribed to my newsletter where I share new content, updates, and my exclusive AI and HA challenge. It’s free and you can unsubscribe anytime with one click.
The approved part is smaller than it sounds
The approved item is useful, but it is not the robot mechanic. It proposes one clearer Assistants and AI area for settings, easier AI-provider discovery, contextual suggestions, and a global way to disable those suggestions. It does not add dashboard generation or automation building.
I like the global switch more than I expected. Some people want AI in every corner. Other people built Home Assistant because they want local control and fewer mystery services. Both groups should be able to use the same platform without arguing every time a shiny button appears. A clear off switch is boring product design, which usually means it is good product design.
This is where the Home Assistant AI roadmap feels sensible. It starts with discovery and choice instead of granting a helper broad power on day one. The settings work can create the front door for later features, but the rest of the house is not built yet.
Tired of reading?
I made a video that walks through the four ideas and compares them with the unofficial option I already use. Watch the Home Assistant AI roadmap video here. The video link is still a draft placeholder while the video is being prepared.
Context could remove a lot of copy and paste
The page-awareness proposal is the part I would notice every day. Imagine opening Assist while looking at an automation. Assist would already know which automation is on the screen, which triggers and actions it contains, and what part you are editing. You would not need to paste a wall of YAML into a chat and then explain why your motion sensor has a name from 2021.
The proposal is about context, not editing power. That boundary is important. Knowing what I am looking at can make an answer more useful without giving the assistant permission to change it. The Home Assistant AI roadmap gets much more interesting when those two ideas stay separate: first understand the problem, then ask before doing anything.
My favourite example is an old automation called something like “night light final fixed two.” We all have one. A useful helper could read its trace, notice that yesterday’s sensor replacement broke an entity reference, and explain the fix in normal words. That saves time without turning Home Assistant into a slot machine where every click may rewrite the house.
Memory is useful, but home chats are private
The memory proposal would save conversations on the Home Assistant server and tie them to the signed-in user. You could start a conversation on one device, close it, and continue later on another. That sounds like a small quality-of-life improvement until you think about what a smart-home chat can contain.
Device names, routines, room details, and pieces of your configuration can all appear in a conversation. Home Assistant would need clear rules for storage, cleanup, retention, and which old chats an assistant may use. The Home Assistant AI roadmap leaves those questions open, which is better than pretending they do not exist.
I want memory when it helps me finish yesterday’s repair. I do not want a mystery scrapbook that remembers every strange test I ran at 2 AM. A visible history, simple deletion, and clear user ownership would make this feature much easier to trust.
Automation authoring needs a human brake pedal
The biggest proposal would let an assistant list, read, create, change, enable, disable, and delete automations. It is also the least advanced of the four items. Its current roadmap status is Considering, not approved.
The proposed safety flow is the part that matters: the helper prepares a preview, and the home maintainer approves it before Home Assistant saves a new or changed automation. The scope is deliberately narrow. Dashboards, scripts, scenes, MCP access, and non-admin authoring are outside this roadmap item.
That makes sense. An assistant that can explain a failed trace is helpful. An assistant that silently edits a lock, alarm, garage door, or water valve is a short path to a very long evening. The Home Assistant AI roadmap needs previews, logs, narrow permissions, and boring confirmation screens more than it needs a clever personality.
ha-mcp already shows what is possible
While the official work is still planned, ha-mcp gives tools such as Claude and Codex structured access to Home Assistant today. It is unofficial and requires setup, care, backups, and clear instructions. It is also broad enough to show why people want this kind of helper.
With ha-mcp, the AI can ask Home Assistant what entities and automations actually exist instead of inventing plausible names. It can inspect traces and history, help with dashboard cards, and prepare a plan based on the real setup. My preferred instruction is deliberately dull: show me the entities, explain the plan, do not change anything yet, and wait for my review.
I documented my tests in two separate articles. The Claude Desktop and Home Assistant test covers the first working path. The Codex and ha-mcp test focuses on dashboards, automations, and debugging. Those tools are not the official helper, but they give the Home Assistant AI roadmap a useful real-world reference.
I do not see the two paths as enemies. The community project moves quickly and proves what users find useful. The official project can take those lessons and build a simpler interface with clearer permissions. One path is rough and working now. The other can become normal for many more Home Assistant users later.
The safety rules matter more than the chatbot
What I like about the Home Assistant AI roadmap is the repeated idea that the human stays in charge. Page context does not automatically mean editing. Automation changes need a preview. AI suggestions should have one global off switch. These are separate proposals, but together they point toward a helper that shows its work.
My own rules would start even smaller. Give the helper read-only access for diagnosis. Let it explain what it found. Ask it to propose one narrow change. Review the exact entities and actions. Make a backup before approving anything important. Keep locks, alarms, garage doors, and water controls outside early experiments.
That process is less magical than saying “fix my home,” but magic is overrated when the bedroom light turns on at 3 AM.
What I will watch next
The Home Assistant AI roadmap does not promise one finished bot or a delivery date. It gives us a direction. Context could stop the copy-and-paste routine. Memory could keep a repair conversation alive across devices. Automation tools could prepare a change and wait for approval. The official version is still mostly on paper, so I will keep checking the issue statuses instead of treating concept images as release notes.
For now, ha-mcp is the working option I can test. The official path is the one I want to see become simple, visible, and safe enough for a normal Home Assistant installation. If it gets there, the best feature may not be the AI itself. It may be the moment the helper says, “I found the problem. Here is the change. Do you want me to save it?”
If your future helper starts writing automations while you sleep, at least make it study first. My Home Assistant AI Recipes book has practical local and cloud ideas it can copy after you approve the homework.
If you want more
Read more in my Home Assistant and AI articles, or compare the official plans with my real Claude ha-mcp test and Codex ha-mcp test. I will update the story when one of these roadmap pieces moves from a GitHub issue into Home Assistant that people can install and use.